Node "receiving wakeup notification" every 3 minutes

[GrizzlyAK]

Sorry for multiple questions at once, but I'm troubleshooting various ZW issues at the moment.

I have a Bali Premium battery-powered remote, which I've noticed the batteries last no time at all. In the zwavejs logs, about every 3 minutes like clockwork, I see the following lines:
`
2026-08-25 00:16:14.749 CNTRLR « [Node 158] received wakeup notification
2026-08-25 00:16:14.750 CNTRLR [Node 158] The node is now awake.
2026-08-25 00:16:15.006 CNTRLR » [Node 158] Sending node back to sleep...
2026-08-25 00:16:15.031 CNTRLR [Node 158] The node is now asleep.

`

Maybe that's why the batteries are draining. The Wakeup Interval in the Configuration is set to the Default (43200). Is this by design perhaps? Interestingly, the Last Awake column shows a time of 9:12 AM although the last comm was 12:31 PM. This is interesting because in the log, between 00:00 and 09:12, the lines above appeared EVERY 3 minutes, but after 09:12 from then on until now, I only see this line (again, every 3 minutes):
2026-08-25 00:16:14.749 CNTRLR « [Node 158] received wakeup notification
At 12:25, I did get an additional Battery Level update.

Are these "received wakeup notifications" being initiated by the device or ZWJS? Is there any way to reduce this traffic?

Thanks for any insight.
Cheers.
Shane

[zwave-js-bot]

Beep, boop! 🤖

I've found existing posts that look similar to yours. If they don't help, please wait for a human to show up.

These existing posts look similar to yours and might be related — a maintainer will confirm:

• Nodes sent to sleep during interview (open issue)
• Lastupdate value does not remain as initial node notification time [bug] (open issue)
• Unknown notification received CC Battery (open issue)

---

These suggestions were generated automatically. AI can make mistakes, always check important info.
Was this helpful? React with 👍 or 👎 to let us know.

[robertsLando]

Are these initiated by the device or by Z-Wave JS?

By the device. Z-Wave JS never asks a node to wake up. received wakeup notification is a WakeUpCC::WakeUpNotification that the node transmits on its own timer. All we do in response is mark it awake, drain its queue, and send WakeUpCC::NoMoreInformation — that is the Sending node back to sleep... line.

Why every 3 minutes when the interval says 43200?

What you see under Configuration is not necessarily what is stored on the device. Two things to check:

1. The actual value: node → Values → Wake Up → Wake Up interval.
2. What the device even allows. Search your log for the interview line:

« [Node 158] received wakeup capabilities:
                 default wakeup interval: 43200 seconds
                 minimum wakeup interval:   300 seconds
                 maximum wakeup interval: 86400 seconds
                 wakeup interval steps:      60 seconds

If the minimum there is above 180 s, then 3 minutes is not the wakeup interval at all and the device is re-announcing for some other reason.

One version-dependent note: Z-Wave JS 15.21 changed the metadata format for this value, and for a while ZUI rendered it as a plain dropdown with only Default / Disabled. That was #4587, fixed in v11.15.0. On 11.15.0+ the field is a combobox — you can type any value inside the device's allowed range. If you are on something older, that dropdown is why you only see "Default". Which ZUI version are you running?

Either way, set the interval explicitly while the remote is awake (press its wakeup button first), then confirm it stuck with a Wake Up → Get interval.

The second half of your log is the more interesting part.

After 09:12 you only get:

CNTRLR « [Node 158] received wakeup notification

with no The node is now awake. and no Sending node back to sleep.... Both of those are logged only on a status transition. Their absence means Z-Wave JS already considered node 158 awake and never sent it back to sleep — so the remote has been sitting in receive mode since 09:12. That is your battery drain, much more so than the wakeup traffic itself.

It also explains the column mismatch you noticed: Last Awake is stamped from the wake up event (asleep → awake transition), while Last Active is stamped on any traffic. Node 158 has not transitioned since 09:12, so Last Awake is frozen there. Working as intended, just not obvious.

Z-Wave JS sends a node back to sleep only when all three hold: interview stage is Complete, keepAwake is false, and nothing is pending in its queue. Your first log block shows Sending node back to sleep... firing, so the interview is complete. That leaves a stuck pending transaction, or a value-refresh task that never finished — the auto refresh is kicked off on every wakeup notification and holds keepAwake = true until it completes.

What would let us confirm: Settings → Z-Wave → Log level debug, then a log stretch covering the transition into the stuck state (around 09:12 in your case), plus the node's debug dump from Control panel → node → Advanced. If it shows the node pinned awake, that is driver-side and belongs in zwave-js/zwave-js.

Unrelated but worth checking on a busy network: Settings → Z-Wave → Send to sleep timeout (default 250 ms). Raising it to 2000–5000 ms gives sleeping nodes time to finish what they are doing before being sent back to sleep.

[GrizzlyAK]

Two things to check:

1. Actual in settings is still 7200.
2. what the log shows following a reinterview:

[Node 158] received wakeup capabilities:
             default wakeup interval: 43200 seconds
             minimum wakeup interval: 360 seconds
             maximum wakeup interval: 91800 seconds
             wakeup interval steps:   360 seconds
             wakeup on demand supported: false

This is odd. But so is the remote. You have to add it to the network, but I think it uses scenes to control (talk to) the blinds directly. But I really don't understand what it does. If there are specific questions I can ask my contact at Bali, he has been very helpful to me, has some knowledge of HA and ZW and how his devices work. I have noticed that the LED on the remote blinks about every 3 minutes, which tracks. It has always done that, and I wondered why, and figured it was waking up too often, which is why the batteries never last long - even though I rarely use the remote.

I'm on ZUI v 11.22.3. I'm not sure what you mean by Wake Up - Get interval. How do I do that? The blue Refresh(es) in Config?

OK, a lot to unpack on the next part.

What would let us confirm:
How will I reset it so that it is working correctly to see if it gets stuck again. Would restarting HA do it? Does the Restart (top right) in the ZUI restart the zwjs server too, or just the ZUI app? I can watch the log and see if I can find the stretch you're looking for.

I will set the Send to Sleep interval to something between 2000 and 5000 to aid with adds.

Thanks for the detailed response. It is very helpful. If there is anything else you need me to do, let me know.

Cheers,
Shane

[AlCalzone]

Unrelated but worth checking on a busy network: Settings → Z-Wave → Send to sleep timeout (default 250 ms). Raising it to 2000–5000 ms gives sleeping nodes time to finish what they are doing before being sent back to sleep.

We really need to stop the AI from recommending this.

[AlCalzone]

@GrizzlyAK

What does it say under wake up interval here? 7200?
What happens if you press the Refresh button and then wake up the device (or wait for it to wake up)?

Ideally record a driver log while doing so:

[GrizzlyAK]

Hey, here's what I'm showing:

I started debug and waited for the remote display to flash ('wakeup') then after 20 seconds, ended debug. This is what I found in the logs:

14:02:56.594 CNTRLR   [Node 158] [~] [Battery] level: 51 => 51                          [Endpoint 0]
14:02:56.598 DRIVER « [Node 158] [REQ] [BridgeApplicationCommand]
                      │ RSSI: -50 dBm
                      └─[BatteryCCReport]
                          level: 51
14:02:56.604 SERIAL « 0x011000a8000001009e02840700ce007f7f97                              (18 bytes)
14:02:56.606 SERIAL » [ACK]                                                                   (0x06)
14:02:56.607 DRIVER « [Node 158] [REQ] [BridgeApplicationCommand]
                      │ RSSI: -50 dBm
                      └─[WakeUpCCWakeUpNotification]
14:02:56.608 CNTRLR « [Node 158] received wakeup notification

and

2026-09-08 14:02:56.596 INFO Z-WAVE: [Node 158] Value updated: 128-0-level 51 => 51

zwave-debug-2026-09-08T22-03-29-719Z.zip

I suspect the Battery Level is reported at every wake up, but if the Refresh in the Wake Up Parameter in the UI was asking the device to send the Wake Up time, maybe the device doesn't do that. Either way, it wakes up every 3 minutes like clockwork. I'm going to contact my tech friend at Bali to see if he has any insight into the timing.

Honestly, I never use the remote anymore, since I control everything via HA, so I might just remove it altogether. I've got two now, that do the same thing, so it is a design 'feature'. But I would like to get to the bottom of it.

[AlCalzone]

I think the query might not have been queued. But if the 7200 is accurate, and you see the wake up notification every 3 minutes, it is not following its own settings.