I would.check your mesh stength if yoi're getting bad temp reports . All 4 of mine are
Perfect. And it is one of my strongest repeaters..only half turning on is another indication of mesh problems...monitor your logs. during temo reports if u see many duplicated reports it is having trouble communicating and you need some more powered devices or repeaters between hub and said device.
@kahn-hubitat and @robwhite922, I'm curious if you're running in S2 mode or not?
yes i am..and if i remember correctly stuff did not work right or i could not get it to pair without s2
i have one that is not in s2 as if i remember correctly the light would not work outside of s2..
anyway this one i dont use for the light just the motion sensor and temp reports and as a strong repeater in the basement and it was on an older firmware anyway so i didnt care.
i also remember needing to pair near the hub then move to final location and then do a zwave repair on just that device.
Hmm, I wonder if that also plays into it. I saw another thread where someone was getting aberrant temperature reports until he put his temp sensors on S2.
I've used a few HSM-200s for years if not decades. Main use is attic temperature at parent's house, and color-coded status display for laundry.
I'm tinkering with one at my place for hallway motion (turns on dim kitchen lights at first motion in the morning, and change the color with motion just to test and tinker).
I'm using the "HomeSeer HSM200 Multi-Sensor" driver, not sure if it was built-in or downloaded elsewhere.
A couple of notes on the hsm200 to help others.
I just got a couple of used ones off ebay to put 1 each in our condo and i wanted a powered temp and motion sensor that reliably reports as we are not there for months at a time and batteries go dead in other sensors.
Anyway one was on firmware 2.7 (reported as 2.07) in the details page.
This firmware has a motion bug that if you have a rule for instance that turns the light on for motion and off after, the off light event retriggers the motion so it never turns off in that case.'
They fixed this in version 2.8 of the firmware. but only marginally there is about a 7 sec delay in triggering motion on a light on/off event.
So if you have a rule that turns off the light after motion make sure there is no xx minute delay or it wont work.
2nd it was a bitch to update the firmware to 2.8 kept dieing at 41%.
I had to re-pair it with no security so it would update much quicker and also have it close to the hub like 5 feet away. Then the firmware update went smoothly.
Also, as others have said if it is not real close to the hub or you dont have a lot of extenders (in my case only 2 zwave devices and it is on the other side of the condo from the hub) you get garbled messages and bad temp reports, Pairing it again in secure s2 mode seems to cure this . Most likely as it has crc or something and resends the messages.
I've been trying to find the firmware. Were you guys able to update the device and do you know where I can get it from?
1 Like
Nm I figured out thank you for the firmware.
1 Like
I'm having the same errors come up.
What did you figure out jsarcone?
Push the button on the side of the device. it will start to blink then push update.
Apologies, I should have posted my question in this thread.
Hello all, I have a HomeSeer Multi-Sensor and it keeps throwing back errors. As far as I can tell, everything is functioning properly, except I get these errors in my logs every few minutes. Anyone have any thoughts?
groovy.lang.MissingMethodException: No signature of method: java.lang.Double.getAt() is applicable for argument types: (java.lang.Integer) values: [0]
Possible solutions: getAt(java.lang.String), next(), putAt(java.lang.String, java.lang.Object), wait(), grep(), getClass() on line 449 (method parse)
What driver.
