Page 1 of 1
HSM100 Motion issue
Posted: 30 May 2013 07:25
by phu2
I just installed the Razberry and got it paired with a HSM100 mutli sensor. The temperature and luminescence appear to be updated but the motion detection will not register motion. It has a state of Idle but will not trip or blink the led when motion is in front of it. I can reset it wit the button on the side and it will work one time but then it goes idle. Any one have a similar issue or some insight into this?
Make sure the HSM100 is
Posted: 30 May 2013 07:25
by PoltoS
Make sure the HSM100 is associated with RaZberry
If associated with Razberry...
Posted: 30 May 2013 07:25
by JV
... it updates the state of the Razberry, not the device itself. Example below, where I tripped the motion sensor (device 7), but it updates the state of device 1:
[2013-06-15 07:09:24.905] RECEIVED: ( 01 09 00 04 00 07 03 20 01 FF 28 )
[2013-06-15 07:09:24.918] SENT ACK
[2013-06-15 07:09:24.919] SETDATA devices.7.data.failureCount = Empty
[2013-06-15 07:09:24.921] SETDATA devices.7.data.lastReceived = 0 (0x00000000)
[2013-06-15 07:09:24.923] SETDATA devices.1.instances.0.commandClasses.32.data.level = 255 (0x000000ff)
All HSM100 update same level
Posted: 30 May 2013 07:25
by JV
I associated one more HSM100/EZMotion and it also updates the same gateway instance:
Experiment, I trigger both devices, this is the logging for first device:
[2013-06-15 07:37:52.031] RECEIVED: ( 01 09 00 04 00 0E 03 20 01 FF 21 )
[2013-06-15 07:37:52.044] SENT ACK
[2013-06-15 07:37:52.046] SETDATA devices.14.data.failureCount = Empty
[2013-06-15 07:37:52.048] SETDATA devices.14.data.lastReceived = 0 (0x00000000)
[2013-06-15 07:37:52.050] SETDATA devices.1.instances.0.commandClasses.32.data.level = 255 (0x000000ff)
And second device immediately after the first:
[2013-06-15 07:37:55.072] RECEIVED: ( 01 09 00 04 00 07 03 20 01 FF 28 )
[2013-06-15 07:37:55.085] SENT ACK
[2013-06-15 07:37:55.087] SETDATA devices.7.data.failureCount = Empty
[2013-06-15 07:37:55.089] SETDATA devices.7.data.lastReceived = 0 (0x00000000)
[2013-06-15 07:37:55.091] SETDATA devices.1.instances.0.commandClasses.32.data.level = 255 (0x000000ff)
Both update device[1] instance[0] command class 32 data level. No means to find out who did it.
I would expect a similar message to device 14 and 7 respectively.
I got your problem. This is
Posted: 30 May 2013 07:25
by PoltoS
I got your problem. This is because the device send Set command (so, it goes to the RaZberry data structure) and not Report. Before we had "mylevel" strucutre for Basic on each device. This contained values sent by the device itself using the Set (in contrast to "level" sent to the device by RaZberry and others). This made it possible to use differenciate the source, but not the target.
We will probably consider to restore this dataholder back.
Can you describe your usecase in more details?
Use case: See that alarm was triggered
Posted: 30 May 2013 07:25
by JV
No way to detect that now...
Or update the light bulb on your web GUI when someone presses a Duwi zwave.me switch.
Any progress on this? I have
Posted: 30 May 2013 07:25
by rosomp
Any progress on this? I have an
http://aeotec.com/z-wave-sensor and it has the same issue. The device triggered does not update immediately.
I have a door sensor and all changes are triggered and notified immediately.