Hi,
I finally switched my network to have my new raz be the primary controller, and have a Aeotec multisensor included in the network. I am working on my own UI to control my network, but I don't understand how the multisensor device works. I know it wakes up periodically. But:
- does it send something to the raz/z-way when it wakes up?
- if so how can I "listen" to that event via the API?
- for motion detection, does that only happen at the wake up interval? Seems not useful in that case?
Sorry for the newbie question - this is my first sensor and I really do not understand how it works in the z-wave context.
Thanks,
P.K.
How does sensors work in z-way/raz?
Re: How does sensors work in z-way/raz?
> does it send something to the raz/z-way when it wakes up?
It usually does. If device supports Wakeup command class (battery devices usually do), it sends a wakeup event, so controller can process queued commands for this device.
> if so how can I "listen" to that event via the API?
Receiving a wakeup event triggers "isAwake" data holder on device object, so you can bind a handler to it (see devices[x].data.isAwake).
> for motion detection, does that only happen at the wake up interval?
When motion is detected, device awakes on itself (regardless of configured wakeup interval) and sends a report to controller. It would be useless indeed to receive a notification hours (or even weeks) after it was triggered
Please note that if several motion events are detected in some relatively short timeframe (usually several minutes, depends on device), the controller may receive only the first one. That is done to not flood the network when there's a continuous motion in the room.
You shouldn't usually listen to wake up events. Just set a handler to actual motion event. All that wakeup things will be handled automatically under the hood.
It usually does. If device supports Wakeup command class (battery devices usually do), it sends a wakeup event, so controller can process queued commands for this device.
> if so how can I "listen" to that event via the API?
Receiving a wakeup event triggers "isAwake" data holder on device object, so you can bind a handler to it (see devices[x].data.isAwake).
> for motion detection, does that only happen at the wake up interval?
When motion is detected, device awakes on itself (regardless of configured wakeup interval) and sends a report to controller. It would be useless indeed to receive a notification hours (or even weeks) after it was triggered
Please note that if several motion events are detected in some relatively short timeframe (usually several minutes, depends on device), the controller may receive only the first one. That is done to not flood the network when there's a continuous motion in the room.
You shouldn't usually listen to wake up events. Just set a handler to actual motion event. All that wakeup things will be handled automatically under the hood.
Re: How does sensors work in z-way/raz?
Thanks pofs, that makes a lot of sense. However it seems not to be working that way. Is there a way for me to check in the logs to see the wake up notificaiton comes in from the sensor?
Instead what I see is: when I click "update all" on the expert UI on the sensor, the command is queued and left in the queue for a very long time (much more than the normal wake up period of 4 minutes).
This is the job queue:
P.K.
Instead what I see is: when I click "update all" on the expert UI on the sensor, the command is queued and left in the queue for a very long time (much more than the normal wake up period of 4 minutes).
This is the job queue:
Code: Select all
n U W S E D Ack Resp Cbk Timeout NodeId Description Progress Buffer
1 W - - - 0.20 9 SensorBinary Get Not delivered to recipient 9 2 30 2 5
0 W - - - 0.20 9 SensorMultilevel V5 Get 9 4 31 4 1 8 5
0 W - - - 0.20 9 SensorMultilevel V5 Get 9 4 31 4 3 8 5
0 W - - - 0.20 9 SensorMultilevel V5 Get 9 4 31 4 5 0 5
Queue length: 4Re: How does sensors work in z-way/raz?
Is the controller set up in association group 1 as discussed here http://aeotec.com/z-wave-sensor/47-mult ... anual.html
Re: How does sensors work in z-way/raz?
Hi pofs,
In my system, i'm constantly polling (every 2 secs) the z-way-server (with the appropriate epoch) and if I detect a node wake, I invoke *.Get() for approved classes, decided by a x-ref of the nodes classes and my list.
I also now have a system whereby do automated *.Get() for non battery devices too
In my system, i'm constantly polling (every 2 secs) the z-way-server (with the appropriate epoch) and if I detect a node wake, I invoke *.Get() for approved classes, decided by a x-ref of the nodes classes and my list.
I also now have a system whereby do automated *.Get() for non battery devices too
Using BMSLink https://linode.bmslink.co.uk with z-way-server. http://linode.bmslink.co.uk:4567
Re: How does sensors work in z-way/raz?
I *think* it is associated because this is the interview result:
*BUT* if I power cycle the sensor, the LED blinks instead of stay steady making me think that the device is not even in the network anymore, and z-way thinks it is in "deep sleep".
Do I need to do an explicit association at inclusion time? I thought that is done by default by the sensor.
P.K.
Code: Select all
/: None (03.01.2015)
1: None (03.01.2015)
max: 5 (03.01.2015)
nodes: 1 (03.01.2015)
supported: true (03.01.2015)
version: 1 (03.01.2015)
security: false (03.01.2015)
interviewDone: true (03.01.2015)
interviewCounter: 9 (03.01.2015)
groups: 1 (03.01.2015)
specificGroup: None (03.01.2015)
Do I need to do an explicit association at inclusion time? I thought that is done by default by the sensor.
P.K.
Re: How does sensors work in z-way/raz?
pkshiu: RaZberry sets iteself in Association groups (if not re-configured).
skiv71: Do Get() periodically (use same period as Wakeup period of this device). This Get will be stored in Queue and transmitted once devices wakes up.
skiv71: Do Get() periodically (use same period as Wakeup period of this device). This Get will be stored in Queue and transmitted once devices wakes up.
Re: How does sensors work in z-way/raz?
pkshiu: blinking LED means the sensor is out of the network or anyhow in trouble. LED ON means in network and awake, OFF is sleeping (or no power;-). When known by the controller, just pushing the button should include it again. Putting parameter 2 to 1 will keep it awake the first ten minutes after inserting the batteries, that gives you the time to interview or configure it easily.
My experience: on USB power the sensor stays awake and works as it should.
On battery, don't try to use another wake up time. I saw it wake up anyhow on 240 sec (led ON), but only telling the controller at the 480 sec configured, not helping to save batteries. Test not (yet) repeated due to next problem that should be solved first.
On battery I found that it looses contact/synchronisation with the controller, resulting in a blinking led and very soon empty batteries. The reason is linked to the communication with the controller. In a normal cycle it sends a wake up notification, controller puts it back to sleep (behaviour seen in the logs; a little strange as the manual gives me the impression the sensor will do that itself too). But when it wants to send some sensor values, the controller is sometimes too fast to put it to sleep again (logs about some ABORT on that) and the sensor gives up with a blinking led, needing a reset. After less than some hours the thing is blocked. So, I guess we'll need some update on the controller software for that.
My experience: on USB power the sensor stays awake and works as it should.
On battery, don't try to use another wake up time. I saw it wake up anyhow on 240 sec (led ON), but only telling the controller at the 480 sec configured, not helping to save batteries. Test not (yet) repeated due to next problem that should be solved first.
On battery I found that it looses contact/synchronisation with the controller, resulting in a blinking led and very soon empty batteries. The reason is linked to the communication with the controller. In a normal cycle it sends a wake up notification, controller puts it back to sleep (behaviour seen in the logs; a little strange as the manual gives me the impression the sensor will do that itself too). But when it wants to send some sensor values, the controller is sometimes too fast to put it to sleep again (logs about some ABORT on that) and the sensor gives up with a blinking led, needing a reset. After less than some hours the thing is blocked. So, I guess we'll need some update on the controller software for that.
Re: How does sensors work in z-way/raz?
For anyone else having problems with the Aeotec multisensor, I just wanted to add that I had the same problem after trying to change the wakeup time. I have two multisensors, one on battery and one on USB. The one on battery I just associated with the network and left alone--it works perfectly. On the other, I tried lowering the wakeup interval (because it was on USB power) and it seems to exhibit the symptoms mentioned above. I put it back on battery and indeed the light would go solid right after re-inclusion, then blink while jobs for it just sat in the queue indefinitely. Back on USB power the light remains on all the time, but I still cannot send it commands unless I wake it up manually and even then it is hit-or-miss. And the controller reports it as "deep sleep" even though the LED is on. Anyway, from my sample size of two, these sensors get glitchy if you play with the wakeup settings.