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
Error while setting up platform eufy #16834
Comments
Clear your |
Done, but did not resolve the issue.
Also tried unplugging and removing the device from the Eufy Home app, then going through the process of readding it, but no luck there as well. |
CC @mjg59 |
I'm having this same issue. I'm not sure which version introduced this issue. Did you ever find a workaround? |
The eufy component started working for me again around 0.83/0.84. Anyone else? IMO, I'm thinking this issue could be closed now if so. |
Not working for me. I tried it using python3 directly importing lakeside and it worked but not via Home Assistant Results : https://community.home-assistant.io/t/help-required-with-configuring-eufy-smart-plug-uk/71304/15 Device T1203 is simply not being discovered |
I'm using eufy bulbs, but listing them explicitly on eufy: !include eufy.yaml and devices:
- address: 10.0.1.101
name: SBSuite2
access_token: CBF39XXXXX4212
type: T1011 I'm on HA 0.84, running on Synology/Docker |
I'm not sure if this is valid for other setup, but on my Docker, the The last version of lakeside is 0.11, and this version is required for detecting T1203-devices. Maybe it's time to update the docker image... |
I'm having the same issue since about 10 days ago HAssio RPi 3 B+ manually adding the component to my configuration.yaml as
|
Having the same issue running Home Assistant v0.86.4. For some reason two of my bulbs work great still....but the other ones do not. and throw the same error you guys already entered. Here is the error:
If anyone has had luck fixing this I would appreciate some suggestions. |
If you're getting the ValueError error, can you try using https://github.com/google/python-lakeside/tree/test_uint32 ? |
This should fix home-assistant#16834
@mjg59 Is there anything we can do if we use Docker? |
I'm afraid I don't know how the docker images are built |
This should be fixed in the next release of Home Assistant. Sorry it took so long - I had something of a conceptual misunderstanding around how Protobufs work and thought this was a much more complicated problem than it actually was. |
Lol those are the most frustrating problems but thanks for your hard work |
Was this introduced to a Home Assistant release yet? I'm still having the problem. |
My Eufy bulbs are about as good as they are going to get brightness is wonky but works for the most part seems to fight the original app |
Hass: 0.92.1
|
Home Assistant release with the issue:
Home Assistant
0.78.3
Last working Home Assistant release (if known):
0.77.3
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io on RasPi3
Component/platform:
https://www.home-assistant.io/components/eufy/
Description of problem:
Have one registered light with Eufy. Prior to 0.78, light worked. After upgrading, the light no longer is found in Home Assistant, and the Eufy platform throws this error on start up.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
The text was updated successfully, but these errors were encountered: