Interim HC3 block scene issues when re-triggered - can't figure out why

[MrNoTip 2]

I have all my old HC2 devices migrated onto a new HC3 setup now, but with the change in LUA syntax, a lot of my scenes need a ground up rebuild. Where I rely on these scenes, such as motion triggered and timed off lighting for my garage and workshop, I've put some very simple block scenes in place until I can get the LUA sorted.

 

This scene is pretty simple - turn on a couple lights when motion is detected, wait 15 minutes and turn them off again. This is cut down from my actual requirement, but it will do for now. The lights are two separate Fibaro Double Switch 2 units.

 

My problem is that a subsequent motion trigger within the 15 minute window is turning these lights off straight away! I really can't fathom how the scene restarting would cause this?

 

 

Please login or register to see this attachment.

 

I'm not sure that the scene is actually running my 'off' command right away when it retriggers - I just can't see any reason the second scene run would somehow 'skip'  the 15 minute delay?

I am wondering if the 'turn on' command is actually functioning as a toggle. Is this a known issue with the HC3 or the Double Switch 2 units?

 

 

EDIT: I just tried manually running and re-running the scene from the HC3 web interface while looking at the device screen in another tab. When the scene is re-run, I can see the devices asynchronously refresh on screen, the state still reports on but the power consumption drops to 0w. A physical check shows that the lights are now off. A third run of the scene turns them back on. The device view through each of the three runs is shown below.....I am starting to feel like this must be a bug or an issue with the double switch hardware?

 

Please login or register to see this image.

/monthly_2025_02/image.png.79dd9e8fef34871652415a37f1e0dd86.png" />

 

 

It looks like protecting the initial instance is a workaround for the issue, but that will prevent the motion sensor simply re-starting the 15 minute wait time on a motion retrigger. Maybe this is a bit much to expect from a temporary block scene, but its certainly a nice to have when I am working down there.

 

 

Any insight or advice appreciated!

Edited February 28, 2025 by MrNoTip
new info

[awlieser 21]

You could use a variable „Garage_Light“ with values On and Off. Put the Off-value into the condition part (not as trigger). Then after switching on, set value to On and after delay set value to Off again.

Edited February 28, 2025 by awlieser

[Brors94 115]

On 2/28/2025 at 2:04 PM, MrNoTip said:

I have all my old HC2 devices migrated onto a new HC3 setup now, but with the change in LUA syntax, a lot of my scenes need a ground up rebuild. Where I rely on these scenes, such as motion triggered and timed off lighting for my garage and workshop, I've put some very simple block scenes in place until I can get the LUA sorted.

 

This scene is pretty simple - turn on a couple lights when motion is detected, wait 15 minutes and turn them off again. This is cut down from my actual requirement, but it will do for now. The lights are two separate Fibaro Double Switch 2 units.

 

My problem is that a subsequent motion trigger within the 15 minute window is turning these lights off straight away! I really can't fathom how the scene restarting would cause this?

 

 

Please login or register to see this attachment.

 

I'm not sure that the scene is actually running my 'off' command right away when it retriggers - I just can't see any reason the second scene run would somehow 'skip'  the 15 minute delay?

I am wondering if the 'turn on' command is actually functioning as a toggle. Is this a known issue with the HC3 or the Double Switch 2 units?

 

 

EDIT: I just tried manually running and re-running the scene from the HC3 web interface while looking at the device screen in another tab. When the scene is re-run, I can see the devices asynchronously refresh on screen, the state still reports on but the power consumption drops to 0w. A physical check shows that the lights are now off. A third run of the scene turns them back on. The device view through each of the three runs is shown below.....I am starting to feel like this must be a bug or an issue with the double switch hardware?

 

Please login or register to see this link.

 

 

It looks like protecting the initial instance is a workaround for the issue, but that will prevent the motion sensor simply re-starting the 15 minute wait time on a motion retrigger. Maybe this is a bit much to expect from a temporary block scene, but its certainly a nice to have when I am working down there.

 

 

Any insight or advice appreciated!

You can also try Quickapps  
This one I have made let you setup motion lights easy for a room  

Just set the lights and motion and the QA in the same room, Choose the dropdown of motionsensor and lights and times and it is up and running

Please login or register to see this link.