-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tado Thermostats not setting supportedThermostatModes #8
Comments
@andrewsayre This project is now discontinued, i no longer have access to the smartthings platform which is undertaking a large amount of change ( it used to conform to the Thermostat Specification, but this is being modified by samsung) . please create a pull request with the required changes and i will merge |
FYI @rafuz Are you able to resolve and submit a PR? I don't have these devices to know the logic of which modes are supported, but can try and sketch something together over the weekend if need be. |
I have the devices, smartthing v2 hub and home assistant so I am able to test the full enviroment. |
@rafuz if you need any help I have a much improved plugin for Homeseer and have a lot more of the functionality fixed in that plugin. And it uses oauth |
Tado (Connect) thermostats (cooling and heating) are not fully implementing the required attributes of the
Thermostat Mode
capability. Specifically, they are not settingsupportedThermostatModes
which is a required attribute. This causes problem in third party integrations with SmartThings that expect this value to be populated, such as seen in home-assistant/core#21298The text was updated successfully, but these errors were encountered: