landolfi

I get that. But shouldn't that be documented somewhere if IoX can't find the ISY when its IP changes as appears to be the case? Otherwise a situation like mine occurs where the Polisy goes offline temporarily during a software update and another device takes its previously assigned IP. What I think we are saying is unless you plan to deal with IoX not finding the ISY when its IP changes, a router reservation is REQUIRED.

SOLVED: It appears the manual IP I had set on the Polisy got reset in the 5.5.9 update, because Polisy now shows DHCP and the IP address has changed, which is why IoX couldn't find it. Meanwhile, another device stole the (former) static IP. I guess I needed both a manual IP and a router reservation.

I can get to the Polisy through the ISY portal web access but IoX doesn't find it. I'm running firmware 5.5.9. I can ping the Polisy and it responds. I just cleared the Java cache since I upgraded to 5.5.9 yesterday, although I am 90%+ sure that IoX has worked previously to this since the firmware update. Any other suggestions?

Has anyone else experienced a situation where IoX can't find Polisy until you ping it? It doesn't happen often but periodically IoX can't find Polisy (which has a static IP) and I have to ping it. First ping usually fails, then when Polisy starts responding, IoX finds it.

Never mind about the ZSE44s. They're battery operated and were just really slow to report.

I have 2 ZSE44s that I use for temperature monitoring, neither of which is working since 5.5.5. Anyone else having trouble with 5.5.5 and ZSE44? Still using the Zooz 700 dongle for Zwave.

Yep, I have an open ticket.

I j I had in parallel had the same thought. The only program that has a reference to that variable's init value is the startup one, and I still haven't restarted. Regardless, if that program had run the variable would be nonzero. It happened again between yesterday and today, whatever the problem is. This time both init and current value were zero. Could this be some bad memory in the Polisy?

The init value got reset to zero again sometime between yesterday and today. I have no idea when because the nifty code MrBill suggested only runs at startup and is otherwise disabled and I haven't restarted the Polisy. I opened a ticket, but the error logs show nothing. The only thing that has changed is I updated firmware to 5.5.4.

Thanks! I thought maybe you picked 42 because you knew I had it set to that once. Because you do seem omniscient…

I assume 42 is just a random value, or does it have to be 42? Does [disabled][Run on Startup] do the same thing as enabling Run on Startup on the Summary tab?

i can’t get a notification for an inIt value change, can I? I had one set for a value change that I could reinstate.

Thanks! Will keep an eye on it. Meanwhile, I set up a startup program to set the current values just in case the init fails.

A follow-up question on state variable behavior: I thought state variables were supposed to have their values persist until changed by a program or a restart, and that init values were permanent until changed? I ask because on firmware 5.5.4, init values have been reset to zero for a couple state variables and there are no programs capable of resetting them to those values. So I assume it had to be IoP? I just added the init values back and took a screenshot for my own sanity to confirm they were there at one time. This reset also happened to all state variables when I upgraded to 5.4.4, but that I suppose is to be expected when the firmware gets updated.

Thanks again! The difficulty I had was understanding how to link the state change with a program, which you explain well above. What I didn't understand was that the link from variable to program is simply referring to the variable in a program (if state.variable >0), which gets evaluated any time the variable changes. I got it working and your min and max value integer variable constants gave me a way to ensure the speakers don't get overdriven. I find that because of wide variations in FLACs ripped from CD, I use the absolute volume setting much more than relative volume changes. Now I just need to remember to use Alexa to make all the changes to volume and not the Jriver app. I also noticed in my case it makes a difference what Alexa spokens are used to call the amp: For instance, for some reason I find Alexa hears "amp volume up" more readily than "Denon volume up". Often she'll take the command as a request to hear the definition of "Denon".

A basic question on using state variables with programs when the state variable increases or decreases: I know a change in a state variable causes an event that can trigger a program, but I am stuck trying to figure out how that works when the change is an increment or decrement. Say I have state variable X and I want to trigger a program A when X changes in value + or -, how do I link that value change to a program? EDIT: After I wrote the above, it occurred to me that a simple > 0 test would probably be enough because it will get checked anytime the state variable change event occurs, is that right?

One question on this: I might be overlooking it, but where is the value of Vol.Adjustment coming from?

Thank very much, exactly what I needed!

Thanks, I used the forum search and didn't see that one. Based on that discussion, it sounds like the best/easiest way is to just create a network resource that specifies an absolute volume level. I thought maybe the state variable would enable me to store the current volume level and then have a network resource to decrease that by (for example) 5 db. But what is confusing to me is how to use a state variable to change volume up or down and why I would want to.

This is a basic question but I can't find anything specific in any of the forums: I don't understand why the Alexa integration supports state variable as well as network resource for volume control, and I'm not clear on how a state variable would work with volume except maybe to set an absolute volume. I already have network resources sending power commands to my Denon receiver, but I'm not clear how the variable setup for the Alexa volume control integration would work, either in the state variable or in a network resource, and I don't want to blow my speakers experimenting. Can anyone provide an implementation example?

I had the same experience with the Update Packages button not doing anything. I did only #2 of the post @Geddy referred to and it all worked fine. One additional thing not mentioned in the post was after the Polisy/ISY restarted, I had to re-download IoX because it complained that my IoX launcher and Polisy/ISY versions didn't match.

I have been back and forth with them because in my case things just weren't running when the IoP became unresponsive. We've eliminated a lot of things but now they're asking about what node servers I'm running. I'm running: MyQ (PG2) Ecobee Sonos Blink Yolink Virtual Wake on LAN I only use Sonos and Yolink in automations. I had the same experience upgrading to 5.5.2. Clicking Upgrade Packages did nothing. I ran the command line commands and other than getting a notification that IoX didn't match ISY version, everything worked fine.

Did you ever get this figured out? I upgraded to 5.5.2 yesterday on the advice of support because the problem continues of the ISY disappearing and devices becoming unresponsive. This time it happened 2X in a day. Usually I am able to get into admin first logging in to Polyglot, then IoX sees the ISY, but that's not working any more, so I had to just pull the plug altogether. Support suggested it could be a firewall or VPN, neither of which I have. The weird thing is that when this happens I can get to the ISY via the ISY portal web interface, but it is only when I log into admin console that the ISY responds to commands. When I do finally get in via AC, there's a long period of refreshing (40 secs to 2 minutes) before it responds.

No, this was a case where the entire node server disappeared from its Polyglot 3 slot. I added it back and it seems to be working OK now.

On a hunch I disabled my Query All program and haven't had any issues since. At least not that I've noticed. Not sure that's the reason because most of the time everything works fine.