0.5.3 t5 now playing not working

[Labmaster]

Isn't this a fix in the wrong place ?

It seems that the "State block" configuration triggers two identical http requests directly one after the other where only one should be triggered, right ?
The ms4lox behaves as it should, so then the probem should be fixed in the loxone config and not be hidden by some special code on the m24lox side.

Now "hismastersvoics" is doing the same mistake as loxone does all the time, by changing functions doing unsuspected things only to hide a problem.

The "state block" is known to behave sometime not as expected but usualy there is always a workaround right ?

[hismastersvoice]

Labmaster
No that is OK, it is a problem between the MiniServer 10.x and a Apache2 update. The MiniServer sends allways the Event twice.

duncan
Thanks for Feedback... I`ll put it in the next update.

[duncan]

discovered a new quirk today:

using the (now working) t5 input to announce whats playing, it announces on all zones in the house, not just the one that has been changed...the other zones dont change what they are playing, just announce what is now playing in the changed zone.

[hismastersvoice]

Did this happen after areboot?