gadgetfreak

Oh no. Then I am back to my original question - why are all my devices turning OFF once the ISY finishes a reboot?

I appreciate it. You are correct, it likely happened after a firmware upgrade, and I didn’t check all my programs and scenes after the upgrade - they were all working, so there wasn't a need. I don't remember when I upgraded the firmware. I agree, there are a lot of options to address this but at the end of the day, it seems that I have a bunch of rebuilding to do. Even if I were to upgrade to the next-gen system, I would want everything to be set up properly in ISY (if I were to do a migration). Oh well. Thanks for all the help.

Thanks. So I guess this is the last time I will ask before I begin the laborious process of re-setting EVERY device in EVERY scene - does anyone know why they reverted to Default and how to easily fix it? Thx in advance.

I figured plugging the ISY into a battery backup (with the PLM directly in the wall) may solve the issue as it can keep the ISY on until the generator kicks in. But, as I am seeing, having all the lights turn off on ISY reboot should not be happening. In the forums, it asks to check if any of my programs are set to run at startup. They are NOT. Below are my settings but I am not sure any of those make a difference.

A few days ago my power went out for around 2 minutes. Unfortunately I didn't have my ISY on a battery backup then (I do now). When the power was restored, all the switches went back to their previous state. But then, the ISY finished rebooting and everything turned off. Does anyone know why that happened? I found an option "Catch up schedules at restart" which was not checked. But I am not sure that is it. Because the ISY simply turned off everything after it rebooted. Does anyone have any other ideas? Thx.

I am also thinking that something may have just gotten messed up during a firmware upgrade but I don't know for sure. So, unless someone gives me another option, I may need to go through every single one of my scenes and every single one of the devices in the scene and determine if I wanted it on or off and then reconfigure it. If that is my only option, can someone please tell me if I should use the Insteon or the Command option? Thx.

But I don't think I have a controller for the scene. I just have a program that runs the scene based on a time of day.

I am running 5.3.4 on an ISY994i. Yes, I assume there were tons of differences in how scenes are handled when I upgraded I just don't understand what they mean now. Attached is a screenshot of part of my scene. I guess in a previous firmware version, each action would say On or Off so that I would know how I programmed each device in the scene. Now, it just says Default. It did that automatically as I never made any changes to the scene. So how do I know that I have this scene programmed to turn ON the attic fan and turn OFF the attic light when I run the scene (as an example)? And do I even need to be concerned about the link type? I have never even seen that before. Thanks.

I have been using scenes for years. Two scenes I use are Away1 and Away2. For simplicity, they include ALL of my devices. In Away1, half are programmed to go on and the other half go off. In Away2, the other half go on and the other half go off. This makes it look like I am living in the house when I am away. They are controlled by programs and a state variable. When the variable is set to Away=1, the programs can run. A program may be something like: "At 6 AM, 10 AM, 2 PM run Away1". Another program would be "At 8 AM, 12 PM, 4 PM run Away2". In all the past years, the scene would show the action for each device. On, off, 100%, 50%, etc. Now, I am all of a sudden seeing that ever action says "Default" and there is a new column called Link Type which also says default. I have searched the forums for explanations and my head is spinning. First of all, why did they change to this new setting to begin with? Everything was working fine. Secondly, how do I confirm what default means for each device? I am looking to make some changes but I don't know what to do. Thanks in advance.

Looks good. Thanks!!!

I am I was logging in through portal access (the second entry). I can confirm that the error does NOT appear when accessing the ISY on the LAN. I am able to save a new program. Good thought! So at least I have a workaround for now. Thank you. Please advise when you can get the portal access working. Thanks.

I get this error in UD Mobile when trying to add a new program:

On a different computer, I completely uninstalled and reinstalled Java. I am still getting that error :(. I also rebooted my ISY. Same error :(.

Thank you for your reply. To address your comments: 1) Yes. Firmware and UI match. 2) You could look at it a different way too. If I listed the exact version, the someone later on may think this issue is that they didn't update. I just wanted to be clear that I knew I was on the latest. But you are correct. I should have stated I am on 5.3.4, the Firmware and UI match and that, as of this posting, it was the latest available version. 3) Yes, I cleared "Installed applications...". I then clicked on the start.jnlp application I redownloaded from the UD wiki. 4) Sorry, I should have been more clear: "Nothing changed. Same error as before". Since I tried actually putting items in the new program call Keurig and got the error, I decided to just create the new proram now, press save and see what happens so I don't waste time again. Nothing I have done helped rectify this:

I launched the Admin Console in the usual manner and got a few device errors (which is not uncommon). I tried to create a new program but, when I clicked "Save Changes", I got an error "Bad Request" and it didn't save. I attempted to clear the Java Cache and relaunch the console but nothing. I am on the latest firmware. Does anyone have any suggestions? Thanks in advance.

Thank you both for your advice. I really appreciate it.

Guys, thank you SO MUCH for your fast replies. I recopied the URL from the my.isy.io portal and it worked. I am not sure what the old URL was that was appearing in my ISY finder originally - maybe an old ISY (?) but it is all working now. Again, I appreciate your fast responses.

I have a scene "Good Night" that turns off all of my lights downstairs (25 lights/devices) when I go upstairs to bed. It is also part of a timed program to all go off at midnight. When I have company sleeping in my guest room in the basement, I want to create a variable called "Sleeping Guests" and, when that variable is set to 1, I want the Good Night scene to do everything EXCEPT 2 of the lights for the hallways - meaning the "Good Night" scene will only control 23 lights/devices. Does anyone know of an easy way to do this without having to create a new scene and replacing it in the program at midnight? Thanks.

From the my.isy.io site, I installed the Admin Console. I got the ISY finder to pop up. When I double click the my.isy one, I first get an XML Parse Error. I press OK and then get an LIB error. I press OK again and then I just get a blank console. Can anyone please help? Thx.

Yes.

I configured this and it works properly for devices. But any scene that I add, Alexa acknowledges that it sent a command but it doesn't do anything. For example, I have one wall switch that is part of a scene with a button on 2 other keypadlincs. So, all 3 devices are in a scene. I add the scene to Echo config but it doesn't respond. It I only add the single wall switch device, it works. But then my keypadlincs are out of sync. Anyone have any ideas? Thx.

I asked. I will post the response if/when I get it. Thank you all.

Because the second ISY is a newer version and, if I have a spare one that I may need in the future, it is good to know that it will be available when needed.

OK all. I have an update for you. The first PLM arrived back around 10 days later and I plugged it into the second ISY I had (more on this in a bit). No communication error! I restored my configuration, had to rebuild my (only) four Alexa command, had to contact UD support to move my license (I likely did something wrong) and I am back up and running! I have now sent my second PLM for repair and will test it out when it gets back. Now I am still scared to plug the PLM into the first ISY - the one that was attached when each PLM originally broke. Michel from UD cannot believe that the ISY would "fry" the PLM and it was just a coincidence. So, if anyone has any suggestions on the best way to test this all when the second PLM comes back, let me know. I can't risk my system going down again - especially when it is working fine now.

@oskrypuch I am not sure if it matters, but your sad reaction to one of my posts seems to have given me a bad reputation on this forum (whatever that means). And, to all, I should be getting the repaired PLM later this week and will keep you all updated.