From 4f2c7b1f1226d9f25263e27f4e1d33adbe2382b8 Mon Sep 17 00:00:00 2001 From: TheJulianJES Date: Fri, 26 Jan 2024 02:28:02 +0100 Subject: [PATCH] Fix Reolink anchor link (#31063) --- source/_integrations/reolink.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/reolink.markdown b/source/_integrations/reolink.markdown index ed332795e11..522216e57b0 100644 --- a/source/_integrations/reolink.markdown +++ b/source/_integrations/reolink.markdown @@ -62,7 +62,7 @@ The latency for receiving the events is the best for ONVIF push and the worst fo For redundancy, these sensors are polled every 60 seconds together with the update of all other entities. Not all camera models generate ONVIF push events for all event types, some binary sensors might, therefore, only be polled. For list of Reolink products that support ONVIF see the [Reolink Support Site](https://support.reolink.com/hc/en-us/articles/900000617826). -To ensure you have the best latency possible, refer to the [Reducing latency of motion events](#Reducing_latency_of_motion_events) section. +To ensure you have the best latency possible, refer to the [Reducing latency of motion events](#reducing-latency-of-motion-events) section. ## Asterisk (*) next to entities listed in this documentation