Release: Reolink Integration v1.6.5
This update fixes wired cameras reporting battery values, adds a simple one-line power status, makes RTSP stream validation reliable when several cameras are set up at once, and adds last motion time and type attributes.
Problem:
- Wired (PoE) cameras on an NVR or Home Hub could show battery readings. The NVR returns placeholder battery data for PoE channels, and the integration treated it as a real battery.
- A battery camera that was plugged in and fully charged showed "not charging," even though the Reolink app showed it as connected to power.
- Power information was split across separate attributes that didn't sit together on the device page.
- RTSP validation could time out when more than one camera was saved close together.
- There was no simple way to see when a camera last detected motion or what kind of motion it was.
- Discovery showed an alarming message when a device didn't respond, even when the cause was usually a network or VLAN setting.
- The Device Bridge occasionally logged a harmless "unable to decrypt body (marker 'c800')" warning that looked like an error.
The Fix:
- Battery vs. wired is now determined from the camera's own capability report. Wired devices no longer show any battery values.
- New power attribute shows everything on one line: "Wired", "Battery, 87%, charging", "Battery, 100%, plugged in", or "Battery, 64%".
- chargingStatus now includes plugged_in, for a camera that is connected to power but not charging (for example, when it's already full).
- RTSP validation now runs one camera at a time, with more time to finish and automatic retries.
- New lastMotionTime and lastMotionType attributes on cameras and doorbells.
- Softer discovery "No response" message that points toward network settings.
- The c800 decrypt message now appears only at Full logging, with extra detail for troubleshooting.
Action Needed:
Update through HPM (update all files together). After updating, open the Reolink Integration app and click Done once.
This converts existing devices to the new power status and clears battery values from wired devices.
The batteryMode attribute has been replaced by power. If any rules or dashboard tiles use batteryMode, point them to power instead.
If a camera's RTSP status still shows timed out, re-save its RTSP preferences and it will be revalidated.Thanks to @gomce62.web for reporting this.
Glad that logs helped and that you have already identified a fix. I also appreciate you keeping the notification use case in mind. I'll try using Hubitat to send Reolink notifications via Rules instead of relying on the Reolink App to send the notifications. Given the improvements Hubitat has made in notifications and geofencing, I suspect your suggestions will work fine.
I just updated my Hubitat to platform release 2.5.2.128 that updated the Reolink Built-in integration to v1.6.4. Safe to assume v.1.6.5 will show up in some future release of the platform?
YES- next platform build
I did read through this thread (relatively quickly, I'll admit) but didn't see anything further on this: So the battery-powered lines (Argus, Doorbell on battery) do NOT work with the Reolink Integration on Hubitat? Apologies for missing anything key on this.
Yes they work but they need a NVR or HUB for some of the features.
There is a TIPS section in the Integration.
Perfect, thank you. Just read through all of it. I guess my confusion came from thinking it was "A home hub" (which I thought Elevation was) when it's Reolink Home Hub. @Ranchitat had also listed the battery-powered line to only work with a Home Hub and didn't list NVR as an option.
This Integration is now built-in for Hubitat BTW.
That's awesome! Congrats!
Thank you - and all those who assisted you with data and testing - so much for all the work you put in to this.
Release: Reolink Integration v1.6.6
Your camera password is no longer shown on the Device Bridge page, and PIR on/off now actually works.
Problem:
- The source password appeared in plain text in each Reolink Device Bridge's State Variables, the page people most often screenshot when asking for help.
- pirOn and pirOff never changed the camera. The camera rejected every request, but Hubitat updated PIR Enabled anyway, so it showed a PIR state that was never real. Doorbells had no PIR commands at all, even though battery doorbells have PIR.
- Battery Wired repeated the battery percentage already shown on the Battery row.
The Fix:
- Password: the Bridge now shows Password: Saved, 10 characters instead, plus Login (OK with the time, or "Failed: wrong username or password") and Last Good Login. The same status appears in green or red under the password field on Edit connection settings, so a wrong password is easy to spot without ever being displayed. The password is stored only in the app on your hub and never appears in the logs.
- PIR: the app reads the camera's PIR settings first, changes only on/off, and updates PIR Enabled only after the camera confirms it. Confirmed on a real battery camera. Battery doorbells get pirOn and pirOff too. The "PIR off, motion suppressed" note is gone, since PIR Enabled already says it.
- Battery Wired now shows just Wired, Battery, Battery, charging, or Battery, plugged in.
Action needed: update through HPM. Everything cleans itself up within a minute, with no need to click Done.
Thanks to @rlithgow1 for raising the password security issue.
When will this hit the next firmware update? (using it from the hubitat native integration not HPM) (Currently running beta) Again, thanx for all the hard work!
Needs to be verified and checked before HE side release. BETA firmware users will see it first.
I just updated my hub to platform 2.5.2.129, and the Reolink Integration is now on v.1.6.5 I can confirm the update resolved the battery attributes now reporting correctly on POE devices connected to NVR as the devices are now showing as "wired." It is also great to see the new "Last Motion Time" attribute, which is really going to help with automations and notifications. I can now retire my custom Reolink App, as your App/Drivers do everything I need and much more. Great job, and thanks again for creating this and being so responsive to the community post.
Excuse the poor detail absorption.
I read 100+ posts and admire the intense work you did but a crap load of info for many models.
I was looking at the v2 Doorbell.
Is the tl;dq (too long, didn't quite get it all) here that I can stream to the Dashboards and pass the stream off to my Raid for storage or do I have to handle that separably via an NVR app.
Not following TBH
Depends on your HE hub and what you’re trying to do.
C8Pro only - RTSP to dashboards.
All can do snapshots in dashboards.
Passing off to a NAS for storage.
That’s handled outside this integration.
Passing off to storage on a NAS requires an NVR such as Camect or Blueiris (I think reolink's own NVR does as well)
Ok, gotit. C8 Pro so good there.
I have a plethora of Blink and the Reolink doorbell would allow me to deprecate one of the cameras.
It's very laggy and the one that really needs to be fast.
I'll poke around the storage software for the NAS.
I have a reolink poe doorbell and it's awesome. My cameras are a mix of Reolink and Foscam. I use Camect.
The Camect hub scares me, 650 USD -> 800 CDN? 
I'll have a look at the the native Reolink NVR and the Frigate Docker.
Probably order the camera anyway due to the responsiveness and quality.
I have a wired doorbell so the v2 Wifi one should be perfect.
Blueiris would also work for you