Thanks for the great plugin - LOVE IT. I think I might found an issue. I have 2 Volumio systems - 1) house (PIHOUSE); 2) vehicle (PILOT). As it sounds my PIHOUSE is always connected to my network (wired) and my PILOT is in my vehicle (and I control it via PILOT.LOCAL via browser, both naturally connected via my phone's hotspot). Looking at the HomeBridge I noticed that the plugin was attempting to connect to the PILOT (which will reconnect to my home WIFI once I have returned home) after it had powered off (after 20-ish minutes). The plugin only has 1 Volumio (PIHOUSE) configured in the JSON file (see below). Not sure how the plugin is picking up the PILOT Volumio system since it's not defined to the plugin. The PILOT Volumio has never been defined to the plugin or to HomeBridge. Not sure if this is a "bug" or "feature". If it is a feature is there way to disable the plugin from attempting to connect to Volumios that aren't in the configuration file but might be connect to the same network at the Homebridge system is (i.e. an "ignore" type parm or a "only defined" parm)? Once I rebooted HomeBridge (and PILOT Volumio is no longer powered on/not on the house network) the plugin doesn't attempt to connect to it and there are no errors in the log.
Thanks for the great plugin - LOVE IT. I think I might found an issue. I have 2 Volumio systems - 1) house (PIHOUSE); 2) vehicle (PILOT). As it sounds my PIHOUSE is always connected to my network (wired) and my PILOT is in my vehicle (and I control it via PILOT.LOCAL via browser, both naturally connected via my phone's hotspot). Looking at the HomeBridge I noticed that the plugin was attempting to connect to the PILOT (which will reconnect to my home WIFI once I have returned home) after it had powered off (after 20-ish minutes). The plugin only has 1 Volumio (PIHOUSE) configured in the JSON file (see below). Not sure how the plugin is picking up the PILOT Volumio system since it's not defined to the plugin. The PILOT Volumio has never been defined to the plugin or to HomeBridge. Not sure if this is a "bug" or "feature". If it is a feature is there way to disable the plugin from attempting to connect to Volumios that aren't in the configuration file but might be connect to the same network at the Homebridge system is (i.e. an "ignore" type parm or a "only defined" parm)? Once I rebooted HomeBridge (and PILOT Volumio is no longer powered on/not on the house network) the plugin doesn't attempt to connect to it and there are no errors in the log.
homebridge-volumio-speakers v0.4.0
Log Info:
[Volumio Speakers] Pilot: Socket connection error: http://192.168.1.184:3000/ Error: xhr poll error at XHR.Transport.onError (/var/lib/homebridge/node_modules/homebridge-volumio-speakers/node_modules/engine.io-client/lib/transport.js:68:13) at Request.<anonymous> (/var/lib/homebridge/node_modules/homebridge-volumio-speakers/node_modules/engine.io-client/lib/transports/polling xhr.js:132:10) at Request.Emitter.emit (/var/lib/homebridge/node_modules/homebridge-volumio speakers/node_modules/component-emitter/index.js:145:20) at Request.onError (/var/lib/homebridge/node_modules/homebridge-volumio-speakers/node_modules/engine.io-client/lib/transports/polling-xhr.js:314:8) at Timeout._onTimeout (/var/lib/homebridge/node_modules/homebridge-volumio speakers/node_modules/engine.io-client/lib/transports/polling-xhr.js:261:18) at listOnTimeout (node:internal/timers:569:17) at processTimers (node:internal/timers:512:7) {type: 'TransportError',description: 0}Thanks