Geddy

No need to change PLM again. I also have the serial and moved it from my ISY994 to eisy without issue using the serial to USB converter cord available at the time the eisy came out. It appears UDI is offering a different cable now that doesn't require going from the serial to USB cables so it might be shorter and one less thing to worry about in the communication aspect. It does concern me that you just replaced the PLM on the ISY994 and you think either it or the ISY are flaky. Might be worth making sure you have a solid backup from the ISY994 before migrating to the eisy to avoid bringing over any funky issues. I will make sure to suggest to you that you make a "hard copy" of all your programs currently on the ISY994. On the Program tab right click on the root folder (usually "My Programs") and use the last menu item of "Copy to Clipboard". Then paste into a text app (for Windows I suggest Notepad). NOT into a word processing app/document - you don't want to risk auto formatting changing things. Save this file somewhere so you can reference the programs after your migration. If you have Z-Wave or are not on 5.x firmware on the ISY994 there might be some adjustments needed for the programs and this file will help a lot of steps with correcting any program issues that might occur.

@NinjaNun welcome to the Universal Devices forums. The hub here would be a Universal Devices hub running ISY (either an ISY994, Polisy, or eisy). Do you have any of those hubs in the mix of what you're attempting to fix?

When did you update to PG3x? And I know you said you did a power cycle recently, but there was a post from @bmercier that the 503 error was from UDX not running. The best way to trigger that is a full power cycle. If you recently updated to PG3x it's quite possible something was stuck in the update when power got pulled last time. Try running the update packages process in Admin Console. (I know this isn't anything to do with PG3->PG3x, but can "cleanup" other functions) If you have UD Mobile connected to that device you should get alerts for it going offline and coming back online and probably even time to reboot. Wait about 2-3 minutes after that reboot notification then use the multi function button to shutdown (three presses). I forget if Polisy shows lights when it's shutdown or not. Then pull the power supply, wait 30-60 seconds and power it back on. Allow several minutes for the device to start up and settle. Should hear some beeps, but also monitor the front lights if you have it in an area you can see the front of the device. If after this still cannot access it I would suggest opening a support ticket. https://www.universal-devices.com/my-tickets

@glacier991 this is not a "general" Home Assistant area. For device assistance you should see if Home Assistance has any support forums. This forum area is mostly for the Home Assistant integration with UD products. Since UD has made a way for HA to be installed on the eisy issues related to those installs are also fine to post in here. But you seem to be having different hardware issues that are not usually supported here. I'm sure the vast user group around here might be able to offer some insight, but you might be better off with HA support options.

My suggestion - don't run anything! Windows has gotten a little better (IMO) with their own security defender or whatever they call it and their firewall has been improved greatly. I haven't run any 3rd party virus software since Win10 came out. I also try to make sure not to visit unhealthy sites and don't randomly click on email links...so that might help some. If all you want/need is anti-virus I like ESET (not a big drain on resources). I run that on my son's computer and it doesn't impact anything he does (lots of gaming). Since you're still getting some java errors and other device issues after setting up the eisy I still think it's either computer system or network related issues you're experiencing. Those are hard to diagnose through forum posts so do think @paulbates suggestion to open a ticket would be beneficial to your issue(s). As for the PG3x access make sure you're using the same user/pass as you use to access admin console. Those the same and only changed via the admin console side. Your picture was very low quality so couldn't tell the exact error. It appears to be a 503 error. This usually meant UDX is not running. If there aren't any updates pending or installing then a full power cycle of the device might be needed. Have you updated the eisy to the current IoX and PG3x? Current release versions can be found here: https://forum.universal-devices.com/forum/339-current-release-announcements/ (click the "Follow" link in the top right of that page to get alerts when new releases are announced.) Glad it went mostly okay. I expect a support ticket will help you greatly. Please post back what ends up helping/resolving the situation.

What happens if you move the time constraint up into the ( ) of the first and statement? Long shot, but first adjustment I might suggest since you say it works fine without the time constraint. Also, is your "switchB" and "switchC" using a "status" or "switched" qualifier? 1st edit: And ( switchB is on <- Is this using "Status"? or switchC is on <- Is this using "Status"? And From 3:00:00 AM To 1:00:00 PM (same day) ) I just made a test program and it worked either way. Post your actual program. You might be using switched where status would be correct. Test and-time - If 'Lamp' Status is not Off And ( 'Office' Status is On Or 'Bed1Lamp' Status is not Off ) And From 6:30:00PM To 7:30:00PM (same day) Then Set 'Office Fan' On Else - No Actions - (To add one, press 'Action') Mine triggers true if I turn "Lamp" on - I was testing with admin console and Alexa so used "status" rather than "switched" (meaning physically activated). If you're "switching on" "switchA 1" with an app, voice command, or another program then you have to use the status. Only if you are manually operating "switchA 1" will it work for "switched open". Since you might be testing outside of your time constraint you should adjust the end time to a time later than your current time so you can run the IF to get it to test currently and not wait until tomorrow.

Going from memory because I installed this ages ago and haven't had to change anything since so hopefully it's still simple. When you installed the Hue plugin (formerly node server) press the button on top of the hub and the plugin should find it and pair to it. I think you might have to restart the plugin. I don't remember if there was a "find hub" button to click when the plugin is first installed/restarted and no hub found. However, try just restarting the plugin and then pressing the button on the hub within about 60 seconds and the hub should be found. You might want to put the logging into debug mode and watch the log run as it pairs with the hub. Once it's connected I would suggest restarting the plugin again and it should pull in all the devices. Please make sure you set up an IP reservation in your router for the Hue Hub! From the notes on the readme for this plugin: This was an issue a lot had in the past, and most will stumble into this if/when they replace routers and the DHCP table changes. Additionally, if you happen to have multiple hubs you have to use a strange way to add the IP addresses: In the configuration area add a custom parameter: bridges Then the IP should be in this format: ["10.0.1.1","10.0.2.1"] Be sure you include the brackets [ ] and the quotes around the IP addresses of the bridges! Lastly, make sure you have admin console closed (not running) while you add plugins. The only way nodes are added to the admin console is at load so if it's open and you add plugins and get new nodes showing in Polyglot dashboard they won't appear in admin console until it is reloaded. Same for UD Mobile, you will need to synchronize the app once things are altered/setup. Hope this helps.

No, but we need a lot more information to help further. I don't completely know how to review/support link tables so others might have other ideas about why they're looking this way. To help deeper please let us know the following: What type of device is turning on? How old is the device? (are you able to see the address/date tag/sticker on the device?) What IoX Firmware and UI are you using? (Admin Console: Help -> About) Make sure they MATCH Perform a "Find/Replace" on the Programs list Right click on "My Programs" folder (root of the program tree) "Find/Replace" Search for the device that is turning on (don't replace it with anything, but just find what programs it is referenced in. Then see if those programs have run unexpectedly) Check your program summary tab to see if a program has recently run to turn the device on How did you setup/migrate to the eisy? Did you come from ISY994 or Polisy? Did you use the same PLM you had before? If you changed PLM did you follow the replace PLM process? It might be as simple as factory resetting the device then performing a restore from the IoX admin console.

Make sure if you're setting these parameters in admin console to click the "button" to the left of the on level and ramp rate. You should see it change "writing" in the device tree momentarily and maybe a "system busy" box pop up and go away. Having to click the button has been a quirk in the admin console since 5.x was introduced. It's not intuitive as many will use the "Write Changes" button at the bottom of the screen. Edit: I just tried with UD Mobile (I had AC open) - had same issue you reported that if I changed on% and ramp rate it did not seem to change. I closed admin console and ran a sync on UD Mobile and the on/off ramped correctly and to the on%. I then reset the on% to 100 and ramp rate to .2 seconds and it correctly updated and operated. I then changed back to lower on% and slower ramp and it worked. Do you have admin console open when you're making the changes on the app? Have you run sync on the UD Mobile app recently? I only ran sync once. Again, my tests were on an individual dimming lamp link device, not a scene. Scenes are a little different monster than controlling the device directly. Can you post a screen shot of the KPL scene? Should show "Device | Action | Status" information. Post of the root of the scene and any controllers of the scene. I'm not very strong in diagnosing scene issues, but know many others here are and maybe they can help at the scene level.

@Nishal & @737simguy not a direct update from @Michel Kohanim, but posted in another thread that they're "very very close".

YES! When you use the Portal URL and connect with the "cloud" option you have to use the my.isy.io portal credentials.

@woodchip you trust Norton a lot more than I do to be a continuous user for so long. I guess I was jaded "back in the day" running it on systems with marginal hardware, but swore it always bogged machines down. To this day my boss runs it on his personal computers and whenever I have to try to support his PCs I have to fight Norton too much to "help quickly". I'll take your word that you've got it setup right so I don't think uninstalling would be ideal. However, as with many things in life...what always "worked well in the past" could actually be causing issues now. Just a variable I would make sure is "disabled" during the backup/restore process (for either ISY994 and eisy). Some around here claim 100s of devices and 500+ programs. That's "tons and tons" to most. I'd say you're probably on the tons side in that it would take longer than most would like to start fresh. Programming is the hardest part, but having that hard copy makes things 1000x more efficient if you do have to start over. At least you'd have support directly with UD at that point. I think the first suggestion I would have is to make sure the eisy is updated to the current firmware and current PG3 versions before trying to restore ISY994 and Z-Wave devices. Are you getting the ZMatter dongle also? Read...read...and maybe make notes on the migration process. If you have network resources make sure you see the note about saving each once after the migration! And since you have X10, Insteon and Z-Wave devices the odds are probably good that some programs will be messed up because of device addresses. This is where that hard copy of programs will come in very handy. I don't have any personal experience with x10 or migrating Z-wave from ISY994, but recall comments about the Z-wave being a stumbling block going from zw to zy or something like that. 👍

Probably best to download a log package the next time this happens and open a support ticket with UD. Attach the log package for them to review. https://www.universal-devices.com/my-tickets Also, since you think it has something to do with the Blue Iris plugin go into the details of that plugin, change the log type to "debug" and then restart the plugin. Allow the plugin to begin and stabilize (maybe 5 minutes) then download that log package and include it with your ticket. There might be something happening with that plugin on startup that can help UD find something causing the issue. I've never seen this issue. But again I don't leave the dashboard logged in/open for long periods of time either.

Yes. That's fine and will get all other updates as they're all built into the newest release. Just configuration. Would need to download the 5.3.0 firmware and "update" with that manually to have the 5.3.0 system back in place. very unlikely! Since you're 100% z-wave be sure that you run a z-wave backup then backup the ISY process to get all the z-wave info along with the ISY settings. Since I'm still new with z-wave I always forget that step. Thankfully I only have 3 z-wave devices and haven't had to rely on restoring a backup since getting them, but it never fails as soon as I hit "backup IoX" I think "rats...didn't make a z-wave backup first!". Good luck! 2 more tips: DO NOT UNZIP/DECOMPRESS the .zip file you download. That's used in .zip format by the ISY994 to update firmware. You're on Windows so doesn't happen automatically (like with some macOS settings). Just as a precaution I always suggest anybody updating firmware to make a "hard copy" of your program. This is a "worst case" CYA process just in case something goes sideways. Was mostly an issue going from 4.x to 5.x, but has been known to bite some in the Polisy/eisy updates - mostly with programs going from "disabled" to "enabled". This process includes all those details and makes it simple to recreate programs if you end up with lost devices or other problems. Again...just "CYA". Open Admin Console Click Programs Tab Right click on the root folder (usually "My Programs") Select last option "Copy folder to Clipboard" Paste into a text editor (Windows = notepad) - NOT a word processing app (Word)

"Nothing" (in reality), but you might want to inset a "wait" for a couple of seconds between a couple of lines. This many triggers (all at once) might make too much Insteon traffic and something is being missed (thus the reason for random lines missing). Or could put a repeat 1 or 2 times, but it would still fire all the lines at once. If you have other "sunrise" programs that is even more traffic that is being triggered. You might want to stagger off of sunset a couple of seconds.

FYI - This has been fixed - pics & files can again be uploaded/added to messages. Thanks @Michel Kohanim!

@Dishboy007 no assumptions made of "if it's safe to use". You should consult Insteon since this is in an attic space and probably exposed to extreme temperatures (assuming it's not climate controlled area). It's probably been exposed to operating temps outside of normal range and could have caused the LED to fail or could have other issues. I'd only trust an electrician that has inspected the outlet to give the approval (or not) of it if was "safe to use".

You're only looking at the change notes for 5.3.4. If you look at 5.3.3 you'd see this: Since you're already on 5.3.0 then you must be running a series 500 z-wave module on the ISY994. The update to 5.3.4 is very easy and minimal involvement (going from memory). This "warning" is/was in all 5.x builds as it did have a major impact on users coming from 4.x. It could have been better worded and maybe included the fact that this mostly applied if coming from old (4.x) firmware. All updates from 5.3.0 to 5.3.4 were mostly superficial with tweaks and fixes along the way. I believe 5.3.0 was the "official" z-wave release then there were tweaks made up to 5.3.4 for the ISY994. You can find the prior releases here: https://forum.universal-devices.com/forum/39-previous-releases/ Reading the release notes for 5.3.1, 5.3.2, 5.3.3, and 5.3.4 might paint a better idea of what was fixed along the way. Not just what was fixed from 5.3.3 to 5.3.4 (as you pointed out). But, it appears that it is working for you correctly. So think this issue is resolved. Just wanted to add to what @DennisC suggested about updating. Sometimes reading about all the releases is better than just looking at the last.

Seems to be a board/hosting issue. UDI has been made aware. Not sure of a fix, but hope it can be fixed soon. Pictures/screen shots are worth 1k words! Seems like the SD card might have been corrupt for a while and not allowing backups to complete successfully. The question I have now is how are you accessing admin console? You're on Windows so what version Java do you have? Make sure you're running "Version 8 Update 401" (downloaded from java.com). Are you using the IoX Launcher to access? When you have the option for "LAN" or "Cloud" which option are you selecting? Try always using LAN (when local). I know you've not had problems "in the past", but they could have been causing issues and you just didn't realize it (causing the corrupt backups for instance?). Make sure they programs are completely shut down/stopped. Not just "disabled". If it's possible to completely stop them. There are a lot of reports of these issues (in the past). If you use Google Site Search (type in the search bar: site: https://forum.universal-devices.com/) and the type your errors you'll see a lot of OLD posts and some kind of recent posts. The really old ones aren't as helpful since it used the old Browser Java Plug-in to access the Admin Console. Since 2018 the IoX Launcher has been the suggested method to access the admin console. Some of the more recent issues have been indicating a corrupt SD card or Firewall and network connection issues. Since this is on an ISY994 there's no current support available. Since you've wiped the existing SD card and unsure if you have a "good" backup it might be easier just to setup the eisy and restart everything from scratch. Unless you had tons and tons of devices, scenes, and programs. The thought is you might not be able to get a good restore on the ISY994 so it isn't worth the time and money to try to recover there rather than just starting fresh with the eisy. Hopefully, if you do get a new microSD card, and can get a valid backup to restore you can then move forward. Good luck! Please post back how it goes.

Try a Google Site Search for old posts. Once they are archived they don’t show up in the forum search results. Just type this in ther search bar (adding your search term to the end): site: https://forum.universal-devices.com Might find old posts about it if they were public.

Seems more like a question for Insteon directly. You should post on their forums or see if their support system can help figure out what's happening. https://www.insteon.com/support In IoX make sure you set the backlight to on to 100%. Note that when you click on it in admin console "Backlight" will show 0%, but it's probably set at 100% already. Just set it to 100% and click "Backlight" (to the left" and that should set that setting. It's a UI "bug" that has been there since 5.x came out and setting the % is not as intuitive as it might be and isn't set by using "Write Changes" button on the bottom of the screen.

Are you running firewall or anti-virus software (other than default Windows security)? Is your network a complicated setup (i.e. v-lans)? Or are you using Mesh type router(s)? (if so try hard wire connection if possible) If no to the above UNPLUG ISY994 remove the micro SD card and reseat it. If that doesn't work, try again and GENTLY rub a SOFT eraser over the contacts. Your SD card could be corrupt or could just be misaligned if you have moved the ISY994 recently. Please review the wiki if you go so far as having to replace the microSD card. https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Replacing/Formatting_an_SD_Card Before you go too far with replacing the SD card also try a different power supply. The specs can be found in the wiki as well.

@stevehoyt not sure if it would help, but have you tried the "Switch Portal Profile" in the PG3 web interface? System -> Switch Portal Profile It will ask you to log into the portal account. Perhaps something got messed up along the way and just need to make sure it's logged into the correct portal account.

Maybe the SDK found here can help. Otherwise, check the wiki (do a search for rest).

That kind of programming is beyond my need so my use/ability with &= has been limited. Just saw it was "binary". No other examples are given (that I saw with brief search) for that. Just keep plugging along and see if you can make something work. Maybe more advanced program gurus can chime in to help.