-
-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Sensibo devices don't show humidity in HomeKit #82896
Comments
Hey there @andrey-git, @gjohansson-ST, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) sensibo documentation |
Have the same issue on my side |
I am not sure this is a sensibo issue but exactly what entities do you have in HA which shows incorrect in Homekit? |
After a bit more of digging, I found it under the climate.{friendlyname} entity and attribute current_humidity :D |
Don't think has anything to do with |
Pretty sure this got fixed with #87051 |
The problem
Sensibo Air and Sensibo AirQ both have humidity information visible in Home Assistant and Sensibo own app.
When exposed to HomeKit through HASS Bridge I can see Humidity icons for both devices in Home.app and show "--".
When Sensibo devices are added natively to HomeKit - I can see the same icon with a value and in device details in Home.app I can see "Current Humidity" value.
I double checked that domains include "Sensors" and the climate devices (and every sensor I can see for them) is not excluded.
What version of Home Assistant Core has the issue?
Home Assistant 2022.11.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Sensibo
Link to integration documentation on our website
https://www.home-assistant.io/integrations/sensibo/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: