Add a Zoneminder availability sensor#20184
Conversation
|
I'm not sure if I understand the purpose. Wouldn't users be able to just track the state of any Zoneminder entity and just check if it became unavailable? |
Yes (kind of), but this feels a little brittle to me. In my case I'm connected to a couple of different of ZoneMinder instances (one over a site to site vpn) and want to bounce the VPN if multiple things I'm connected to aren't connecting properly. It makes for a simpler automation for there to just be a binary sensor per ZoneMinder host, rather than looking through the camera entities and picking one from there. It could also be problematic if you moved cameras from one host to another and that was the camera you were using to track host availability. Additionally, the cameras, switches and sensors are tracking the availability of the ZoneMinder monitor (the camera), this is tracking the availability of the ZoneMinder system. There's a bunch of situations where a single monitor could go offline but the ZoneMinder system is still connected. |
|
I'll update docs for this platform tonight. |
Description:
In #18946, I hooked up the existing ZoneMinder entities with the availability of ZoneMinder. It would be useful to have this information available to automations. The simplest approach appears to be creating a new binary sensor platform.
This should be rebased and then merged after #20182.
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#8206
Checklist:
tox. Your PR cannot be merged unless tests passIf user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
REQUIREMENTSvariable (example).requirements_all.txtby runningscript/gen_requirements_all.py..coveragerc.If the code does not interact with devices: