-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
[BUG] Socket closed #361
Comments
25.3.2021, 13:42:05 [Stuehub] (Stuehub)ERROR (3)- refreshCurrentActivity TimeoutError: Can't open WebSocket within allowed timeout: 10000 ms. - Stack : TimeoutError: Can't open WebSocket within allowed timeout: 10000 ms. |
I can confirm to have the very same issue. |
Hi, Did you check with Hoobs support ? I have no such issue reported on regular homebridge, might be some problem with websockrets / hoobs itself. no error on the plugin side from the error stack I see. |
I did not yet contact hoobs support because so far to me it looked obvious that the issue was caused by harmony plugin. |
I ditched Hoobs and converted to Homebridge. No problems. :-) |
the plugin can't open a websocket, maybe because ports on the system are blocked or already in use. Can't do anything about that. It is either network related or a conflict with the host. I have already seen such error on hoobs, but don't really know what thez are doing above homebridge .... |
OK - I will open an incident on hoobs as well. |
Or move to regular homebridge 😀 |
Not an option. Way to much manually maintenance required. This installation was rock solid for over a year now. |
Same issue here without Hoobs: Several times a day just "socket closed": Sometimes with the following messages |
Looks like solved. |
Thank you for reporting. If you still have socket close, it means your hub becomes unreachable at some point but it can reconnect so that was my main concern. |
I am getting the following errors.
Am using Hoobs.
25.3.2021, 01:06:34 [Stuehub] (Stuehub)ERROR (1)- refreshCurrentActivity Error: WebSocket closed with reason: undefined (undefined). - Stack : Error: WebSocket closed with reason: undefined (undefined).
at WebSocketAsPromised._handleClose (/home/hoobs/.hoobs/node_modules/websocket-as-promised/src/index.js:353:19)
at WebSocket.listener (/home/hoobs/.hoobs/node_modules/websocket-as-promised/src/index.js:311:64)
at WebSocket.emit (events.js:315:20)
at WebSocket.emitClose (/home/hoobs/.hoobs/node_modules/harmony-websocket/node_modules/ws/lib/websocket.js:198:10)
at Receiver.receiverOnFinish (/home/hoobs/.hoobs/node_modules/harmony-websocket/node_modules/ws/lib/websocket.js:815:20)
at Receiver.emit (events.js:315:20)
at finish (internal/streams/writable.js:657:10)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
25.3.2021, 01:06:34 [Stuehub] (Stuehub)WARNING - socket closed
25.3.2021, 01:06:54 [Stuehub] (Stuehub)ERROR (2)- refreshCurrentActivity TimeoutError: Can't open WebSocket within allowed timeout: 10000 ms. - Stack : TimeoutError: Can't open WebSocket within allowed timeout: 10000 ms.
at PromiseController._handleTimeout (/home/hoobs/.hoobs/node_modules/promise-controller/src/index.js:172:19)
at Timeout. (/home/hoobs/.hoobs/node_modules/promise-controller/src/index.js:178:43)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7)
Config
Your config section of platform. Please do not post your whole config and especially with logins / passwords !
Additional context
The text was updated successfully, but these errors were encountered: