You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 6, 2023. It is now read-only.
In working out the various bits of info on these cameras, I have discovered how the Reolink client does device discovery on the network, and I built a component for it. Even though I have a 1.0 release I have only tested in the dev environment. Also it will not do much on its own, but this integration could be setup to listen for its events and then kick off config flows for discovered devices. Right now the only sample I have of this is the from scratch integration I have been working on, but that is currently a private repo because I don't have it to a stable point yet. Since this integration is what inspired me to dig deep into the Reolink API I wanted to give back in some way so I broke the discovery code out and built it as its own component.
On its own all you would see is just the events with the data, so it needs this integration to support the event to be useful here. I do need more data to flush out the information in the discovery packets so if you want to help, please install the component and run it in debug mode (via logger) and open issues in the repo with your Packet Traces and some basic device info (not the log entries as that is considered sensitive) and I can see about expanding the reported information.
To the devs here, if you are interested in supporting this, and my document is confusing/not enough (which is mostly likely true) Please do not hesitate to reach out with a PM and I can see about either helping you or possible creating a pull request to add support for this in.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In working out the various bits of info on these cameras, I have discovered how the Reolink client does device discovery on the network, and I built a component for it. Even though I have a 1.0 release I have only tested in the dev environment. Also it will not do much on its own, but this integration could be setup to listen for its events and then kick off config flows for discovered devices. Right now the only sample I have of this is the from scratch integration I have been working on, but that is currently a private repo because I don't have it to a stable point yet. Since this integration is what inspired me to dig deep into the Reolink API I wanted to give back in some way so I broke the discovery code out and built it as its own component.
https://github.com/xannor/ha_reolink_discovery
On its own all you would see is just the events with the data, so it needs this integration to support the event to be useful here. I do need more data to flush out the information in the discovery packets so if you want to help, please install the component and run it in debug mode (via logger) and open issues in the repo with your Packet Traces and some basic device info (not the log entries as that is considered sensitive) and I can see about expanding the reported information.
To the devs here, if you are interested in supporting this, and my document is confusing/not enough (which is mostly likely true) Please do not hesitate to reach out with a PM and I can see about either helping you or possible creating a pull request to add support for this in.
Beta Was this translation helpful? Give feedback.
All reactions