DieWalge
June 26, 2025, 9:10am
1
Hi all,
I’m running into a strange issue with the Reolink integration in Home Assistant and was wondering if anyone else has experienced something similar.
Two of my Reolink cameras – an E1 Pro and a RLC-823A (S2) – successfully connect to Home Assistant over HTTPS, and the logs confirm that all Reolink API calls (e.g. GetDevInfo, GetNetPort, etc.) return code: 0. However:
No entities are created The devices do not appear in the UI
The cameras did work in my HA environment for quite a while and then suddenly stopped working. Other camera models (including another E1 Pro and 823A) still work just fine on the same HA instance.
No rtsp entry in GetAbility response → might block GetRtspUrl call
But the RTSP streams themselves are working (tested with App/VLC)
Similar models do return <rtsp>3</rtsp> and work perfectly in HA
Full GitHub issue (with log analysis and test results):
opened 10:01AM - 12 Jun 25 UTC
### The problem
Two Reolink cameras successfully connect over HTTPS and API com… mands return `code: 0`, but in Home Assistant **no entities are created and they remain invisible in the UI**.
This seems to be a **regression**: these cameras were working correctly as recently as October 2024, on HA `2024.10.x`, including full entity creation (camera, motion sensor, etc.).
---
### Affected devices
| IP | Device | HA status |
|------------------|---------------------------|-------------------------|
| 192.168.21.243 | Reolink E1 Outdoor Pro | ❌ No entities created |
| 192.168.21.41 | Reolink RLC-823A (S2) | ❌ No entities created |
| 192.168.21.42 | Reolink Duo Floodlight | ✅ Works correctly |
| 192.168.21.49 | Reolink Doorbell | ✅ Works correctly |
| 192.168.16.47 | Reolink E1 Outdoor PoE | ✅ Works correctly |
---
### Tests performed
- HTTPS/API commands successful (`GetDevInfo`, `GetNetPort`, `GetUser`, etc.)
- RTSP stream is playable in VLC and Reolink App & Desktop
- Fresh HA install confirms no interference or caching
- Factory reset + SD wipe & IP change done for `.243`
- Verified `.21.x` subnet overall functionality since `.42`/`.49` are OK
---
### Environment
- HA OS: 2025.5.3
- Core: 2025.5.3
- Supervisor: 2025.05.3
- Integration: built-in `reolink`
- `stream:` integration active
---
### first analysis and tentative conclusion (based on user observation)
The integration appears to **silently skip calling `GetRtspUrl`** at least for these two cameras (`E1 Pro` and `RLC-823A`), preventing entity setup despite successful connection and API.
Both affected cameras (192.168.21.41 and 192.168.21.243) do not expose rtsp support in the GetAbility response, even though their RTSP stream is fully functional and reachable externally.
As a result, GetRtspUrl is never called and the cameras remain unconfigured in Home Assistant.
Important note: Both affected cameras (E1 Pro and RLC-823A S2) were fully functional in Home Assistant in the past — using the same firmware and configuration they have now. One of the two cameras has intentionally not been reset in order to preserve the known-good state for testing.
Additional technical detail:
In the latest logs, the two working cameras (192.168.21.42 and 192.168.21.49) both indicate RTSP capability in their `GetAbility` responses:
- 192.168.21.42 (Reolink Duo Floodlight) includes an explicit `<rtsp>3</rtsp>` field in the XML payload.
- 192.168.21.49 (Reolink Doorbell) proceeds to a successful `GetRtspUrl` call, returning both main and sub stream URLs.
In contrast, the two non-working cameras (192.168.21.243 and 192.168.21.41) **do not expose a `rtsp` field at all** in their `GetAbility` data — despite their RTSP streams being functional and accessible externally (e.g., via VLC).
This absence appears to prevent the integration from calling `GetRtspUrl`, which ultimately results in no entities being created.
This difference seems to be the deciding factor.
From my perspective as a technically interested user (not a developer), this suggests that the root cause of the problem is not within the camera firmware or configuration itself (not changed!) — but rather in Home Assistant Core, the built-in Reolink integration, or possibly the `reolink_aio` Python library used underneath.
Specifically, it looks like a change in how the integration interprets the result of the `GetAbility` call:
Previously, the absence of an explicit `rtsp` field might not prevent `GetRtspUrl` from being called. Today, the missing `rtsp` key seems to result in silently skipping the stream setup, leaving no entities at all but all this is just pure speculation.
Happy to provide additional logs or test dev versions.
Thanks for your help!
### Logs
192.168.21.243 Reolink E1 Outdoor Pro => NOT successful!
192.168.16.47 Reolink E1 Outdoor PoE => successful!
[home-assistant_reolink.log](https://github.com/user-attachments/files/20706674/home-assistant_reolink.log)
192.168.21.42 Reolink Duo Floodlight => successful!
192.168.21.41 ReoLink-823-S2 => NOT successful!
192.168.21.49 ReoLink-Doorbell => successful!
[reolink 2.log](https://github.com/user-attachments/files/20721001/reolink.2.log)
Seen the same issue?
Found a workaround?
Any help, confirmation or comments would be really appreciated!
Thanks,