Eufy light switches initially work but after some time they are no longer controllable from Hassio, The Eufy application still works fine when this occurs. Resetting the switch fixes the issue for a little while but the issue eventually comes back and the switch has to be reset again. The log file is filling up with looping error messages (currently 951 occurrences).
configuration.yamleufy:
username: [email protected]
password: !secret eufy_password
devices:
- address: 192.168.7.134
access_token: CAB97F9490E7410B
type: T1211
name: Smart Switch
- address: 192.168.7.133
access_token: 4D4CB87620254F87
type: T1211
name: Smart Switch
- address: 192.168.7.108
access_token: 8B25953ED3C94FA8
type: T1211
name: Smart Switch
- address: 192.168.7.110
access_token: CCDBAC1E1DAB4DF1
type: T1211
name: Smart Switch
2020-04-03 08:43:01 ERROR (MainThread) [homeassistant.helpers.entity] Update for switch.main_lights fails
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
await self.async_device_update()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 476, in async_device_update
await self.hass.async_add_executor_job(self.update)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/eufy/switch.py", line 34, in update
self._switch.update()
File "/usr/local/lib/python3.7/site-packages/lakeside/__init__.py", line 246, in update
response = self.get_status()
File "/usr/local/lib/python3.7/site-packages/lakeside/__init__.py", line 242, in get_status
response = self.send_packet(packet, True)
File "/usr/local/lib/python3.7/site-packages/lakeside/__init__.py", line 232, in send_packet
return device.send_packet(self, packet, response)
File "/usr/local/lib/python3.7/site-packages/lakeside/__init__.py", line 97, in send_packet
length = struct.unpack("<H", decrypted_packet[0:2])[0]
struct.error: unpack requires a buffer of 2 bytes
Same issue here -- and it appears to be common among all Eufy components. In my case, I'm using a Eufy bulb. There have been some fixes in the past to address this that have helped, but I'm still intermittently seeing this issue. There are two workarounds I'm currently aware of:
Both seem to resolve the issue for days->weeks.
New HA user here with fresh Hass.io set up starting at ~107.5. Eufy integration config is just the username and password. Having exactly the same issue as described.
Bulbs have DHCP static IPs on same network as HA. I鈥檓 rarely getting more than a day of it working before having to restart HA. Bulbs stay controllable through Eufy app at all times.
Same issues here. Eufy integration is almost unusable currently.
I've got three T1012s set up the same way with local access tokens and mine are at times really sluggish and occasionally failing to update at all. I don't currently have any stacktraces in my logs, but I've had over 1000 "Updating eufy light took longer than the scheduled interval" messages over the course of two days. My lights have good days and bad days but it could be anything up to a couple of minutes before they respond to controls from Hass. The Eufyhome app is always lightning fast and like OP restarting Hass or power cycling the bulb will fix the issue for a time.
I have eleven T102 light bulbs that were working fine on 0.89... I updated to 0.113.0 and they are barely working, as described above. My log id full of "Updating eufy light took longer than the scheduled update interval 0:00:30".
Afaik, there were no updates on lakeside component, so there were no changes on how HA handles Eufy lights. Am I right?
If I restart HA, they work fine for hours/days and, suddenly, start to ignore commands from the HA, but keep working on eufy app...
Auto-discovery doesn't work with T1012 smart bulbs, both on my trusted LAN and segregated IoT VLAN.
Most helpful comment
Same issue here -- and it appears to be common among all Eufy components. In my case, I'm using a Eufy bulb. There have been some fixes in the past to address this that have helped, but I'm still intermittently seeing this issue. There are two workarounds I'm currently aware of:
Both seem to resolve the issue for days->weeks.