Geddy

I agree, but I'm sure 994 had its growing pains too. I was "late" to the party with the 994 just before they went into 5.x beta versions. I can recall a lot of issues during that development. Thankfully many take for granted how reliable systems were, but more so how "basic" they were (even though advanced for what they could/can do). With an almost limitless expansion in the Polisy/eisy era with Polyglot the variables to cause issues are just as limitless. While my eisy does seem to run just as stable as my trusty 994 many appear not to be as lucky. However, I'm not trying to run a bunch of different systems either. I know it's the desire of UDI to have a device as stable and reliable as the 994 (based on posts made elsewhere over time). It's just a lot harder to hit a moving target these days than it was in the past.

@thedishking what PG3x version are you running? I think random disconnects was something fixed recently. Current release area shows: PG3x 3.1.36 There's a beta post for PG3x 3.1.37 if you wanted to try that. Somewhere in the past I had a time where node servers would drop connection and not re-start. I have not had that problem recently so not sure if you're running an older version of PG3x or not. If you are at 3.1.36 or 3.1.37 make sure you fully power cycle the device (by pulling the plug). If still experiencing the issue please submit a support ticket so UDI can properly document your issues and attempt to fix for you, but also improve PG3x moving forward. https://www.universal-devices.com/my-tickets

Are you using the same computer for when you're home and when you're remote? This happens a lot to me when I'm trying to connect from a different computer to a remote device. The address is just gone. Best ,"simple", solution is to save the current addresses in the IoX Finder window by clicking "SAVE" on the bottom of that window. It will save it to a file like this "ISY-Finder.Thu 2023.07.27 05.37.20 PM.state" You can rename it to something like "Property A ISY Address.state" and/or "Property B ISY Address.state". Then load the appropriate file if it blanks out depending on your location. Saves you the effort of logging into the router to get the IP address each time you move locations. But...be sure you setup IP reservation with the routers at each location so the device is always at the same IP! Another solution is if you have portal subscriptions for both locations you can add the Portal URL then save the file (as above). You then have one file with both locations listed. Just log in using the Portal URL/Address (and credentials) each time. It's not location specific that way.

Do you have the Hue hub set with an IP reservation in the router? Do you have the IP referenced in the node server setup? Are you running this on Polisy or eisy? If on Polisy is this PG3 or have you migrated to PG3x (this is not a suggestion to go to PG3x if you haven't only a question...don't blindly go to PG3x without reading more about it - note the process removes PG2 from the Polisy) As I said, I'm running this node server. I'm on eisy so PG3x. I have the same udi happening, but not queuing. I put the log into debug and restarted the node server and did get this QUEUING line, but it went right though. (snip of my log below) 2023-07-27 00:00:08,551 MQTT udi_interface.interface INFO interface:_message: Successfully set 88010958c2dd0b :: GV5 to 24 UOM 100 2023-07-27 00:00:08,679 MQTT udi_interface.interface INFO interface:_message: Successfully set 88010958c2dd0b :: ST to 9.4488 UOM 51 2023-07-27 00:00:08,784 MQTT udi_interface.interface INFO interface:_message: Successfully set 88010954beaa0b :: GV5 to 64 UOM 100 2023-07-27 00:30:24,003 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message longPoll 2023-07-27 00:30:24,004 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING longPoll If your router has the hub at a static IP then the node server should find it. And it wouldn't work if it's not finding the hub at other times of the day so that's probably far fetched for troubleshooting, but worth checking. Maybe it's reloading something at midnight and can't find the hub so causes a drop. When it drops does it reconnect and stay running? How long before it reconnects? (on the UD Mobile notifications) At this point I would suggest you open a support ticket and supply a full log for the node server and possibly a PG3/PG3x log package with your ticket so it can be reviewed. https://www.universal-devices.com/my-tickets

Not sure. I don't have any Zigbee devices so haven't done any testing yet. As @xlurkr points out he knows of one that doesn't work. If you've got some try them out. If they don't work open a support ticket letting UDI know what brand/model/function doesn't work. Maybe they've got to fine-tune/target specific brands. As with Z-Wave it appears that Zigbee, while a standard, allows each manufacturer to handle things differently. It's got to be a crap shoot for UDI to figure out what does or doesn't work. This is where the user base trying what they've got and letting them know first hand really helps UDI and the rest of the userbase.

@pkauf it happens. But to get on the list of included devices be sure you put the device with the brand (and other info) into the request thread:

@pkauf As @lilyoyo1 pointed out these devices aren’t supported yet. The release post is found here: What you need to focus one is:

Could be Hue device (hub) issue. I run same node server and don’t have any disconnect issues. Perhaps the network connection to the Hue hub is going out or the device (Hue hub) is having other issues. Download the log file from the node server and see if you see anything happening at midnight. Not sure if the Hue app has any history or logs.

@saclarkdoc plug in network cable and reboot (might not be needed, but good idea). The eisy will disable wifi automatically. Note, since using a different network connection the IP address might change, and if you’ve setup DHCP reservation for the wifi MAC addresses you’ll need to alter it for the wired MAC addresses. But as @DennisC suggests…please read the wiki for the eisy User Guide. It has a lot of good information that helps.

@xlurkr What firmware are you running? And have you power cycled the Polisy since any recent firmware update? There were reports by others that Z-Wave quit working with recent Zigbee firmware release that I think is being worked on. I haven't noticed any other comments about the Zigbee portion not working now. You might want to open a support ticket if a simple power cycle doesn't fix it. Either use the multi-function button to reboot the Polisy or remove the power supply, wait 30-60 seconds and plug it back in. Wait several minutes before attempting to open admin console.

I always prefer and suggest wired. Less chance of something blocking/interfering with a wired signal Support ticket - https://www.universal-devices.com/my-tickets/ If you don't want to open a support ticket then use Google Site Search for this forum and enter the errors with quotes around them and you'll find several posts and options of solutions.

So what you’re saying is “works as written in the User Guide”? https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide

Yes, works exactly like it did for my ISY994. Cannot handle node server devices, but perfect for Insteon devices. However, I would suggest looking at setting up UD Mobile for full feature access with the eisy.

Looks like you started a new thread about this that has you going down a path to solution. Locking this one so you’re not getting help on the same issue in two places.

Yes, Moblinc (Pro) works with the eisy (at least as of current attempted use) but only for basic Insteon and Z-wave devices. It does not allow any node server or Zigbee devices to be found. You might want to begin looking at UD Mobile as an optional replacement. Information for that can be found here on the forums and in the UDI Wiki. Especially since Mobilinc hasn't been updated in ages.

@Spencer welcome to the forums! How are you connecting while remote? If using the ISY Portal then you don’t need a local setting. See the wiki for setup using ISY/UD Portal https://wiki.universal-devices.com/index.php?title=ISY_Portal_MobiLinc_Configuration The connection only uses one user/password. If you’re using a portal to access while remote you cannot use a local setup as well because that will use the admin/pass for local connection. Leaving the local server and ports blank will allow connection through the portal to work no matter where you are.

Probably because not many people use such programs these days. That wiki page hasn't been edited since 2018, and before that 2016 so I'm sure all the programs have changed a lot through the years. Glad you got it working though! Good luck finding the setting in the latest version of the firewall software. I'm sure it will move to a different spot next version. Gives them a reason to charge for "updated" software.

No, those are just clock entries. Not sure why they're happening, but they remain out of sync. That's been an issue some commented on when the eisy was released. The only traffic is are the events at 12:46:16 mentioning "Restore". I just opened my event viewer for a few minutes and get this: Wed 07/19/2023 02:06:24 PM : [ Time] 14:06:25 1(0) Wed 07/19/2023 02:06:54 PM : [ Time] 14:06:55 1(0) Wed 07/19/2023 02:07:24 PM : [ Time] 14:07:25 1(0) Wed 07/19/2023 02:07:54 PM : [ Time] 14:07:55 1(0) Wed 07/19/2023 02:08:23 PM : [ Time] 14:08:25 1(0) Wed 07/19/2023 02:08:53 PM : [ Time] 14:08:55 1(0) I don't have any motion sensors and had no other Insteon traffic during this time.

Unsure if there's a "simple" way to wipe out IoX so I'd suggest opening a support ticket and see if that's even best course of action. There might be other "tricks" they can suggest given the current state of your system. Since the front power button is the multi function button used to reset the function it's best just to use a finger to press it. Paper clip isn't needed. I'm not sure if there's another button to push that would need a paper clip to access (It's been a while since I examined the eisy case). I think this will be part of what support needs to help with. If you've got the new PLM connected to the eisy and Insteon support box checked (on configuration tab) and you've linked the devices again then you shouldn't have issues. Also make sure that your Firmware and UI match (Help -> About). More than likely your devices aren't linked properly. I think you made a comment earlier that devices were added from the restore attempt, but you weren't able to control them. That's because the eisy and PLM are probably unable to communicate because of broken link tables from a (probable) failed migration attempt.

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.

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.