Status Not Updating in Admin Console

[dukdukgoose]

I see a thread started by Richardl007 with a similar issue, but I'm starting a new thread as I believe my situation is different.  I've been using ISY99 for years with Insteon dimmer switches, on/off switches and motion detectors.  I've just noticed that button pushes on my dimmer or on/off switches are not updating status on my Admin Console.  Here's my specific situation.  I have a scene with two dimmer switches set as controllers on a 3-way circuit.  A motion detector triggers a program that turns on one of the dimmer switches when motion is detected and another program turns off the switch when the motion detector switches off.  When the motion detector turns on the dimmer switch, it shows as "On" in the Admin Console and "Off" after it is switched off.  Everything seems to be working properly.

I now want to update the program that turns off the light.  I want to have the option to keep the light on after motion is no longer detected.  I've added an If condition to my "Off Program" that checks to see if either of the controllers is switched on.  That's when I noticed something odd.  If I manually turn on either of the dimmer switches, they still display as "Off" in the Admin Console.  They display as "On" if the motion detector switches on the light.  I've checked other circuits and devices and all are behaving similarly.  I can turn switches on and off from the Admin Console and they accurately report status back to the console (displaying on or off).  Likewise, they accurately report status if triggered by a motion detector.  However, manually activating the switch doesn't change the status in the Admin Console.  For example, if I turn on a light from the Admin Console, it displays as "On."  If I manually turn off the light at the switch, the light goes off, but the Admin Console still displays the switch as "On."  Since I'm relying on button pushes at the switch to determine what the program does, it seems important that these button pushes are registering on the Admin Console, but they are not.

Any help is greatly appreciated!

 

[larryllix]

44 minutes ago, dukdukgoose said:

I see a thread started by Richardl007 with a similar issue, but I'm starting a new thread as I believe my situation is different.  I've been using ISY99 for years with Insteon dimmer switches, on/off switches and motion detectors.  I've just noticed that button pushes on my dimmer or on/off switches are not updating status on my Admin Console.  Here's my specific situation.  I have a scene with two dimmer switches set as controllers on a 3-way circuit.  A motion detector triggers a program that turns on one of the dimmer switches when motion is detected and another program turns off the switch when the motion detector switches off.  When the motion detector turns on the dimmer switch, it shows as "On" in the Admin Console and "Off" after it is switched off.  Everything seems to be working properly.

I now want to update the program that turns off the light.  I want to have the option to keep the light on after motion is no longer detected.  I've added an If condition to my "Off Program" that checks to see if either of the controllers is switched on.  That's when I noticed something odd.  If I manually turn on either of the dimmer switches, they still display as "Off" in the Admin Console.  They display as "On" if the motion detector switches on the light.  I've checked other circuits and devices and all are behaving similarly.  I can turn switches on and off from the Admin Console and they accurately report status back to the console (displaying on or off).  Likewise, they accurately report status if triggered by a motion detector.  However, manually activating the switch doesn't change the status in the Admin Console.  For example, if I turn on a light from the Admin Console, it displays as "On."  If I manually turn off the light at the switch, the light goes off, but the Admin Console still displays the switch as "On."  Since I'm relying on button pushes at the switch to determine what the program does, it seems important that these button pushes are registering on the Admin Console, but they are not.

Any help is greatly appreciated!

 

I don't know if the older ISY99 has this feature but have you done a link chart comparison or at least a Device Restore from the admin console? Links can go MIA at times.

It is possible your PLM is losing it's grip also.

[dukdukgoose]

Thanks so much for the quick reply.  Here's what I see when I compare links:

I do see the mismatch, so I assume that's indicative of my problem(?)  FWIW, I'm seeing similar mismatches on several other devices.  I see from the Wiki that E2 indicates a Controller, but I'm not seeing what EA (the mismatch) represents.  In any case, is my next step to try Restore Devices?  I don't have any reason to believe my PLM is failing.

Again, I greatly appreciate the assistance!

[kclenden]

The mismatch you see isn't really a mismatch.  The difference E2 -> EA is a normal process whereby devices update a link based on real time communication.  To be more specific, the "2" in "E2" tells the device to use 0 SmartHops when communicating with other devices.  SmartHops are the way that a device tells other devices to repeat its message.  So to begin with the device is set not to have any devices repeat its messages.  This is to keep traffic on the electrical line to a minimum.  If a device finds that its messages aren't getting through, then it increments the Smart Hops by one and stores it in its Links table.  In your case, the "A" that you now see means that SmartHops have been set to 2 which means that any messages it sends will be repeated two times to make sure its message is received by the intended recipient.

The AC is simply doing an exact match to determine if a record is the same, but in this case, even though there is a mismatch, it does not indicate that anything is wrong.

[kclenden]

On 7/26/2020 at 8:58 PM, dukdukgoose said:

Any help is greatly appreciated!

 

On 7/26/2020 at 9:44 PM, larryllix said:

It is possible your PLM is losing it's grip also.

Based on the issues you describe, I think it's much more likely that your PLM is slowly losing its mind.  Here's why:

• When you implement a command from the AC, it changes the status of the device purely because you executed the command from the AC, not because it gets message from the device.
• When you execute a scene from the AC, all device statuses are updated in the AC because you implemented the scene from the AC, not because the AC is getting messages from all of the devices.
• I believe, but am not sure, that when the motion sensor turns on a scene, the AC changes the status of all the devices included in the scene based on receiving an "On" from the motion sensor.  I believe all of the scene acknowledgment messages from the devices go to the motion detector and not the AC.
• When you press a switch, the AC updates the status of that device based on receiving an "On" or "Off" from that device.  It can only do this if the PLM has a link associating itself with the device.  When the PLM starts losing its mind, these links start disappearing.

Unfortunately, there isn't a command that allows you to compare the links in the PLM with what the ISY thinks they should be.  So you have two options:

• Use the AC to display the links in the PLM.  Based on the number of links reported compared to the number of devices you have, make an educated guess as to whether some are missing.  Or, if you know how to decode the Links table, you could look for specific links associating the PLM with the devices that don't seem to update in the AC when activated locally.
• You could restore the PLM.  If the device status start appearing in the AC when you activate them locally then you know that there were missing links in the PLM table.

[dukdukgoose]

Thanks so much for the help.  I need to carve out some time to look over the links and see about the PLM.  I appreciate the education!