Announcement

Collapse
No announcement yet.

HS-MS100 stuck on motion

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    HS-MS100 stuck on motion

    Problem Solved! Must be inches away from the Znet when you do the include.

    I just got 3 of these and I can't get any of them to work. I was able to include them and they indicate motion after that one time only. They are stuck on motion. I changed the time out setting to 10 seconds from the default of 600 seconds but it doesn't help. I am running the zwave plug-in 3.0.2.0 and HSPro 3.0.0.531. Is there more detailed instructions somewhere? The instruction sheet that it comes with is woefully short on detail about the settings. What's the secret?

    The secret (or more likely something I forgot about) is that when you do an include the device needs to be close to the Zwave controller or else you won't get a complete registration and setting of parameters. That's the case here. I excluded these motion detectors and then re included them with the devices held within inches from the Znet controller. Now they all work as they should. The first time I included them they were 5 feet from the Znet on the other side of a wall. I figured it would be close enough as it has been for other devices but not these motions.

    #2
    Hi noopara,
    I have the same issue my new HS-MS100+ is stuck on Motion. I excluded it and did an include with it a few inches from the Z-NET as you found. Mine is still stuck on Motion.
    My Z-NET is also brand new. My only Z-Wave device so far. Did you find anything else required to get the Motion Sensor working? I also need to do a factory reset on the HS_MS100+ first before the include or exclude. Now that I have it included I can do the "Test Connectivity" and retrieve the Settings from the motion sensor if I wake it up first,
    I reset the timeout from 600 seconds to 30 seconds and set the polling interval to 1 minute, trying to get it working BUT no luck. I too am interested in better instructions.
    Any suggestions you may have would be greatly appreciated.

    Thanks
    Tom

    Comment


      #3
      If the HS-MS100+ is the only Z-Wave device you have you must make sure that it's not to far from your Z-NET. Run the optimize routine for the Z-Net. The more Z-Wave devices you have the better. I have 44 Z-Wave devices spread all over my house so I have a wide mesh without any problems in communicating with any device. The three HS-MS100+ motions that I have are all working ok. The only down side of these is that in a high traffic areas the batteries won't last very long. I have one of them outside under the eve over the back door of my garage to trigger a flood light to come on at night. After a few months the battery is already at 70%. It works for now but will probably eventually fail from weather exposure. I will probably end up replacing it with a hard wired unit.

      Comment


        #4
        Hmm, I have the same problem. Brand new Z-Wave USB stick, 3 new sensors and nothing works. The software does not even pull the battery levels and is stuck in "motion". Will open a ticket with HS and return the junk.

        Comment


          #5
          i bought a dozen of these a while back but only got around to using a couple. Just installed a new one tonight and setup went fine -- until I put the back on and put it on the wall. Then it exhibited "stuck on motion", which led me to this thread. Even with short (20 sec) timeout, it never reset. After an hour or two of of tinkering, I found that WITHOUT the back it worked fine, but WITH the back it failed. SO, i pulled out that little round foam piece that pushes against the battery -- and now it works great.

          Not clear exactly why that foam is needed anyway -- the battery plugs in super tight. Also no idea why it would cause an issue -- maybe some mechanical stress on the circuit or something.... But clearly my device doesn't like the foam, so it's gone. Those of you having trouble may want to experiment.

          Comment


            #6
            Originally posted by TheGerman View Post
            Hmm, I have the same problem. Brand new Z-Wave USB stick, 3 new sensors and nothing works. The software does not even pull the battery levels and is stuck in "motion". Will open a ticket with HS and return the junk.
            I'm starting to feel the same way...Can't get my cameras setup, none of my motion sensors work properly, support responses are really slow. I was really excited to start this project but didn't expect to fight with everything every step of the way. Only thing that worked out of the box was the SmartStick+ and my leak detector.

            Comment


              #7
              I'm having the same problem. I have 2 of these and had issues with the one that's been running for a year or so now and it got stuck on motion.
              Just changed it out to the "backup" and it has the same issue. I even took out the foam. Didn't make any difference. it's still stuck with a timeout of 5 minutes.
              Seems to me that either something changed and HS doesn't see the no motion or these sensors all decided to quit cooperating all at once all over the world. :P
              Either way... I'm not happy with these sensors. These 2 are replacements for another pair that ate batteries.

              Comment


                #8
                Have two out of three of these motion sensors stuck on motion as well. Set to 30 second timeouts.


                pace

                Comment


                  #9
                  I gave up on them after 4 have failed and picked up the Fibaro eyeball. So far, it's been pretty good except for losing zwave once. Had to reset it.
                  My most reliable motion sensors have been the ecolink brand.

                  Comment


                    #10
                    Have you guys tried to optimise the device( must be done individually because it is a end device, even with usb power)

                    Comment


                      #11
                      Optimizing won't fix a stuck open. Only thing that fixed it was a complete reset.

                      Comment

                      Working...
                      X