Aeotec Multisensor 6

[Toonix]

Out of 20 times my Aeotec Multisensor 6 start switching on all my z-wave switches in the house on it's own. I don't know what control-panel does during loading, but the chances that the Multisensor going crazy afterwards are pretty common.

When it happens i need to remove them from my z-wave, reset them and include them again. Guess from now on I should keep the logs when using control panel so that i can analyze it in case they go crazy afterwards.

[daradib]

Have you tried changing the device configuration to Binary Sensor report instead of the Basic default?

[Toonix]

They start to act this after a couple of month but allway after I used zwave-control-panel to add more devices. I'm pretty sure they where on Binary Sensor since they worked a long time.

The support from Aeotec is asking if the association group did change since the log shows this:

2017-04-11 17:30:24.575 Info, Node026, Received Basic set from node 26: level=255. Sending event notification. 2017-04-11 17:30:24.575 Detail, Node026, Notification: NodeEvent 2017-04-11 17:30:24.611 Detail, Node026, Received: 0x01, 0x09, 0x00, 0x04, 0x04, 0x1a, 0x03, 0x20, 0x01, 0xff, 0x31 2017-04-11 17:30:24.611 Detail, 2017-04-11 17:30:24.611 Info, Node026, Received Basic set from node 26: level=255. Sending event notification. 2017-04-11 17:30:24.611 Detail, Node026, Notification: NodeEvent 2017-04-11 17:30:24.705 Detail, Node010, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x0a, 0x03, 0x26, 0x03, 0x63, 0xbd 2017-04-11 17:30:24.705 Detail, 2017-04-11 17:30:24.705 Info, Node010, Received SwitchMultiLevel report: level=99 2017-04-11 17:30:24.705 Detail, Node010, Refreshed Value: old value=0, new value=99, type=byte 2017-04-11 17:30:24.705 Detail, Node010, Changes to this value are not verified 2017-04-11 17:30:24.705 Detail, Node010, Notification: ValueChanged 2017-04-11 17:30:24.757 Detail, Node011, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x0b, 0x03, 0x26, 0x03, 0x63, 0xbc 2017-04-11 17:30:24.757 Detail, 2017-04-11 17:30:24.757 Info, Node011, Response RTT 5995 Average Response RTT 3558 2017-04-11 17:30:24.757 Info, Node011, Received SwitchMultiLevel report: level=99 2017-04-11 17:30:24.757 Detail, Node011, Refreshed Value: old value=0, new value=99, type=byte 2017-04-11 17:30:24.757 Detail, Node011, Changes to this value are not verified 2017-04-11 17:30:24.757 Detail, Node011, Notification: ValueChanged 2017-04-11 17:30:24.785 Detail, Node021, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x15, 0x03, 0x26, 0x03, 0x63, 0xa2 2017-04-11 17:30:24.785 Detail, 2017-04-11 17:30:24.785 Info, Node021, Received SwitchMultiLevel report: level=99 2017-04-11 17:30:24.785 Detail, Node021, Refreshed Value: old value=0, new value=99, type=byte 2017-04-11 17:30:24.785 Detail, Node021, Changes to this value are not verified 2017-04-11 17:30:24.785 Detail, Node021, Notification: ValueChanged 2017-04-11 17:30:24.920 Detail, Node026, Received: 0x01, 0x11, 0x00, 0x04, 0x00, 0x1a, 0x0b, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x07, 0x08, 0x00, 0x00, 0x00, 0x7f

Node026 is the multisensor.

could that be the problem? does control plane change assosiation group during discovery?

[daradib]

Received Basic set means that it's configured as the basic default. It should say Received SensorBinary report when configured as a binary sensor under the configuration tab. The problem might be something else, this is just a suggestion.

[Toonix]

Well this was my first suggestion too and when it happened the first time I went to the console and hammered in binary but as you might know it switches in the console allway back and so I never was sure it worked...So when it still happened I had to remove and include it again...That helps till it starts someday again after I have to use the console.