You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For each tado 'room', I see a temperature, but no humidity sensor in Homebridge, MacOS (Mojave, so not latest) nor iOS (15).
In iOS both sensor types for both tado's native HK and also HB (from this plug-in), are offered as automation triggers. So a room with a single rad and TRV offers 4 sensors as triggers.
In MacOS, NO temp. nor humidity sensors are available as triggers.
All of which raises some questions in my mind.
This plug-in does offer some functionality not available from tado's native HK implementation, but for these sensor types (temp. and humidity), there is very little difference, both being absent or available as triggers in MacOS and iOS respectively. The only difference really is that tado creates sensors for each device, whereas this plug-in only creates them for each tado 'room'. So in a room with 2 rads each with a TRV, in iOS I have 6 possible sensors to use as a trigger.
Other than that, what is the point of using this plug-in rather than tado's own HK implementation?
Not knocking this plug-in as it does offer more elsewhere, but for temp and humidity, not so much.
Also, for these sensors, what does "separateTemperature" and "separateHumidity" actually mean?
They are currently the default of false for both, but they appear separately in Homebridge and no humidity at all in Home.app (apart from as trigger). So what those config options mean is as clear as mud to me. Does it perhaps make them available for each device rather than just for each room?
Anyone comment on the above, the author of this plug-in perhaps?
The text was updated successfully, but these errors were encountered:
Anyone comment on the above, the author of this plug-in perhaps?
I fear the author has abandoned this project. No comment to any issues and no further development.
Me personally, I think showing temperature and humidity on a per room (zone in tado-speak) basis is the only reasonable way. Why would there be different values for one room (in normal people‘s living conditions, not superstar mansions. Superstars maybe have different zones for 1 room :) ).
I currently only have access to iOS 16 devices, and at least there everything is working as I expect - temperature and humidity shown for every room, and available as trigger for automations (no „separate sensor“ options set in platorm settings). As far as I remember this used to be the same for iOS 15?
For each tado 'room', I see a temperature, but no humidity sensor in Homebridge, MacOS (Mojave, so not latest) nor iOS (15).
In iOS both sensor types for both tado's native HK and also HB (from this plug-in), are offered as automation triggers. So a room with a single rad and TRV offers 4 sensors as triggers.
In MacOS, NO temp. nor humidity sensors are available as triggers.
All of which raises some questions in my mind.
This plug-in does offer some functionality not available from tado's native HK implementation, but for these sensor types (temp. and humidity), there is very little difference, both being absent or available as triggers in MacOS and iOS respectively. The only difference really is that tado creates sensors for each device, whereas this plug-in only creates them for each tado 'room'. So in a room with 2 rads each with a TRV, in iOS I have 6 possible sensors to use as a trigger.
Other than that, what is the point of using this plug-in rather than tado's own HK implementation?
Not knocking this plug-in as it does offer more elsewhere, but for temp and humidity, not so much.
Also, for these sensors, what does "separateTemperature" and "separateHumidity" actually mean?
They are currently the default of false for both, but they appear separately in Homebridge and no humidity at all in Home.app (apart from as trigger). So what those config options mean is as clear as mud to me. Does it perhaps make them available for each device rather than just for each room?
Anyone comment on the above, the author of this plug-in perhaps?
The text was updated successfully, but these errors were encountered: