Aeotec ZWA039 & zwavejs2mqtt - no battery reporting

Hardware
1

Not sure if this is the correct place to share this… if not, please direct me elsewhere!

I’m running the latest version of zwavejs2mqtt as a standalone container on a Pi. I have multiple Zwave devices, all working without issue. I have recently added 5x Aeotec ZWA039s (aërQ Temperature and Humidity Sensor v2.0). These devices are reporting their temperature and humidity without issue, but they are not providing their current battery status.

Has anyone else experienced this? Is there a configuration flag I need to change?

Any comments would be appreciated.

J.

2

I know this sounds dumb but I’ve spent months chasing this same issue on multiple aeotec sensors (including this one) and what I accidentally learned this weekend is that removing the battery and replacing it on all the aeotec devices that weren’t reporting battery, immediately started reporting battery. This is after probably close to 30 remove/re-adds over the last 3 months with me trying to get the battery to work (because some of my aeotec sensors have always detected battery).

3

Thank you for your suggestion. I will try that… hopefully the reporting of battery is not a one-time transmit when the device first powers up!

4

Hi. Mine is reporting false for low battery but 0% battery. It is a new good battery. I tried taking it out and putting it back, but no effect. Any advice?
Thanks!

5

Unfortunately, ~48h after re-inserting battery, the device is once again showing as battery status unavailable.

I seem to remember that Nabu Case had brought zwavejs2mqtt under its wing? Is there a proper forum/place to report bugs?

6

Not sure if you resolved this or not but what usb dongle are you using? I use the aeotek gen 5 and have no problems worth mentioning.

When I used the conbee and another type (can’t remember) for testing I had a TON of issues with almost every type of device that I never experienced with the Gen5

7

I can add that I got one of these devices in early June, and have not had any problem with it reporting battery levels.

8

This is late, but just for the sake of the thread, I have seven of these and they’ll report battery for a while - and then all of a sudden drop to 0% and stop reporting.

There was a firmware update in November 2022 that supposedly fixed it, and introduced the ability to do a battery calibration, but I’m still seeing the 0% reports.

9

Hi guys,
I experience the same issues with the ZWA039 and obviously there is a fw update available:
Update ZWA039 aerQ Sensor V2.03 : Aeotec Help Desk (freshdesk.com)

However, mine is already on 2.1.1
image

I just placed a support case to Aeotec and will report, if I hear something back.

10

It’s the same firmware. What Aeotec calls 2.03, Zwave JS calls 2.1.1. Weird, but it is, what it is.

And this firmware still makes me mad and I decided to replace all Aeotec for something else in very near future.
Battery levels reporting is pure madness. Battery level drops to 0 whenever it decides to, reinserting the battery as only solution.
I refuse to reinsert batteries every week just to keep the right values.
This crap will have to leave…

11

I don’t think that’s true. Why do you think so?

2.01 == 2.1
2.02 == 2.2
2.03 == 2.3

Aeotec and other vendors use zero-padded minor numbers, Z-Wave JS doesn’t. Z-Wave JS includes the “patch”-level version, while most vendors don’t.

12

Because i did download id, did install it and that was the outcome… :wink:

13

Are you sure it was successful? Is HA showing the right value.? I don’t think that is correct.

14

Well, it said DONE or so and the value changed, that I can remember for sure. I could try again, that would not kill me.

15

I would try a re-interview. You could also look in the device diagnostic file to make sure the versions listed are the same as HA is showing in the UI.

16

So, this time having a hard time… Sending the firmware to the sensor aborted already 4 times just around 90%. Timeout… AAAARGGHHH, that was not my plan for today’s evening :slight_smile:

17

I’ve said already in some other topics, that I’m ditching all Aeotec crap out of my house.
This experience only makes that feel stronger.

14x already timed out the upgrade, battery went down from 80 to 30% due to the heavy traffic…

Still nowhere…

For comparison, upgrading firmware of 3 Qubino power sockets took me 30 minutes and all were done on first attempt.

I’m so done with Aeotec, really… :-1:

18

So, after getting a second, new battery from 100 to 10% on, I think the 40ed attempt, i just took that sensor and stamped it to dust. I’m usually a very quiet and patient person.

After 4 hours of trying to shoot the firmware in to that piece of crap, I just exploded a bit.

Well, enough is enough. Aeotec is joining my blacklist. Next to Apple, Peugeot, Ziggo, anything Tuya, and KPN telephony it landed on an absolute denial list. Will never come in to my house anymore.

Cheers, I’m having a drink and finaly give some attention to my lovely wife :wink:

19

For completeness, I have a ZWA039-C, and ZWaveJs was reporting the firmware as 2.1.1; and now after the update it’s 2.3.1.

So I guess…
2.01 == 2.1.1
2.02 == 2.2.1
2.03 == 2.3.1

I did just put a brand new battery in though, and now after the update it’s being reported as only 20%.

20

The battery reporting on these are useless, which is a shame as otherwise they’re really good. I’m hoping to find a solution to notify me when they haven’t reporting anything for over an hour… still working on an automation that might work.