btreinders

If you are really on PG3x somehow then the username is now the same as the AC.

@johnnytYou wouldn't want to post that image somewhere would you?

UDI should at least post the SSD image somewhere with instructions on how to re-image it for people not afraid to do it. Not having water leak detection right now worries me. At least with Home Assistant I do have some functionality but yes the Polisy and eISY need to be able as a user to fix when they go down. This wasn't even my fault. I did an update packages and this is what I got.

My Polisy is still down hard and I am freaking out. So dependent on this automation now! Ticket opened, @Michel Kohanimresponded a few times on Friday and nothing since. I am assuming I need an image of the SSD installed which I am sure I can do if I just had one. Hopefully they respond today.

Huh, well I am not smart I should have made those energy values init values when they change! Doh!

I lost my monthly energy usage data stored in state variables when I did a restore so I guess I don't understand why you think that data is backed up.

But you lose any variable that you keep values in like energy usage for each month as an example.

Upgraded packages for PG3x and after about 5 minutes it said to reboot but I had walked away for a bit and when I came back the AC was grayed out but did at least let me try to reboot. Never came back even after power cycle. Guess I'll have to hard reset and restore it. Edit: @Michel KohanimWon't hard reset, LED just stays green no matter how long I hold the reset button. Guess it's time to open a ticket.

Should the stations update their status when the controller itself initiates watering? I seem to have to query a station to see that it has turned on, otherwise it never changes. Thank you

@Chris Jahnwas able to fix the issue for me. Here is what worked. Had to enable all and then disable all the ones that should have been. @Chris Jahnwrote Hi Brent, Can you please do this from ssh: sudo mv /var/isy/FILES/CONF/ENABLED.D2D ~ Restart IoX All your programs should be enabled at this point from ssh: ls -lt /var/isy/FILES/CONF/ENABLED.D2D Post result here @btreindersI had to sudo the ls command or it would say permission denied and it did not find the file. @Chris Jahnwrote Ok, now disable a few programs using the Admin Console and do the following (this time it should exist) sudo ls -lt /var/isy/FILES/CONF/ENABLED.D2D sudo cat /var/isy/FILES/CONF/ENABLED.D2D Restart IoX and see if programs are enabled/disabled as they were prior to restart. Hope this helps others get their reboot issue fixed.

Just upgraded against my better judgement and yup, all programs disable every reboot. Wish I had seen your post @jaydrosybefore I did it. I opened a ticket as well. One thing I noticed was there was a 5.7.1 and 5.7.2 available as selections for the current firmware in opening a ticket. That seems strange since there isn't anything in the forum about those later versions. Or is that just to future proof the ticket submission for a few versions?

@johnnytThat is what I used to think too but my old ISY Pro definitely ran more than 1000 programs, I'd say I had at least 1200 or more then. The only issue I ever noticed was you definitely had to change the java memory to 1024 or whatever it was or the AC would not run at all. Although now that I think about it I did have issues rebooting sometimes. I unchecked query at startup and that seemed to help. But yes, all better on the Polisy for sure.

@RRalstonDon't bother submitting a ticket. They disabled manual IP on purpose. I can give you the instructions they gave me on how to enable it manually but the disclosure was they would not support any issues I'd run into. I gave in and changed my router to supply addresses 99 - 255 instead of 150 - 255 like I had, just took some finagling of other devices first. Then I could have the router set a static IP. I always used 99 for the ISY and had many devices, programs, apps etc that would have had to change to a new IP.

@johnnytHuh, I just thought the upgrade caused it. I saw it happen during the 5.6.4 upgrade but it never happened again during reboots for me anyway. Good to know. I think my way of fixing works the best and is just one click and you are good again. Manually doing a find on all hash tags and then manually disabling them would take a long time in my case. Just have to remember to add any news ones to the program.

@johnnyt Yes. Very similar to @dbwarner5above except I don't disable them at startup automatically. I have a program called Stop Execution that is disabled by default. In that program I set a variable to a 0 and the main folders under My Programs that have disabled programs in them only execute if that variable is a 1. The if statement needs to be something that happens quite often so I used my pool pump watts variable to trigger it since it changes a quite often. I have that with some other things as well that change quite often. I also have a program called Begin that runs at startup and waits 15 minutes before setting that variable to a 1 because I used to have an issue where just rebooting the old ISY would cause all disabled to become enabled. That must have gotten fixed a while ago. I didn't use @dbwarner5's method of auto disabling them because I was trying to troubleshoot the issue for UD. I should just go ahead and disable them all at restart and then only send a notification if they did happen to be enabled. @dbwarner5Yes, my old ISY would get so bogged down the only way to fix it was a restore of the backup. Like you I have a lot of programs, over 1800 currently and over 200 disabled by default.

@dbwarner5Another way to solve this is to have one program that disables all programs that should be and one that enables all that should not be disabled. Or just one that does both. I know this is a pain when you create new ones as you need to add them to the correct one but once you have these two you can disable or enable all of them with one click. I also don't let any programs execute for 15 minutes following a reboot just to make sure the disabled programs don't get enabled by an upgrade. I have many that have to be disabled since they will just turn on and off a device continuously if they are enabled and completely overload the Polisy. Also, my program execution will stop if the programs become enabled while the Polisy is executing normally just to be sure. I also set up a notification if this happens at reboot or during normal execution. I had issues a few years ago with all programs becoming enabled randomly and it was a life saver when I upgraded to 5.7.4 because there were issues with that upgrade as well. Hope this helps anyone with issues.

Sorry, Ecobee

@Jimbo.Automates The server went down at 9:16 pm last night, or at least that is when I got the notification. May have happened before that because IoX does not know it went down in this case until it sets a temperature and then checks to see if it changed. PG3x looks fine when it happens. Restarting the node server fixes it. I will PM you the log package. Thank you!

Thank you! Really appreciate it!

Yes, I even had more than 1024 with the ISY994. 5.6.4 says it changed that to 2048.

I restarted IoX and I did use that video when I installed it.

5.6.4 IoX and 3.2.3 PG3x on a Polisy. I am in the mobile app after having it install the notification node server and hitting the plus to add a notification.

First error I got was I have over 1024 programs and subsequent tries results in the error in the screenshot. I am on the latest IoX and PG3x on a polisy. Thank you.

Upgrade wasn't straight forward, waited for the beeps and then waiting for the reboot to happen I saw MQTT errors scrolling in the tail of log so fast it could not keep up. I don't have the MQTT node server installed either. ISY was not responsive, could not open PG3x or AC. After an hour of this I rebooted from command line. Everything came up and everything seems ok.

I did submit a ticket but today I tried a few more times after failing at least 5 times and now they are working. If they give any insight I will definitely post it here though.