Fails if zone is unavailable during startup

[petedavey]

If for some reason the extension is started during a time the zone is unavailable, and then the zone is made available after the script is running -it will not process the turn on event. Easy to replicate, simply make the zone unavailable by whatever means necessary (power off, disconnect network) and start the app. Then, while it's running, make the zone available and then play back music. The on event is never processed / sent to the trigger device. I've attempted to study other plugins that don't have this problem but have had issues trying to re-write this code to make it more resilient to these situations.

[billmag]

I'm considering adapting this approach with two tweaks, and was curious if you've made any progress on this particular issue. My plan was to:

1. Change the configuration so that I can monitor some zones, but ignore others (I only have power hungry amps I want automatic control of on a couple of them).
2. Change the output method to power on a USB port on the same Linux box as my Roon server (running on an Intel NUC). This would let me skip the extra hardware by simply wiring a 5V to 12V USB "step up" cable directly into my 12V trigger.

But, I wasn't sure if this project is even working for more recent versions of Roon or if anyone else is working on it?

[petedavey]

To speak to your specific question if I've made progress - no. I tried fixing it using GPT and to no avail. As long as the plugin starts when the zone is available, all seems to be well. But yeah def not ideal. I have other plugins that are zone dependent to work but they will continue to function regardless if they are started before or after a zone is made available.

The tweaks I was able to make work was for it to work for a specific zone and also a countdown function for it to power things down that also displays a running timer in the Roon extensions interface. So if I stop music, it has a 15 minute power-down timer that runs.

I don't know how you would alter it to the point where it is "telling" a different device to turn on or off. This is specific to an arduino style device (which I also have issues with staying on wifi). Lots of moving pieces here and simplifying it would be ideal.

[billmag]

Do you have your extension code in a public fork somewhere?

Also, any pointers to specific Roon Extension docs you're using? I don't think I'm going to have much time to work on this in the short term, but happy to keep this issue in mind when I get a chance to investigate.