...
Just as the hardware authenticates with the Gumband Cloud, it also needs to authenticate with the SDK to ensure only expected hardware interacts with exhibits. The SDK gets the list of connected hardware from the Gumband Cloud, and then allows hardware to connect and authenticate with the same ID / token combination.
| Info |
|---|
Available in version |
SDK “Waiting for Auth” Queue
...
SDK HARDWARE_ONLINE & HARDWARE_OFFLINE Callbacks
...
I added a HARDWARE_ONLINE callback for the SDK when the token is accepted and the SDK sends back true on hardwareId/authenticate. I also added a hardware "expiry" timeout that triggers a HARDWARE_OFFLINE event in the SDK if the heartbeat for a particular harwareId isn’t received within 20s. The current docs have this heartbeat at 13s per, is that accurate?