Geddy

Thanks, but it's GEDDY (as in Geddy Lee - from Rush - best band ever!) Further, to mention somebody on the forums start with @ then typing their name a list should appear under and select the name it should put a bubble around their name. It then sends a notification on the forums. Otherwise, posts might go unread by the person you're trying to address. Like this: Once selected would then look like this: @saclarkdoc (Since I've quoted you in this reply you'll probably get a notice that you were quoted, but if I hadn't it would say you were mentioned. Like this: ) Now...to your questions (oh, and you can split quotes out by selecting text and a popup shows up for "quote selection" Before I do though...I would like to make sure you review the UDI wiki. You can read and search there for any other questions you might have: https://wiki.universal-devices.com/index.php?title=Main_Page If you are local to your device these are mostly interchangeable at this point. "Local" should grab the admin.jnlp directly from the eisy. Whereas the "Cloud" will grab the file from UDI's site to match your firmware. IoX Launcher was developed in the 5.x time of beta testing so that people wouldn't have to clear cache all the time and would automatically pick the correct UI for the Firmware. Since we all know "UI and FW must match!" (FW = firmware) 🤓 Although, I will comment that anytime you update the firmware it's still good practice to clear java cache. During eisy updates I have often had the "Local" version complain that it doesn't match FW after an update so it's just standard operating practice (SOP) to clear java cache (checking all 3 boxes in the process) and running a new "start.jnlp" to make things happy. "Response type 10" is due to a missing switch/module/node. Because the ISY process doesn't now how to reach whatever it was before it fills the line with this. If you have a printed version of your programs from the old ISY994 maybe it has the device that it should be. You should be able to click on the line and see if it has devices as an option to update to. (Old thread that mentioned this issue: https://forum.universal-devices.com/topic/39625-programs-have-response-type-10-on-them/) It might be a "starting" point to rebuild your "sensor timing data" - not 100% sure what you mean by that...if you mean "programs" yes. You seem to like using the word "sensor" a lot. Please clarify what DEVICE you mean rather than "sensor". (I feel like I'm channeling @Goose66 a little bit here remembering this post he made a while back.) Finally, best way to share a program on the forums is by selecting the program, right click, last option in the menu will be "copy to clipboard" then paste into the forum reply. If you wanted to you can use the code brackets in the formatting bar to insert as plain text, but that's not really necessary. Screenshots aren't helpful because usually people will want to help edit/alter the program and the text version is easy to be copied and edited by those helping you. (Please review @MrBill's signature seen on page 1 of this thread) Like this: ~Flood-Motion If '~NodeServers / ~Ring / ~932 Driveway (Motion)' is switched Motion And From Sunset + 1 hour To 6:30:00PM (same day) Then Set 'Desk Lamp' On 100% Set '~NodeServers / ~Hue / Couch' On Wait 2 minutes Set 'Desk Lamp' Off Set '~NodeServers / ~Hue / Couch' Off Else - No Actions - (To add one, press 'Action') Don't worry about that. It's not important and just fine to be disabled (that's the default status). I believe that's from an old ISY## time that would setup port forwarding options, but most don't worry about it and it being disabled is default and fine to be left alone. There used to be a menu option in the file menu to enable/disable internet access. That's gone, but apparently the Help -> About still shows the setting. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Enable/Disable_Internet_Access (see...for the ISY26/ISY99 era of products) Before you go much further, since you have a NEW PLM and you might have devices in your system from the restored backup you made you could run into issues. I'm not sure the real best way to proceed if you're leaving the restored backup data in the eisy to build from here. I would have factory reset the eisy (10 button presses - mentioned in the wiki!) or opened a ticket with UDI Support to get help completely clearing out the ISY information you restored from the backup. It could create link issues if you try using "exiting" devices that came from an unknown backup version. I don't know if you could attempt a PLM Restore with the devices in the ISY system currently then go through a Restore Device for each device. When I suggested clean slate I meant "100% pure clean slate". Don't use any info from the backup you tried to restore because it could have errors you don't know about in there. Good luck!

@apostolakisl I think you missed the hidden part about what the program is actually doing. @Bob Amott has different brightness levels based on time of day/night that he is trying to trigger. It's not the difference of on time. THIS is the meat of the problem. The programs aren't triggering the correct brightness! (at least that's how I interpreted the "challenge"). I think the option given by @Goose66 should work for activating the proper brightness. Will be interested in heard the results. Actually, I do have a program somewhat like @apostolakisl mentioned at the end, but I don't use motion sensors. I have a program that sets the on level (30%) during a particular time (night) in the "THEN" and 100% in the "ELSE". When the switch is controlled during the "THEN" time the lights do only come on to 30%. All other times they're 100%. So, it is possible either way. Just depends if you have those lights as part of other scenes triggering with other programs.

@saclarkdoc Sounds good. Probably a good decision based on prior comments and info you were showing. Hopefully you can setup to best suit your needs these days compared to the "old" setup. I'm sure a few things will be different along the way, but it's an option to be a learning experience and even possibly a time to review just what you've got and how it's all incorporated. Remember Insteon has products now and even their new i3 line (from the sounds of it UDI is working with Insteon to get i3 support implemented with the latest firmware). This even gives you a chance to see what other options you have if you need to make further investment in automation with the support of node servers and the ZMatter option. Good luck, and certainly post any new stumbling blocks you might run into (as new topics!) and the community is here to help out!

@hart2hart @saclarkdoc I think it should show in safe mode. I've never tested. It just means there's no PLM connected. @saclarkdoc at this point you've gone fairly deep into digging down the ISY994 path. Your current firmware for the ISY994 that you got running is VERY old (4.2.18). It's probably not of value to continue down that path if you only have a USB PLM. How many devices do you have? You might be better served just starting over with the eisy. This is is one of those times that not having a "current" backup huts. Also, if you had not kept up the ISY994 to the latest firmware (5.3.4) to be able to migrate there's almost nothing you could do. If you have anything in the eisy you should copy your programs (right click the root directory, last option on the menu will be "copy to clipboard", paste that in a TEXT editor (i.e. Notepad, not Word or other word processing program). This way you at least have a printed copy of all your programs to recreate them once you're running on the eisy. Otherwise, your issue is much too complicated to try to handle through forum posts (IMO). You would need to be active near same time and even then some complicated steps ahead to be attempted. Good work trying to get this far along, but after 4 days it probably would have been easier to rebuild the system using the eisy than what you've gone through.

@ccclapp unsure what you want from here either. But this thread was basically dead. It would be best to start a different discussion here. You're taking onto a topic that started almost a year ago and had stalled out a couple of times.

You said you've tried all the tricks, but have you physically pulled the power supply to force a restart? There have been some hang-ups in the update process that even hitting "reboot" in admin console did not actually force a total reboot of the eisy. That seems to have been fixed most recently, but make sure you've pulled the power, wait 10-20 seconds, plug back in, wait 3-5 minutes then try logging into admin console and checking firmware/UI version. Then try logging into PG3x and checking that version. If you still aren't up to 3.1.36 log out of PG3x then attempt an "upgrade packages" button push in admin console. If you've done all that then support ticket is your best option (as suggested above).

Where did you get the PLM from? If you bought recently and directly from Insteon then you should use their tech support to see if they can assist with any additional troubleshooting after you've read through the UDI wiki. Otherwise, yes, hope you can return/replace what you've got.

@mmb “EOL” usually means there has been an announced time of ending support. The ISY994 just went “EOL” after 14 years. Polisy has been unavailable for quite a while so I’m not sure when you bought yours, but it’s been out for almost 4 years and UDI has said they will continue to support it for at least many years (IIRC 3-5 years might have been mentioned). Meaning that would be supported for at least 7 years (at a minimum). Not sure what you are “annoyed” by given that amount of planned support. Considering some companies release devices and support much less time before a new product is released (I’m specifically thinking of router manufacturers). It’s amazing the life of UDI products and their (free) support for them. It’s not without their trying to get supplies to continue the Polisy line, but was better to explore other options and release the eisy. I think your original question was answered clearly. If you need more clarification the best way to ask this would be directly to UDI via their “Contact Us” options on their website. The forums are mostly user-to-user support. Providing the best guess from what many of us have read and inferred from other posts on the forums.

@TJF1960 not sure. But shouldn’t be an issue for those sizes. Make sure you zip them just to be sure they’re compressed as much as possible. Other option would be to open a support ticket (https://www.universal-devices.com/my-tickets) and attach them there, then PM @bpwwer your ticket number.

@TJF1960 send to @bpwwer via PM on the forums.

If you're using Windows and run start.jnlp and no icon is being added to your desktop this usually means you need to clear the Java cache and try again. In the past when Java updates it will remove the icon from the desktop and many have tried to add it by just running start.jnlp again, but it won't actually add the icon because Java thinks it is already there. So clearing the cache (selecting all 3 boxes in this process) should allow you to add the icon again next time you run start.jnlp. What "sensors" are you trying to control? As @MrBill states above typically "sensors" aren't "controllable". Since the problem above (not putting icon on the desktop) might imply that you haven't cleared the Java cache I'm betting that your Firmware and UI don't match (next time you're in Admin Console use the Help -> About menu and compare "Firmware" and "UI" versions. They should match, EXACTLY (even the time stamp). This is from a previous version for my system: What "instructions" are there? You might need to refresh your methods with the UDI Wiki paying specific attention to the eisy User Guide. https://wiki.universal-devices.com/index.php?title=Main_Page After you've reviewed the migration steps that @MrBill links to and further read some of the eisy User Guide hopefully you'll be up and running with the eisy. Finally: Not many people would risk downloading power point files. So in the future if you're posting images please save as image file types and only post images. Typically images or text files are all that are needed to help troubleshoot most problems around here.

Correct assumption...at least I assume as well. Looks like the internal card is no longer being offered on UDI's store site so maybe they're only selling the USB ZMatter dongle since that would work with Polisy and eisy options without having to open the case for the Polisy. Since IoX has always been geared only to Polisy and eisy then I would assume both units would be on this upgrade path and make all ZMatter hardware operational. Didn't appear to be at least according to the release: https://www.universal-devices.com/zigbee/ And in the announcement post: Unless wall switches are considered "modules".

@Michel Kohanim Nice stuff! Updated eisy from 5.6.2 just fine in a little over 3 minutes to first reboot. System seemed to go offline and/or reconnected the node servers during the process (got alerts on UD Mobile), but when logging into PG3x it showed I needed to reboot so went back to admin console (no notice to reboot) and rebooted. Reboot (button press in admin console) worked as expected. NOTE TO OTHERS: Lan access did require java cache clearing and new running of start.jnlp/IoX Launcher (https://isy.universal-devices.com/start.jnlp) to have FW/UI match. Didn't try cloud before clearing/reboot steps. System seemed to come up fine with node servers connected and working. Now if I only had zigbee devices to try!

You’re showing still on PG3x 3.1.33. This was a known issue with that version and fixed in 3.1.36. Best to press the button 6 times to shut down (power light should turn red after 30-60 seconds). Once red press it again to turn on. If it doesn’t shutdown then pull the power supply. Wait a little bit and power back up. Allow about 2 min to fully boot then try PG3x to see if you’re still on 3.1.33. Then use admin console and upgrade packages to get 3.1.36 installed. Will need to reboot once it is installed.

@someguy looks like you’re on a Polisy and running PG3. You’re probably on the most current version for PG3. The release you linked to is for PG3x that until recently was only for eisy. You can move up to PG3x, but if you are still using PG2 then you shouldn’t because that will be removed. You can always fine the current release announcements in this forum area: https://forum.universal-devices.com/forum/339-current-release-announcements/ The current suggested/recommended method for updating is always through admin console using the “upgrade packages” in the Configuration tab. You are on the most current version of IoX so you’re good there. (As of today!) You can find how to move to PG3x in the wiki: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Upgrading_to_PG3x There are some posts about that from others that updated to PG3x so maybe read those posts. But just know there is no going back if you make the move and realize you didn’t really want to. Once you’re on PG3x you would run the “upgrade packages” and it should bring you up to 3.1.36 (current PG3x version).

Nothing I can do about it. That's something @bpwwer or @bmercier would know about.

@tmorse305 I don't think node servers auto update on restart anymore. There might be a different upgrade process. Look at the purchases area and it might have an "update" option. I wouldn't uninstall, but perhaps just reinstalling in the same slot would force the new version to install.

@LKO another option is checking out the Coffee Shop area of the forums. Some people are/were selling their old ISY994 (and/or some Polisy). Perhaps they still have them available if you just wanted to stay in the ISY994 product line. But, agree with @MrBill that eisy is the only current upgrade path. I would try a different power supply for the current ISY994 though as it could have taken most of any surge from a hit. But eisy has the same interface as ISY994 for java admin console and doesn't require cloud connection (although the UD Portal does add a lot of functionality). The eisy does add the ability to run node servers to add a lot of different systems into the ISY system for control and automation with one hub. It just requires a UD Portal account, but not a ongoing subscription to be able to buy/install most node servers. (Note: Some node servers might require a portal subscription, but I'm not 100% sure which ones - I think Ring might be the only one currently.)

@rick.curl I get the thought of #1, but when you think/consider what's offered in the Portal subscription for the price it can't be beat! ($20 for TWO years!) But maybe check the wiki for info about other remote connection options: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Remote_Connections NOTE: that the certificate portion is beyond the scope of support from UDI. So your VPN comment might be the best option for your situation. From my experience the Portal connection works great, and the likely hood of down time is fairly slim. How often do you really use the app to control something in the house while remote? I only ask because I almost never do. (That's the whole point of automation, right? Not to have to do something manually.) I'm surprised when somebody makes a comment along the lines of #2 above.

@Kevin N Welcome to the forums! The "Query All" program was the default/stock program in the ISY994 firmware. It was used to check status of all devices. It's not necessarily needed as long as you have good communication within your system, but it can be helpful if you have line noise or if the ISY994/PLM are missing commands or status updates. Since you just created the program and it was looking at the status the 3am query might have triggered if the status changed and the ISY updated and triggered the program. I don't have any of the devices you are using and would never automate my garage (for the fact I don't want something able to randomly open (or close) my garage). So I can't help with a suggestion of how to alter the logic so that doesn't happen, but deleting the 3am query all is fine...as long as you don't have other communication issues. You should also check if you have the setting of "query at restart" selected (on Configuration tab) as that could potentially trigger if the ISY994 reboots randomly.

@kzboray make sure you open a support ticket for this. It’s the best way to notify of bugs/issues that need to be targeted for updates.

@JCizek I get what you're saying. I only offered it as an option for an app that is being developed and maintained. Glad that @James Peterson chimed in and hopefully able to update the app. I tried Agave during beta for iOS, but ended up sticking with Mobilinc at the time. It's all in what you've got setup that works for you now rather than setting up something new all over again. Good luck getting things updated and working again!

@dennisric another option to the method @DennisC links to is dependent on how good you are with networking. You could change the DHCP table of your new device to match the old and your ISY994 should connect if it is in a valid DHCP range. Once you’re back into the ISY994 please remove the static option and allow auto DHCP. You can then change the router back if you want/need to. This kind of issue is why the preferred method was a router DHCP reservation rather than the Static IP being set on the ISY994. Too many people forgot this was set and end up having to reset the device without a current backup. Your issue has nothing to do with “June 1st”. It’s your network and as you stated you had the ISY994 set with a static IP.

@JCizek since Agave isn't being developed (link below to most recent update from the developer) I doubt you'd get much help on this issue. My suggestion would be to try out UD Mobile. It's currently being developed by UDI and has support here on the forums and an extensive wiki section for setup and help.

@kewashi nice work! Just opened up a new discussion area for this: https://forum.universal-devices.com/forum/426-hubitat/ Good luck!