Skykit devices run two independent applications, Skykit Control (Note: the Control Android app on the device is distinct from the Skykit Control web interface) and Skykit Player. Each app checks in with Skykit separately, and each can succeed or fail on its own. These statuses normally match. If they don’t, the cause is usually one of the reasons below.
Read more about our two-app architecture here.
What Each App Reports
App | What is does | Where you see its status |
|---|---|---|
Player app | Plays content, syncs with Beam, downloads media | Skykit Beam (Displays) |
Control app | Manages the device in the background: heartbeats, commands, software updates, device health | Skykit Control (Device list, Status Tab) |
Common Reasons the Statuses Differ
Status hasn’t caught up yet
Status updates when a device checks in, so a device that just went offline or came back online can briefly show different status in different places. Offline notifications typically arrive 5-15 minutes after a device goes offline. If the statuses differ after 15 minutes, keep reading.
One app can reach Skykit and the other can’t
Each app communicates over its own channel, so a network restrict can affect one app but not the other. For example:
Control is Online but content isn’t syncing: The network is up, but the Player all can’t reach content services. On cellular (LTE) devices, this can also mean the carrier has throttled the connection after a data limit.
Control is Online but commands are delayed or failing: A firewall or SSL/DPI inspection is likely blocking real-time messaging, and the device is using its slower backup connection.
What to Do
Wait 15 minutes and refresh both Beam and Control.
Check Endpoint Tests. In Skykit Control, go to Device Detail > Network > Endpoint Tests. This shows which required domains are passing or failing so your IT team can update the allow list.
Check your firewall allow list against Network Firewall Configuration for Skykit. All required domains must be allowed on TCP 443, and NTP on UDP 123.
Try Rebooting. Send a Reboot command from Skykit Beam or Skykit Control, whichever is showing as offline. Sometimes one of the apps may have crashed in the background, and a reboot can bring it back online. You can also power cycle by unplugging, waiting at least 10 seconds, and plugging it back in.
Review the Event History tab to see when disconnections happen and whether they affect other devices on the same network or Wi-Fi access point.
Contact support@skykit.com if the statuses still don’t match. Include the device serial, status shown in each app, and a screenshot of the Diagnostic Screen if you can get one.