From 3545fb44bc9354daa151b0899ee98db5f036a6e4 Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Fri, 16 Dec 2022 09:49:42 +0100 Subject: [PATCH 01/17] Add reolink documentation --- source/_integrations/reolink.markdown | 102 ++++++++++++++++++++++++++ 1 file changed, 102 insertions(+) create mode 100644 source/_integrations/reolink.markdown diff --git a/source/_integrations/reolink.markdown b/source/_integrations/reolink.markdown new file mode 100644 index 000000000000..88ec160d1c0a --- /dev/null +++ b/source/_integrations/reolink.markdown @@ -0,0 +1,102 @@ +--- +title: Reolink NVR/camera +description: Instructions on how to integrate Reolink devices (NVR/cameras) into Home Assistant. +ha_category: + - Camera +ha_iot_class: Local Polling +ha_release: 2022.12 +ha_domain: reolink +ha_codeowners: + - '@starkillerOG' +ha_config_flow: true +ha_platforms: + - Camera +ha_integration_type: integration +--- + +The integration allows you to control [Reolink](https://reolink.com/) NVRs or cameras. + +{% include integrations/config_flow.md %} + +## Known reolink firmware bugs + +
+There is a BUG in Reolink NVR firmware: it only sends ONVIF event-notifications if motion happened on the camera connected to its very first (index "0") channel. +Reolink is aware of this and are working on fixing the problem. +
+ +
+Reolink doorbell presses only generate ONVIF event-notifications when the doorbell is directly connected to your network. +When connecting the Reolink doorbell to a NVR, no doorbell press events are generated. +Reolink is aware of this and a solution is already implemented in beta firmware. +
+ +## Services + +The Reolink integration supports all default camera [services](https://www.home-assistant.io/integrations/camera/#services) and additionally provides the following services: + +### Service `reolink_cctv.set_sensitivity` + +Set the motion detection sensitivity of the camera. Either all time schedule presets can be set at once, or a specific preset can be specified. + +| Service data attribute | Optional | Description | +| :---------------------- | :-------- | :----------- | +| `entity_id` | no | The camera to control. +| `sensitivity` | no | The sensitivity to set, a value between 1 (low sensitivity) and 50 (high sensitivity). +| `preset` | yes | The time schedule preset to set. Presets can be found in the Web UI of the camera. + +### Service `reolink_cctv.set_backlight` + +Optimizing brightness and contrast levels to compensate for differences between dark and bright objects using either BLC or WDR mode. +This may improve image clarity in high contrast situations, but it should be tested at different times of the day and night to ensure there is no negative effect. + +| Service data attribute | Optional | Description | +| :---------------------- | :-------- | :----------- | +| `entity_id` | no | The camera to control. +| `mode` | no | The backlight parameter supports the following values: `BACKLIGHTCONTROL`: use Backlight Control `DYNAMICRANGECONTROL`: use Dynamic Range Control `OFF`: no optimization + +### Service `reolink_cctv.set_daynight` + +Set the day and night mode parameter of the camera. + +| Service data attribute | Optional | Description | +| :---------------------- | :-------- | :----------- | +| `entity_id` | no | The camera to control. +| `mode` | no | The day and night mode parameter supports the following values: `AUTO` Auto switch between black & white mode `COLOR` Always record videos in color mode `BLACKANDWHITE` Always record videos in black & white mode. + +### Service `reolink_cctv.ptz_control` + +Control the PTZ (Pan Tilt Zoom) movement of the camera. + +| Service data attribute | Optional | Description | +| :---------------------- | :-------- | :----------- | +| `entity_id` | no | The camera to control. +| `command` | no | The command to execute. Possibe values are: `AUTO`, `DOWN`, `FOCUSDEC`, `FOCUSINC`, `LEFT`, `LEFTDOWN`, `LEFTUP`, `RIGHT`, `RIGHTDOWN`, `RIGHTUP`, `STOP`, `TOPOS`, `UP`, `ZOOMDEC` and `ZOOMINC`. +| `preset` | yes | In case of the command `TOPOS`, pass the preset ID here. The possible presets are listed as attribute on the camera. +| `speed` | yes | The speed at which the camera moves. Not applicable for the commands: `STOP` and `AUTO`. + +**The camera keeps moving until the `STOP` command is passed to the service.** + +## Camera streams + +This integration creates a few camera entities, one for each stream type with diffrent resolutions: Main, Sub, Ext and Images. +The Sub stream camera entity is enabled by default, the other streams are disabled by default. +The Images stream provides a sequence of image snapshots giving very low latency at the cost of a very low frame rate, this can be used when the hi-res RTMP/RTSP video stream are too laggy. + +## Configuration options + +In the options menu, the following parameters can be configured: + +| Parameter | Description | +| :------------------- | :---------------------------------------------------------------------------------------------------------- | +| Protocol | Switch between the RTMP or RTSP streaming protocol. | + +## Unsupported models + +The following models are not to be supported: + +- Battery-powered cameras +- B800: Only with NVR +- B400: Only with NVR +- D400: Only with NVR +- Lumus From 060b8b49c0fedfcae62e5c6a918b32551f7bb71a Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Tue, 20 Dec 2022 10:01:52 +0100 Subject: [PATCH 02/17] Update reolink.markdown --- source/_integrations/reolink.markdown | 57 ++++++++++++++++----------- 1 file changed, 33 insertions(+), 24 deletions(-) diff --git a/source/_integrations/reolink.markdown b/source/_integrations/reolink.markdown index 88ec160d1c0a..29ce90a0810e 100644 --- a/source/_integrations/reolink.markdown +++ b/source/_integrations/reolink.markdown @@ -31,6 +31,39 @@ When connecting the Reolink doorbell to a NVR, no doorbell press events are gene Reolink is aware of this and a solution is already implemented in beta firmware. +## Camera streams + +This integration creates a few camera entities, one for each stream type with diffrent resolutions: Main, Sub, Ext and Images. +The Sub stream camera entity is enabled by default, the other streams are disabled by default. +The Images stream provides a sequence of image snapshots giving very low latency at the cost of a very low frame rate, this can be used when the hi-res RTMP/RTSP video stream are too laggy. + +## Configuration options + +In the options menu, the following parameters can be configured: + +| Parameter | Description | +| :------------------- | :---------------------------------------------------------------------------------------------------------- | +| Protocol | Switch between the RTMP or RTSP streaming protocol. | + +## Unsupported models + +The following models are not to be supported: + +- Battery-powered cameras +- B800: Only with NVR +- B400: Only with NVR +- D400: Only with NVR +- Lumus + +## Reducing latency and load time + +To get considerebly lower lattency and faster loading, a addon can be used to convert the RTSP stream to a WebRTC stream. +1) In the configuration options of this reolink integration, select 'RTSP' as stream protocol. +2) add https://github.com/allenporter/stream-addons to the [addon repositories](https://my.home-assistant.io/redirect/supervisor_add_addon_repository/?repository_url=https%3A%2F%2Fgithub.com%2Fallenporter%2Fstream-addons). +3) Install en start the 'RTSPtoWeb - WebRTC' addon. +4) The [RTSPtoWebRTC integration](https://www.home-assistant.io/integrations/rtsp_to_webrtc/) should now be automatically discovered. Navigate to the integrations dashboard in Home Assistant and install this integration. +5) Check in the 'development tools' -> 'status' that the camera attribute 'frontend_stream_type' now shows 'web_rtc' for the reolink cameras. + ## Services The Reolink integration supports all default camera [services](https://www.home-assistant.io/integrations/camera/#services) and additionally provides the following services: @@ -76,27 +109,3 @@ Control the PTZ (Pan Tilt Zoom) movement of the camera. | `speed` | yes | The speed at which the camera moves. Not applicable for the commands: `STOP` and `AUTO`. **The camera keeps moving until the `STOP` command is passed to the service.** - -## Camera streams - -This integration creates a few camera entities, one for each stream type with diffrent resolutions: Main, Sub, Ext and Images. -The Sub stream camera entity is enabled by default, the other streams are disabled by default. -The Images stream provides a sequence of image snapshots giving very low latency at the cost of a very low frame rate, this can be used when the hi-res RTMP/RTSP video stream are too laggy. - -## Configuration options - -In the options menu, the following parameters can be configured: - -| Parameter | Description | -| :------------------- | :---------------------------------------------------------------------------------------------------------- | -| Protocol | Switch between the RTMP or RTSP streaming protocol. | - -## Unsupported models - -The following models are not to be supported: - -- Battery-powered cameras -- B800: Only with NVR -- B400: Only with NVR -- D400: Only with NVR -- Lumus From ad4bcc24fd80b1cf95b073ad3915e2961651014d Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Tue, 27 Dec 2022 20:29:11 +0100 Subject: [PATCH 03/17] fix spelling --- source/_integrations/reolink.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/_integrations/reolink.markdown b/source/_integrations/reolink.markdown index 29ce90a0810e..ba6e5313b891 100644 --- a/source/_integrations/reolink.markdown +++ b/source/_integrations/reolink.markdown @@ -33,7 +33,7 @@ Reolink is aware of this and a solution is already implemented in beta firmware. ## Camera streams -This integration creates a few camera entities, one for each stream type with diffrent resolutions: Main, Sub, Ext and Images. +This integration creates a few camera entities, one for each stream type with different resolutions: Main, Sub, Ext and Images. The Sub stream camera entity is enabled by default, the other streams are disabled by default. The Images stream provides a sequence of image snapshots giving very low latency at the cost of a very low frame rate, this can be used when the hi-res RTMP/RTSP video stream are too laggy. @@ -57,10 +57,10 @@ The following models are not to be supported: ## Reducing latency and load time -To get considerebly lower lattency and faster loading, a addon can be used to convert the RTSP stream to a WebRTC stream. +To get considerebly lower lattency and faster loading, a add-on can be used to convert the RTSP stream to a WebRTC stream. 1) In the configuration options of this reolink integration, select 'RTSP' as stream protocol. -2) add https://github.com/allenporter/stream-addons to the [addon repositories](https://my.home-assistant.io/redirect/supervisor_add_addon_repository/?repository_url=https%3A%2F%2Fgithub.com%2Fallenporter%2Fstream-addons). -3) Install en start the 'RTSPtoWeb - WebRTC' addon. +2) add https://github.com/allenporter/stream-addons to the [add-on repositories](https://my.home-assistant.io/redirect/supervisor_add_addon_repository/?repository_url=https%3A%2F%2Fgithub.com%2Fallenporter%2Fstream-addons). +3) Install en start the 'RTSPtoWeb - WebRTC' add-on. 4) The [RTSPtoWebRTC integration](https://www.home-assistant.io/integrations/rtsp_to_webrtc/) should now be automatically discovered. Navigate to the integrations dashboard in Home Assistant and install this integration. 5) Check in the 'development tools' -> 'status' that the camera attribute 'frontend_stream_type' now shows 'web_rtc' for the reolink cameras. From 07cc262885b3a69670464f396f5091b764fa7bb2 Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Tue, 27 Dec 2022 23:11:34 +0100 Subject: [PATCH 04/17] Update source/_integrations/reolink.markdown Co-authored-by: J. Nick Koston --- source/_integrations/reolink.markdown | 45 --------------------------- 1 file changed, 45 deletions(-) diff --git a/source/_integrations/reolink.markdown b/source/_integrations/reolink.markdown index ba6e5313b891..ce91d48660cc 100644 --- a/source/_integrations/reolink.markdown +++ b/source/_integrations/reolink.markdown @@ -64,48 +64,3 @@ To get considerebly lower lattency and faster loading, a add-on can be used to c 4) The [RTSPtoWebRTC integration](https://www.home-assistant.io/integrations/rtsp_to_webrtc/) should now be automatically discovered. Navigate to the integrations dashboard in Home Assistant and install this integration. 5) Check in the 'development tools' -> 'status' that the camera attribute 'frontend_stream_type' now shows 'web_rtc' for the reolink cameras. -## Services - -The Reolink integration supports all default camera [services](https://www.home-assistant.io/integrations/camera/#services) and additionally provides the following services: - -### Service `reolink_cctv.set_sensitivity` - -Set the motion detection sensitivity of the camera. Either all time schedule presets can be set at once, or a specific preset can be specified. - -| Service data attribute | Optional | Description | -| :---------------------- | :-------- | :----------- | -| `entity_id` | no | The camera to control. -| `sensitivity` | no | The sensitivity to set, a value between 1 (low sensitivity) and 50 (high sensitivity). -| `preset` | yes | The time schedule preset to set. Presets can be found in the Web UI of the camera. - -### Service `reolink_cctv.set_backlight` - -Optimizing brightness and contrast levels to compensate for differences between dark and bright objects using either BLC or WDR mode. -This may improve image clarity in high contrast situations, but it should be tested at different times of the day and night to ensure there is no negative effect. - -| Service data attribute | Optional | Description | -| :---------------------- | :-------- | :----------- | -| `entity_id` | no | The camera to control. -| `mode` | no | The backlight parameter supports the following values: `BACKLIGHTCONTROL`: use Backlight Control `DYNAMICRANGECONTROL`: use Dynamic Range Control `OFF`: no optimization - -### Service `reolink_cctv.set_daynight` - -Set the day and night mode parameter of the camera. - -| Service data attribute | Optional | Description | -| :---------------------- | :-------- | :----------- | -| `entity_id` | no | The camera to control. -| `mode` | no | The day and night mode parameter supports the following values: `AUTO` Auto switch between black & white mode `COLOR` Always record videos in color mode `BLACKANDWHITE` Always record videos in black & white mode. - -### Service `reolink_cctv.ptz_control` - -Control the PTZ (Pan Tilt Zoom) movement of the camera. - -| Service data attribute | Optional | Description | -| :---------------------- | :-------- | :----------- | -| `entity_id` | no | The camera to control. -| `command` | no | The command to execute. Possibe values are: `AUTO`, `DOWN`, `FOCUSDEC`, `FOCUSINC`, `LEFT`, `LEFTDOWN`, `LEFTUP`, `RIGHT`, `RIGHTDOWN`, `RIGHTUP`, `STOP`, `TOPOS`, `UP`, `ZOOMDEC` and `ZOOMINC`. -| `preset` | yes | In case of the command `TOPOS`, pass the preset ID here. The possible presets are listed as attribute on the camera. -| `speed` | yes | The speed at which the camera moves. Not applicable for the commands: `STOP` and `AUTO`. - -**The camera keeps moving until the `STOP` command is passed to the service.** From c1b33bd74dc52a3c37de17c23f3928d827545a6d Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Tue, 27 Dec 2022 23:17:32 +0100 Subject: [PATCH 05/17] Update reolink.markdown --- source/_integrations/reolink.markdown | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/source/_integrations/reolink.markdown b/source/_integrations/reolink.markdown index ce91d48660cc..583ccb6985ab 100644 --- a/source/_integrations/reolink.markdown +++ b/source/_integrations/reolink.markdown @@ -4,7 +4,7 @@ description: Instructions on how to integrate Reolink devices (NVR/cameras) into ha_category: - Camera ha_iot_class: Local Polling -ha_release: 2022.12 +ha_release: 2023.1 ha_domain: reolink ha_codeowners: - '@starkillerOG' @@ -55,12 +55,3 @@ The following models are not to be supported: - D400: Only with NVR - Lumus -## Reducing latency and load time - -To get considerebly lower lattency and faster loading, a add-on can be used to convert the RTSP stream to a WebRTC stream. -1) In the configuration options of this reolink integration, select 'RTSP' as stream protocol. -2) add https://github.com/allenporter/stream-addons to the [add-on repositories](https://my.home-assistant.io/redirect/supervisor_add_addon_repository/?repository_url=https%3A%2F%2Fgithub.com%2Fallenporter%2Fstream-addons). -3) Install en start the 'RTSPtoWeb - WebRTC' add-on. -4) The [RTSPtoWebRTC integration](https://www.home-assistant.io/integrations/rtsp_to_webrtc/) should now be automatically discovered. Navigate to the integrations dashboard in Home Assistant and install this integration. -5) Check in the 'development tools' -> 'status' that the camera attribute 'frontend_stream_type' now shows 'web_rtc' for the reolink cameras. - From 5f2976e3c8ae5a74e9471f5c4b3040c459dbc1eb Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Wed, 28 Dec 2022 11:23:05 +0100 Subject: [PATCH 06/17] Update source/_integrations/reolink.markdown Co-authored-by: J. Nick Koston --- 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 583ccb6985ab..1103532428af 100644 --- a/source/_integrations/reolink.markdown +++ b/source/_integrations/reolink.markdown @@ -33,7 +33,7 @@ Reolink is aware of this and a solution is already implemented in beta firmware. ## Camera streams -This integration creates a few camera entities, one for each stream type with different resolutions: Main, Sub, Ext and Images. +This integration creates a few camera entities, one for each stream type with different resolutions: Main, Sub, Ext, and Images. The Sub stream camera entity is enabled by default, the other streams are disabled by default. The Images stream provides a sequence of image snapshots giving very low latency at the cost of a very low frame rate, this can be used when the hi-res RTMP/RTSP video stream are too laggy. From 463ea20b952d1297c5f81e2b685208f5f2c39b1b Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Wed, 28 Dec 2022 11:23:18 +0100 Subject: [PATCH 07/17] Update source/_integrations/reolink.markdown Co-authored-by: J. Nick Koston --- 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 1103532428af..a6380db198cf 100644 --- a/source/_integrations/reolink.markdown +++ b/source/_integrations/reolink.markdown @@ -34,7 +34,7 @@ Reolink is aware of this and a solution is already implemented in beta firmware. ## Camera streams This integration creates a few camera entities, one for each stream type with different resolutions: Main, Sub, Ext, and Images. -The Sub stream camera entity is enabled by default, the other streams are disabled by default. +The Sub stream camera entity is enabled by default; the other streams are disabled by default. The Images stream provides a sequence of image snapshots giving very low latency at the cost of a very low frame rate, this can be used when the hi-res RTMP/RTSP video stream are too laggy. ## Configuration options From e5a543188cb6ec4d2de26b5bc95054d288e86c7e Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Wed, 28 Dec 2022 11:23:40 +0100 Subject: [PATCH 08/17] Update source/_integrations/reolink.markdown Co-authored-by: J. Nick Koston --- 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 a6380db198cf..bf47581f7c9a 100644 --- a/source/_integrations/reolink.markdown +++ b/source/_integrations/reolink.markdown @@ -35,7 +35,7 @@ Reolink is aware of this and a solution is already implemented in beta firmware. This integration creates a few camera entities, one for each stream type with different resolutions: Main, Sub, Ext, and Images. The Sub stream camera entity is enabled by default; the other streams are disabled by default. -The Images stream provides a sequence of image snapshots giving very low latency at the cost of a very low frame rate, this can be used when the hi-res RTMP/RTSP video stream are too laggy. +The Images stream provides a sequence of image snapshots giving very low latency at the cost of a very low frame rate; this can be used when the hi-res RTMP/RTSP video stream has too much lag. ## Configuration options From 933236b81b15ba6f5ad3fd1362a34d886cc30f45 Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Wed, 28 Dec 2022 11:23:56 +0100 Subject: [PATCH 09/17] Update source/_integrations/reolink.markdown Co-authored-by: J. Nick Koston --- 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 bf47581f7c9a..8c45f2f06c1a 100644 --- a/source/_integrations/reolink.markdown +++ b/source/_integrations/reolink.markdown @@ -18,7 +18,7 @@ The integration allows you to control [Reolink](https://reolink.com/) NVRs or ca {% include integrations/config_flow.md %} -## Known reolink firmware bugs +## Reolink firmware limitations
There is a BUG in Reolink NVR firmware: it only sends ONVIF event-notifications if motion happened on the camera connected to its very first (index "0") channel. From eecf06e088c18dcffbba9795ac7ae6a9f6dc7149 Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Wed, 28 Dec 2022 11:24:23 +0100 Subject: [PATCH 10/17] Update source/_integrations/reolink.markdown Co-authored-by: J. Nick Koston --- source/_integrations/reolink.markdown | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/source/_integrations/reolink.markdown b/source/_integrations/reolink.markdown index 8c45f2f06c1a..bc6dc3afd54f 100644 --- a/source/_integrations/reolink.markdown +++ b/source/_integrations/reolink.markdown @@ -21,8 +21,7 @@ The integration allows you to control [Reolink](https://reolink.com/) NVRs or ca ## Reolink firmware limitations
-There is a BUG in Reolink NVR firmware: it only sends ONVIF event-notifications if motion happened on the camera connected to its very first (index "0") channel. -Reolink is aware of this and are working on fixing the problem. +The Reolink NVR only sends ONVIF event-notifications if motion happens on the camera connected to the first (index "0") channel.
From d0a6702319b7be30289a053bb7a258b6b94110f0 Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Wed, 28 Dec 2022 11:24:52 +0100 Subject: [PATCH 11/17] Update source/_integrations/reolink.markdown Co-authored-by: J. Nick Koston --- source/_integrations/reolink.markdown | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/source/_integrations/reolink.markdown b/source/_integrations/reolink.markdown index bc6dc3afd54f..302cfbffe6c7 100644 --- a/source/_integrations/reolink.markdown +++ b/source/_integrations/reolink.markdown @@ -25,9 +25,7 @@ The Reolink NVR only sends ONVIF event-notifications if motion happens on the ca
-Reolink doorbell presses only generate ONVIF event-notifications when the doorbell is directly connected to your network. -When connecting the Reolink doorbell to a NVR, no doorbell press events are generated. -Reolink is aware of this and a solution is already implemented in beta firmware. +Reolink doorbell presses only generate ONVIF event notifications when the doorbell is directly connected to your network. No doorbell press events are generated when connecting the Reolink doorbell to an NVR.
## Camera streams From a564895af84f3febf5390825bfa1283a3c0945a1 Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Wed, 28 Dec 2022 11:29:29 +0100 Subject: [PATCH 12/17] remove table --- source/_integrations/reolink.markdown | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/source/_integrations/reolink.markdown b/source/_integrations/reolink.markdown index 302cfbffe6c7..26915bb60f7b 100644 --- a/source/_integrations/reolink.markdown +++ b/source/_integrations/reolink.markdown @@ -36,11 +36,7 @@ The Images stream provides a sequence of image snapshots giving very low latency ## Configuration options -In the options menu, the following parameters can be configured: - -| Parameter | Description | -| :------------------- | :---------------------------------------------------------------------------------------------------------- | -| Protocol | Switch between the RTMP or RTSP streaming protocol. | +In the options menu, the `Protocol` can be configured to RTSP or RTMP streaming protocol. ## Unsupported models From b09f0a86460696ed68cfe62bcefe4ba31a3eaa92 Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Wed, 28 Dec 2022 11:43:46 +0100 Subject: [PATCH 13/17] Update reolink.markdown --- source/_integrations/reolink.markdown | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/source/_integrations/reolink.markdown b/source/_integrations/reolink.markdown index 26915bb60f7b..8dd17413eefd 100644 --- a/source/_integrations/reolink.markdown +++ b/source/_integrations/reolink.markdown @@ -38,13 +38,19 @@ The Images stream provides a sequence of image snapshots giving very low latency In the options menu, the `Protocol` can be configured to RTSP or RTMP streaming protocol. -## Unsupported models +## Tested models -The following models are not to be supported: +The following models have been tested and confirmed to work: + +- RLN8-410 NVR +- RLC-811A +- Reolink Video Doorbell PoE +- Reolink Video Doorbell WiFi + +The following models are not supported: - Battery-powered cameras - B800: Only with NVR - B400: Only with NVR - D400: Only with NVR -- Lumus From cd99ee7774012a2473746105c908b3d43dba0d73 Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Wed, 28 Dec 2022 11:47:47 +0100 Subject: [PATCH 14/17] Update reolink.markdown --- source/_integrations/reolink.markdown | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/source/_integrations/reolink.markdown b/source/_integrations/reolink.markdown index 8dd17413eefd..c6501fc9b78f 100644 --- a/source/_integrations/reolink.markdown +++ b/source/_integrations/reolink.markdown @@ -47,10 +47,4 @@ The following models have been tested and confirmed to work: - Reolink Video Doorbell PoE - Reolink Video Doorbell WiFi -The following models are not supported: - -- Battery-powered cameras -- B800: Only with NVR -- B400: Only with NVR -- D400: Only with NVR - +Battery-powered cameras are not yet supported. From 834c7a88c07cca44538a8355e6086c5b2c070dec Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Wed, 28 Dec 2022 11:50:59 +0100 Subject: [PATCH 15/17] move limitiations to the bottom --- source/_integrations/reolink.markdown | 15 +++++---------- 1 file changed, 5 insertions(+), 10 deletions(-) diff --git a/source/_integrations/reolink.markdown b/source/_integrations/reolink.markdown index c6501fc9b78f..ca3ec70becd4 100644 --- a/source/_integrations/reolink.markdown +++ b/source/_integrations/reolink.markdown @@ -18,16 +18,6 @@ The integration allows you to control [Reolink](https://reolink.com/) NVRs or ca {% include integrations/config_flow.md %} -## Reolink firmware limitations - -
-The Reolink NVR only sends ONVIF event-notifications if motion happens on the camera connected to the first (index "0") channel. -
- -
-Reolink doorbell presses only generate ONVIF event notifications when the doorbell is directly connected to your network. No doorbell press events are generated when connecting the Reolink doorbell to an NVR. -
- ## Camera streams This integration creates a few camera entities, one for each stream type with different resolutions: Main, Sub, Ext, and Images. @@ -48,3 +38,8 @@ The following models have been tested and confirmed to work: - Reolink Video Doorbell WiFi Battery-powered cameras are not yet supported. + +## Reolink firmware limitations + +- The Reolink NVR only sends ONVIF event-notifications if motion happens on the camera connected to the first (index "0") channel. +- Reolink doorbell presses only generate ONVIF event notifications when the doorbell is directly connected to your network. No doorbell press events are generated when connecting the Reolink doorbell to an NVR. \ No newline at end of file From 765c7ec9ffa75d0dcc54409128c2c79db536fdc1 Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Wed, 28 Dec 2022 11:58:30 +0100 Subject: [PATCH 16/17] use integrations/option_flow.md --- source/_integrations/reolink.markdown | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/source/_integrations/reolink.markdown b/source/_integrations/reolink.markdown index ca3ec70becd4..8b5b1031abb4 100644 --- a/source/_integrations/reolink.markdown +++ b/source/_integrations/reolink.markdown @@ -18,16 +18,18 @@ The integration allows you to control [Reolink](https://reolink.com/) NVRs or ca {% include integrations/config_flow.md %} +{% include integrations/option_flow.md %} +{% configuration_basic %} +Protocol: + description: Switch between RTSP or RTMP streaming protocol. +{% endconfiguration_basic %} + ## Camera streams This integration creates a few camera entities, one for each stream type with different resolutions: Main, Sub, Ext, and Images. The Sub stream camera entity is enabled by default; the other streams are disabled by default. The Images stream provides a sequence of image snapshots giving very low latency at the cost of a very low frame rate; this can be used when the hi-res RTMP/RTSP video stream has too much lag. -## Configuration options - -In the options menu, the `Protocol` can be configured to RTSP or RTMP streaming protocol. - ## Tested models The following models have been tested and confirmed to work: From b5a757cdf6359c63dc86deea64571ea9abd0d205 Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Wed, 28 Dec 2022 15:54:03 +0100 Subject: [PATCH 17/17] clearify limitations --- source/_integrations/reolink.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/reolink.markdown b/source/_integrations/reolink.markdown index 8b5b1031abb4..928454731a9f 100644 --- a/source/_integrations/reolink.markdown +++ b/source/_integrations/reolink.markdown @@ -43,5 +43,5 @@ Battery-powered cameras are not yet supported. ## Reolink firmware limitations -- The Reolink NVR only sends ONVIF event-notifications if motion happens on the camera connected to the first (index "0") channel. -- Reolink doorbell presses only generate ONVIF event notifications when the doorbell is directly connected to your network. No doorbell press events are generated when connecting the Reolink doorbell to an NVR. \ No newline at end of file +- The Reolink NVR only sends event-notifications if motion happens on the camera connected to the first (index "0") channel, therefore the binary sensors of all channels will only be updated when the first channel sees motion. +- Reolink doorbell presses only generate ONVIF event notifications when the doorbell is directly connected to your network. The doorbell visitor binary sensor will not work when connecting the Reolink doorbell to an NVR. \ No newline at end of file