Reolink playback error while getting mp4: Server disconnected

[M4n197]

The problem

Hi,
the playback of recordings from my Reolink Duo 3V PoE recently stopped working (again) on all of my devices.

The error message I get when I want to playback recordings is Reolink playback error while getting mp4: Server disconnected. All other features of the camera still work.

Workaround

When I restart the integration and after that the camera itself, the fault clears until it shows up again some days later.

further information

I'm thinking this behavior is not related to the firmware of the camera because I've experienced the problem with:

• the original version from last year (Reolink-Duo-3V-PoE.4060_2409142214.IPC_NT15NA416MP) I rolled back to recently (after issues with the latest updates, see Reolink playback expected video/mp4 but got video/x-flv #144001).
• the update from march v3.0.0.4669_2503101441 with semi-official patch
• the update from may (released in june) v3.0.0.4867_2505072123 which I'm currently using again

This problem might be related to or triggerded by the "Auto Reboot" schedule set in the camera.
I will look into this...

What version of Home Assistant Core has the issue?

core-2025.6.3

What was the last working version of Home Assistant Core?

No response

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

home-assistant_reolink_2025-06-19T06-01-14.983Z.log

Example YAML snippet

Anything in the logs that might be useful for us?

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]

Not sure what is going on here.
To which things do you have the Duo connected, only Home Assistant?

[M4n197]

Yes, only Home Assistant.

[M4n197]

I am now pretty sure that the scheduled “Auto Reboot” triggers this behaviour, as does the manual restart via the integration.
I will deactivate this function for the time being and perhaps work on an alternative by utilizing a Home Assistant automation.

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[mtruch]

@starkillerOG - I am having this same issue with my Reolink Duo 3 PoE. Same situation, only connected to Home Assistant (I also occasionally use the Reolink app, but no cloud account with Reolink, and no NVR).

[starkillerOG]

@mtruch I just check with my Reolink Duo 3 PoE with a SD card and the camera directly connected to HomeAssistant.
The recordings play just fine in Home Assistant on a windows PC using firefox.

Are you using a MAC or windows PC?

[mtruch]

@starkillerOG I'm using a Linux desktop (Fedora), but also tried this on a couple of Android devices (via companion app) and on an older Mac. That said, when I tried it again to confirm (just now), it works properly (the previous time I checked when it didn't work was before I updated to the most recent Home Assistant and Home Assistant OS versions (and the associated restart)).

The previous time it worked for a few days before it stopped working (and didn't work for several days). I'll continue to monitor it to see if it was a one-off issue or if it comes back.

[M4n197]

@mtruch Have you checked whether the scheduled "Auto Reboot" triggers this behaviour?