Geddy

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.

@Crunchie58 welcome to the Universal Devices forums. ISY is the controller service for devices that Universal Devices manufacture. Currently their offering is the eisy product. You can learn more about Universal Devices from their website: https://www.universal-devices.com/ This site is not affiliated with YoLink. This area is meant more for the YoLink plugin that works with the eisy to allow the YoLink products to work with other home automation products that the eisy controls. If you're looking for specific YoLink support you should review their site: https://shop.yosmart.com/ I think the support section of YoLink's site gives an idea of how often the temp will update. I've not used their products personally so don't know that answer.

None that I've seen. It appears that eisy and Polisy will continue to be developed in parallel, but of course the focus is on the added functions that the eisy can handle. As far as IoX and PG3x both should be able to be maintained on the Polisy for the foreseeable future. I think the mention for upgrading from Polisy to eisy is only if you want the ability to do more with the eisy going forward. Certainly something to ask UD directly. You can contact them directly through the link on their website. https://www.universal-devices.com/contact-us/

This just means the last time the program evaluated it was false. https://wiki.universal-devices.com/ISY_Programs:Icon_Colors "Partly red - not currently running, but last ran the ELSE code" To test if the program "Then" runs correctly right click the program and select "Run Then". It should run a complete cycle of the then (assuming nothing triggers the program during the wait to cause the program to re-evaluate). More than likely the light level was higher than 20% causing the "IF" to be False. Since you have nothing in the else nothing happened. Remove the 20% condition and test it. My guess is you are really only wanting/needing the lights to come on when it's not the middle of the day. Finally: Please note the better/easier way to share programs in the forums is to right click the program then select "COPY to clipboard" (be sure you select the COPY option). then paste it as text in the forum post. This helps others trying to help offer alterations to the program without having to type it or recreate it locally. It also makes the program searchable in the forums for future assistance (or memory jog should you run into this issue again).

Do you have a backup from before folder creation? I'd restore that backup and see if that puts things back to "normal". Can you share a screen shot of this? There should be a root folder then a sub folder that would have devices and other folders in it. Didn't think it was possible to add another folder higher than root. What probably happened is you just renamed the root folder. I've done that one on mine and it's not an issue. I think the default was "Network" then "My Lights". It's been ages since I renamed mine so don't know for sure. Just going off some old images in the wiki. But as @DennisC make sure you remove everything from the folder first. Right click on any devices in the folder and select "remove from folder". Once the folder is empty you can right click on the folder and select "Delete folder". Reference: https://wiki.universal-devices.com/Tree_View_(Navigation)_Pane

@Jay E Process @Techman describes is outlined in the wiki (written for old ISY99 and ISY26, but still applies to ISY994, Polisy, and eisy. https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Adding_a_Device#Adding_by_Linking_Method

I doubt Ring sends any sort of status when motion stops. It's usually just an on/trigger and "records" for a preset period of time. The worst thing is if the camera you have is a battery operated camera then there's probably a "cool down" period and it doesn't trigger back-to-back motion if within the cool down period. My experience with Ring has been this way (only triggers on motion, not when motion "ends"). Wired devices that I have (Ring Doorbell Pro and Wired Floodlight Cam) will trigger back-to-back, but a battery operated Spotlight Cam that my neighbor has says he only gets a motion alert about every 5 minutes.

@SHM when you reboot next try logging in and look at the programs summary tab and sort by "last run time". See if there is something that is triggered as @n_sievers suggests. That will give you an idea if it's a program. The "Query at Restart" and "Catch up schedules at Restart" options are on the Configuration tab. I might suggest unchecking those as first attempt of troubleshooting. Also check for any programs that are set to specifically "Run At Startup". This option can be seen in the Programs Tab under "Summary" and then sorted by the "Run At Startup" column. Right click on any program that has a status "ON" to view the program and see if any conditions were met to trigger that program when rebooted. To disable "Run At Startup" right click on the line and select "Disable Run At Startup" (think about it before blindly doing that though...that's sometime a good option to have on if/when you lose power during the day and it comes back later in the day it will run those programs when the device boots back up). Otherwise, are any of your devices really old (no set time, but maybe things pre-2013-2015)? They could be having the dreaded "all on" issue from lots of traffic at startup. Hard to tell what's really happening. I'm not sure if there's a sure fast "date" that things were fixed on the device firmware side, but something could be causing issues if it's an older device. No way to keep admin console open/connected through a reboot to watch the event viewer, but if you're able to log in and get event viewer open and set to level 3 as lights still come on it might also shed light on commands being triggered/sent through the system.

Did you submit a ticket to get help on this? Not being a macOS user I'd say the error appears to be a macos system issue. There isn't anything that the IoX Launcher would be trying to "auto update" as best as I know (from the Windows side of using the system). Since you got the Java issue resolved I think there would be something in the macOS world that is trying to update something when the IoX Launcher is running that's causing issues. It would be interesting to learn if UDI had any other information to offer on a support ticket.

@Kentinada glad you got it working. I was going to suggest that you make sure the Remote Access is enabled and active. Some of us had issues a while back and noticed that the remote access was enabled and configured, but not active. On the Portal account check here:

@kewashi I think in this instance you'd be better off opening a support ticket with UDI rather than trying to get help on the forums. If this isn't a common issue not too many users would be able to help on this and UDI would be able to troubleshoot quicker/deeper/better than waiting on forum posts. Support ticket: https://www.universal-devices.com/my-tickets

@WShellshear do you use Z-Wave? Easy...look here: https://forum.universal-devices.com/forum/339-current-release-announcements/ If you currently have 5.0.16C then get that again (if you're using Z-wave) Series is the board type. See this post for info how to tell the difference: https://forum.universal-devices.com/topic/29371-zwave-tips-and-tricks/ If you don't use Z-wave (even if you have a board) then the current should be 5.3.4. Seems that you come here to get help, but you don't really read the links people provide you because all this information is easily found by reading the wiki and just the categories of the forums. Hopefully you get it sorted out. The more that I read your earlier posts I think you've got computer issues rather than ISY994 issues. Are you running any firewalls or virus software on the computer(s) you're trying to access the ISY994? Are you using the IoX Launcher (start.jnlp) process to access the admin console?