Strange issue with Adjust Scene command.

[Algorithm]

In each of two bathrooms, I have a 2474D SwitchLinc 2-Wire Dimmer controlled by a 2420M Motion Sensor.  These motion sensors (and all the motion sensors throughout the house) are configured to send ON-only commands, and are directly linked to the SwitchLincs.  Now on either side of the master bedroom bed is 2334-222 8-button KPL.  When a certain button is turned on, and if it is dark (approximately between sunset and sunrise), it causes the corresponding bedside lamp, and the bathroom lights, to come on at 35% brightness, and then runs a program which uses Adjust Scene to set to 35% the ON LEVEL of the bathroom SwitchLinc scene controlled by the motion sensor.  All of this has worked fine for years.

Last Saturday, we had a power outage which lasted eight hours (we have very few power outages, and have never before had one anywhere near this long).  When the power came back and the system rebooted, everything appeared normal, apart from a couple of dead KPLs, which are being replaced.  But, and here is the issue, those bathroom SwitchLinc / Motion scenes are behaving strangely at night (though they are fine during the day).

When the bedside KPL button is turned on, the bedside lamp and the bathroom light both come on to 35%, as they should.  But the instant one walks into the bathroom, the bathroom lights immediately comes on to full brightness.  Then, perhaps one minute later (when the motion is again triggered), the bathroom lights return to 35%, and thereafter operate properly for the rest of the night.  So it seems that the Adjust Scene command is indeed setting the scene's ON LEVEL, but that either that Adjust Scene command is delayed (there are no programmed delays in any of the related programs), or the SwitchLinc's response to that adjustment is delayed (which seems really bizarre).

The ISY log shows the remaining commands, but does not show the Adjust Scene commands (presumably by design), though they are obviously being sent.  Also, I don't know what the built-in delay of the motion sensors is; whether they send a new ON command every ten seconds, or every minute, or some other interval; so I don't know how many times the motion is re-triggering and sending a new ON command, once or many times, before the SwitchLinc responds to the adjusted ON LEVEL.  I have tried a Restore on the SwitchLinc, which did not change anything.  Looking for some further troubleshooting ideas.

 

[Techman]

It's possible that the power outage corrupted the device link tables. You should first try to do a restore device on all the hardwired insteon swiches and keypads that are common to the bathroom lights.

You should also try a reboot on the controller.

[Algorithm]

Problem solved; thanks for the reply though.

With Event Viewer open, I ran the program to set the reduced on-level, and was surprised to see ISY attempting to write to several different devices, with the bathroom SwitchLinc being last of all, and taking about a minute-and-a-half, which explains the delay.

On examining the devices, I discovered that they were all wireless devices which had updates pending, and a closer look showed, in the Administrative Console, that the button to automatically write changes to wireless devices was enabled.  I normally keep that button disabled, and it seems that when ISY reboots, it enables that button--something to be aware of in the future.

With that button now disabled, and again running the program, response was immediate, and all is back to normal.

 

[IndyMike]

20 hours ago, Algorithm said:

Problem solved; thanks for the reply though.

With Event Viewer open, I ran the program to set the reduced on-level, and was surprised to see ISY attempting to write to several different devices, with the bathroom SwitchLinc being last of all, and taking about a minute-and-a-half, which explains the delay.

On examining the devices, I discovered that they were all wireless devices which had updates pending, and a closer look showed, in the Administrative Console, that the button to automatically write changes to wireless devices was enabled.  I normally keep that button disabled, and it seems that when ISY reboots, it enables that button--something to be aware of in the future.

With that button now disabled, and again running the program, response was immediate, and all is back to normal.

 

@Algorithm, Ive been bitten by this a number of times in the past.  Typically occurred after a power outage.  I don't have a solution for the button being re-enabled.

What I can offer is an easy method for updating motion sensors (actually this is all UDI).  Some time back UDI gave us the ability to write updates to sensors when they detect motion -

BSMT Sensor Program - [ID 004A][Parent 0066]
If
        'Motion/RF / BSMT-Sensor' is switched On
     Or 'Motion/RF / BSMT-Sensor' is switched Off
Then
        Set 'Motion/RF / BSMT-Sensor' Write Changes
 Else
   - No Actions - (To add one, press 'Action')

Works like a charm.  I normally keep the program(s) disabled and re-enable when I notice a pending write... I also keep the automatic writes to battery devices disabled (until they reset).

 

[CoolToys]

That looks great but I only get "on" or "off" not "Switched On" or "Switched Off"?

[Geddy]

@CoolToys "Switched On" or "Switched Off" is found using the "control" option. 

On/Off is typically in the "Status" option of the Then statements. 

 

[IndyMike]

56 minutes ago, CoolToys said:

That looks great but I only get "on" or "off" not "Switched On" or "Switched Off"?

Refer to @Geddy's post for how to implement the "Switched On/Off".

Status on/off will also work for triggering the program:

BSMT Sensor Program - [ID 004A][Parent 0066]
If
        'Motion/RF / BSMT-Sensor' Status is On
     Or 'Motion/RF / BSMT-Sensor' is switched Off
Then
        Set 'Motion/RF / BSMT-Sensor' Write Changes 
Else
   - No Actions - (To add one, press 'Action')

 

[Algorithm]

@IndyMike thanks for posting that.  I've been using similar programs for years, and like you I keep them disabled and only enable them when I know there are updates pending.  But it's good to have them brought to the foreground again, where others may benefit from them as well.

[IndyMike]

On 7/19/2024 at 5:20 PM, Algorithm said:

@IndyMike thanks for posting that.  I've been using similar programs for years, and like you I keep them disabled and only enable them when I know there are updates pending.  But it's good to have them brought to the foreground again, where others may benefit from them as well.

I had a feeling that you knew about the motion sensor programming feature.  I figured it was worth a shot.  I often forget about the older features and "re-discover" things by looking though old posts.

Good to see you on the forum again.