-
Notifications
You must be signed in to change notification settings - Fork 6
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
Socket Closed without sending response #6
Comments
I believe it was a change to the Eufy API. See issues 2, 4, 5 & 6 at https://github.com/sebmos/node-eufy-api I ended up dumping my bulbs and went with a bunch of Tuya stuff |
Is this module dead for now? If so I think noting this on the readme page should be mentioned. |
@dancocos I wouldn't call it dead, as it still works for some lights. I still hold out hope that Eufy will fix the bug in their firmware. But it's true that this API doesn't support their server-side API, which Eufy uses for remote control (and as a fallback for the same bug, which they're also affected by.) |
Dear @sebmos |
@jgadzhiev - My response is a bit slow, as I had to start using the Eufy plugs again. It appears the bug isn't fixed, sadly. My bulbs worked for a bit, and then they stopped. |
Still see the same problem.
@sebmos any solutions or alternatives? |
Hi, I’m getting an error when booting up Homebridge. Both are Eufy white/color bulbs. As Homebridge starts, I see the plugin “Add Accessory” and identify each bulb. However, it then generates and error “connecting to accessory: Error: Socket closed without sending response.” It then removes the accessory (bulb). Any thoughts? Tried reinstalling the plugin.
The text was updated successfully, but these errors were encountered: