Just switched from Homeseer to Hubitat. Enrolled all of my devices. Used the alternate user created driver by Groovy. Just updated Hubitat to 2.2.4.145. I have 3 Homeseer HSM200 multi-sensors. They intermittently freeze the motion sensor to active.
Any Ideas?
I’m actually tracking this down.. I have one doing the same thing.. It seems to just stop sending motion notifications.. While continuing to send the other sensor values..
Yeah, having the same issue here as well but it’s been doing that for a long time now...I think ever since switching to Hubitat. I mainly use it for the RGB light to show alarm status but would be nice to have another motion sensor for lighting etc. Hope you can track it down.
I’ll move it over to my development hub tomorrow and get the zniffer on it
1 Like
I'm testing on my dev hub right now.. As expected it is reporting motion for the moment.. But I suspect, based on history this will stop sometime today.. I have it up on zniffer so I should be able to get a lot more information on why this is happening..
2 Likes
Brian, Any progress on the flakey sensor?
Are you using Bryan's community driver instead of his stock HE driver? I noticed that happens with his community driver (that supports the crummy LED light), but motion works with his stock driver (which does not support the light). For me this stinks since without both, the device is about useless to me.
I am using a community driver by Groovy. It seems that is more about being slow to reset to [No Motion]. The one out in the cold garage is the most flakey one. The other 2, which are inside, seem to function normally.
Also, I got them to make mostly white light (for a night light) by setting the hue to 27 saturation to 99 and level to 100. I have no idea how it works!
When I originally used the stock HE driver the light would turn white when motion was detected.
Thanks
Do you have a link to that one? The one I have goes active and never goes inactive. A delay is better than never. lol
Yeah that's Bryan's community one. Groovy is the language HE runs on (or something similar I'm not a dev).
Any news on this? One of mine stopped working again today. Seems unplugging it fixes it for a while, but then it stops reporting again some days later. It does still report other readings like temp, illuminance, but not motion.
Yea.. that is basically what I have come up with.. There is something wrong with this device.. Rebooting the device seems to fix it..
I was reading thru the firmware release notes and found this.
"Reports of nodes requiring a power cycle to get them to talk again were coming in. They are rare but frequent enough it was decided to put additional checking in to reboot if there are more than 10 frame delivery failures in a row or if it has been more than 18 hours since the last communication."
Could that same process be exposed so that we can automate the reboot? instead of having to unplug the unit.
It seems that it is mostly about not returning to "Inactive" state in a timely fashion. Could it be the polling frequency? One returns within 2 minutes. The other 2 take forever to return to inactive. Both are in colder temperatures. They all are inactive at the beginning of each day.
Scott
Hello I have 2 HSM 200 motion detectors and I have the same problem, when I configure the 2 on my zwave network, they freeze. So I kept only 1, the other is in the drawer...waiting for a firmware?
