I just released v1.4.10 to production: Reolink | Homey
Fixes
- privacy mode stays available while a battery camera is in standby, so your flow cards keep working
- timeouts when several cameras report over the same hub connection
Can you upgrade to v1.4.10 and test again?
I want to make a flow sending a snapshot when movement is registered. I use the “when person detected”. I use the tag for snapshot and send a push with image, where I use the tag from when card. I also put in a 2 second delay.
When I run a test, it sends me an homey logo picture. So the push works. It seems that it can not retrieve the snapshot. I have also tried implementing an “then card”, using the “take snapshot” card. But this does not produce any tag to use in the push card.
I had the same problem. The solution was not to take the snapshot “from this flow”—which is the option offered right at the top of the selection—but rather to explicitly select the device with the snapshot further down the list.
Ahh. Thanks. That worked!!
All my cameras have been pretty stable recently, thanks for the recent updates
I created a test release 1.4.12 where we now rely on the push events for the battery percentage.
Hmmm, tried that test version. If anything, it seems to have made it worse, as now it doesn’t update the battery % even on app restart. It doesn’t seem to update at all. But switching back to the release version a couple hours later and as soon as the app restarts it updates (but only when you restart the app with the release version).
EDIT: I did a little digging, and the battery state updates seemed to be working better until the end of July. It appears to have gotten worse since the install of version 1.4.8 of the app, after which restarting the app updated it. Not sure if that helps at all?
I’m experiencing a strange issue with my Reolink NVR and Homey Pro 2023.
Everything works perfectly for a while, but after a few days Homey suddenly stops receiving motion, person and vehicle detection events from Reolink.
The strange thing is that the live camera feeds in Homey continue to work perfectly. The cameras and NVR are still reachable, and detection also continues to work normally within the Reolink app itself. It’s only the motion/person/vehicle triggers in Homey that stop working.
The only way I’ve been able to get the detection events working again is by restarting the Reolink NVR and/or restarting the Reolink app on Homey. After that, everything works again for a while, but eventually the same problem returns.
I’m using:
-
Homey Pro 2023
-
Reolink NVR (RLN16-410)
-
Reolink cameras connected through the NVR
-
TP-Link Omada managed switch (SG3218XP-M2)
-
TP-Link Deco network
I’ve already disabled EEE (Energy Efficient Ethernet) on the switch, but unfortunately the problem returned.
I find it strange that nobody seems to be helping me or responding to my message about this issue. I would really appreciate it if someone could take a look or let me know if they are experiencing the same problem.
Since the live feeds keep working, it seems like the connection itself is still active, but the event/detection communication between Reolink and Homey somehow stops after a while.
Have you “locked” the Homey and the camera to the specific Deco that’s closest to them? This prevents them from switching nodes
Yes! The Homey and the NVR has also a static IP.
Not the best solution, but you can use a Flow like this:
You can restart any app from within a Flow using the Power User experiment. So just restart the Reolink app every few hours automatically, that might fix it.
I just released v1.4.13 to test
Fixes
- Battery percentage updates sync reliably again (when awake).
- Battery camera in standby gets a second connection attempt after a short wake delay when failed to connect
Here is an update on the “camera/doorbell not detected when adding” reports.
I released v1.4.14 to test where I have improved how the app finds and connects to Reolink devices during pairing. It now reaches cameras and doorbells because some models with older/self-signed security settings got skipped which turned out to be what tripped up a lot of these devices.
Could you help me confirm it on your setup? The update rolls out via the Homey App Store, so it may take a little while to reach you. Once you’re on the new version:
Please switch on logging so I can see exactly what happens on your Homey:
• Open the Reolink app settings (Homey → More → Apps → Reolink → the gear).
• Tick “Enable debug logging”.
• Copy the “Support key” shown there and send it to me in a DM with your issue.
Thanks for all the detailed reports!
Hi Welcome to the community.
On what version so you experience this issue?
Please switch on logging so I can see exactly what happens on your Homey:
• Open the Reolink app settings (Homey → More → Apps → Reolink → the gear).
• Tick “Enable debug logging”.
• Copy the “Support key” shown there and send it to me in a DM.
Changes in 1.4.14 (stable):
- Fixed detection of cameras that use a legacy TLS handshake
- Fixed an error when controlling a battery camera while it is in standby
- Improved video and snapshot handling during reconnects
- Adjusted the ONVIF event emitter for hubs with many cameras
Changes in 1.4.15 (test):
- Fixed capability listeners being registered again on every reconnect (no more “listener already registered” warnings)
- Fixed cameras behind a Home Hub Mini not integrating; rapid ONVIF re-authentication no longer locks the account
- Fixed the first step of the pairing wizard
- Added ONVIF enable-flag logging on hub connect for diagnostics
@Koktail is there a chance at some point that we might get some NVR system stats on the device card for the NVR?
The NVR display provides plenty of details like Firmware Version, IP, UID, Network Traffic, Storage Usage & date Recording From, CPU Usage, RAM Usage, and which cameras are online & their network bandwidth.
It would be really helpful if you could access information like this from Advanced Flows. A few examples:
Sending alerts (and possibly even automated reboot of NVR) when CPU usage is above a threshold for a period of time, or if RAM usage is above a threshold.
Alert you if Recording From becomes less than a set period.
Alert you to Network bandwidth issues, or Firmware updates have occurred.
I would greatly appreciate if you could respond with your thoughts on this please. Thank you.
It’s already on my todo list. But currently not the priority.
In case your NVR speaks SNMP
https://community.homey.app/t/app-pro-snmp-network-devices-your-ups-nas-and-switch-ports-in-homey/158664
Might be another option.
