Name: Button A
Brand and model: Samsung SmartThings Button
Device ID: 99
Device Type: Samsung Zigbee Button
Note: I introduced this button to manually switch on smart switch in case the motion light app not working
Test Summary:
2020-06-09 21:03:18.047 – initial motion detected
2020-06-09 21:06:02.315 – Motion no longer detected and device #2 is now in OFF state
2020-06-09 21:06:05.624 – Motion is detected again, this time device #2 is NOT ON at all
2020-06-09 21:06:05.798 – Device #2 been requested to switch on, but nothing is happening
2020-06-09 21:06:35.651 – Device #3 is double tapped, to override the action to turn on the light
2020-06-09 21:06:36.230 – Device #2 confirmed it is now ON
1st question that pops out (not going to have a chance to do a full look until later) why have you added the sensor in as a additional sensor aswell? That might be your issue.
That shouldn't be there, the idea for that is I have 2 rooms with a sensor in each, when I go into one room and set off the app I want the lights to turn on. I then move to the 2nd room with maybe another app and the lights in there turn on but I have added that sensor to the 1st app aswell (as a additional sensor) now both rooms will stay on untill both detectors time out. So the additional sensor is not a trigger sensor but is a hold on sensor.
Yep, remove that "second" WC sensor in the additional sensor options.
Can also be used in large or irregularly shaped rooms to keep the lights on. My basement, for example has one sensor at the bottom of the stairs to turn the basement light on, and a second near the wash machine to keep the lights on, and a third sensor in the opposite corner near the breaker panel. None of these sensors alone can see the whole basement.
But that's all it does. It "keeps the lights on" but it doesn't turn the lights on. If that's what you want then perfect . If you have more than one sensor in the room you can also add them all to the main motion option aswell, then if they turn off they would come back ON by any of them.
Is this a temp thing or is it staying? If it is I would suggest that you add something like "if on stay ON" in the override section of the app. Then the app will stay in sync with the switch.
Okay, I've removed the additional sensor and renamed the device and app to start with "WC" (easy to see in the device and app list.
The following is the motion light app now:
Hm... that's kinda pointless to have an automated motion light if the user needs to wait 30s every time it switched itself off, don't you think?
The toilet/powder room/WC is regularly used by the family, and I setup this to avoid them touching the light switch due to the covid. And I setup 1 minute delay (in theory) to save the electricity (plus it looks cool....if it works....)
It's just to test your device and prove strength of mesh.
As a professional lighting commissioning engineer, your not going to save any energy doing this. It's a switch device correct? The inrush alone will wipe that. You would be better have a delay of 5 mins as it allows them to do their business without the light turning on and off.
So that I understand this correctly, to test the z-wave mesh strength is to:
wait for the light to turned off
wait 30 seconds
make a movement again
if that is correct, it works as expected.
The intermittent issue is happening when I tried to make a move right after it switched off (well, it's intermittent, sometimes works, sometimes does not work).
Then it's a device or mesh issue. What I suspect is happening is your trying to send a ON before the device has reported that it's OFF so the app or driver thinks it's still ON and doesn't send anything.
What is your motion sensor? What are the built in timeouts for that device? I wonder if that could have anything to do with it - maybe the motion sensor hasn't fully reset. For my motion lighting I use an extra bit of delay before turning a light off to account for this.