Reolink Doorbell Battery not entering sleep state

[adamckbatchelor]

The problem

For the past few days (likely after the core 2024.11.1 update, but not entirely sure) my Reolink Doorbell Battery has been staying awake and draining battery (about 10% day). Nothing I do with its settings can get it to enter sleep state. I have reduced PIR sensitivity, switched it to the Home Hub wifi network (instead of my personal router), removed any dashboard camera views, turned off any related automations, and also factory reset the camera. The config file indicates TCP push is enabled. I'm stuck and I'm not sure what else can be the problem here.

What version of Home Assistant Core has the issue?

core-2024.11.1

What was the last working version of Home Assistant Core?

core-2024.11.0

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Reolink

Link to integration documentation on our website

https://www.home-assistant.io/integrations/reolink

Diagnostics information

config_entry-reolink-01J95BF88TZ7P6745Y634JR8EZ.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @starkillerOG, mind taking a look at this issue as it has been labeled with an integration (reolink) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of reolink can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign reolink Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

reolink documentation
reolink source
_{^{(message by IssueLinks)}}

[starkillerOG]

@adamckbatchelor Very sorry for the inconviniance.
Sounds like this is indeed caused by the recent TCP push connection changes.

Will investigate the issue this weekend and see how to resolve it.
I have a Home Hub and battery doorbell myself, so should be able to reproduce it.

[adamckbatchelor]

Thank you! And a quick update, the Sleep Status is reporting the doorbell is sleeping now, after I turned PIR off and on again. But the battery drain issue remains.

[marsp88]

Same here. Since the update, the battery life went from 3+ weeks to 3 days. I disabled all camera entities and tried different protocols with no changes.

EDIT: I noticed that a previous config form HA 2024.10.4 (with normal battery life) states "ONVIF push" but the current config states "TCP push"

[Bruhildo]

I am having the same issue. However, I disabled the doorbell on Home Assistant (not the home hub) and still having the battery drain issue.

[adamckbatchelor]

I fully removed the Reolink integration from Home Assistant and noticed the excessive battery drain continuing, but rebooting the doorbell seems to have fixed it

[starkillerOG]

I think I have pinned down the issue, and have resolved it in the upstream library. The fix will be included in the next HA patch release. Will let you know when its available

[starkillerOG]

HA 2024.11.3 is now available and should have fixed the issue.
If the doorbell is still not entering sleep state once updated to HA 2024.11.3 please let me know.

If you appreciate the reolink integration and want to support its development, please consider sponsering the upstream library or purchase Reolink products through this affiliate link.

[adamckbatchelor]

Thank you @starkillerOG for implementing this so quickly. I've had the integration back up for a day and only 1% battery drop so far so it definitely looks like the issue has been resolved!

[starkillerOG]

Thanks for the confirmation and support @adamckbatchelor

[Bruhildo]

Thanks @starkillerOG . Mine is also going back to sleep after the patch.

But still on that, and likely unrelated to the integration, I have notice that even though I have the PIR sensitivity set as very low (20% or lower) the doorbell is detecting movement often. On HA I can see that culprit are usually cars (about 7 meters away from the doorbell). Changing sensitivity does change this much and I believe this may be another cause for battery to be going down fast.

Have any of you faced the same issue? Changing sensitivity not doing much on terms of reducing triguers/sensors?

[RobinLenaerts-r0627775]

for me, unfortunately it has not worked. I updated this morning and even reconfigured the integration and disconnected and reconnected my doorbell to the hub.
Still I lose 10%+ a day.

According to the reolink app the camera is getting accessed almost 3 hours a day, sometimes more.

PiR is turned off for me so I doubt the camera getting triggered is the cause of the issue.

I would greatly appreciate any help resolving this. If you need any more info from my side I'd be happy to help :)

my HA is running on docker if that matters in any way.

[starkillerOG]

@RobinLenaerts-r0627775 if you disable the reolink integration for a day, does the battery drain stop?

Do you have the stream of the battery doorbell in a dashboard somewhere? If so do you scroll by this dashboard every day/have a wallpanel showing the dashboard?

[starkillerOG]

@RobinLenaerts-r0627775 the diagnostics info and a debug log for your hub with the battery doorbell would be useful to figure out what is going on. Could you post those?

[adamckbatchelor]

Unfortunately, I think I'm noticing the issue again. After 1 full day at 100%, its dropped to 93% over the course of maybe 15 hours. I've attached the diagnostics file and the debug log. Hopefully this helps further figure out the issue.

home-assistant_reolink_2024-11-24T04-00-20.073Z.log
config_entry-reolink-01JDA1P4R7ZPYPBA957WD8JJ2C.json

[RobinLenaerts-r0627775]

@starkillerOG I disabled the integration last night and will try to post an update here soon with results

[RobinLenaerts-r0627775]

@starkillerOG I disabled the integration last night and will try to post an update here soon with results

After disabling the integration gesterday, the battery kept draining. I disconnected and reconnected the doorbell from the hub this morning and the draining stopped. I just reconfigured the integration and enabled the debug logging. will try to update again later today.

[RobinLenaerts-r0627775]

@starkillerOG 8% got drained since my last comment 13 hours ago, I downloaded the debug log for the integration.
home-assistant_reolink_2024-11-25T09-40-38.530Z.log
I halved the file since it was way too big. hopefully this helps, Do you need anything else?

[starkillerOG]

@adamckbatchelor I see quite some {'cmd': 'Snap', 'channel': 0, 'snapType': 'sub', 'width': 1024, 'height': 1024, 'token': '<token>'} in your log, meaning that something is requesting snapshots of your camera, which will wake it up.
This might be a automation which uses the snapshot service, or it may be a dashboard which has the camera view on it (each time you open that view, it will request a snapshot, which will wake the battery camera).

[starkillerOG]

@RobinLenaerts-r0627775 your debug log was very helpfull, the issue is with the "DingDongOpt" command.
It is sending that every 1 minute which will wake the battery doorbell.
I thought I had fixed that, and it should not send the "GetDingDongList", "GetDingDongCfg" and "DingDongOpt" commands every minute anymore, but only 1x per hour.

But I now see I made a typo:
https://github.com/starkillerOG/reolink_aio/blob/ef93565f6ee266163340603f797abe7a8f53e325/reolink_aio/api.py#L103-L117

"DingDongOpt," should have been "DingDongOpt", I placed the "," wrong.

Will get that fixed ASAP.

[RobinLenaerts-r0627775]

awesome! glad I could help! thanks for being so quick with the responses @starkillerOG

[marsp88]

I fixed the typo manually and can confirm that battery life is back to normal. Only 4% down in 48 hours. Thank you!

[starkillerOG]

@marsp88 thanks for the confirmation!

The HA beta release is now available if you want to update.

[jezzaaa]

I haven't tried to reset the doorbell yet; probably in the next few days. The image below shows the massive difference in battery consumption between the times when the integration was on and when it was off (where the gap is, from around 12:30 to 17:00).

The sleep status is showing "sleeping" events every few minutes. Is it possible the integration is waking up the doorbell when it's getting the current status?

[adamckbatchelor]

For myself, I do think the battery drain has been fixed after the first December update of Home Assistant. I'll post again if anything changes, but it has been about 5 days since the update with no significant draining before or after a full charge.

[starkillerOG]

@adamckbatchelor glad to hear it is fixed for you

[starkillerOG]

@jezzaaa the constant waking events are definetly the issue.
Do you have the doorbell stream on a dashboard that is often viewed or on a wallpanel?
Do you have the doorbell (stream) connected to something like blue iris or firgate?

Could you share a diagnostic file and make a 5 minute debug log while the doorbell is constantly waking and post those two files here?
https://www.home-assistant.io/docs/configuration/troubleshooting/#debug-logs-and-diagnostics

[jezzaaa]

@jezzaaa the constant waking events are definetly the issue. Do you have the doorbell stream on a dashboard that is often viewed or on a wallpanel? Do you have the doorbell (stream) connected to something like blue iris or firgate?

Yeah that makes sense. I don't run blue iris or frigate, and I don't have a wall panel, so that wouldn't explain it. I have a camera page on a dashboard but I don't have that open unless I want to view it.

Could you share a diagnostic file and make a 5 minute debug log while the doorbell is constantly waking and post those two files here? https://www.home-assistant.io/docs/configuration/troubleshooting/#debug-logs-and-diagnostics

Generating 5 minute debug log now...

[jezzaaa]

Files attached
home-assistant_reolink_2024-12-09T22-03-00.945Z.log
config_entry-reolink-01JD4AZ82CP1JSAVVKX05XD0KC(1).json

[palmenmichiel]

Chiming in here; Massive battery drain after connecting an Argus 3 ultra to the home hub. Seems to be the same issue as described here; it constantly goes from sleep-awake every minute.

I have everything turned off on the camera (No PIR, no audio recording...) and have no reference to the camera in homeassistant (No dashboard, no feed). Also not connected to Frigate (Even completely turned off my frigate docker to make sure).

I don't know what's causing these wake-ups.

[marceskenazi]

I was having similar battery drain issues as well.
With Chime disabled in HA (keeping Home Hub and Doorbell enabled), battery would last 3 days.
With Chime and Doorbell disabled, battery would last 5.5 days.
With the whole Reolink integration disabled, battery has lost only 1% over 27 hours.

[palmenmichiel]

I was having similar battery drain issues as well. With Chime disabled in HA (keeping Home Hub and Doorbell enabled), battery would last 3 days. With Chime and Doorbell disabled, battery would last 5.5 days. With the whole Reolink integration disabled, battery has lost only 1% over 27 hours.

I was able to pinpoint it to the Reolink home hub. When connected to the hub, there’s a lot of battery drain (most likely due to the constant wakes which are only visible in homeassistant). Disconnecting it from the hub causes a big improvement in battery life. So, as far as I can see, it’s not related to homeassistant or Reolink integration, but the home hub itself. I’ve created a Reolink support ticket.

[marceskenazi]

I was having similar battery drain issues as well. With Chime disabled in HA (keeping Home Hub and Doorbell enabled), battery would last 3 days. With Chime and Doorbell disabled, battery would last 5.5 days. With the whole Reolink integration disabled, battery has lost only 1% over 27 hours.

I was able to pinpoint it to the Reolink home hub. When connected to the hub, there’s a lot of battery drain (most likely due to the constant wakes which are only visible in homeassistant). Disconnecting it from the hub causes a big improvement in battery life. So, as far as I can see, it’s not related to homeassistant or Reolink integration, but the home hub itself. I’ve created a Reolink support ticket.

I'm assuming you mean disconnecting Home Assistant from the Home Hub. I need the Battery Doorbell connected to the Home Hub as that is my Chime.

As I said above, I have disabled the Home Assistant Reolink integration entirely, but the Doorbell is still connected to the Home Hub. My battery is at 98% after 20 hours.

I hope Reolink can sort it because without the Home Hub as an intermediary, you cannot connect the battery doorbell to Home Assistant at all.

[starkillerOG]

@jezzaaa I see you have the CPU usage enabled on the Home Hub device, please disable that entity.
That may solve the issue.
(I just added the relevant command as a waking command, such that this will not cause issues anymore in HA 2025.1.0).

I also see you are running battery doorbell firmware "v3.0.0.4076_24092112".
I could reproduce issues with waking of the battery doorbell on firmware "v3.0.0.3478_24050605" and it was solved when I updated to firmware "v3.0.0.4430_24121109". Please contact Reolink support and ask for them to push this newer firmware to your battery doorbell.

[starkillerOG]

@palmenmichiel I have seen the same issues with my battery doorbell when connected to the Home Hub when the doorbell firmware was on "v3.0.0.3478_24050605", it would wake up every 3 minutes. This was solved by updating to "v3.0.0.4430_24121109". Moreover, the constant waking would also happen if the battery doorbell was only connected to the Home Hub and HomeAssistant or any other means of accesing the camera was OFF. So indeed there was some firmware bug in older firmware that caused these wake-ups and battery drain.

On which firmware version are you?
I would advice you to contact Reolink support and ask them to push a new firmware version to your doorbell.

[starkillerOG]

@marceskenazi which HA version do you run, which battery doorbell firmware version do you have, and do you have the CPU usage entity enabled on the Home Hub?

If possible, share your diagnostics file from the Home Hub:
https://www.home-assistant.io/docs/configuration/troubleshooting/#debug-logs-and-diagnostics

[marceskenazi]

@marceskenazi which HA version do you run, which battery doorbell firmware version do you have, and do you have the CPU usage entity enabled on the Home Hub?

If possible, share your diagnostics file from the Home Hub: https://www.home-assistant.io/docs/configuration/troubleshooting/#debug-logs-and-diagnostics

Home Assistant: 2024.12.5
Doorbell firmware: v3.0.0.4183_24102607
I probably did have CPU usage enabled in the Home Hub in the Reolink integration in Home Assistant.
As I said above, I deleted the entire integration, so have no logs. After I deleted it, my battery is at 94% after 5 days.

After reading your other replies, I have asked Reolink support for firmware v3.0.0.4430_24121109 as you suggest.

[palmenmichiel]

@palmenmichiel I have seen the same issues with my battery doorbell when connected to the Home Hub when the doorbell firmware was on "v3.0.0.3478_24050605", it would wake up every 3 minutes. This was solved by updating to "v3.0.0.4430_24121109". Moreover, the constant waking would also happen if the battery doorbell was only connected to the Home Hub and HomeAssistant or any other means of accesing the camera was OFF. So indeed there was some firmware bug in older firmware that caused these wake-ups and battery drain.

On which firmware version are you? I would advice you to contact Reolink support and ask them to push a new firmware version to your doorbell.

It's an argus 3 ultra, so not a battery doorbell. It is on the latest firmware (Both Hub and camera).

Back and forth with Reolink they've now suggested to replace the device, but I doubt that'll resolve the issue. It seems like a software bug, but so far they are not replying to my questions on how to access the logs to see what or why is causing this drain.

[marceskenazi]

v3.0.0.4430_24121109 has new power options for the Battery Doorbell. However, they won't be fully implemented until new firmware is available for the Home Hub. I'm hoping that, in the meantime, it cures my battery drain problem. I'm waiting for Reolink to push it my way.

https://support-d.reolink.com/hc/en-us/articles/37759740487833-Introduction-to-Power-Options-for-Reolink-Doorbell-Battery

I'm guessing there is a version of this new firmware for the Argus 3 Ultra as well. It won't show up as available unless you ask Reolink support for it.

[starkillerOG]

94% after 5 days

@marceskenazi that sounds like a expected and normal battery usage, about 1% a day seems very good.
Glad it is now working for you. It probably was the CPU entity.

[starkillerOG]

@palmenmichiel "latest firmware" does not say much since the Reolink app does not always discover the newest firmware. Reolink support can push a new firmware to your device.

What firmware version is the Argus 3 ultra at, and your Home Hub?

[marceskenazi]

Yes. That is normal. But I deleted the Reolink integration entirely to achieve this. I'm waiting for the new firmware to drop before I reinstall it.

…

On Mon, 30 Dec 2024, 13:04 starkillerOG, ***@***.***> wrote: 94% after 5 days @marceskenazi <https://github.com/marceskenazi> that sounds like a expected and normal battery usage, about 1% a day seems very good. Glad it is now working for you. It probably was the CPU entity. — Reply to this email directly, view it on GitHub <#130525 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQ44MSER2QYSAS2OMY6YEH32IFAFNAVCNFSM6AAAAABRWQQCSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRVGQ2TONZYHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[jezzaaa]

@jezzaaa I see you have the CPU usage enabled on the Home Hub device, please disable that entity. That may solve the issue. (I just added the relevant command as a waking command, such that this will not cause issues anymore in HA 2025.1.0).

Wow, that's likely to have fixed it for me:

I also see you are running battery doorbell firmware "v3.0.0.4076_24092112". I could reproduce issues with waking of the battery doorbell on firmware "v3.0.0.3478_24050605" and it was solved when I updated to firmware "v3.0.0.4430_24121109". Please contact Reolink support and ask for them to push this newer firmware to your battery doorbell.

After bedding in the CPU usage change for a week, I will do this, but I suspect this is not necessary with the massive improvement due to disabling CPU usage.

Thankyou so much @starkillerOG!

[starkillerOG]

@jezzaaa glad it is finally resolved for you!

[marceskenazi]

I got firmware v3.0.0.4430_24121109 from Reolink.

It seems you have to disconnect the Battery Doorbell from the Home Hub and make it a standalone device connected to your home WiFi in order for it to find the firmware after it has been pushed.

I installed it, reconnected the Doorbell to the Home Hub on its internal WiFi, and then reinstalled the Reolink integration in Home Assistant. I left the CPU usage and SD 0 storage entities disabled as suggested above.

After 30 hours, the fully charged battery is now at 96%. This extrapolates to approximately 4.5 weeks on a full charge. So this new firmware and/or leaving those 2 entities disabled has almost done the trick, though these stats are not quite as good as when the Reolink HA integration was deleted.

I'm hoping Home Assistant firmware 2025.1 will improve things even more.

The new power options in v3.0.0.4430_24121109 are not visible as they are reliant on new firmware for the Home Hub. This upgrade is expected at the end of the month. I imagine this Doorbell firmware will be officially released then as well.

I'd also like to say that Reolink customer support has been outstanding. Despite the 8 hour time difference between me in the UK and Reolink in Hong Kong, quick email communication was possible and they were keen to help.

And, finally, Happy New Year to all.

[starkillerOG]

@marceskenazi glad it is now resolved for you too!
HomeAssistant will always cause a tiny bit of extra battery consuption since it will poll and wake the camera every 1 hour for about 10 seconds. This ensures the HA state stays in sync, also when you change settings in the Reolink app. So this will be about 4 minutes per day of extra wake time. In most cases this should be comparable to the amount of motion events that also wake up the camera so should not effect the battery time much.

In HA 2025.01.0 I fixed the issue with the CPU usage entity, but I did not do anything regarding the SD storage entity since in my testing this did not seem to wake the cameras/cause extra battery drain.

Could you enable the SD 0 storage entity again and test if this does something regarding the battery drain?
If so, I can also reduce the poll interval of that entity from 1 minute to 60 minutes.

[starkillerOG]

Happy New Year to all!

HA 2025.01.0 includes some new improvements regarding the battery sleep status and will be released Jan 3th.
If the doorbell (or other cam) is still not entering sleep state once updated to HA 2025.01.0 please open a new issue so I can debug further.

If you appreciate the reolink integration and want to support its development, please consider sponsering the upstream library or purchase Reolink products through this affiliate link.

[marceskenazi]

@marceskenazi glad it is now resolved for you too! HomeAssistant will always cause a tiny bit of extra battery consuption since it will poll and wake the camera every 1 hour for about 10 seconds. This ensures the HA state stays in sync, also when you change settings in the Reolink app. So this will be about 4 minutes per day of extra wake time. In most cases this should be comparable to the amount of motion events that also wake up the camera so should not effect the battery time much.

In HA 2025.01.0 I fixed the issue with the CPU usage entity, but I did not do anything regarding the SD storage entity since in my testing this did not seem to wake the cameras/cause extra battery drain.

Could you enable the SD 0 storage entity again and test if this does something regarding the battery drain? If so, I can also reduce the poll interval of that entity from 1 minute to 60 minutes.

I've been away for a few days.

I was waiting for HA 2025.01.0 to drop before I started testing again. It is now available, but I'm hearing about this firmware breaking integrations in HA, so I will hold off until a newer version arrives.

Meanwhile with v3.0.0.4430_24121109, after 5.5 days, the battery is at 80%. Extrapolates to about 4 weeks on a full charge.

[marceskenazi]

I have now also been given new firmware for the Home Hub. v3.3.0.352_24121160

I have tried Home Assistant 2025.1.0 but, as expected, some of my integrations broke. I've also tried 2025.1.1 which didn't help.

[starkillerOG]

@marceskenazi interesting, i don't even have that home hub firmware yet. Do you also have release notes for that firmware?

"Some of my integrations broke", but the Reolink integration was working just fine right, or did you also have issues with Reolink?

[marceskenazi]

@marceskenazi interesting, i don't even have that home hub firmware yet. Do you also have release notes for that firmware?

"Some of my integrations broke", but the Reolink integration was working just fine right, or did you also have issues with Reolink?

The Reolink integration was fine. Govee and some of my Zigbee devices dropped out. So I've reverted to 2024.12.5

Reolink support pushed that Hub firmware to me out of the blue. But I had reported a bug that PIR sensitivity didn't 'stick' when you changed the value. The new Hub firmware fixed that, but has introduced other problems. The main one being that the Home Hub doesn't function as a Chime anymore. A big problem for me and I'm in discussion with support. The 8 hour time difference between me and them makes progress a bit slow, although they always reply as soon as they can.

Also, the promised new Power Options are not visible, even with both new firmwares.