Geddy

@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!

@TSinclair I had the same problem this morning. Looks like it's an issue with ISY Portal. See this from @bmercier that they're working on this issue.

You should upgrade your Polisy though. I think most of us have seen that not keeping the Polisy (and now eisy) updated can sometimes cause problems. Thankfully, the update process is fairly simple by just opening the Admin Console for IoP (ISY on Polisy) and hitting the "Upgrade Packages" button. With the Polisy there will be 4+1 beeps when the process is complete. If you can't hear the beeps then hope you can see the LEDs on the front. Once the two right lights stop flashing and you have a solid left it should be complete. You can keep up with what is the current version for your device(s) in the Current Release Announcement area of the forums. If you don't visit the forums often then I suggest you click on the "Follow" button on that page and setup notifications to email you when new posts are made. Actually, I just did this today. I migrated from ISY994 running 5.3.4 to eisy running IoX 5.5.3 and PG3x 3.1.18. There were a couple of road bumps, but in all I'd say it took less than 30 minutes to migrate everything. I have about 40 Insteon devices, 1 (new) z-wave device, and 2 node servers. I only migrated the Insteon install as z-wave was new for me. Since I only had 2 node servers and didn't have anything using them (at the time) I just started over with those and they installed great. UDI has released several updates since eisy was released that have really improved the performance. I expect this to continue as more bugs are found and ironed out.

Thanks for the heads up. New forum added! Post moved into it. https://forum.universal-devices.com/forum/414-eisyir/

Did you follow step 12 of the migration process in the wiki? https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migrating_from_994/Polisy_to_eisy

If you just got the eisy and it shows IoX version of 5.4.5 then it needs to update. When you log into the web dashboard of the eisy what is the version of PG3x? There was previously an issue with updating devices around that version, but I thought UD reported that was corrected and devices should update correctly again. If it is not then please open a support ticket - https://www.universal-devices.com/my-tickets IoX current version = 5.5.3 PG3x current version = 3.1.18 (as of time of this posting - referenced here: https://forum.universal-devices.com/forum/339-current-release-announcements/)

From the "UI"? There was never a way (that I recall) to submit a ticket from anything other than directly on UD's website. Need to login to: https://www.universal-devices.com/my-tickets/ The email method hasn't been working for a while so the only way is to submit a ticket is through the site. Looks like it's just suffering some font issues. The link is there, but it's very hard to see given that the font color must have changed.

No, topic suggests this is for z-wave migration. "How to migrate to ZMatter Z-Wave using an ISY-994 Backup" Perhaps checking out the wiki eisy user guide would help with other migration questions.

@TRI0N yes, the link to “more info” in the Hue NS remains broken. I usually just find the PG2 page on GitHub. There is a PG3 repository, but think the basics are still the same as PG2. Here is the info: https://github.com/exking/udi-hue-pg3 But I think most of this is also in the setup area of the node server.

So you must have missed the steps in setting up the eisy with UD Mobile that setup a trial with UD Portal. I think it was in all the release and setup information that was initially released. It was certainly in the videos that were made available to help with the onboarding process originally. And it’s in the wiki, but does appear there is a dead link to the actual migration part….but it should be the same/similar to the ISY994 to Polisy process…. https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Setup_ISY_Portal_for_Remote_Access/Alexa/GoogleHome/IFTTT Polisy migration link info: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Migrating_from_994_to_Polisy And in case you missed it….here is the wiki for using UD Mobile to setup the eisy. In the linked video it mentions the portal trial about 55 seconds in… https://wiki.universal-devices.com/index.php?title=UD_Mobile#eisy_WiFi_Configuration

Agreed, the "announcement" still mentions the beeps, but I mentioned in my reply that the eisy doesn't have a speaker so the beeps don't matter anyway. Those instructions were written for Polisy users and are still being used (even for eisy updates). I also mentioned in my reply perhaps allowing 30 minutes as some have suggested they waited that long and it was ready to fly. It has been a while since I ran old updates and I don't time how long I wait as I'm usually off doing other things and come back to it much later. No. I don't get why people assume that flashing the hard drive helps. It's not needed...and there's other ways to handle it. Great! I was going to give you a link to other steps that would have resolved it, but glad these worked. They aren't the suggested route now because one of the steps might upgrade everything and things in freeBSD have been known to break things in UDI's setup in the past. So now that you're at this point please just keep up to date by following the "Upgrade Packages" button. Glad you got lucky with one that did. Many others have posted even after upgrade the NS didn't start or didn't feed the nodes to the IoX system correctly. That's why the reinstall was needed. Make sure it's working as expected on Admin Console. You might still need to reinstall for it to properly handle everything.

You can't use HTTPS in the Polisy to connect to the ISY. It needs to be HTTP. Wiki instructions: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#ISYs Step 3 = Make sure you use HTTP and not HTTPS If you mean via IoX Launcher then see this section: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Can't_Find_Polisy