Greetings All,
I only have one HSM100 (always a little scared to buy another). Here is an ongoing issue I have had for over 2 years.
Right out of the box, or after the HSM100 batteries were replaced, no motion would be reported. Homeseer worked with me to make sure all the settings and configs were correct, but determined it needed to be replaced. This single unit was replaced 3 times.
I found that it you mess with it enough hitting the config button, turn it away for 10 min, constant motion, or rescan it, etc. It would eventually start working. I really never found the pattern that worked.
I got the best of me, so I disabled all my motion scripts for he last 6 months. Having a z-wave system w/o an occupancy sensor, is well, a little boring. If I am going to install a product, it has to work 100% of the time, no burps.
I decided to give it another go a few days ago. Replaced the batteries, and programmed it back into the system. Same issue. I messed with it for days and found out that after you hit the blue config button, make you changes, you have to let it timeout the 10 mins, and here is the trick that seems to work 100% of the time so far....you have to hit the blue button AGAIN (don't change any settings this time), and let it timeout. It then works like a champ. I have repeated this procedure about 10 times now.
Anyway, I know there are others that are having other issues with the HSM100, but not similar to mine. So, I am wondering if it is my older first generation z-wave HA-22 transmit/receiver? I know it is not capable of sending out optimiziation commands, so what other problems lurk with it? I know its effective range is < 20 feet (otherwise I get timeout errors on any sensor). I have on order the new Z-Stick-S2 (arrives Tuesday) to see if that solves these issues, plus the HSM100 issue.
By the way, what about the ZIR000 as reliable motion sensor. Anyone mess with that? Should I switch that that or another alternative?
I only have one HSM100 (always a little scared to buy another). Here is an ongoing issue I have had for over 2 years.
Right out of the box, or after the HSM100 batteries were replaced, no motion would be reported. Homeseer worked with me to make sure all the settings and configs were correct, but determined it needed to be replaced. This single unit was replaced 3 times.
I found that it you mess with it enough hitting the config button, turn it away for 10 min, constant motion, or rescan it, etc. It would eventually start working. I really never found the pattern that worked.
I got the best of me, so I disabled all my motion scripts for he last 6 months. Having a z-wave system w/o an occupancy sensor, is well, a little boring. If I am going to install a product, it has to work 100% of the time, no burps.
I decided to give it another go a few days ago. Replaced the batteries, and programmed it back into the system. Same issue. I messed with it for days and found out that after you hit the blue config button, make you changes, you have to let it timeout the 10 mins, and here is the trick that seems to work 100% of the time so far....you have to hit the blue button AGAIN (don't change any settings this time), and let it timeout. It then works like a champ. I have repeated this procedure about 10 times now.
Anyway, I know there are others that are having other issues with the HSM100, but not similar to mine. So, I am wondering if it is my older first generation z-wave HA-22 transmit/receiver? I know it is not capable of sending out optimiziation commands, so what other problems lurk with it? I know its effective range is < 20 feet (otherwise I get timeout errors on any sensor). I have on order the new Z-Stick-S2 (arrives Tuesday) to see if that solves these issues, plus the HSM100 issue.
By the way, what about the ZIR000 as reliable motion sensor. Anyone mess with that? Should I switch that that or another alternative?
Comment