Geddy

@zsima you could use the "Repeat" function in the program. I don't typically use repeat; therefore, I don't have much experience with it. Know that any change in the "IF" statement will cause the program to re-evaluate might stop the wait and/or repeat portion. You can read more about programming in the ISY Cookbook found in the UD wiki. While it was written in the ISY994 days (and some even before) much is still applicable today. It can get even more advanced by using deactivated programs that are called by other programs. Options are limitless. Just have to "play" and learn what works for what you're trying to achieve. Note: To test the program disable the program (so the "if" isn't evaluated), right click the program and select "RUN THEN". That should run the lights and waits that you setup. If I do this I'll reset all the waits to something like 10-20 seconds so the lights cycle quicker than waiting hours.

@zsima Lots of ways to do this, but the best is to start with the "IF" for being from Sunset to Sunrise (next day), You can also make a folder with folder conditions that would only allow the folder to be "true" from Sunset to Sunrise (next day) and then programs inside there to turn lights on and off at set times. Random-On-Example If From Sunset To Sunrise (next day) Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') What you can then do is add waits and turn lights on then more waits and turn off. I do this some with programs to run when out of town to randomly turn lights on and off. I add a fixed wait time then a random wait time to at least get some difference for the starting time and/or the time between when lights are turned off. Note, since random really is just that I add the fixed time to be sure the lights are on for at least 2 hours. You could alter/adjust to fit what you're trying to do. Like this: Random-On-Example2 If From Sunset To Sunrise (next day) Then Wait 2 hours Wait 21 minutes (Random) Set 'Backdoor' On Set 'Front Door' On Set 'Table' On Wait 2 hours Wait 1 hour and 21 minutes (Random) Set 'Backdoor' Off Wait 1 hour and 21 minutes (Random) Set 'Front Door' Off Wait 1 hour and 21 minutes (Random) Set 'Table' Off Else - No Actions - (To add one, press 'Action') Folder conditions setting: (Note, folder conditions are special and should not be set on the root folder ("My Programs"). Any folder condition controls all programs within THAT folder. If the Folder is "False" nothing in that folder will trigger.) Tests - Folder Conditions for 'Tests' If From Sunset To Sunrise (next day) Then Allow the programs in this folder to run.

It seems you might have a sudden line noise issue. Kind of difficult to find, but follow the troubleshooting tips in the wiki and you'll be on your way to figuring out if this is the issue. https://wiki.universal-devices.com/INSTEON_Signal_/_Noise_Troubleshooting Things to check for are new devices added, old appliances that might be running on same circuit of either the switch or the PLM, as simple as phone charger left plugged in could be going bad. @MrBill had a good post that I remember helped others in the past. Check this process out for assistance. If you mean "work as regular" meaning turning the load connected to the switch on/off that's expected...just means the switch is working normally. Just the "smarts" of it might not be working. If it's in a scene it should still be working the scene because the ISY writes the links to the switch. (I think this is expected...I don't have many scenes to directly compare/test with). Now that you have another device not working it's either the noise or sadly a PLM could be dying. I'd troubleshoot the noise first.

@SHM split out from where you or originally posted since it's really a different issue (and specific to your issue). This way it allows YOU to get the help for YOUR issue. Since the other thread had a solution (that didn't apply to your issue) it's better to have started a new topic to get help and find a solution that works for you. Would you post the program that's setting the variable? Do you have just one program that is set to adjust the variable on motion and again when it times out? What is your program that is setting the variable back to 0? What are you attempting to do with the variables?

Glad you got it sorted out. Seems like you might have had an old "version" of the start.jnlp file. There was an issue several months ago (October 2023) about that happening when something changed in the background (best I can explain). I was going to ask when you were getting the "not found" error. If it was a pop up what you just did (using a fresh downloaded start.jnlp file fixed). Previous posts about the "not found" issue: https://forum.universal-devices.com/topic/42008-iox-finder-error-not-found-warning/ https://forum.universal-devices.com/topic/42159-iox-finder-not-found-error-message/ https://forum.universal-devices.com/topic/42176-not-found-message-when-starting-iox-launcher/ If you're saying you're getting it in the IoX Finder title bar that's something different. But, sounds like you got it resolved. As to where stored addresses are kept they're probably in the .state files Here's some wiki info related to other issues, but I think one of them might keep the info of manually entered IP information. https://wiki.universal-devices.com/Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored Usually though manually entered IP addresses can be removed without issue.

@Edmund Lam After you make the change you want be sure to hit "Backlight" button to the left of the setting. That should make it adjust. (This was a change made early in IoX 5.x days - back when only the ISY994 was available) Note there appears to be a longstanding UI issue that when you first open admin console the backlight setting will not display what you have it set to. Do not think this means it will revert to "On 0 / Off 0". The device is set properly, but the UI is not displaying the correct value. Not sure if this is a bug or just a function of Insteon and how IoX reads (or can't read) the value set at the device level.

@andrew77 have you made sure that your portal subscription is active? In another post @bmercier said he made some changes related to the Alexa connection this morning that might have been causing issues. The scene issues working/not working outside lights seems like it might be a local communication issue that isn't triggering the scene correctly. Remember "noise" isn't always created by NEW things added. Some have found that failing power supplies for other equipment/devices or even phone chargers randomly left plugged in can suddenly add noise or degrade powerline signals.

Are you running any anti-virus or firewall software (other than Windows default programs)? Turn those completely off and try again. Maybe after disabling you should clear the cache, delete old start.jnlp/admin.jnlp files download fresh IoX Launcher from UD site ("My ISY" on top right) run new start.jnlp and accept any java alerts What address are you using in the ISY Finder window to access the ISY994? Are you using a local IP or Portal connection? When do you get this error? When logging in or after the window has been open (a while - hours)? Admin console is not designed to be open 24/7. Have you set any "funky" settings in Java to be high security? Make sure you're running "generic" java downloaded from https://www.java.com/en/download/ (current version is Version 8 Update 401).

@glacier991 Questions to learn more to try to help: What phone system are you using? Android or Apple? Are you using UD Mobile or another app/system to trigger boundary crossing? When testing is UD Mobile active on the screen, running in the background, or stopped/forced quit? If using UD Mobile while at the location go to Geofence and hit “Trigger Enter Command”. Is the result instant or delayed? How recently have you setup the Geofence? You might need to set 2 fences with one further out for some GPS signal delays. Have you rebooted your phone lately? (Random, but just a step in troubleshooting 101)

Please be sure to update here what support finds and when/if fixed what was done to fix this so we know and it might help others if they should run into this type of issue in the future. Hopefully it's a simple fix and you're up and running again soon.

As I mentioned in my earlier reply: Of course...as you said there's also a post about it in the "Current Release" area of the forums, but there is also a link to it in the wiki. It's just 100% easier for me to suggest going to UD's main site and clicking the "My ISY" link. It's not really all that intuitive, but having suggested downloading it so many time it's simple to point to that location. Did you get things squared away? Were you running a firewall or antivirus software on the computer in question?

Make sure you relaunch admin console if it was open when you added a plugin. Nodes are only loaded to admin console on load. It’s suggested not to have admin console open when adding or editing plugins. Then all new nodes or changes are read by admin console on launch. Did you migrate from ISY994? If so you have to select and save all network resources. This is a step in the migration process.

@dpierre if you can access admin console the Polyglot uses the same credentials (as @tlightne posted) If unable to get into admin console you can reset credentials by pressing the multi-function button depending on your device. This can be found in the wiki. For the eisy: https://wiki.universal-devices.com/Eisy:User_Guide#Reset_Credentials

@ctviggen1 are you running antivirus and/or firewall software on the computer? Disable both, clear Java cache (checking all 3 boxes). Delete any old copies of start.jnlp (and/or admin.jnlp). Download a new IoX Launcher (start.jnlp) from UD site (click on “My ISY” on the top right). If doesn’t go away, but still able to find and access ISY then you can ignore it (based on old replies from @Michel Kohanim on this issue…used Google Site Search to find old posts with this issue). https://forum.universal-devices.com/topic/32124-socket-open-failed-ssdpclient/ https://forum.universal-devices.com/topic/21736-socket-open-failed-ssdp-client/

@apostolakisl Tesla recently updated their API so @Panda88 might need to update the plugin. The good news is they’re now supporting 3rd party more…hopefully it’s good for the plugin use.

Yes, I believe it should be identical. I did not use UD Mobile when on the ISY994 so don't have firsthand knowledge, but know UD Mobile works with IoX 5.x and up. Since ISY994 ran 5.x it is supported and should work the same. In the UD Mobile Wiki there are steps for migrating from ISY994 to eisy. https://wiki.universal-devices.com/UD_Mobile Sadly, no. This would be a nice addition, but not one I've seen.

You've got an issue of two devices trying to handle DHCP (double NAT). The Deco needs to be put into AP mode. I've got an Older Deco m9...in the app click "More" on the bottom right, then "Advanced", "Operation Mode = Access Point". This should DISABLE DHCP on the Deco. You will need one device plugged directly into the Arcadyan (if it has multiple ports. From there you can use all the Deco satellites as switches (usually they have 2 network ports...or at least the older style did). The problem is if you're connecting the ISY994 to the Deco, but your computer is on the Arcadyan wifi then it's as though they are two different networks and not really talking one to the other. Looking quickly online looks like settings on that modem/gateway are fairly limited. There doesn't appear to be a way to bridge or setup DHCP reservations on the modem. I guess you could allow the DECO to setup DHCP and be on a "double NAT" network, but this could cause issues (like you're experiencing). The other option you have is to leave it as you have it. Just connect your computer to the DECO network. I would set it up as a different wifi SSID and use it 100% for anything that needs to talk to other devices on your network (i.e. computer -> ISY, computer -> wireless printer).

Sounds like you might have some setup issues. My Moblinc Pro works just fine with my eisy. I have Mobilinc Pro installed on iOS and have UD Portal subscription so I use the my.isy.io and portal credentials to setup remote access on Mobilinc. Though I do suggest using UD Mobile since it's much more robust for Polisy/eisy users I still like the setup I have with Mobilinc and the ease if/when I need a mobile app. Be sure you're setting up Moblinc as described in the wiki: https://wiki.universal-devices.com/ISY_Portal_MobiLinc_Configuration

@EWhite just be sure to install the firmware on the ISY994 that is specific for z-wave and no PLM! Otherwise, it will always go into safe mode and potentially cause issues. Source: the 5.3.4 release post

Are you still getting the error? Thought you implied it went away after you updated the firmware. Make sure you shutdown any anti-virus and firewall programs, clear the Java cache (temp internet files) - be sure you check all 3 check boxes in the process. Delete any old start.jnlp and admin.jnlp files on your system. Download a new start.jnlp from the UD Site (click My ISY on the top right of their site). Run start.jnlp and accept any Java alerts. Then run the “IoX Launcher” icon placed on the desktop. If you still get the error take a screen shot of it to show when you get the error. Usually this error only happens if the computer or ISY drop network connection. Seems like your network or something on your computer might be causing communication issues. This is why you have to shutdown anti-virus and firewall programs you might be running.

You cannot. That's Z-Wave "standard". It will continue to advance until a point (I forget where it gets to before re-starting, but I've know many have commented on this in the past). Maybe look for posts from @lilyoyo1 about it. I'm not strong enough on Z-Wave to answer this one. I'll just revert to what I've seen a lot of other users suggest is that you must "exclude" a device before "including" it. You might have attempted to add it while something is still in the IoX system so you might need to remove all the nodes dealing with the motion sensor(s) and then factory reset the sensor and exclude/include to bring them back in cleanly. I'm sure more advanced z-wave users will chime in and help you out for sure.

That's a different issue. There was a question recently about trying to figure out when power went out to a device. HA! It was a breaker in a post by @jec6613. Good comment there about a Z-Wave device with a battery backup. But, I think you'd be better off hiring an electrician to come in and test the circuit to see if they can figure out why it trips (regularly?). Don't just stick a band-aid on a possible electrical issue!

If you tried it yesterday (Wednesday, 1/17) it seemed there was an issue during the day. Might have been related to your connection problem. Why "wait" until you're back at the office location? Just turn wifi off and use cell signal to test it while you're sitting at home and you can monitor in/out communication and probably figure this out without leaving the house. I get that you're probably on wifi at the office too, but to me step one would be "fix" remote connection on mobile network. Yep. Sounds about right.

My first question would be why do you think devices are going "offline"? Do you think you have issues or are you trying to get a notification for if you ever end up having an issue? I do not think there is a way to get any such notification since there doesn't appear to be a node of status for an individual device. If there is/was then there would be increased network traffic always sending a query out to the device to listen for a reply. Thus adding needless Insteon traffic to the system and possibly over working the ISY994. With that in mind as @jec6613 comments about the heartbeat. As far as I know only Insteon battery devices send heartbeat signals. None of the wired devices do (or at least not that I've seen/experienced). There are examples of programs in the wiki and (old) ISY cookbook that should give you information for writing a program for heartbeat signals. Turning the question back to you though about why you think this is something you need. If you're having signal issues then the biggest question should be what is causing the problem. Just getting an alert isn't going to help resolve the issue.

@GHenry FYI for future programming help please try to share the program in text format. Right click on the program and select "Copy to Clipboard" (be sure you use the COPY command...should be the last option). Then paste it as text in the forum post. This allows anybody offering support to edit the program without having to type so much of it in (as @paulbates did above). It also makes the program searchable in the forum should you have a reason to trigger your memory and find it down the road or perhaps help others that might have a similar issue. Lucky you only get it twice. It will trigger anytime either of your IF statements is true. So if you are having temperature changes right around your target you could get multiple alerts. Somebody recently had this question about another temperature or warning alert. I believe the answer there was to set a variable so the program only triggered once. You could set a temp variable and that is then triggered by another program to send the alert. With that you could set a min/max temp to alter the variable so you might not get multiple alerts of the same temperature change.