FYI - My Zen34 was just purchased last week and already had firmware 1.3. I tested the custom driver mentioned in a couple of previous posts, however, I'm still experiencing the periodic battery report spam.
I just double checked my logs. Only 2 battery level notifications over the past 24 hours.
My battery is at 100%. Is yours lower? Wondering if notifications happen more frequently as battery level declines...
In my case, it's a brand new purchase. Battery is reporting 100% (many, many times...).
The new one I installed on the 9th with version 1.03 firmware, reported battery status 1 time the next day on the 10th, about 50 times on the 11th and about another 50 on the 12th. I switched it to the custom driver, on the 13th. It made two battery reports that day about 12 hours apart it did the same on the 14th. It has yet to report battery status today.
1 Like
I went back and tried the custom driver posted here again. This time I actually paid attention and when through it's setup procedure ("Tap Up x 7"). So far, it's gone through two reporting intervals (12 hrs) with only one battery event for each.
Perhaps the other drivers are not properly initializing/setting up the Zen34. I'd assume the device needs to be awake to receive the setup, and the procedure the custom driver does ensures this. So, hitting "config" with the other drivers at some random time may not actually be doing anything.
1 Like
This seems possible. I have been watching these dimmers since reinstalling them and I noticed that it took a couple days before the leds changed to the colors that I selected in the driver. After they finally changed, I haven’t had any more spammy device alerts.
Using the custom driver now for the past week and everything seemed to be going well until this morning. I woke up to this
When this happens, it slows the zwave mesh to a crawl. Luckily, nothing mission critical relies on zwave in my house.
And yes, 433 battery reports in 1 hour. I replaced the batteries 2 weeks ago with new Duracell 2032s because the previous continuous battery reports killed the batteries. I really want these to work out, but I’m going to have to get rid of them if this problem can’t be fixed.
EDIT: After posting this, it’s now over 500 events, so off I go to try to get it to stop. Batteries are still at 100% miraculously.
EDIT 2: Pressing one of the buttons seems to have stopped the reporting for now. I have been using these daily, but they’re in the Master Bathroom, so they don’t get a great deal of use.
EDIT 3: This is on a C-5 with 2.3.0.121 firmware. Other z-wave devices (only using z-wave plus) are rock solid and the Zen34s are very responsive, so I’m pretty sure it’s a device issue.
EDIT 4: I submitted a ticket to Zooz support.
Thank you for the update Ken. If it's just one device, it could be an issue with this particular unit and we'll do our best to resolve this for you in the support request you sent.
Both have done this previously. There are also a number of other posts in the forum about the battery reporting every 6 or 7 seconds, so I’m not assuming it is an isolated issue.
My first hunch is that it's the same issue I had with the open/close sensor not to long after it released. Here is the first post that mentions it and you'll see me and several others having issues with the device spamming battery levels. They were able to fix it with a firmware update, so hopefully they'll be able to do the same with this.
2 Likes
We released firmware 1.3 to address it and anyone who had issues before confirmed they were resolved by the release so now we need to go back to trying to replicate it again with the new firmware on multiple platforms to see if and how this can be tackled.
Just parroting @Ken_Fraleigh 's experience. In my case I lasted ~25 days on the custom driver without issue. Then it again starting spamming battery reports during the 12 hour reporting interval. In my case there was a noticeable hit to the hub's performance during the spam, so I've removed the switch from my system for now.
Hopefully the issue can be reproduced and resolved with a firmware update.
The one I was recently having trouble with stopped when I moved it closer to the hub. When it was spamming the hub, I held down the bottom button until the light started flashing at which point it became solid blue (using a repeater). I performed the same operation on the one that wasn't spamming the hub, and it was solid green (direct connection). After moving the Zen34, it tested as direct hub connection and stopped spamming the battery reports. It has been two weeks now, but I haven't put it back to its home yet. When it was spamming reports, it would take around 10 seconds for a z-wave device to turn on via automation or from the device page, luckily I am mostly Zigbee here.
