Hi - Sorry if this is annoying. The extension works perfectly for me except it tends to crash after a few hours. (I’m running it on an Intel NUC with Windows 10.) I thought it might be related to the computer I’m using for Roon control going to sleep, but I haven’t been able to reproduce the problem that way. Here is the error message.
<- REQUEST 272 com.roonlabs.sourcecontrol:1/convenience_switch {“control_key”:“38805077”}
c:\Users\jaweb\Music\roon-extension-harmony-master\roon-extension-harmony\node_modules\node-roon-api\transport-websocket.js:47
this.moo.close();
^
TypeError: this.moo.close is not a function
at Transport.close (c:\Users\jaweb\Music\roon-extension-harmony-master\roon-extension-harmony\node_modules\node-roon-api\transport-websocket.js:47:18)
at WebSocket.Transport.ws.onclose (c:\Users\jaweb\Music\roon-extension-harmony-master\roon-extension-harmony\node_modules\node-roon-api\transport-websocket.js:18:14)
at WebSocket.onClose (c:\Users\jaweb\Music\roon-extension-harmony-master\roon-extension-harmony\node_modules\ws\lib\WebSocket.js:446:14)
at WebSocket.emit (events.js:182:13)
at WebSocket.cleanupWebsocketResources (c:\Users\jaweb\Music\roon-extension-harmony-master\roon-extension-harmony\node_modules\ws\lib\WebSocket.js:950:8)
at Socket.emit (events.js:182:13)
at emitErrorNT (internal/streams/destroy.js:82:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
Can you advise me about what the issue might be?
I see the same error has been observed with other extensions.
https://community.roonlabs.com/t/roon-extension-alarm-clock-v0-7-4/21556/202?u=john_webb