core: Ecobee integrated through Homekit Controller keeps becoming "Unavailable"
The problem
I hve an Ecobee Smart Thermostat integrated using the Homekit Controller integration. I have a Unifi network with dedicated IOT vlan. The access point it 10 feet from the thermostat in the same hallway. The thermostat is connected to a 2.4GHz network dedicated to IOT devices and is assigned to the IOT vlan. Firewall rules have been made to allow IOT devices on this network to talk to my Homeassistant server, but no other networks. This configuration has been working well for over a year, but recently my thermostat keeps going Unavailable intermittently for anywhere between 2 minutes and an hour, usually less than 30 minutes at a time though. If I pull the thermostat off the wall and reattach it the thermostat will show up in homeassistant again, but the problem will return again shortly. I removed the homekit controller integration and re-added the Ecobee and it will work shortly before having the issue again. During all the times it becomes Unvavailable in HA, I can still connect to the thermostat through the Ecobee app.
What version of Home Assistant Core has the issue?
2022.7.6
What was the last working version of Home Assistant Core?
2022.7.3
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-48904e84bdd6211de37745b0db693de3-Ecobee-7c15c212084211eb80bc3d31684fee56.txt
wouldn’t let me paste .json filetyep so type changed from .json to .txt
Example YAML snippet
No response
Anything in the logs that might be useful for us?
2022-07-24 13:06:11 ERROR (MainThread) [homeassistant.core] Error executing service: <ServiceCall climate.turn_off (c:01G8RX1H5XPBM245TZD7BSSXB2): entity_id=['climate.ecobee']>
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 2
- Comments: 20 (7 by maintainers)
I’m extremely aware of that (it won’t even start without said variables, which I’m (obviously, I hope?) using!), but I was asked to mention the error, so I did. You’ll note when I initially mentioned I had to roll back I didn’t burden anyone with my error details…