Switched sensor from USB to battery powered but HA/OZW doesn't get it

Hi,

I recently got an Aeotec Multisensor 6.
I used the supplied USB cable to power the sensor until I had it included in HA and finished its configuration.
Yesterday I put batteries in that thing and removed the USB power connection.

Now HA (or the OZW stack in HA) still seems to think that the node is on “wall power”, because everytime I start HA, I get ZWave errors in OZW_Log.txt and messages that seem to indicate that the node should be available at all times, like:

 Detail, Node021,   ZW_SEND_DATA Request with callback ID 0x13 received (expected 0x13)
 Info, Node021, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
 Warning, Node021, WARNING: Device is not a sleeping node.
 Error, Node021, ERROR: node presumed dead

What can I do to convince HA otherwise?
I already did a node_refresh but that didn’t change anything.

Sebastian

IIRC, this is mentioned in the Aeotec Manual, but you have to pair the sensor according to the way it will be used (wired vs. battery), and if you change the power method, you have to re-pair it.

I’m going by memory here, but you might want to verify in the manual.

I looked at the Aeotec user manual and also the (more detailed) tech manual, but I found no mentioning of this - in the contrary, the user guide says:

For the purposes of installation and setup, even if you intend to power your sensor with batteries, we recommend utilizing the provided USB cable for setup

This recommendation would not make any sense if removing/re-including of the sensor was necessary to switch to battery power, since all settings go back to factory defaults when removing the sensor from the network.

Sebastian

The settings on the device do not revert to default when you remove the sensor from the network.

I think I remember seeing the statement in the pairing section. I’ll be able to verify when I get home tonight.

I think you’re half right :wink:
Removing and re-including the sensor seems to have resolved the issue.
The node is now marked asleep when it doesn’t answer - instead of declared dead.

Unfortunately the sensor seems to have lost all customized settings, which is not that big of a deal since I wrote them all down…

Sebastian

:smile:

I’ve unpaired and re-paired my multisensor a bunch of times and I’ve never seen it lose the customize settings. Not sure what’s going on there.

1 Like

Thanks a lot! I don’t have this passage in the PDF manual I downloaded, so apparently they changed the behavior and your version seems to be newer.

Sebastian.