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
When a thermostat also exposes a humidity sensor on the same endpoint, the humidity sensor currently gets configured as a secondary service, and not as the optional CurrentRelativeHumidity characteristic for said thermostat service.
It's (for some reason?) not possible to ungroup these two services, meaning the accessory tile in Home will only show a sensor icon and not the current state of the thermostat.
A possible solution might be to simply skip service creation for humidity sensors in case climate is also exposed on the same endpoint. Adding the optional characteristic should also be rather trivial, because we probably can reuse proven code from #854. 😉
Related devices
No response
Related Devices
RBSH-RTH0-ZB-EU
RBSH-RTH0-BAT-ZB-EU
Steps To Reproduce
No response
Expected behavior
A thermostat service with the optional CurrentRelativeHumidity characteristic gets exposed to HomeKit, and no additional humidity service is created.
Main tricky part is that two separate converters need to be aware of each others behavior, so they (unfortunately) need to be coupled somehow.
I'll think about what the possibilities are..
Functionally though, you still have all the data available in HomeKit, right?
So you can still make whatever automations you'd want for this?
Main tricky part is that two separate converters need to be aware of each others behavior, so they (unfortunately) need to be coupled somehow. I'll think about what the possibilities are..
Why would they need to be coupled?
Wouldn't we just skip the basic humidity sensor if we detect a climate expose, or am I missing something? 🤔
Functionally though, you still have all the data available in HomeKit, right? So you can still make whatever automations you'd want for this?
Technically yes, but the UI is kinda messed up.
The thermostat doesn't show up correctly because the humidity sensor seems to be treated as the main accessory service (it's the tile on the right).
It's probably because the basic sensors are created first? If I exclude the sensor by default, and later on explicitly include it, it's showing up more or less as expected.
Is there an existing issue for this?
Describe the bug
When a thermostat also exposes a humidity sensor on the same endpoint, the humidity sensor currently gets configured as a secondary service, and not as the optional
CurrentRelativeHumidity
characteristic for said thermostat service.It's (for some reason?) not possible to ungroup these two services, meaning the accessory tile in Home will only show a sensor icon and not the current state of the thermostat.
A possible solution might be to simply skip service creation for humidity sensors in case
climate
is also exposed on the same endpoint. Adding the optional characteristic should also be rather trivial, because we probably can reuse proven code from #854. 😉Related devices
No response
Related Devices
Steps To Reproduce
No response
Expected behavior
A thermostat service with the optional
CurrentRelativeHumidity
characteristic gets exposed to HomeKit, and no additional humidity service is created.Device entry
Status update
No response
Messages from this plugin
No response
This plugin
1.11.0-beta.5
Homebridge
1.7.0
Zigbee2MQTT
1.37.1-dev
Homebridge Config UI X (if applicable)
No response
The text was updated successfully, but these errors were encountered: