node-sonos-http-api icon indicating copy to clipboard operation
node-sonos-http-api copied to clipboard

Reconnect error log

Open olem10 opened this issue 2 years ago • 3 comments

Due to the poor battery performance of the Sonos Roam I leave it off for most of the time. This leads to a lot of errors in the console output/logs when the device is not reachable. Approx. 10 times every 8 seconds the following error shows up: 2022-05-29T10:03:13.965Z WARN resubscribing to sid null failed Error: connect EHOSTUNREACH 192.168.0.128:1400 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1138:16)

The http-API does however still work and the Roam works fine when reconnected. Maybe there in a future update could be added support for dynamic discovery and removal of devices to avoid the error messages and resubscription to missing devices?

Thanks for a great piece of software.

olem10 avatar May 29 '22 10:05 olem10

Yeah, this is a known error that I haven't looked into. It was designed to "drop" players that are disconnected, but something is off with that logic. It wasn't a huge problem then, since it was rarely people disconnected individual players, but now with the cordless players, this is probably more common.

See https://github.com/jishi/node-sonos-http-api/issues/605

jishi avatar Jul 04 '22 10:07 jishi

Any news on this?

I have a Sonos Roam, and that is obviously on / off at random times, but flooding my syslog when not reachable with Error: connect EHOSTUNREACH Only restarting the service will fix it (temporary)

martin072 avatar Nov 15 '23 18:11 martin072

happens in my case too and it seems to have the negative effect on swallowing request :-(

bausi2k avatar May 07 '24 09:05 bausi2k