Hello,
Received my first HS-MS100+ motion sensor yesterday.
I am running the Z-Wave S2 security beta plugin, 3.0.2.229.
The product description and manual indicate that when this device is line powered, via the micro USB power port, that it will behave as a repeater.
I take this to indicate that it should behave as an always-listening node, that it should respond to optimize and audit commands without having to be woken up via the service button.
I have tried including the motion sensor in several different fashions:
S2 secure, battery removed and line powered.
S2 secure, battery inserted and line powered.
S0 unsecure, battery removed and line powered.
S0 unsecure, battery inserted and line powered.
In each case, the motion sensor was excluded from the network and factory reset via a 20 second button push, before being re-included.
In each case, the motion sensor would not behave as a repeater/listening node:
Optimize commands would fail, node could not be reached.
Node audit would fail, unable to send frame to node.
As a battery powered device, it's operating perfectly. I see a root node with motion sensor and battery status child devices. Battery status updates when the included with a battery, and the motion detection works.
Optimize commands work fine if I press the service button during the optimization.
However I was really hoping this would behave as a repeater to strengthen my z-wave network.
What am I doing wrong, is there a particular song and dance I must do during inclusion to alter the behaviour?
Is there a particular configuration parameter I have to push to the device?
Am I misunderstanding the meaning of "acts as a repeater"?
Or is it simply not working as intended?
Cheers.
Received my first HS-MS100+ motion sensor yesterday.
I am running the Z-Wave S2 security beta plugin, 3.0.2.229.
The product description and manual indicate that when this device is line powered, via the micro USB power port, that it will behave as a repeater.
I take this to indicate that it should behave as an always-listening node, that it should respond to optimize and audit commands without having to be woken up via the service button.
I have tried including the motion sensor in several different fashions:
S2 secure, battery removed and line powered.
S2 secure, battery inserted and line powered.
S0 unsecure, battery removed and line powered.
S0 unsecure, battery inserted and line powered.
In each case, the motion sensor was excluded from the network and factory reset via a 20 second button push, before being re-included.
In each case, the motion sensor would not behave as a repeater/listening node:
Optimize commands would fail, node could not be reached.
Node audit would fail, unable to send frame to node.
As a battery powered device, it's operating perfectly. I see a root node with motion sensor and battery status child devices. Battery status updates when the included with a battery, and the motion detection works.
Optimize commands work fine if I press the service button during the optimization.
However I was really hoping this would behave as a repeater to strengthen my z-wave network.
What am I doing wrong, is there a particular song and dance I must do during inclusion to alter the behaviour?
Is there a particular configuration parameter I have to push to the device?
Am I misunderstanding the meaning of "acts as a repeater"?
Or is it simply not working as intended?
Cheers.
Comment