AEON Labs/MultiSensor 6 no requests to mqtt

[fastvd]

Checklist

• I am not using Home Assistant. Or: a developer has told me to come here.
• I have checked the troubleshooting section and my problem is not described there.
• I have read the changelog and my problem is not mentioned there.

Deploy method

Docker

Z-Wave JS UI version

3.17.0

ZwaveJS version

0.9.0

Describe the bug

i have some MultiSensor 6 sensors from AEON Labs, they have been working great with my Fibaro HC3 for a few years now...I have now bought a z-wave dongle Z-stick 7 from Aeotec to try and work live with my HA which has been for a few has been running on Raspber for years...
on HC3, the sensors worked with firmware 1.12, when I connected them to Z-Wave JS UI, I immediately noticed the problem that the sensor did not give the MOTION status correctly. I updated the firmware to 1.17 and this problem disappeared.

To Reproduce

but yesterday just like that, 2 of my sensors out of 3 that I transferred to HA+Z-Wave JS UI stopped giving their status in HA...I thought it was a problem with Z-Wave JS UI, but when I went to the EVENTS tab , then I see that the sensor sends data to the Z-Wave JS UI itself, but it does not get to the MQTT broker and according to HA itself. Restarting the broker and HA itself did not help.

Expected behavior

i put those 2 problem sensors back on the HC3 and everything started working fine again. At the same time, 2 Fibargroup Double Switch 2 FGS223 relays are still working without any problems. And also, for the test, I transferred the Danfoss Popp Wireless Thermostatic Valve TRV 010101 battery device, the data comes with it, but there is a problem that when HA starts, it starts in the OFF status... I overcame this with simple automation, but the fact remains!

Additional context

No response

[robertsLando]

Hi @fastvd and thanks for your issue, could you attach some Application logs that show the event coming? Better with debug enabled, debug should show when a message is published to mqtt, we should see the event coming and then a consecutive publish and if not an error.

[kpanchen]

This sensor works perfectly fine with Z-Wave JS since I've started using it, I have a few of them and currently on firmware 1.13 (latest for my version of the sensor).

1. You cannot have version 1.12 and update to 1.17 (or from 1.17 go back to 1.12), there's an explanation on the AEOTEC website here: https://aeotec.freshdesk.com/support/solutions/articles/6000036562-how-to-update-multisensor-6-z-wave-firmware-
   You need to pick a proper version for your sensor.

2. Sensor can report motion in two modes: binary and notification, which one is sent by sensor depends on the configuration parameter 5 which exposed in UI.

[fastvd]

I read what is written on the website, but still I updated 3 sensors from 1.12 to 1.17...
1 piece still works on z-wave JS UI, and the 2 pieces that started to malfunction on z-wave JS UI I transferred back to fibaro hc3 and they still work perfectly there!
PS: I'm more than sure that if I return them to z-wave JS UI again, they will start working correctly there again... there is some problem with z-wave JS UI that I haven't caught yet!

[robertsLando]

@AlCalzone any clue?