homebridge-eufy icon indicating copy to clipboard operation
homebridge-eufy copied to clipboard

Socket Closed without sending response

Open decavent opened this issue 5 years ago • 6 comments

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.

decavent avatar Dec 25 '19 20:12 decavent

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

digitalec avatar Dec 25 '19 22:12 digitalec

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

dancocos avatar Jan 09 '20 20:01 dancocos

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

sebmos avatar Jan 27 '20 20:01 sebmos

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

jgadzhiev avatar Oct 20 '21 06:10 jgadzhiev

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

sebmos avatar Nov 09 '21 20:11 sebmos

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?

viseshrp avatar Dec 02 '22 23:12 viseshrp