Long time user with lots of Insteon equipment and what I thought was pretty reasonable knowledge of the Insteon protocol and isy software but I'm running into some issues so thought I'd come back to the forums and see if anyone has some thoughts. I've moved mostly to home assistant but still love the eisy for insteon management and use it primarily for that so don't spend as much time in the interface as I used to.

I feel like I may be running into some bugs in the eisy and would like to get a sense if other people are having these issues or it's just me.

I had a power outage and it seemed to have fried my PLM (eisy is on UPS and stayed up), I replaced it with a spare and used the eisy to do the swap. Most of my house seemed to get updated fine with the new PLM address but for some reason most KPLs didn't and I've been having to factory reset them and restore them.

This brings me to my first odd issue, some of my KPLs have had their database record in the eisy zeroed out. Logs complain about not being able to read the file and if I look in /var/isy/FILES/CONF/ on the eisy I see the file (XXXXXX.REC) there but of zero size. This happened once before and I removed those devices and readded them to fix it. This time it was three different KPLs. Both times it only happened to KPLs.

My next odd issue is these are all 6 button KPLs tied to fanlincs, so the 4 middle buttons have mutually exclusive buttons for fan speed. I've done it the exact same way with a scene for each speed for 15+ years. When I readd these KPLs and set them up from scratch the buttons don't work correctly anymore. When you hit Fan Low instead of that light coming on the other three do. Fan High turns them all on. I've double checked my scenes and they look the same as other ones that are working. I'm wondering if some how the eisy isn't setting up the insteon scenes properly any more.

Lastly, everything is soooo sloooow and it didn't used to be that way on the old 994i. Things should be so much faster on the new hardware. I don't even know what it's doing I just stare at the "System Busy" progress bar which very slowly goes to 100% then happily starts over again and again. I pull up the event viewer and there is nothing going over the wire. I look at the OS and it's using barely any CPU. I had to do a switch swap and it took over 30 minutes.

Anyway I'd love any thoughts or suggestions on how to stop the database from becoming corrupt or fixing my KPL scenes.

Edited Thursday at 09:14 PM3 days by apnar

When you swapped out the PLM did you follow the atached procedure ?

Replace PLM Procedure (EISY or POLISY).pdf

20 minutes ago, Techman said:

When you swapped out the PLM did you follow the atached procedure ?

Replace PLM Procedure (EISY or POLISY).pdf

Yes.

I deleted and redid my fan button scenes and they seem to be behaving now so that may have just been a fluke.

What a coincidence. I have 4 devices that have multiple changes to their settings depending on time of day. Two SwitchLincs and two KeypadLincs. Depending on time of day things like on level and button backlighting is changed. I noticed that these changes stopped working at some point. I followed the same error message trail and that's when I found the devices in question were either missing it's .REC file, or a .REC file with 0 bytes.

The good news I was able to fix it once by copying the .REC of an identical model device to the filename for the device that was missing. This immediately restored the ability to control these parameters (no reboot, admin console still open). Doing it this way I did not have to remove/re-add the device. I just ensured I copied the .REC file from a matching model.

On a whim I adjusted the program that changes the parameters to include a 1 second delay in the changes. Previously they were all back to back. The thinking was maybe some IoX process was failing to write these files without a delay. I don't know if it was the underlying cause or not but since then I have not had the issue come back. This system has been running with the same keypad/switchlincs for over 6 years and I don't know exactly when the problem started. I do know that it happened to each of them over time. I assumed the device itself had stopped responding to the parameter changes. Once I found the file issue I figured it could have happened during any number of changes between moving PLMs, from ISY994, to Polisy/IoP, to eISY/IoX, and not counting the handfule of backup/restores that have occured.

@pinlawr , Interesting that you are seeing the .Rec files reset on devices where you are writing parameter changes. Very curious if your program delay helps reduce or eliminate the problem.

Unfortunately, copying a .REC file from one device to another will not completely resolve the problem. The REC file is a binary memory map for the specific device. When you copied the REC file to the missing device you also copied all of the source device's settings and scene members.

The following is a REC file from one of my Switchlincs viewed in Hex. The items in Red are the link table contents for the device.