Bumbershoot

Well, whatever the cause, a good habit of making backups saved the day here. I've got a new PLM on the way, speaking of backups...

I had no idea that the PLM would fail in a way that make it lose links. I figured it would fail suddenly and completely due to power supply issues(which it eventually did). I didn't notice it, because most of the complex interactions with the system were by simple programs or through scenes activated by a KPL button press. Most everything seemed to work normally, right up the the PLM failure (and the KPL button presses even after). Anyway, I'll keep up the habit of backing up every time I make a change... Thanks again.

@IndyMike, I installed a backup from last winter and got a count of 560 links this time. That looks loads better. The system has been pretty stable for years, as we're comfortable with the way it operates. I doubt we'll see any functional difference, just ISY and related software being slightly out of date, and that's easy to update. Thanks for your help with this! EDIT: By the way, the program that originated this thread now works as intended!

That's good information. I just did a PLM count with a quiet house and the count was 160, which is better, but still seems pretty short, given the scenes and devices (two six button KPL's and one eight button). The eight button controls an "All ON" and "All OFF" scene, which has 37 devices included, so it's still low.

My mistake. I forgot to hit the "Count" button... I currently have 98 links, and I used to have many hundreds. I'll restore the ISY and PLM and see how it goes.

@IndyMike, if I'm understanding you correctly, I could restore an ISY backup that was working prior to the PLM dying, and after that's complete, perform a restore on the PLM? I have plenty of good backups, as I've been scrupulous about backing up whenever I've made a change. I've rebuilt a few scenes, and yes, it's painful to do that, and I've got probably 80 Insteon devices, and roughly 40 scenes. A restore sounds like a good solution, if I understand correctly. Right now, the PLM shows 0 links (after restarting both the PLM and the eISY).

No change in behavior after performing the PLM restore procedure to the letter. It looks like the switch sees the new PLM, and I can control it from the AC. I don't understand why the program doesn't work at all. In the screenshot below, the links are the same from both the ISY and switchlink dimmer, and the dimmer appears to see the new PLM.

I initially did power cycle both the eISY and the PLM. The device restore doesn't resolve the problem. I'll give both devices another power cycle. My old PLM was actually over 10 years old before it failed completely. The system has been stable for years, but the new PLM has way fewer links than I expected, so I'm thinking that the old PLM has been somehow dropping links for some time before it failed (I don't know if that's even possible).

eISY running ISY software 6.0.5_10. I did power cycle the eISY a couple of times, but not the PLM as well. I'll give it a try a little later today.

Background: I had to replace a PLM recently, and I've had to rebuild several scenes, and 'scnCooking was one of them. The two switchlink dimmers in the "If" stanza of this program are also in a scene that creates a three way for the track lights. I've restored these devices, factory reset them, updated the scenes several times and updated this program several times. For reasons I'm not understanding, this program will not work, as the "Fast Off" for either of these switchlink devices is not captured by the ISY software. I can run the "Then" stanza from the AC and the "scnCooking" is turned off correctly. A fast off does indeed turn off the track lights appropriately, but the program doesn't run. The status of the switchlinks will not update in the AC unless a query is run, then the status is updates. I'm a bit baffled by this. I'd appreciate any insights here. Thanks! CookingFastOff - [ID 0008][Parent 000A] If 'Devices / dirKitchen / sldTrackLightNorth' is switched Fast Off Or 'Devices / dirKitchen / sldTrackLightSouth' is switched Fast Off Then Set 'Scenes / scnCooking' Off Else - No Actions - (To add one, press 'Action')

Painless upgrade here. Had to clear the Java cache as described below to use the admin console. So far, all is well.

The host OS for eISY is not Linux but another UNIX variant called FreeBSD. This can be confirmed at the command line by running the command: uname -a Here's the output of 'uname -a' on my eISY: [admin@eisy ~]$ uname -a FreeBSD eisy 14.3-RELEASE-p5 FreeBSD 14.3-RELEASE-p5 #5 releng/14.3-n271450-382f54740ee4-dirty: Tue Oct 28 19:30:07 PDT 2025 root@bsdev143.isy.io:/usr/obj/usr/src/amd64.amd64/sys/eisy amd64 IIRC, the reason Linux was not chosen by UDI when they were first porting the ISY software to the Polisy device had to do with licensing restrictions/problems with software licensed under the GPL (Gnu Public License), which is the license that Linux is published under. The FreeBSD license, in contrast, is considered to be a more permissive license, which I believe UDI found better suited to their needs: https://docs.freebsd.org/en/articles/license-guide/

I'm on the latest/greatest from UDI, and I've never had the duplicate issue. I upgraded to get the new API, had a problem with the Ambience white bulbs not showing up as nodes, so I did a few install/uninstall cycles as the plugin was updated. Once the issue was fixed, I had to resave the programs that referenced the bulbs, and things have been good since. The plugin has worked both on the trial and standard (paid) versions (1.0.6 and 1.0.7). Having access to the Hue motion sensor is a nice benefit of the upgrade -- the response seems fast, pretty much on par with an Insteon motion sensor. Looking at my debug log for the plugin, I'm not seeing any errors.

FWIW, I upgraded to 1.0.7 and everything appears to be good. No duplicates.

No, it's okay for my purposes, as I won't use that value in any useful way. I have a leftover WeatherFlow Air unit about fifteen feet away from this sensor that I use for home automation purposes/reporting. The motion sensor looks to be interesting. With early testing, the response to motion appears to be really fast.