Cloud based discover anomalies

[gtb]

Yes, I know SD recommends against using cloud based discovery (and I mostly don't use is, but I do offer it as an option for one of my apps). But I have observed a couple of what I consider to be anomalies (errors) in the results.

First, if one uses the IPv4 endpoint, or the default endpoint, which redirects to the IPv4 endpoint (ipv4-api.hdhomerun.com), no device that supports IPv6 is in the device list, even if it has an IPv4 endpoint (that is true for both tuners and DVR storage devices for my use case).

Second, if one uses the IPv6 endpoint (ipv6-api.hdhomerun.com), the endpoint address for HDFX-4K returns the IPv4 endpoint address, not the (global) IPv6 address (which the logs on the device shows it obtains). FWIW, the DVR storage endpoint (running on a Linux host) specifies the IPv6 addresses

I would like to see both endpoint return *all* devices reachable via the protocol. Alternatively, those cloud discovery endpoints should be entirely removed (or return all empty arrays as the first stage to removal).

Thanks for your consideration.

[nickk]

First, if one uses the IPv4 endpoint, or the default endpoint, which redirects to the IPv4 endpoint (ipv4-api.hdhomerun.com), no device that supports IPv6 is in the device list, even if it has an IPv4 endpoint (that is true for both tuners and DVR storage devices for my use case).

That is correct. Matching is via public IP address and we don't know the public IPv4 address of a tuner that connects to our servers using IPv6.

Second, if one uses the IPv6 endpoint (ipv6-api.hdhomerun.com), the endpoint address for HDFX-4K returns the IPv4 endpoint address, not the (global) IPv6 address (which the logs on the device shows it obtains). FWIW, the DVR storage endpoint (running on a Linux host) specifies the IPv6 addresses

Agreed it should be returning the IPv6 address. I will take a look.

[gtb]

That is correct. Matching is via public IP address and we don't know the public IPv4 address of a tuner that connects to our servers using IPv6.

Perhaps IPv6 capable devices (if they also have an IPv4 address) should also attempt to contact the servers via IPv4 to add those devices to the returned IPv4 api discovery list (since the IPv4 address is valid, and a client may not have IPv6 capability while still being on the same local/private network)?

Agreed it should be returning the IPv6 address. I will take a look.

Thanks for looking.


If it is not at all clear, I consider this issue a very very very low priority (especially since using the cloud based discovery is not a recommended approach, and I primarily use local broadcast/multicast discovery). Thanks.