Slalom

Lee that was essentially what I had done. I found out that when I ran the restore for the plm it did not restore everything to the devices. Devices generally were missing some but not all of the plm records. I was able to resolve this by restoring all of the devices. A little bit confused but back up and running. Thanks to both Lee and Stu.

I have already done that. More than once. And on all subsequent tries the order was definitely proper.

Pretty sure that I did the right order but perhaps I screwed up. At this point I guess it is more important to figure out how to recover. Can someone help?

Yet another PLM took a dump so I ordered another and replaced it. I followed the directions in the WIKI basically: powered down the ISY replaced the modem restored the modem The new plm does not see updates from the devices but can query their status. The devices operate normally and when queried the ISY programs control them as expected. I have tried to restore devices and i have compared their link tables against what the ISY thinks should be there all to no avail. The wireless devices (remote Linc 2 and the Leak Sensors) seem to work correctly. I have also found that if I remove a device and re-add it to the system it works correctly. So the questions are: What did I do wrong? And (perhaps more importantly) how do I fix it without removing and reinstalling all of my devices. Thanks for any help.

Why Insteon? Why not an output on the M1 with any appropriate noisemaker.... Doorbell Buzzer Chime

I currently have a number of Kwikset units and would be happy to participate in a testing program when you are ready. I was going to use the Elk interface but would rather work with UD.

I use my elk to detect power failure and make sure everything else is on a UPS...

Knew it had to be something stupid Thanks!

Hi The following program decrements the variable at a rate of one click per second, pretty much as expected. If Elk Zone 'MB Closet Motion' is Normal And $sMasterBedroomClosetMotion > 0 Then Repeat Every 1 second Wait 1 second $sMasterBedroomClosetMotion -= 1 Else - No Actions - (To add one, press 'Action') I had thought that this program would increment the variable at the rate of one click per second... But it pretty much counts up as fast as it can until it hits the limit. If Elk Zone 'MB Closet Motion' is Violated And $sMasterBedroomClosetMotion < $iMasterBedroomClosetMaximumOnTime And $sMasterBedroomClosetOffOverride is 0 Then Repeat Every 1 second $sMasterBedroomClosetMotion += 1 Wait 1 second Else - No Actions - (To add one, press 'Action') I was relatively certain that the second program worked until the ISY was rebooted. But it certainly does not now. Firmware is 3.1.16 with the elk module. The first question is why doesn't the second program work as expected. But in addition to that, even the first program went into 'hyper-speed' when I did not have the wait construct in it as shown below. I would have thought that the 'repeat every ' construct should be enough to set the rate. What am I doing wrong? If Elk Zone 'MB Closet Motion' is Normal And $sMasterBedroomClosetMotion > 0 Then Repeat Every 1 second $sMasterBedroomClosetMotion -= 1 Else - No Actions - (To add one, press 'Action')

I have seen this quite often on 3.1.16 I notice that it is much more prevalent when I log in using vpn so that the ISY is not on my local network.

Hi Slalom, This issue is actually caused by Elk sending a steady stream of ready/not ready messages when both Area 1 and a common area is not armed. They are aware of the problem and are currently looking at possible solutions. A suggested work-around is to not use common areas for now, and instead use Isy and/or Elk rules to accomplish the same. Thanks Chris I will have to look at how I can do that!

Elk Common Area Issues still exist in 3.1.16

Still an issue with elk common areas although it seems better. When the only thing stopping area 1 from being armed is that area 2 is not armed. Area 1 no longer flashes. It just shows not ready to arm... This is correct. But if I switch the drop down to area 2 to review / arm it. The drop down immediately reverts to area 1.

I spoke too soon. The problem still exists. Seems to be resolved in 3.1.14,

Seems to be resolved in 3.1.14,