waffles

No, when I set it up, I did not. However, does this matter? I since rebooted/restarted the IoX several dozen times over the past year or so when introduced my 49 hrs version. I'd expect that after each IoX restart, it would start 'fresh', based on which programs are enabled/disabled. Am I misunderstanding this?

Hmm, but isn't it disabled, i.e. should not run at all??

Just noticed something: All 'Leak Sensor- 25hrs' programs show as not enabled (as they should, because I turned them off to not interfere with their 49hrs versions). However the 2a programs show entries under Last Run Time and Last Finish Time. How can this be explained?

I now added this program. I believe it's not quite the same approach as yours, but shouldn't that do the same thing? (It seemed faster to program):

Thanks @DennisC; could you elaborate a bit more how you do this? Also, what would be the benefit for doing this? (Not challenging, just trying to learn here.)

Appreciate your insights @tmorse305 and @oberkc! With 'manual restart' I meant clicking here: I have maybe some 100 Insteon devices on the network, pretty much all of the switches, dimmers, etc. are dualband. All that in a fairly typical single family home - nothing too crazy. Overall the system is pretty robust, I get the occasional miscommunication, that I am somewhat familiar with from the home we moved from a few years ago that had a similar setup. Let me post all programs of this leak sensor setup to provide a complete picture (It's basically an adopted version of this big thread: I originally had started out without IF for the wet sensor, but added it later based on this post: Here it goes: Control 1, 2a,2b, and 3 is set up for each of the 10 sensors These are the 'common' programs: Last but not least this one is for me to manually reset the variables, if I ever have to do maintenance: I have a duplicate set up for the original 25 hrs, but it should be completely disabled: I have a few other programs, but nothing (that I am aware of) that should interact with, let alone stop the sensor programs. Do you guys see anything that could cause this stopping problems?

@tmorse305I initially had the wait times in all of my 2a and 2b programs set to 25 hrs, but then changed a while ago to 49 hrs. here are 1 and 2b: Do you see anything 'off'?

(Note: I changed the wait time in the code from originally 25hrs to 29 hrs, as I would miss the heartbeats too often.) I have a bunch of leak sensors that I set up with help of one the posts in this forum. After a IoX restart the 'monitor' programs seem to launch and run properly (green), but most if not all of them stop (turn red) after a day or so. Usually another manual restart is enough to keep them running for good. What am I doing wrong here? This is after a restart: This is what it often looks like after a day or so: (Note: I changed the wait time in the code from originally 25hrs to 29 hrs, as I would miss the heartbeats too often.)

Awesome, @brians, thanks for catching this. My AC and the Portal are back up again!

Then ran: "sudo pkg upgrade -f mongo-c-driver" Thank you @smileyw; I found the file and changed it via VI and ran the command. I did a reboot afterwards, but I still cannot connect to the AC and the UDI Portal shows my Polisy as offline. I am not quite sure how to understand the system message from the upgrade attempt. Did it actually work?

Could you please elaborate how to do this? (I am still dead in the water with my ISY)

I tried updating my Polisy from 5.5.4 to 5.5.5 via the Admin Console. I heard a bunch of beeps (not sure if 4, since the device is in a different room) shortly after. Now I can no longer access the AC, the ISY Portal shows it as not connected and PG does not seem to be running. I can still SSH in and also PG2 is up and running. I tried power cycling it a few times and tried what had helped me in the past: sudo pkg install -r udi pkg sudo /usr/local/etc/udx.d/static/udxops.sh upgrade.polisy as well as: sudo service udx restart But no luck thus far. I usually launch the AC uncached/directly, but now I am getting this error: The IoX Finder cannot find the device either. Any thoughts on how to get this fixed?

Prefect! Thanks @brians

I have a bunch of programs that I would need to enable or disable. Rather than setting the check mark one by one, I was wondering if there was some sort of mass change option for that.

Just to offer another data point: I just upgraded via AC from v.5.5.0 to v.5.5.2. It only took a few minutes until my Polisy Pro was back online. All seem to have gone well. Note: I have a fairly simple setup with Insteon devices only, no Zwave or alike.

Thanks guys! @bmercier, @Geddy It would be nice to be able to make a full back up of the Portal settings. The current export function to cvs does not cover all the necessary commands and/or settings. Even nicer would be to be able to restore such a backup at a later stage. (This would only leave the somewhat tedious clean-up/rebuild part in Alexa, e.g. rebuilding Groups, but that's a different department/company :-))

FYI: a complete redo of the commands after deleting them from Alexa and the UDI Portal first seems to have worked.

Hello Neighbor Thanks for your help! Michel also replied in the meantime. He had me do via SSH: sudo pkg install -r udi pkg sudo /usr/local/etc/udx.d/static/udxops.sh upgrade.polisy I added a couple of Reboot and Upgrade Package via the AC, as the unit was still not connecting. That seemed to be enough to bring it fully back online. So I am up and running again, now with v.5.5.0

I tried the 'update package' again and now I have lost Portal access and the Polisy's middle and right LEDs are blinking fast. I can still connect via SSH and and the AC comes up, but throws errors. F/W still shows as 5.4.5. I opened a ticket yesterday and awaiting a response. In the meantime, is there anything I can try myself to get at least to a working state again? TIA!

Looks like you got yours to upgrade. How did you do it?

My Polisy only shows a solid LED on the left. Ticket created. Thanks!

As of a few weeks ago, Alexa is complaining that a "Device is unresponsive" after triggering a voice command for an Insteon device/scene on my ISX (Polisy). All commands are typically executed correctly and all seems to be working fine. I disabled/re-enabled the skill, but this did not help. Any idea what's going on? TIA!

My Polisy is Insteon only. Should this upgrade still work for it? I have done the "Launch the Admin Console, go to the Configuration tab, click on Update Packages. Warning, this might take a while depending on how current your OS is.." twice already with wait times of some 15 min in between, but no beeps or changes in the version number.

Thanks @Geddy; I had retried the refreshs but to no avail. Luckily I had an old csv file, even though a bit (out)dated. I had opened a ticket with UDI in parallel and there the conclusion is that it's really not possible that something wiped it out on the back end. I have no idea what caused it, so I am thinking it *must* have been a glitch in the Matrix . It's not the end of the world and I have most of it up and running again.

Thanks @MrBill; to me it seems more of an issue with the Portal/UDI side, as all my entries were gone. I have since started recreating everything. It's still work in progress; currently it looks like this: