-
-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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
HomeKit Thermostat Not Communicating Properly With Home Assistant after 2024.8 #123963
Comments
Hey there @Jc2k, @bdraco, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) homekit_controller documentation |
I have a HomeKit connected thermostat and haven't noticed this issue with interval temperature reporting. I have noticed, however, that the thermostat will be "unavailable" when I submit set-temperature and on/off requests via Google Assistant. Google will intermittently report, “Sorry, I couldn’t reach the home assistant,” just for this device, but respond to all other HA inquiries, indicating, to me, that there may indeed be a problem with HomeKit Thermostat communication. |
@bdraco Unfortunately no change in behavior with #124115. Below are the logs and diagnostics again. Did homekit_controller poll all characteristics every minute prior to the 2024.8.0 update? I wonder if the thermostat is not loosing connection but rather is programmed to only send the temp and humidity values after a certain amount of change has occurred (0.5°C and 2% humidity). |
Yes it used to poll every 30s but since that caused crashes on devices and was not in line with what the Home app did in iOS so we removed the polling for characteristics that are marked as push (evented) and and let the device decide when to send the data. We only poll characteristics that are marked poll only now |
If you need to poll more frequently than the device sends updates, if we don’t have the generic entity update service wired up to be able to poll on demand from an automation I can look into adding support for that next week |
Here is an automation for polling shades more frequently that could likely be adapted. I’m not sure that’s hooked up in homekit_controller though so it might not work without some changes. I’m traveling this weekend so I’m not in a position to check |
It looks like that’s not wired up to override and poll. That’s going to require some refactoring. I’ll look into implementing it next week if travel goes ok |
#124582 will allow you to create an automation to poll as frequently as you like |
…_controller (home-assistant#124582) related issue home-assistant#123963
I use homekit for an Ariston boiler that is compatible and in addition to a sampling frequency problem it lacks precision, now it only shows integer data but no decimals. But the decimals are taken into account, that is, round the temperature but do not truncate the decimal. |
The problem
Instantly after updating to Home Assistant 2024.8, all Mysa thermostats controlled via HomeKit stopped reporting their temperature live. Currently, the temperature updates every 0.5°C where previously it updated every 0.1°C. Retrieving the set temperature also sometimes fails after changing it.
I have rebooted HA and the thermostats with no luck. The thermostats still behave normally in the native app.
It almost seems like after 2024.8.0, HA is subscribing to updates from the thermostat and the thermostat is only providing occasional updates.
What version of Home Assistant Core has the issue?
core-2024.8.0
What was the last working version of Home Assistant Core?
core-2024.7.4
What type of installation are you running?
Home Assistant OS
Integration causing the issue
homekit_controller
Link to integration documentation on our website
https://www.home-assistant.io/integrations/homekit_controller
Diagnostics information
homekit_controller-a6a60571538ca51b32e2a54d328980c0-Mysa-6febe8-f5327fb1e2f71046880ba271f699393d.json
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: