Geddy

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.

If you're just wanting to set the variable to a number remove the & part and just leave it = "number" But you're trying to add multiple lights to a variable. Other lights would then use +=. Are you running any programs off the variable? Remember State Variables can send events causing other programs to run. Integer Variables do not trigger events. https://wiki.universal-devices.com/ISY_Users:V5:Program_Variables Another note is if any lights are on a dimmer maybe change the IF to "Status NOT off". This way the light could be at a % of brightness, but not "ON" and would increase the value since it wasn't "off".

Going from memory I think the risk of bricking a Polisy was limited mostly to 1st gen or initial build systems. Having bought it just before the eisy was announced means it more than likely doesn't have the same risk as devices that were part of what UD called the "geek batch". I guess the device you're running at home falls in that category so that's why you think it might "brick" if you update. However, since UD has a fix for the issue you should submit a ticket for both devices and get them brought up to date so you don't worry about it going forward. Again, just going from memory of posts about the brick risking issue (even then it was a very, very small number impacted) according to posts/comments.

No, this should show disabled and is no longer a setting that means anything (IMO). I think it was something older ISY devices used. No, if you’re trying to update firmware make sure you meet the requirements for the version you are going to. Follow the install directions in the link I provided earlier. DO NOT UNZIP THE FILE YOU DOWNLOAD! Since you are on 4.9 you should make a text backup of your programs (right click the “my programs” folder and the last option should be “copy folder to clipboard”. Paste that into a text editor (NOT a word processing app) - for Windows I suggest notepad. Save that file for reference in case any programs use “adjust scene” you will need to adjust those after the update. There were significant changes from 4.x to 5.x in scene setup to integrate z-wave so that usually breaks some programs that have “adjust scene” in it. Check the programs tab after updating and fix programs before doing anything else. If I recall looking at the summary tab might help too showing programs that might have issues. You might want to search (I’d suggest google site search) the forums for issues when updating from 4.x to 5.x related to programs being broken.

I don't think anything "prompts" you to make a new recipient. You must click on "ADD" at the bottom of the screen. Once you click "Add" it will add a line in the "Group" box below the SMTP settings area. There you must type the "NAME" then click on the line to the right (under "Recipients". It will pop up this box: Once you have that box you click on "Add" and it should give you a window in that box to type an email address. (Box above for examples only. I used TAB after typing an example address in then click "Add" again to get another line to add another address.) In the ISY994 era there were issues with the UD Default Mail server. That was later fixed in firmware updates. If you don't use Z-wave or have Z-wave 500 series board then you should be on firmware 5.3.4 for ISY994. If you're using Z-wave 300 series then you should be on 5.0.16C (but I'm not 100% certain this was "fixed" to be able to use the default server). There were updates in the 5.x firmware to allow use of the UD Default server again. However, because it is "generic" and could be sending lots of email alerts there are reports of the default server being filtered at times. That is why it's suggested to use a 3rd party email system. Most often Gmail is the easiest method. If you followed the directions in the wiki to setup the Gmail user/password method it should work without fail. Not sure why/how Google locked your account, but wouldn't bother appealing it...unless it's your personal account, and that would be very crucial to get access back. But I would suggest setting up an ISY only account, but make sure you log into it within 4-6 months to keep it "active". Otherwise, Google will lock dormant/inactive accoutns. https://wiki.universal-devices.com/ISY994:Configure_Mail_Server_Settings#Configuring_gmail_Account That might mean you have bad credentials or are trying to access the server too much. But, seems like you got the default to work again. Just seems like you didn't have the process to add Recipients correct. I have used Gmail to send alerts since day 1 of my using ISY (then ISY994). I've not had any issues with sending/receiving alerts through email using a Gmail account setup specifically for ISY alerts. Used it with ISY994, Polisy, and eisy. Works perfectly if you set it up as outlined in the wiki. I agree, that many might have given up, and most that use Polisy or eisy have the great ability to get the Notification plugin and user UD Mobile or other apps for push alerts.

Evidence that reliance on cloud services means things in the cloud could change and break stuff even without doing anything. Probably the same issue @carteriii, but not certain. Just seems that if your notifications are working each time and the setup with Alexa isn't then perhaps something at the Alexa level has broken the routine process. I know some have posted that if you disable the ISY skill it's possible a routine becomes broken (i.e. it drops the ISY devices) and therefore has to be rebuilt. But if you and OP have rebuilt the routines then does seem to point to an Alexa (cloud) issue of not doing what once worked in the past. Sadly, OP is still using ISY994 so doesn't have the notification plugin ability. They do have a Polisy, but it's not setup. That's a whole different set of issues depending on how old that device is. Lots of updates to apply to that thing.

@carteriii this issue is an issue with the IoX Launcher shortcut from last summer. First, what version of Java are you on? What computer OS are you using? (Win 10/11, macOS, other) Confirm Java is up to date (As of today from java.com: Version 8 Update 401) Don't run any other "fancy" versions or higher version numbers. Admin Console is designed to run on standard Java Runtime Environment (JRE) downloaded directly from java.com. Please clear your Java Cache (be sure to check all 3 boxes in this process), Delete any old start.jnlp and/or admin.jnlp files on your system, Download a new file from the UD Site (link to the start.jnlp), Run newly downloaded file This "not found" issue should be resolved. Hopefully you've opened a support ticket as @bmercier mentioned. Even though ISY994 is no longer supported he was offering to help review for this specific issue. Otherwise, you can see what the errors are from this section of the wiki: https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages Looking at some of the error messages it seems that it could be a corrupt SD card on the ISY994. Also, do you know if you have any programs stuck in a loop or could be stuck in a loop? That might be causing the "Queue(s) Full, message ignored" message. Typically error "-170001" is considered an information code, but if there's an error following it that's key. (Couple of posts related to this error: Link 1 & Link 2 - using Google Site Search to find archived posts like these) Have you changed anything locally on your network recently? New router, new extender(s), new connected devices? Is the ISY994 set for automatic DHCP (IP address)? In the past it was common for people to set the static IP at the device level, but more recently it's been strongly encouraged to rather handle IP reservations at the router/gateway level and allow the device to auto connect to DHCP. Since one of your errors is "System -140000 my.isy.io" I wonder if you're having network interruptions. Also, please make sure that your Portal License is still active! If you did open a support ticket and got this issue resolved please post the fix so that it might help others should they have this issue and search the forums for help.

Clear your Java cache (checking all 3 boxes) then get a new start.jnlp from the UD site (clicking “My ISY” in the upper right of the site. Run that for a new IoX Launcher icon on your desktop. Then the “local” option will be updated. as with the ISY994 anytime the IoX firmware is updated you should perform this process if using the “local” option. Otherwise, as @paulbates suggests the “cloud” option should match, but if you have an issue just clear the Java cache and reload start.jnlp and you should be good. I always suggest getting a new version of the start.jnlp file from the UD site as they do sometimes make backend adjustments….rare, but has been known to happen.

Is your eisy wired to router or using WiFi? I guess I’ve been lucky I never had to schedule reboots of my routers. Seems like network issues if you’re having to reboot a “name brand” router often. I’d look at resolving those issues before saying it’s an eisy issue. But that’s just me…why live with scheduling rebooting a router rather than fixing the issue (ie buying a different router!).