j0dan

Thanks. Seemed to do it for me.

That's what's going on here too!! I had the problem on 3.3.6 and was an upgrade from a similar version. Was driving me insane wondering why certain lights and fans were randomly turning on/off.

I get all sorts of strange UI glitches after link tables are corrupt. Statuses in programs don't always line up either when the ISY switches link tables around. This can make other devices turn on/off and keypadlinc statuses incorrect. Are scene attribute changes not very common in others programs? I kept them with 5 second delays between everything and it did *seem* to take longer before things broke.

When will the new version be released? My Insteon network has deteriorated into a buggy system that only occasionally works due to bugs in the ISY firmware. I'm tired of errors and light switches not doing what they are programmed to do.

Through programs, physically pressed and interacted with. All of the devices so far are in scenes that are adjusted in programs. It seems like the more the device is used, the greater a chance of it being corrupted. Which fits in line with your database locking problem. I don't know if the .REC becomes empty, but the GUI either has it confused with another device or there's nothing there. The GUI doesn't always display what is in the .REC either. We need a logging system where we can actually see what's going on with programs and devices. It should log things like when programs run, what their status was when it was ran. If something strange happens on my network, I should be able to see what triggered it in the log. Right now I can't.

Any update after the weekend? Disabling those programs have stopped it from happening so far, but after checking other devices, it looks like any device that gets accessed often is having this problem. I've found several more devices with bad link tables. I did figure out the garage door glitch thankfully. Was related to this problem but several steps removed. BETTER LOGGING WOULD HELP!!!!

I haven't been sent another SD card yet. I may have one here to test with if it makes sense to. But like you said, that is not likely the problem.

Are you sure this can't be caused by LED brightness commands? That's the only thing in common with the 3 devices that have this issue. I have an ICON switch that gets the same scene adjust commands as two of the other devices with this problem and its link table has never been corrupted. I've disabled the LED brightness commands for now to see if that helps. Can you PLEASE make a way to load the link tables from a device to fix the internal link table? I have this happening on two well used KeypadLinc's. I've spent many MANY hours re-configuring the same devices and programs. When will a new release with bug fixes to test be available?

Sounds like a match indeed - my devices link table did match the ISY after the restore when the device was not working properly. Do you by chance have either a RemoteLinc or ControlLinc is in affected scene? There seems to be a UI glitch around the handling of these two devices (at least in my setup). The UI seems to think that the ControlLinc and the RemoteLinc can be a responder - which does not make sense. I've been thinking that may be the source of the issue for me - but it sounds like it may be something more fundamental. Michael. The bug for me seems to happen when I adjust scenes using programs. It can take anywhere from hours to days for the problem to happen. I either have the internal ISY link table become empty or even get swapped with another devices. It has nothing to do with what's in a scene. I don't have any RemoteLinc or ControlLinc's. I might buy one of the new RemoteLinc's after someone else has worked out all the bugs.

That sounds similar to the bug I'm having a hell of a time with. Check the link tables and see if the ISY link table matches up with the device one. After doing a restore device, you would have written the bad link tables from the ISY to your device. (They will match after a restore, but won't work correctly.)

3.1.9 I'm having it really bad with 3.1.9. It's happening several times/day. I've been restoring just the .REC file to fix it. Last night my garage door opened on its own when I turned off the bedroom lights!!!

Any potential fixes for the link table overwriting? 3.1.8 is still doing it for me. I'm just living with a broken system instead of recreating my scenes and programs every few days.

For example: If Status 'Living Room / Lamp A' is not Off Or Status 'Living Room / Lamp C' is not Off Or Status 'Living Room / Corner Lamps' is not Off Or Status 'Living Room / Living Room Light' is not Off Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') This program fires if Lamp A is already on, and Lamp C is turned on or off. I have a few programs that do things like update the LED brightness on switches based on other lights or the brightness in the room. It's causing a lot of extra traffic and possibly contributing to a more serious bug with the ISY overwriting it's internal link tables. So I'm trying to minimize the amount of times these programs fire. How can I optimize these programs?

Michel: Are the ISY link tables stored in the CONF/xxxxx.REC files on the SD card? Could I just back up and restore that one file when the link table gets corrupted or deleted?

Is it possible that updating LED brightness could cause this problem? I use those options quite a bit and recently enabled those. I've put 4 second delays in everywhere too.