Aeotec MultiSensor 6 - Motion Detection

TheDarthFather · February 20, 2020, 10:26pm

Hello,
I installed HA on a Synology NAS using the HA docker image.
I am testing an Aotec Multisensor 6 in 1.
I paired it succesfully and HA receives data every 1h.
However for motion detection I need real time data.

So, using a guide from HA, I’ve tried setup the Aotect node “Command Options” to “Binary Sensor Report”.
It seems is saved … but it does not seem to detect anything.
I tried an automation from the standard ones … Turn On The Light when motion is detected … but I dont have any available trigger so I assume something is not ok.

Is there any way to debug this to make sure I am not missing anything ?

Thank you!

firstof9 · February 21, 2020, 2:54pm

So you woke up the node then sent the configuration options via the zwave control panel to set the sensor to Binary Sensor Report?

TheDarthFather · February 21, 2020, 6:34pm

Hi,
Actualy it works … it seems after a few tries the settings were corectly “saved”.
I did one test automation (test if status changes from 0 to 8) and it works.

I still have a few questions:

When motion is detected I see the status changes in 8 in general … and once changed in 3 … what is the difference (screen below) ?
If I create the predefined automation (Turn On The Light when motion is detected) and try to use the template, I can’t link the motion sensor … (Add Binary Sensor of Type Motion device) . Is there any specific setup to make sure this is recognised as such ?

freshcoast · February 21, 2020, 6:43pm

A value of 3 means the cover was open (“Tampering (case opened)”). Did you open and close it?

firstof9 · February 21, 2020, 6:49pm

Per the tech sheet:

Tampering Product covering removed 0x03 Vibration is triggered

The binary sensor hasn’t been loaded since it’s not set to Binary Sensor Report

Parameter 5 (0x05)
Which command would be sent when the motion sensor triggered.
1 = send Basic Set CC.
2 = send Sensor Binary Report CC.

To get the binary sensor you are looking for Parameter 5 has to be set to 2.

OR
Make a binary sensor template based on the burglar sensor state switching from 0 (No motion) to 8 (Motion detected)

In case you want their tech sheet it’s here

TheDarthFather · February 21, 2020, 8:30pm

Ok … I am officialy lost
Here is what I did to setup the Binary :

Selected everything as in the printscreen below.
Preseed on the sensor back-button
Pressed on Setconfig Parameter button …
…

image737×803 16.9 KB

firstof9 · February 21, 2020, 8:34pm

You have to wake the sensor up before pressing “Set config parameter”

freshcoast · February 21, 2020, 8:35pm

You want to reverse steps 2 and 3. Press the “Set Config Parameter” first, which will queue up the config change. Then when you wake up the device, the command will be sent. Otherwise, if you wake up the device first, it may go back to sleep before you send the command.

firstof9 · February 21, 2020, 8:40pm

Hmmm the manual says it’s suppose to stay awake for 10 mins when you manual wake it…

firstof9 · February 21, 2020, 8:42pm

You’re doing these steps?

Manual:

Waking up Multisensor 6.

In order to configure Multisensor 6, you must either (1) wake up Multisensor 6 using the below button press function, or (2) temporarily put your Multisensor 6 on USB power. 

1. Press and hold Multisensor 6 Action button

2. Wait until the RGB LED turns into a Yellow/Orange Color

3. Release Multisensor 6 Action Button

The LED on Multisensor 6 will now rapidly blink its Yellow/Orange LED while it is in its awake state. You may send in any configurations or commands from your current gateway to configure your Multisensor 6.

4. Tap the Action Button on Multisensor 6 to put Multisensor 6 back to sleep, or wait 10 minutes. (recommended to manually put it back to sleep to conserve battery life).

freshcoast · February 21, 2020, 8:44pm

Well, with a wake up time like that, you could do it either way!

I think typical time is maybe 10 seconds, some are much faster, sometimes it’s configurable. The safe way (IMO) is to just queue up the command and let OZW send it at the right time.

The missing step is probably the “press and hold”, not just a press.

TheDarthFather · February 21, 2020, 8:48pm

It seems is going back to slep very fast ?

2020-02-21 20:45:35.547 Detail, Node005, Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x05, 0x06, 0x73, 0x06, 0x01, 0x01, 0x00, 0x14, 0x95
2020-02-21 20:45:35.547 Detail,
2020-02-21 20:45:35.547 Info, Node005, Received a PowerLevel Test Node report: Test Node=1, Status=Success, Test Frame ACK Count=20
2020-02-21 20:45:35.547 Detail, Node005, Initial read of value
2020-02-21 20:45:35.547 Detail, Node005, Initial read of value
2020-02-21 20:45:35.547 Detail, Node005, Initial read of value
2020-02-21 20:45:35.547 Detail, Node005, Notification: ValueChanged
2020-02-21 20:45:35.549 Detail, Node005, Notification: ValueChanged
2020-02-21 20:45:35.551 Detail, Node005, Notification: ValueChanged
2020-02-21 20:45:35.680 Detail, Node005, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x05, 0x05, 0x70, 0x06, 0x07, 0x01, 0xff, 0x7f
2020-02-21 20:45:35.702 Detail,
2020-02-21 20:45:35.702 Info, Node005, Received Configuration report: Parameter=7, Value=255
2020-02-21 20:45:35.703 Detail, Node005, Notification: ValueAdded
2020-02-21 20:45:37.841 Info, Node005, Value::Set - COMMAND_CLASS_CONFIGURATION - Command Options - 5 - 1 - Binary Sensor Report
2020-02-21 20:45:37.842 Info, Node005, Configuration::Set - Parameter=5, Value=2 Size=1
2020-02-21 20:45:37.842 Detail, Node005, Queuing (Send) ConfigurationCmd_Set (Node=5): 0x01, 0x0c, 0x00, 0x13, 0x05, 0x05, 0x70, 0x04, 0x05, 0x01, 0x02, 0x25, 0x7b, 0xcc
2020-02-21 20:45:37.842 Detail, Node005, Queuing (Send) ConfigurationCmd_Get (Node=5): 0x01, 0x0a, 0x00, 0x13, 0x05, 0x03, 0x70, 0x05, 0x05, 0x25, 0x7c, 0xc9
2020-02-21 20:45:37.842 Detail,
2020-02-21 20:45:37.842 Info, Node005, Sending (Send) message (Callback ID=0x7b, Expected Reply=0x13) - ConfigurationCmd_Set (Node=5): 0x01, 0x0c, 0x00, 0x13, 0x05, 0x05, 0x70, 0x04, 0x05, 0x01, 0x02, 0x25, 0x7b, 0xcc
2020-02-21 20:45:37.849 Detail, Node005, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-02-21 20:45:37.899 Detail, Node005, ZW_SEND_DATA delivered to Z-Wave stack
2020-02-21 20:45:42.132 Detail, Node005, Received: 0x01, 0x07, 0x00, 0x13, 0x7b, 0x01, 0x01, 0xac, 0x3c
2020-02-21 20:45:42.132 Detail, Node005, ZW_SEND_DATA Request with callback ID 0x7b received (expected 0x7b)
2020-02-21 20:45:42.132 Info, Node005, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2020-02-21 20:45:42.132 Warning, Node005, WARNING: Device is not a sleeping node.
2020-02-21 20:45:42.132 Detail, Node001, Expected callbackId was received
2020-02-21 20:45:42.132 Detail, Node001, Expected reply was received
2020-02-21 20:45:42.132 Detail, Node001, Message transaction complete
2020-02-21 20:45:42.132 Detail,
2020-02-21 20:45:42.132 Detail, Node005, Removing current message
2020-02-21 20:45:42.132 Detail,
2020-02-21 20:45:42.132 Info, Node005, Sending (Send) message (Callback ID=0x7c, Expected Reply=0x04) - ConfigurationCmd_Get (Node=5): 0x01, 0x0a, 0x00, 0x13, 0x05, 0x03, 0x70, 0x05, 0x05, 0x25, 0x7c, 0xc9
2020-02-21 20:45:42.143 Detail, Node005, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-02-21 20:45:42.143 Detail, Node005, ZW_SEND_DATA delivered to Z-Wave stack
2020-02-21 20:45:46.256 Detail, Node005, Received: 0x01, 0x07, 0x00, 0x13, 0x7c, 0x01, 0x01, 0x9c, 0x0b
2020-02-21 20:45:46.256 Detail, Node005, ZW_SEND_DATA Request with callback ID 0x7c received (expected 0x7c)
2020-02-21 20:45:46.256 Info, Node005, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2020-02-21 20:45:46.256 Warning, Node005, WARNING: Device is not a sleeping node.
2020-02-21 20:45:46.256 Detail, Node001, Expected callbackId was received
2020-02-21 20:45:52.133 Error, Node005, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-02-21 20:45:52.133 Detail, Node005, Removing current message
2020-02-21 20:45:52.133 Detail, Node005, Notification: Notification - TimeOut

firstof9 · February 21, 2020, 8:49pm

Once the switch to OZW 1.6 hits things like this won’t be much of an issue, they should just work.

Are you using the USB power option with the sensor @TheDarthFather ?

Your log shows the command being sent, but no ACK was returned to confirm the setting was accepted

TheDarthFather · February 21, 2020, 8:51pm

I am on bateries …

firstof9 · February 21, 2020, 8:53pm

Ok so you’re holding the button for about 3 seconds, the LED turns yellow/orange and blinks fast right?

TheDarthFather · February 21, 2020, 8:53pm

yes, indeed

TheDarthFather · February 21, 2020, 8:55pm

Doing it again:

2020-02-21 20:54:05.221 Detail, Node005, Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x05, 0x06, 0x73, 0x06, 0x01, 0x01, 0x00, 0x14, 0x95
2020-02-21 20:54:05.221 Detail,
2020-02-21 20:54:05.221 Info, Node005, Received a PowerLevel Test Node report: Test Node=1, Status=Success, Test Frame ACK Count=20
2020-02-21 20:54:05.221 Detail, Node005, Refreshed Value: old value=1, new value=1, type=byte
2020-02-21 20:54:05.221 Detail, Node005, Changes to this value are not verified
2020-02-21 20:54:05.221 Detail, Node005, Refreshed Value: old value=1, new value=1, type=list
2020-02-21 20:54:05.221 Detail, Node005, Changes to this value are not verified
2020-02-21 20:54:05.221 Detail, Node005, Refreshed Value: old value=20, new value=20, type=short
2020-02-21 20:54:05.221 Detail, Node005, Changes to this value are not verified
2020-02-21 20:54:05.221 Detail, Node005, Notification: ValueChanged
2020-02-21 20:54:05.223 Detail, Node005, Notification: ValueChanged
2020-02-21 20:54:05.224 Detail, Node005, Notification: ValueChanged
2020-02-21 20:54:05.358 Detail, Node005, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x05, 0x05, 0x70, 0x06, 0x07, 0x01, 0xff, 0x7f
2020-02-21 20:54:05.358 Detail,
2020-02-21 20:54:05.358 Detail, Node005, Refreshed Value: old value=255, new value=255, type=byte
2020-02-21 20:54:05.358 Detail, Node005, Changes to this value are not verified
2020-02-21 20:54:05.358 Info, Node005, Received Configuration report: Parameter=7, Value=255
2020-02-21 20:54:05.358 Detail, Node005, Notification: ValueChanged

firstof9 · February 21, 2020, 8:56pm

Once it’s blinking it should accept the config setting, and keep blinking until you push the button again.

TheDarthFather · February 21, 2020, 9:02pm

Is not consistent:

Either is blinking for 2-3 secs, goes green and shuts doewn
Either start with green and dies in a few secs …

PS: This is more frustarting than learning linux 25 years ago when they had no drivers

firstof9 · February 21, 2020, 9:03pm

Try plugging USB power into it then try. The manual says that is an option.
Likely less frustration that way too.