Announcement

Collapse
No announcement yet.

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

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Thrag
    replied
    Originally posted by Rupp View Post
    Did you try new batteries, these devices do not report battery level correctly so they may need to be replaced.
    I replaced the batteries last night, and when I got home today I did notice that it correctly reported no motion shortly after leaving the garage. So hopefully that was it.

    I was wondering why the batteries seemed to never go down

    Leave a comment:


  • Rupp
    replied
    Originally posted by Thrag View Post
    I just started having a problem where the hsm-100 is never reporting no motion. It was working for a little more than a month, then a few days ago I noticed the garage light I have controlled by the motion sensor never turns off, and the status of the motion detector never changes from 'motion'. I do have the sensitivity set above 200, but it's was working fine like that for a month at least. Any ideas appreciated.
    Did you try new batteries, these devices do not report battery level correctly so they may need to be replaced.

    Leave a comment:


  • Thrag
    replied
    I just started having a problem where the hsm-100 is never reporting no motion. It was working for a little more than a month, then a few days ago I noticed the garage light I have controlled by the motion sensor never turns off, and the status of the motion detector never changes from 'motion'. I do have the sensitivity set above 200, but it's was working fine like that for a month at least. Any ideas appreciated.

    Leave a comment:


  • Guest's Avatar
    Guest replied
    Just received my first HSM100 & motion detection does not work

    Temp, battery and light intensity work fine but motion indicates it has never been set and I cannot get it to update. I have read all the info I can find, but there does not seem to be a consistent procedure for fixing the problem. Can you post the latest summary of what action I should take to fix this issue?

    Thanks

    Leave a comment:


  • Adidas4275
    replied
    after tinkering with the device for a little while and rescanning it I have had it working for about a month or so without issue

    Leave a comment:


  • dschoppe
    replied
    Originally posted by Adidas4275 View Post
    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..
    I don't have any HSM100s yet, but I noticed this in the troubleshooting section of the OEM installation manual:

    Problem: Motion is always detected even when there is no one in the room
    Solution: Lower the Sensitivity Configuration parameter. Note that setting the Sensitivity Configuration parameter above the default of 200 may cause motion to be continuously when EZMotion is battery operated. If EZMotion is operated from an external power supply and the Stay Awake Configuration Parameter is set to a nonzero value, then the Sensitivity can be set above 200.
    See troubleshooting on page 9.
    http://www.expresscontrols.com/pdf/E...wnerManual.pdf

    Could this be the issue?

    Don

    Leave a comment:


  • loowee
    replied
    hsm100

    Same here :/
    And what's worse is that it is pretty much the best sensor I have come across as of today ! Sensor wise of course, power supplies are in deed a major downer...

    Good luck !

    Leave a comment:


  • niewoo
    replied
    If that's what's needed then they won't work in my setup. I hope I can get full refund if that's the case. I would have expected more for $74.

    Leave a comment:


  • loowee
    replied
    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 !

    Leave a comment:


  • niewoo
    replied
    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)

    Leave a comment:


  • niewoo
    replied
    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)

    Leave a comment:


  • Elo
    replied
    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!

    Leave a comment:


  • kaldoon
    replied
    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.

    Leave a comment:


  • loowee
    replied
    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 ?

    Leave a comment:


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

    Leave a comment:

Working...
X