@spockfish , any ideas on what is going on here? Would there be any harm in setting up a cron job to restart the extension periodically? The problem occurs most evenings (when I am home to notice).
NB, this is only a problem of the display RoPieee adjusting to music now being played by the zone the display is monitoring. The music endpoints (also running RoPieee) don’t exhibit any strange behaviour.
Happens both ways. The latest log was a single zone.
Last night, we were playing music in a grouped zone (kitchen and livingroom). Since we were sitting in the kitchen, I restarted that display. Some time later (after dinner and discussion), we relocated to the living room, and I had to restart that display. Music continued to play unabated.
I don’t think so. It happens with a single zone, like this morning (last feedback given).
For clarity, regarding last night:
Start music in grouped zone.
Music starts playing in both.
Kitchen display blank, so restarted extension.
Music plays for a few hours.
People relocate to Living Room.
Music is still playing.
Living Room display is blank, so extension is restarted.
Music continues to play for the evening. Displays stay “connected” for duration.
At no time does the display lose a connection while music is playing, irrespective of duration. The display must be in “sleep” mode (clock or dark, depending on setting) for it to fail to “wake up”.
I just ran a test, grouping 3 zones. My son’s display woke up fine, connected to the same switch as the core. The other didn’t, which is connected to a different switch (the kitchen and living room displays). BTW, these are all ethernet.
So, this leads me to suspect some issue with this network segment. It is interesting that it is the display which fails, not the playing of music, and the failure is related to noticing that the watched zone has started. Also, interesting that the extension restart never fails (eg its mechanism is more fault tolerant somehow).
I decided to write a simple bash script that restarts the extensions of the displays every 4 hours during the normal listening day. I am pleased that this seems to have masked whatever the problem was that was occurring.