Device authorization grace period

[djp952]

I am trying to do some optimizations to limit the amount of discovery-related queries/broadcasts that need to be sent to keep track of the tuner Device Authorization string(s). Users aren't typically going to be adding/removing tuners on a regular basis (well, maybe except for me - lol), so the only legitimate reason I have for frequently gathering this data is to refresh the Device Authorization string(s).

I was wondering if there is a definitive grace period on these strings, as in an amount of time that the backend will accept an otherwise expired authorization string as valid. Knowing this would allow me to tone down the discovery requests to default to perhaps 75% of that threshold, and also prevent the user from increasing the interval beyond that.

Thank you as always for your time and support!

[nickk]

The DeviceAuth changes every sync (roughly every 8 hours or when a scan completes) and is good for 24h.

DeviceAuth is included in the discovery response so best just to run discover every couple of hours and pick it up from discover.

Nick

[djp952]

The DeviceAuth changes every sync (roughly every 8 hours or when a scan completes) and is good for 24h.

DeviceAuth is included in the discovery response so best just to run discover every couple of hours and pick it up from discover.

Nick

Excellent - thank you sir!