ISY or Sonos Polyglot issue - False Positive

[carealtor]

I'm not sure if this is an ISY issue or an issue with the Sonos (not cloud SonosController) Polyglot.  It only happens with this one program and it involves the Sonos Polyglot.

I have it set up so the whole house amplifier (WHA) turns on if Sonos is playing.  It works, but every several days I notice the WHA is on when it shouldn't be.  As you can see, the player is Stopped, but the program shows as green.  If I "Run(If)", it still shows green.  What ends up fixing it is to resave the program by picking any line in the program, hitting "Update" (without making any changes), and then hitting "Save Changes".  Now it will show red (correctly) and "Run(If)" will turn off the WHA.

Edited September 4, 2020 by carealtor

[carealtor]

I'm really surprised that nobody finds it interesting that there is a very obvious logic flaw here.

[Michel Kohanim]

@carealtor,

Those programs are disabled?!

With kind regards,
Michel

[carealtor]

50 minutes ago, Michel Kohanim said:

@carealtor,

Those programs are disabled?!

With kind regards,
Michel

I set up 3 programs to separate the 3 conditions in my "real" program so I could see which one was causing the problem.  The problem exists both in my "real" program, and when I manually Run(If) the disabled program.

What is so interesting, as I said in the first post, is that forcing the program to re-save will fix the problem.

Edited September 4, 2020 by carealtor

[carealtor]

@Michel Kohanim

I just had the same thing happen again.  The program had a green strip even though the condition(s) were all false.  I manually "Run(If) and it stayed green.  I highlighted a line in the program and hit "Update" (without making any changes), and then hit "Save Changes".  Now it will show red (correctly) and "Run(If)" turns off the WHA.

I believe it has something to do with the Sonos nodeserver as this is the only program that is giving me this issue.

[gzahar]

I see similar situation with programs involving node servers (but not Sonos specific) after a reboot of ISY. I can also fix the issue by toggling the state of the node in the ‘if’ statement.

What version are you running? One of the newer RCs has a fix for a similar issue with ELK nodes. Was hoping it also fixed this. I haven’t tried the last two.

You are seeing this reoccur without an ISY restart?

[gzahar]

I see similar situation with programs involving node servers (but not Sonos specific) after a reboot of ISY. I can also fix the issue by toggling the state of the node in the ‘if’ statement.

What version are you running? One of the newer RCs has a fix for a similar issue with ELK nodes. Was hoping it also fixed this. I haven’t tried the last two.

You are seeing this reoccur without an ISY restart?

[lilyoyo1]

I've been using this node servers for a long time without having any issues with it (knock on wood)

[carealtor]

@gzahar

I'm on the latest and greatest version of everything.  I just did some testing with rebooting ISY and there does indeed seem to be an issue there.  My false-positive shows up whenever I reboot the ISY.  What I can't say for sure is if this is the only time it shows up.  What I am also noticing is that the Sonos Nodeserver is not showing any Status (it is blank) for this player after ISY reboot.  Yet the condition "is Playing" is returning true.  

[lilyoyo1]

14 minutes ago, carealtor said:

@gzahar

I'm on the latest and greatest version of everything.  I just did some testing with rebooting ISY and there does indeed seem to be an issue there.  My false-positive shows up whenever I reboot the ISY.  What I can't say for sure is if this is the only time it shows up.  What I am also noticing is that the Sonos Nodeserver is not showing any Status (it is blank) for this player after ISY reboot.  Yet the condition "is Playing" is returning true.  

I've noticed this too after a reboot of either the router or ISY (mostly with Harmony). I think there's a handshake issue when the systems reconnect to one another