I have a HSM100 that is correctly reporting when it is tripped but I assume never sends the non-trip to Vera2 as it continually shows the red running man and has tripped=1. These are my current values for the HSM100:
1-Sensitivity (0-255): 100
2-On time (0=always fire or 1-255): 10
3-LED on/off (0 or 255): 255
4-Light Threshold (0-100): 100
5-Stay Awake (0-255): 0
6-On value (0 or 1-100 or 255): 255
The wakeup for the HSM100 is the default 1800.
I have two scenes setup, one to turn lights on and one to turn them off, based on whether the HSM100 is tripped or not and unfortunately the lights don’t go off due to it never being reset.
Any suggestions on what to do or try? Has anyone encountered this before?
Delete the motion sensor part of the HSM100 and readd it?
Exclude and readd the HSM100?
My HSM100 get stuck every once in a while. I have two and there does not seem to be any rationale for when it occurs. But they do not become unstuck until they sense motion again.
Hmmm… The manufacturer of the HSM100 I’m having troubles with is by Ryherd Ventures. The good one is manufactured by Express Controls. Any one else having troubles, and who is the manufacturer?
Mine have said that too, but then eventually switch over. Perhaps it’s not fully configured. Maybe try a [tt]Configure node right now[/tt], wait a few seconds and hit the blue button on the HSM100.
One of my HSM 100’s is staying stuck in the tripped mode. Tried the exclude / include with no change. The odd behavior, from these units, always seem to appear when it time to change the batteries.
So I have this installed on a switchable and selectable power supply @ 4.5 volts, I also have the soldered the 3v resistor per instructions on another thread. for the record, I did this on BOTH units. I noticed this is reporting as tripped every 5 to 10 minutes even thought its facing a wall at the moment… I just increased the power supply voltage to 7.5v thinking that this adapter may be suffering voltage drop similar to the low battery issue in the previous post…
It’s held up for 10 minutes at the moment with no false readings. I’ll post back shortly with an update, but it may simply be false readings due to voltage drop… fingers crossed.
UPDATE:
False Triggers were originally @ 5 minutes apart running at 4.5V with resistor in-line.
@ 7.5 volts, i’m receiving false positives every 11 minutes.
I’ll switch to 9v on the adapter and see if they are farther apart, or (hopefully) eliminated…
Further UPDATE
9v still erradic false triggering.
I should note that I had this problem with the sensor BEFORE I installed the resistor so i’m thinking it’s simply hardware problems.
Note both of mine are wired to a/c per the link above and have had the device lock in “motion detected” condition. Vera reports the batteries at 100% and 95%, so a low voltage condition should not be an issue.
[quote=“big517, post:17, topic:171618”]It was 200, I dropped it to 180.
The older one that works fine is set to 220 I believe.[/quote]
Thanks. Yeah, I’ve seen odd behavior with the sensitivity really high, but I have mine at 230 and that works fine.
Note both of mine are wired to a/c per the link above and have had the device lock in “motion detected” condition. Vera reports the batteries at 100% and 95%, so a low voltage condition should not be an issue.[/quote]
That is exactly what I did, I ordered a few of those and installed on both sensors even though 1 was already working fine, that changed nothing.
For diagnostic purposes, you could try associating a light near the HSM100 to group 1 (IIRC) and see if the that light is then correctly turned on and off by the sensor.