Skip to content
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

Open
decavent opened this issue Dec 25, 2019 · 6 comments
Open

Socket Closed without sending response #6

decavent opened this issue Dec 25, 2019 · 6 comments

Comments

@decavent
Copy link

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.

@digitalec
Copy link

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

@dancocos
Copy link

dancocos commented Jan 9, 2020

Is this module dead for now? If so I think noting this on the readme page should be mentioned.

@sebmos
Copy link
Owner

sebmos commented Jan 27, 2020

@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.)

@jgadzhiev
Copy link

@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
May I ask if there is indication of Eufy has made a mentioned fix or not?
Thank you.

@sebmos
Copy link
Owner

sebmos commented Nov 9, 2021

@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.

@viseshrp
Copy link

viseshrp commented Dec 2, 2022

Still see the same problem.

[12/2/2022, 5:14:25 PM] [eufy] Error loading power state on device: Google home  -  Error: Socket closed without sending response
    at Timeout.<anonymous> (/homebridge/node_modules/homebridge-eufy/node_modules/node-eufy-api/lib/tcp-socket.js:153:48)
    at listOnTimeout (node:internal/timers:564:17)
    at processTimers (node:internal/timers:507:7)
[12/2/2022, 5:14:25 PM] [eufy] Error connecting to accessory: Error: Socket closed without sending response
    at Timeout.<anonymous> (/homebridge/node_modules/homebridge-eufy/node_modules/node-eufy-api/lib/tcp-socket.js:153:48)
    at listOnTimeout (node:internal/timers:564:17)
    at processTimers (node:internal/timers:507:7)
[12/2/2022, 5:14:25 PM] [eufy] Removing accessory: Google home

@sebmos any solutions or alternatives?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants