reolink_aio icon indicating copy to clipboard operation
reolink_aio copied to clipboard

Question about UUID

Open xannor opened this issue 1 year ago • 7 comments

I was wondering if you looked into using the cameras UUID as an identifier instead of relying only on MAC.

I ask, because I have run into two issues relying on MAC/DHCP.

  1. Wifi enabled cameras, also usually have an ethernet port as well, but the integration will detect them as separate devices if both are connected. Not a big issue, but also I have one wifi camera that is never detected by DHCP (maybe because its wifi mac is in a different range.)

  2. Sometimes my cameras will shift IP addresses and the integration does not pickup the change. I dont know if it just missed the DHCP broadcast or if for some reason it is ignoring the new IP. The only way I can resolve this is to either manually edit the config with the new IP or add/remove the integration.

The reason I ask is because I have a custom integration I built when I was writing my own ReoLink component, and this integration uses the broadcast UDP packets/protocol of the client app. https://github.com/xannor/ha_reolink_discovery

I am thinking of modifying this to push the equivalent of a dhcp notification to the reolink integeration, however there is a limitation of at that level, I cannot decipher if the device is IPC or non-IPC so it can push reolink devices that the integration cannot talk to. Through the protocol it is possible to discover the IP, MAC, name, and UUID of a device, though not necessarily all of that info.

UUID is nice since it is unique per device, though possibly not always present, but I believe anything that supports the remote access functionality requires one, and it is available even if the functions are disabled.

xannor avatar Nov 08 '23 14:11 xannor