Aeotec Z-Wave Plus Multi-Sensor 6 - OH Thing Frequently goes offline

I have an Aeotec MS-6 sensor that frequently gets marked as OFFLINE in OH3

[ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:a52e4d9555:node9' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
[ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:a52e4d9555:node9' changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to ONLINE

It seems that the expected time between communications is less than the actual.

Here is an example from 1 hour:

2022-02-04 13:53:37.384 Thing 'zwave:device:a52e4d9555:node9' changed from ONLINE to OFFLINE
2022-02-04 14:16:29.106 Thing 'zwave:device:a52e4d9555:node9' changed from OFFLINE to ONLINE
2022-02-04 14:23:37.440 Thing 'zwave:device:a52e4d9555:node9' changed from ONLINE to OFFLINE
2022-02-04 14:50:34.914 Thing 'zwave:device:a52e4d9555:node9' changed from OFFLINE to ONLINE
2022-02-04 14:53:34.604 Thing 'zwave:device:a52e4d9555:node9' changed from ONLINE to OFFLINE

Does anyone have the same issue with this device? Is there anyway to fix this?
A few minutes later, it wakes up and sends a message and gets marked online again.

This should not be happening for a battery device. I noticed in the Zwave DB several versions of the device. Do you know what one you have? On one version there is a parameter 9 that talks about USB power/awake. If the binding thinks the device should be awake all the time that could be the issue.


Hi @apella12

I checked out my device and I also see the multiple items you noted in the DB. From my node xml I have the following:


Which appears to match 4 items with different FW versions:

I’m not exactly sure how to tell what FW version is on board this device but OH reports this 1.10. What I’m not sure of is it that means that it is assuming that number and using that DB entry or if that was parsed from the device.

For config item #9 that is reported as 257 dec or 100000001 bin. Apparently the MSB is the power mode and 1 = battery mode, so that is correct. However the LSB is sleep state and it it set to 1 so it is supposed to keep awake for 10 mins for battery mode. This seems incorrect

I noticed that the stay awake in battery mode is configurable in parameter 2:

However that appears to already be set to 0.

Not sure if this is related, but another interesting thing is that the device is physically marked as ZW100A while the DB entries are for ZW100. Not sure if that means anything since the mfgr, dev ID, and dev type still match the db.

I would go with the 1.10 version since that is what OH reports.

Also it seems parameter 9 is correct for a battery device. (Could try set the power mode to 0 on parameter 9, but it seems it is set to 0 on parameter 2). So the bad news is that is likely not causing the offline/online problem.

The next level of investigation is to set the Zwave binding to debug and try to catch one of the on/off cycles and see if there are any helpful messages.


1 Like