Aeotec Multisensor6 not reporting to zwave2mqtt

Configuration Z-Wave
1

I think I am stuck with the problem that the Aeotec Multisensor 6 does not report in regular intervals or when the PIR motion sensor is activated.

I am using HASS.io with the zwave2mqtt add-on. The Aeotec Zstick and the sensor are properly discovered and I can talk to both, I can see their configuration parameters in zwave2mqtt and even change them. So it seems that the zwave networking is properly working.

I configured the sensor to report certain sensor values in regular intervals (see screenshot below), but all I see in MQTT-Explorer are config parameters, auto-discovery descriptions and the like, but no actual sensor readings.

I have a short polling interval for the gateway and I see this in the debugging console with time delay as the pollign interval:
OpenZWave Info, Node003, ApplicationCommandHandler - Unhandled Command Class 0x31
OpenZWave Detail, Node003, Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x03, 0x06, 0x31, 0x05, 0x03, 0x0a, 0x00, 0x04, 0xcb
OpenZWave Detail

Node003 is the Aeotec Multisensor6.

Somebody who may help?

blurp
blurp738×1546 69.7 KB

2

I have no knowledge of zwave in hass, but I know that there was some issue with the aeotec multusensot and a firmware update is avalailable. Do you have that firmware?

3

The sensor was 1.12 and I am upgrading to 1.13 in this moment. lets see-

4

The firmware update to 1.13 worked. not sure what was the problem, but the reporting seems to happen now, but a lot of other problems with it. Will do a seperate posting on that.

5

Cool, please use “mark as solution” for others.

6

Actually I am not sure that this was the solution. I think the main culprit was that “Basic Set” just does not work for motion sensors and the sensor (48-1-0) needs to be set to “Binary sensor report”.

But if that does not help, go and upgrade the firmware.