untripping an HSM100 when light manually turned off

Community Playground General Discussions
1

i have an HSM100 configured with a 20 minute time out so that periods of sitting quietly in the room do not result in the light turning off.

problem is that when i leave the room and turn off the light manually then walk back into the room within 20 minutes the sensor does not turn the light back on.

i tried creating a scene triggered by the light switch being turned off that set tripped to 0 on the sensor, hoping that would reset the sensor’s timer, so if i walked back into the room a minute later it would turn on – but, doesn’t seem to work.

anyone have any suggestions? am i barking up the wrong tree? thanks.

2

The HSM100 sends the tripped signal every time its tripped. Assuming that there are no delays in your network causing the slowdown / delay, try raising the sensitivity using Para 1.

JOD.

3

All my five battery-operated HSM100 don’t send the tripped signal within the time out interval.

4

my HSM100s dont send the tripped signal until the timeout expires either :frowning:

@JOD- what is the magic to get them to do that (without setting the timeout to 0, which means the lights will never get turned off automatically and it will eat batteries)?

5

I have two scenes. Kids Rm. Motion Tripped. When the armed sensor is tripped will turn on the outlet for the TV.
Attached are the settings for the sensor.
The other scene, Kids Rm. Motion Reset. When the armed sensor resets (no motion) turns the outlet off.
But if the TV turns off for the reset scene and there is movement in the room the TV turns back on right away.

JOD.

Edit. Take it off batteries, run it on a wall wart and have it on 24/7

6

if you turn the TV appliance module off then within your 4 minute timeout have motion in front of the sensor, does it turn your TV back on?

mine just ignores me in that window.

(i can’t get off battery sadly, i don’t have AC power where the sense needs to sit)

7

The penny just dropped for me, now I see the issue.
You are picking a latched state for 20mins, it wont release that state until that timer expires and due to the configs being contained in the device you cant reset that timer with code, the options are momentary with no timer or latched with a timer. If you go momentary you could add delays within the scene but you are concerned about battery life. I think you are boxing yourself in with that 20 min time.
There is no work around that I can see with this device other than reducing the timer and increasng the sensitivity, except turning the light switch back on when you enter the room ;D

JOD.

8

thanks, that’s what i was afraid of.

it seems so 20th century to have to turn on the light myself when i walk into a room :slight_smile:

9

The only way to return to 21th century seems to be:

Install two HSM100 …

HSM100 A with a very short ‘On Time’ (shortens battery life!): if tripped, switch on light.

HSM100 B with ‘On Time’ 20 min: if un-tripped, switch off light.

10

I had similar issues. In the end I went the whole hog and converted my HSM100s to mains power.

This allowed me to set the sensor to always awake (parameter 5 = 1) and continuous trip (para 2 = 0). At the time I was on 1047 which couldn’t handle the timeout logic in the sensor correctly so I built all the logic in Lua. More work but it passed complete control to me and overcame the problem.

For your app it could work this way.

With para 2 set to 0 the sensor is continuously tripped but is never automatically reset. Instead you do this from your code when conditions dictate. The scene that is triggered when the light is manually switched off simply resets the sensor immediately instead of waiting for the time out. If you forget, the time out will eventually switch off the light anyway. Note that you will need a short delay to ensure that you are out of range before the reset takes place. You’ll also need some logic to time out your sensor.

It’s a bit like keeping a dog and barking yourself but this works a treat for me.