HSM100 not updating motion. Temp, Light and battery works great - Fixed!

[Guest]

I have changed the no motion to 0,1,2,3 and set it always on...

I cannot get it to up date to no motion.... i have new batteries and I have changed the batteries..

I have removed the node and readded it.... i have optimized the not 3 or 4 time and it only reports motion..


the thing is..... the red light goes on and off with motion, no motion.... so i dont understand why the motion value doesnt change.


any help would be great.

thanks. it seems that there are many people who have similar issues.

under last changed it says never set....

[Guest]

well it just randomly started working.... i put it up against the wall and changed the sensitivity from 200 to 1 then to 100 then to 180 and it finally updated....

whew...... i was worried

[Rupp]

well it just randomly started working.... i put it up against the wall and changed the sensitivity from 200 to 1 then to 100 then to 180 and it finally updated....

whew...... i was worried

For some odd reason it takes these devices a long time to start reporting. But once they start reporting they seem to work really well.

[Guest]

i am setting up events with conditions like the delayed action video how to.....

and it works great when i have the Sensor set to always on and the motion off delay set to 1 min....

but if i change it to sleep and like 30mins and keep the Motion Off delay set at 1 min it doesnt update the motion after 1 min.

is the sleep state for all 4 sensor? (motion, lumens, temp and bat) or just 3 (bat, lumens and temp)

it would be great if the motion "pushes" its change in device value when ever it gets motion (- delay) setting and the other 3 sensors were tied to the sleep state....

but i am not sure..... I dont think i will be able to use my motion detector to reliably control lights if it only detects motion and send that to homeseer once in 30 mins....

it works great when it is always on....

i will keep tinkering

[dhayner]

I have similar issues with my HSM100 "Child 31 Motion Detector". The other 3 items update regularly but the motion hasn't updated since Jan. 3. I can't think of anything monumental that happened that day to begin causing this. Are there other reports of the same issue? I've just started scanning the board for it & ran across this pertinent subject line first.

DH

[loowee]

HSM100 not updating motion

Exact same problem here...
All values are correctly updated every hours ( wakup delay ) but motion will only update if I manually wakeup the darn thing. I removed and re-added the node more than 5 times.

Tought it was a signal problem but then the other values would not work either if that was the case.

For that price, I would expect a solid product, I guess I will have to limit myself to wall plug proximity for constant ON connected to 5V power source.

anyone ?

[kaldoon]

Exact same problem here...

What version of the software are you running?

[loowee]

HSM100 not updating motion

2.4.0.6
Updated at least from 3 versions since then and same problem...

Thx !

[Rupp]

How long have you had the device? It could just be a bad device?

[loowee]

Had them for weeks but motion never actually worked with it. I doubt it is the unit that is defective since the 3 sensors we have here all have the same problem. Also, I just re-added the nodes and one of them did not respond correctly, it only added motion and temp for values, no luminance ...

Very strange random issues that all seem to revolve around signal problem, could the zwave switches we have ( homepro ) be incompatible ?

[kaldoon]

Did you wake up the sensors and re-scan them? Can you post that part of the log. The Homepro switches have nothing to do the with issues with the HSM100's.

[Elo]

I have the European version of the sensor. I am using external power. I have set it to delay lights off 1min. Increased sensitivity to 255. Red LED set to show detection. Sleep time 60min (everytime HS rescans it it sets the sleep time back to 60min for some reason). If I set it to always awake it stops reporting motion or HS stops detecting it. If I let it go to sleep as pr. defualt it works fine reports motion then waits 1 minute and if continued motion it reports it again.....

I have not waited for a considerable time after changing to always awake to see if it starts reporting!

[niewoo]

I'm having similar issues. I have 2 HSM100s (Non-EU version). I can't seem to reliably get all of the data to update - motion has been very intermittent on one of them, and non-existent on the other for several days. Only luminance and temperature seem to update on a regular basis.

I've run numerous tests in ZSeer and there are no dropped packets. A test of 10 packets takes about 2-3secs to run, so about similar to the rest of the devices in that areas of the house. I'm constantly trying to re-optimize the network and move devices around, and it certainly appears to be signal related as sometimes they appear to work better and other times worse, although the ZSeer tests work no matter what.

Here is the log after the rescan:

2/24/2010 9:32:49 AM Device Update Device: Z-Wave Main Entry Child 2 Temperature value set to 69.3 (6930/F)2/24/2010 9:33:00 AM Device Update Device: Z-Wave Living Room Child 3 Luminance value set to 75 (7500/%)2/24/2010 9:33:00 AM Device Update Device: Z-Wave Living Room Child 3 Temperature value set to 67.7 (6770/F)2/24/2010 9:33:22 AM Z-Wave ---------------------------------------------------------------------------------2/24/2010 9:33:22 AM Z-Wave ********** Reloading Z-Wave Device with Node ID of 2 **********2/24/2010 9:33:22 AM Z-Wave Contacting node 2 to get supported features2/24/2010 9:33:22 AM Z-Wave Device: Z-Wave Main Entry Root Device 2 (Node 2) supports class(es): COMMAND_CLASS_MULTI_CHANNEL_V2, COMMAND_CLASS_SENSOR_MULTILEVEL, COMMAND_CLASS_CONFIGURATION, COMMAND_CLASS_WAKE_UP, COMMAND_CLASS_ASSOCIATION, COMMAND_CLASS_BATTERY, COMMAND_CLASS_MANUFACTURER_SPECIFIC, COMMAND_CLASS_NODE_NAMING, COMMAND_CLASS_VERSION2/24/2010 9:33:22 AM Z-Wave Attempting to get manufacturer ID from device 2...2/24/2010 9:33:23 AM Z-Wave Z-Wave manufacturer ID: 30=1EH (HomeSeer Tech), Type: 2=2H, ID: 1=1H2/24/2010 9:33:23 AM Z-Wave Z-Wave device 2 version: Lib: 2.40 App: 1.102/24/2010 9:33:24 AM Z-Wave Device supports 1 groups for associations2/24/2010 9:33:24 AM Z-Wave Programming device Z-Wave Main Entry Root Device 2 (2) to send wake-up notifications to HomeSeer.2/24/2010 9:33:24 AM Z-Wave Setting wake-up interval for device Root Device 2 to 1 hours and 0 minutes.2/24/2010 9:33:25 AM Z-Wave ========== Done with Z-Wave Device with Node ID of 2 ==========2/24/2010 9:33:27 AM Z-Wave Setting wake-up interval for device Root Device 2 to 1 hours and 0 minutes.2/24/2010 9:33:27 AM Z-Wave Sensor woke up and value for WAKEUP_INTERVAL was successfully set.2/24/2010 9:33:31 AM Z-Wave ********** Done with sync of Z-Wave Device with Node ID of 2 **********2/24/2010 9:33:31 AM Device Update Device: Z-Wave Main Entry Child 2 Luminance value set to 28 (2800/%)2/24/2010 9:33:31 AM Device Update Device: Z-Wave Main Entry Child 2 Temperature value set to 69.5 (6950/F)2/24/2010 9:33:31 AM Device Update Device: Z-Wave Main Entry Child 2 Luminance value set to 27 (2700/%)2/24/2010 9:33:51 AM Z-Wave ---------------------------------------------------------------------------------2/24/2010 9:33:51 AM Z-Wave ********** Reloading Z-Wave Device with Node ID of 3 **********2/24/2010 9:33:51 AM Z-Wave Contacting node 3 to get supported features2/24/2010 9:33:52 AM Z-Wave Device: Z-Wave Living Room Root Device 3 (Node 3) supports class(es): COMMAND_CLASS_MULTI_CHANNEL_V2, COMMAND_CLASS_SENSOR_MULTILEVEL, COMMAND_CLASS_CONFIGURATION, COMMAND_CLASS_WAKE_UP, COMMAND_CLASS_ASSOCIATION, COMMAND_CLASS_BATTERY, COMMAND_CLASS_MANUFACTURER_SPECIFIC, COMMAND_CLASS_NODE_NAMING, COMMAND_CLASS_VERSION2/24/2010 9:33:52 AM Z-Wave Attempting to get manufacturer ID from device 3...2/24/2010 9:33:58 AM Z-Wave Z-Wave device 3 version: Lib: 2.40 App: 1.102/24/2010 9:33:59 AM Z-Wave Device supports 1 groups for associations2/24/2010 9:34:00 AM Z-Wave Programming device Z-Wave Living Room Root Device 3 (3) to send wake-up notifications to HomeSeer.2/24/2010 9:34:00 AM Z-Wave Setting wake-up interval for device Root Device 3 to 1 hours and 0 minutes.2/24/2010 9:34:01 AM Z-Wave ========== Done with Z-Wave Device with Node ID of 3 ==========2/24/2010 9:34:04 AM Z-Wave Setting wake-up interval for device Root Device 3 to 1 hours and 0 minutes.2/24/2010 9:34:04 AM Z-Wave Sensor woke up and value for WAKEUP_INTERVAL was successfully set.2/24/2010 9:34:09 AM Z-Wave ********** Done with sync of Z-Wave Device with Node ID of 3 **********2/24/2010 9:34:09 AM Device Update Device: Z-Wave Living Room Child 3 Luminance value set to 70 (7000/%)2/24/2010 9:34:09 AM Device Update Device: Z-Wave Living Room Child 3 Temperature value set to 68 (6800/F)2/24/2010 9:34:09 AM Device Update Device: Z-Wave Living Room Child 3 Luminance value set to 76 (7600/%)2/24/2010 9:34:09 AM Device Update Device: Z-Wave Living Room Child 3 Luminance value set to 79 (7900/%)2/24/2010 9:34:09 AM Device Update Device: Z-Wave Living Room Child 3 Temperature value set to 67.7 (6770/F)

[niewoo]

Sorry - formatting got whacked ...

2/24/2010 9:32:49 AM Device Update Device: Z-Wave Main Entry Child 2 Temperature value set to 69.3 (6930/F)
2/24/2010 9:33:00 AM Device Update Device: Z-Wave Living Room Child 3 Luminance value set to 75 (7500/%)
2/24/2010 9:33:00 AM Device Update Device: Z-Wave Living Room Child 3 Temperature value set to 67.7 (6770/F)
2/24/2010 9:33:22 AM Z-Wave ---------------------------------------------------------------------------------
2/24/2010 9:33:22 AM Z-Wave ********** Reloading Z-Wave Device with Node ID of 2 **********
2/24/2010 9:33:22 AM Z-Wave Contacting node 2 to get supported features
2/24/2010 9:33:22 AM Z-Wave Device: Z-Wave Main Entry Root Device 2 (Node 2) supports class(es): COMMAND_CLASS_MULTI_CHANNEL_V2, COMMAND_CLASS_SENSOR_MULTILEVEL, COMMAND_CLASS_CONFIGURATION, COMMAND_CLASS_WAKE_UP, COMMAND_CLASS_ASSOCIATION, COMMAND_CLASS_BATTERY, COMMAND_CLASS_MANUFACTURER_SPECIFIC, COMMAND_CLASS_NODE_NAMING, COMMAND_CLASS_VERSION
2/24/2010 9:33:22 AM Z-Wave Attempting to get manufacturer ID from device 2...
2/24/2010 9:33:23 AM Z-Wave Z-Wave manufacturer ID: 30=1EH (HomeSeer Tech), Type: 2=2H, ID: 1=1H
2/24/2010 9:33:23 AM Z-Wave Z-Wave device 2 version: Lib: 2.40 App: 1.10
2/24/2010 9:33:24 AM Z-Wave Device supports 1 groups for associations
2/24/2010 9:33:24 AM Z-Wave Programming device Z-Wave Main Entry Root Device 2 (2) to send wake-up notifications to HomeSeer.
2/24/2010 9:33:24 AM Z-Wave Setting wake-up interval for device Root Device 2 to 1 hours and 0 minutes.
2/24/2010 9:33:25 AM Z-Wave ========== Done with Z-Wave Device with Node ID of 2 ==========
2/24/2010 9:33:27 AM Z-Wave Setting wake-up interval for device Root Device 2 to 1 hours and 0 minutes.
2/24/2010 9:33:27 AM Z-Wave Sensor woke up and value for WAKEUP_INTERVAL was successfully set.
2/24/2010 9:33:31 AM Z-Wave ********** Done with sync of Z-Wave Device with Node ID of 2 **********
2/24/2010 9:33:31 AM Device Update Device: Z-Wave Main Entry Child 2 Luminance value set to 28 (2800/%)
2/24/2010 9:33:31 AM Device Update Device: Z-Wave Main Entry Child 2 Temperature value set to 69.5 (6950/F)
2/24/2010 9:33:31 AM Device Update Device: Z-Wave Main Entry Child 2 Luminance value set to 27 (2700/%)
2/24/2010 9:33:51 AM Z-Wave ---------------------------------------------------------------------------------
2/24/2010 9:33:51 AM Z-Wave ********** Reloading Z-Wave Device with Node ID of 3 **********
2/24/2010 9:33:51 AM Z-Wave Contacting node 3 to get supported features
2/24/2010 9:33:52 AM Z-Wave Device: Z-Wave Living Room Root Device 3 (Node 3) supports class(es): COMMAND_CLASS_MULTI_CHANNEL_V2, COMMAND_CLASS_SENSOR_MULTILEVEL, COMMAND_CLASS_CONFIGURATION, COMMAND_CLASS_WAKE_UP, COMMAND_CLASS_ASSOCIATION, COMMAND_CLASS_BATTERY, COMMAND_CLASS_MANUFACTURER_SPECIFIC, COMMAND_CLASS_NODE_NAMING, COMMAND_CLASS_VERSION
2/24/2010 9:33:52 AM Z-Wave Attempting to get manufacturer ID from device 3...
2/24/2010 9:33:58 AM Z-Wave Z-Wave device 3 version: Lib: 2.40 App: 1.10
2/24/2010 9:33:59 AM Z-Wave Device supports 1 groups for associations
2/24/2010 9:34:00 AM Z-Wave Programming device Z-Wave Living Room Root Device 3 (3) to send wake-up notifications to HomeSeer.
2/24/2010 9:34:00 AM Z-Wave Setting wake-up interval for device Root Device 3 to 1 hours and 0 minutes.
2/24/2010 9:34:01 AM Z-Wave ========== Done with Z-Wave Device with Node ID of 3 ==========
2/24/2010 9:34:04 AM Z-Wave Setting wake-up interval for device Root Device 3 to 1 hours and 0 minutes.
2/24/2010 9:34:04 AM Z-Wave Sensor woke up and value for WAKEUP_INTERVAL was successfully set.
2/24/2010 9:34:09 AM Z-Wave ********** Done with sync of Z-Wave Device with Node ID of 3 **********
2/24/2010 9:34:09 AM Device Update Device: Z-Wave Living Room Child 3 Luminance value set to 70 (7000/%)
2/24/2010 9:34:09 AM Device Update Device: Z-Wave Living Room Child 3 Temperature value set to 68 (6800/F)
2/24/2010 9:34:09 AM Device Update Device: Z-Wave Living Room Child 3 Luminance value set to 76 (7600/%)
2/24/2010 9:34:09 AM Device Update Device: Z-Wave Living Room Child 3 Luminance value set to 79 (7900/%)
2/24/2010 9:34:09 AM Device Update Device: Z-Wave Living Room Child 3 Temperature value set to 67.7 (6770/F)

[loowee]

hsm100

On my part, we have changed all batteries for 5v power supplies and setup the sensors to be awake all time, therefore becoming an additionnal repeater in the mesh network. Flawless since then but no luck whatsoever on batteries, I am pretty sure it has something to do with signal which would be weaker on batteries ( 4.5v compared to 5v on PS ).

Good luck to all !