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
2022-09-11 22:54:14.960 WARNING (SyncWorker_2) [homeassistant.helpers.frame] Detected integration that attempted to call BleakClient with an address instead of a BLEDevice. Please report issue for eq3btsmart using this method at homeassistant/components/eq3btsmart/climate.py, line 189: self._thermostat.update()
2022-09-11 22:54:24.687 WARNING (MainThread) [homeassistant.components.climate] Setup of climate platform eq3btsmart is taking over 10 seconds.
2022-09-11 22:55:07.316 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: climate.eq3btsmart
2022-09-11 22:55:56.977 WARNING (SyncWorker_2) [homeassistant.components.eq3btsmart.climate] Updating the state failed: Exception on write using bleak
2022-09-11 22:56:07.416 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: climate.eq3btsmart
Additional information
installed on raspberry 4, 4GB
The text was updated successfully, but these errors were encountered:
Hey there @rytilahti, mind taking a look at this issue as it has been labeled with an integration (eq3btsmart) you are listed as a code owner for? Thanks! (message by CodeOwnersMention)
The problem
new HA installation,
eq3 thermostats are visible via bluetoothctl but keep unavailable
see attached logfile
What version of Home Assistant Core has the issue?
8.5, 64bit
What was the last working version of Home Assistant Core?
none
What type of installation are you running?
Home Assistant OS
Integration causing the issue
eq3btsmart
Link to integration documentation on our website
https://www.home-assistant.io/integrations/eq3btsmart/
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
installed on raspberry 4, 4GB
The text was updated successfully, but these errors were encountered: