Geddy

Make sure you refresh the page. Maybe even hard refresh depending on your browser (Chrome (and edge) is CTRL + F5). Somebody earlier reported the issue and after removing a node server that wasn't in use something triggered it to match. But I just ran the update (no issues other than restarting Hue node server) and refreshed the page and showed 5.5.5 just fine.

@rahnee looks like IoX 5.5.5 is good to go now.

I 100% agree. Thankfully I do not rely on node servers so haven't worried about such issues. They really seem great for people that need them and rely on them. My system isn't that complicated and not spread between multiple ecosystems that would require node servers to monitor/control everything through ISY. I think most (as with PG2) have always just taken the leap of faith a little more blindly and trusted that there would be support for the systems they're using. To me, I've always looked at node servers as something somebody made to support their system. They then offered it to others at large through PGC/PG2. With the development of PG3/PG3x UDI gave those developers a way to get paid for their development and (ongoing) support. Some have probably been more diligent with their development and support than others. But at the end of the day I see this more as an individual offering rather than company offerings and at that level feel that ongoing usability and support should be hopeful at best. Case in point that @bpwwer mentions at least one has recently decided to abandon development and turn their offerings over to others. Sadly, people that had purchased those node servers might now have to wait for them to be usable again. I highly doubt that many individual developers have a true license that is in place. I would assume it's under an blanket license agreement with UDI as a part of the developer level process. You bring up a lot of great and valid points for your situation and concerns. Others just take the leap of faith and keep on trucking.

Do you mean trial before you buy? Or something specific to the license? @palayman many node servers do offer a trial period. This gives you the ability to install and make sure they work before you commit. That information is usually seen in the details of each node server. Elk (for example) shows this: So you can try it for a month then pay $30 to have ongoing access to it.

What kind of "disaster waiting to happen" are you envisioning? My eisy+ZMatter sits in a cabinet and doesn't get moved/touched/adjusted. So it's a set it and forget it device. Minimal disaster ability to inflict issues with it (for my install). Do you have an issue with other USB devices randomly falling out of the port they're inserted in? If so, something else is wrong. I've never had a USB device disconnect without exerting some force to remove it from the host device. I'd say this is the same for eisy + ZMatter dongle. I haven't measured it, but there are 4 total USB ports available. ZMatter takes one and PLM takes another. My ZMatter sits off the rear USB port and the PLM is in one of the 3 on the side. I'm not sure how many USB devices you plan to plug into the eisy, but there are still 2 perfectly usable ports available. And if you're worried about the ZMatter taking up space there are USB extension cables to remove the dongle from the eisy unit itself. Personally, I feel the eisy is a nice little update from the Polisy. It's a much smaller footprint and only the ZMatter antenna add to the height. It's only slightly larger than the ISY994, but has a ton of new capacity. Sure, it's not as big or bulky (or shiny) as the Polisy, but it's just as good (if not better depending on what can be run in parallel down the road).

@Illusion Have you attempted to contact Insteon to see if their support has any tips/tricks not mentioned here or thought of? https://www.insteon.com/support I guess it could be that they're just old and have failed, but only partially.

@wacvmd No.

@Steve L glad you found it. Wasn't really sure what you were asking since you kind of floated all over the subject of what you really needed to know. For each node server you install there should be a "Details" button for the node server. From there you can see the configuration area for most node servers. Generally it's a good rule of thumb not to have Admin Console open while you're adding/adjusting node servers. Typically one of the steps is to restart Admin Console so it will load any new nodes being sent to the ISY. It seems that you might have installed the node servers while admin console was open and your reboot allowed the nodes to push to admin console correctly. And the general wiki is about all you'd need for Polyglot. Make sure you review the entire eisy user guide in the wiki: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide

Since you don't have the "Update Packages" button and you say you're on 5.4.0 your Polisy is out of date. The easiest path is to open a support ticket to get assistance with bringing the system up to date. Please open a ticket here: https://www.universal-devices.com/my-tickets

@rahnee FYI - merged your other thread (Locks not updating status) into this thread since they've evolved into the same discussion. At least now you've got them added to the system. Just can't get status to update. Had different people replying to each thread.

@rahnee I think this is an ongoing z-wave issue with multiple products. There are several threads mentioning this for other devices. The best way to alert UDI that this is happening is through a support ticket. It would allow them to help with a specific issue and hopefully help the rest having the issue at present. https://www.universal-devices.com/my-tickets Just make sure you're on the latest release for IoX as I think 5.5.4 did have an update for Schlage z-wave locks, but might still be having some issues.

@TRI0N Be careful using the word "certified". I don't think there's a real difference once a node server goes into the production store. I do not know of any "review" or process of making the change from non-production to production status. So "certified" isn't quite accurate. @aca2b2 the reply from @TRI0N is correct in that "non-production" should be more considered a "beta testing" area. Some developers are using the non-production store as an area to test features. So while they might be usable there might be some that are still being altered and could cause problems. Of course, we've seen the same be true for "production" store node servers. Each production node server should have a forum area that hopefully the developer is monitoring to offer support. The ability to charge for node servers was introduced as part of Polyglot 3 (PG3/PG3x). As node server popularity grew the requirement for the developers to support and maintain the node servers was seen as an area to support the developer's time and efforts by charging for a license.

Correct, but your statement was that as you wrote the program the light still turned off after the wait if you turned the switch off. You made it sound as though you want it to stay on (which when you changed to status did leave it on). To do that you'd have to add the 2nd part of the "IF" for "not switched off". In my program when I turned the office on my lamp came on. If I turned the office off during the wait the lamp remained on. Because I had manually controlled the switch off. You would need to add: And 'Keypanels / Great Room / GR KPL #2- H' is not switched Off Put that in your IF of the original as you have it above and the lamp should stay on if you turn off the switch (manually) during the wait period. Sorry...really beating that horse now. Just goes to prove sometimes there is more than one way to achieve desired result. But think we've hijacked original post too much. My closing remark is that I'm on eisy IoX 5.3.3 and works as expected. OP (@AllDigital was having issue with the wait because variable was changing before the wait and thus causing the IF to become FALSE and stopping the running of the THEN during the wait so the resetting of the variable never occurred. The reason their other programs ran with waits in them was probably because the if remained TRUE and allowed the whole THEN to complete. Once the IF becomes FALSE the THEN stops and runs ELSE. So maybe put the wait in the ELSE then set the variable after the time. Or, as @vbphil and @MrBill mentioned using 2 programs.)

I feel for that horse! As @Javi points out you need that 2nd condition in your "IF" to make the program false. I ran a test and you have to have the second condition if you're using switched. As in the reference (pg 160) of the cookbook. In my program I have the office being manually turned on causing a lamp to come on. If I manually turn the office off the light stays on because it was true. During the wait the program became false and stopped the "THEN". Because there is nothing in the else the lamp will stay on until I turn it off. test1 - If 'Office' is switched On And 'Office' is not switched Off Then Set 'Desk Lamp' On Wait 2 minutes Set 'Desk Lamp' Off Else - No Actions - (To add one, press 'Action') Status works for your situation because you only have the one condition being checked. Once the "STATUS" is true then the program runs THEN. If you then change the status to be off it turns your program FALSE and thus ends the "THEN" so anything that turned on would remain on. Since there's nothing in the ELSE there's nothing happening when the program goes FALSE. If you have Admin Console open while testing you should see the program turn green when true and running then. If you turn it off while running THEN it would put the red along the side of the program indicating that it's FALSE and no longer running THEN. I think it's an unfortunate page break in the cookbook that Figure 153 applies to 9.3.4, but it does reference "above program". Figure 152 goes to the prior section of simple conditional programming.

@Jason Madden this is nothing new to the eisy. The Polisy had similar restrictions. This has been somewhat discussed in another thread focused more on setting static IP, but your issue also revolves around the same issue for apparently why UDI made this change. Support! There were comments (when Polisy was released) that the number of support tickets dealing with network issues and users that set static IP. Many would set the (static) IP on the ISY994 rather than applying a router IP reservation then changed network equipment created a lot of tickets for support. In an attempt to limit such issues the devices are set to not be altered by users. Additionally, with the implementation of node servers some external systems use different ports to communicate and could cause conflicts so I believe UDI made further use of limiting the port options so that internal and external connections would be handled by the eisy (and Polisy) and not something users could easily "corrupt" by using different (potential conflicting ports). I'm not sure what you mean by: Seems like it would just be the firewall to allow eisy in/out access and wouldn't impact other devices. But only you know your (apparent) intricate network situation. I wouldn't expect anything to change from the hardware side as it's been this way since the Polisy was released (about 3 years ago). (really, "scores"? A "score" = 20...yeah...getting technical and comical, but figured you could handle it since you have a technical question/issue) And FYI - I am a user; just like you and most others here. I'm not affiliated with Universal Devices in any capacity. Just a user helping others out; like so many here.

Why not just change your time to now and see if it works? You don't have to wait until 5:30pm for something to work. Make it active now and test it. Most times you can just right click the program an say "run then", but you're right if you're trying to test time frame you've developed. Just adjust the time to be active now until 5:30 tomorrow. Then once you confirm it works adjust back to 5:30pm and go about your day. Also, as mentioned above...for future reference...right click the program you're working on and the last option of the menu is "Copy to Clipboard". Use that to paste the program to the forums. Your screen shots work, but often to save somebody time with typing to HELP YOU having the text of the program is easier than an image. @MrBill and I both suggested that above, and you ultimately used screen shots. Yes, much more helpful than your (original) generalizing of what you thought the program was doing, but would have saved time from Day 1.

@TRI0N the preferred method to post programs to the forums is using the “Copy to Clipboard” option at the bottom of the menu when you right click on a program. The XML has useless info. The “Copy to Clipboard” is then pasted as plain text, and thus very easy to read by all others. Seems like you typed the other info. Would have been simple to see the “same day” or “next day” setting in your first post if this method was used rather than XML, and helped right away.

Just IoX portion. The Polyglot backups are handled on the web side. But I think it does appear to backup nodes that are being fed to IoX. I figure if something is updating the part that's being backed up could be causing some delays (congestion). At least in hypothetical theory. Right?

True, but I never timed it on the ISY994. I would say it was longer on the older device. I just remember it taking a while, but not something I'd get up and walk away to wait on. Like you I don't go altering the system all that much so don't tend to run backups normally. Saving them in the cloud and on regular system backups add to that peace of mind that I'll have a recent backup if/when needed. Strange that a backup 4x the size took that much longer. Are you running many node servers? I only have 2 installed/running at the moment. I wonder if they're logging something causing bogging things down. I know Michel has said the system should be capable to handle many processes at once. Will be interesting to see if anything is done/mentioned about it in updates.

I've not experienced any slowness, but I don't have a vast system of programs. Just to test I just updated 3 of my programs and hit save. It took less than 2 seconds to save. I have < 80 programs (give or take). Again, not experienced this here. Even loading "Local" version of admin console. I can open admin console, allow it to complete then click program tab and be ready to work in < 15 seconds. My backup took about 1 minute. My backup size is just about 100kb. All my times were using the local option to open admin console on a wireless laptop on the other side of the house from the eisy that is hard wired to my network. I'm no longer running the ISY994 so cannot compare to current times for same handling. I have the Java parameters set as @MrBill stated (max & min). If you're seeing continued delays you should open a support ticket so that UDI knows this is specifically happening. There have been so many forum messages over the last month+ that I'm sure it's difficult to keep up with all the "little" things causing users potential issues. https://www.universal-devices.com/my-tickets

@breischaft One thing to watch out for....don't make changes in BOTH windows. Consider it just like having Admin Console open when installing/updating a node server. It's somewhat live, but some UI doesn't update correctly. I can't confirm this, but know it is/was a problem when adding node servers that it was always suggested to close/restart admin console so the nodes would populate correctly. If you go changing a program in one window the other will probably not show the change. And if you change a function in the other vice-versa. So keep up with where you're making adjustments and restart the other window if you need a fresh view. I just tried in the eisy and indeed can open two admin consoles at once. I tested a program and the status did update on the tree display. So that's at least updating live. And as @MrBill stated the sub link did show that I had 3 subs in use at the time (portal + 2 local). I tried with UD Mobile and Moblinc, but they both connect through the portal so didn't open/use any other subscriptions.

@n8ur9irl and @TRI0N since it seems that this bug should have been fixed in 5.5.4 please open a support ticket with UDI to see if there are still issues or if there's something else to try to get these locks to connect. https://www.universal-devices.com/my-tickets/

@oatflake The original reason for the “Query” program was to sync all devices and the ISY. Doing it at 3am meant there would generally be low traffic/noise so Insteon traffic would be processed better. It’s not really needed, but if you start having noise issues then it helps by bringing status in sync daily. It also helps if you have battery devices to trigger a status sync when other traffic/noise might not interfere. You could disable it and see if you have status sync issues. But it doesn’t usually harm anything to just run daily. If you’re having issues with it then it might indicate other system issues.

@n8ur9irl see if you update to 5.5.4 (just released) and see if it works. Looks like one of the bug fixes is for adding Schlage locks.

@kzboray I was thinking the same thing. With another portal update planned for tomorrow my hopes are high there won't be issue. But at least @bmercier knows what was done today to fix it in case there are more problems ahead. Thanks for the updates @bmercier!