--- title: "Changes to device status check-in frequency (heartbeat interval)" slug: "changes-to-device-status-check-in-frequency-heartbeat-interval" updated: 2026-11-03T16:44:00Z published: 2026-11-03T16:44:00Z canonical: "support.skykit.com/changes-to-device-status-check-in-frequency-heartbeat-interval" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.skykit.com/llms.txt > Use this file to discover all available pages before exploring further. # Changes to device status check-in frequency (heartbeat interval) > Starting Tuesday 13th October, Skykit devices on accounts with a custom heartbeat interval will move to a standard 5-minute check-in interval. This keeps device status consistent across Skykit Beam, Skykit Control, and the API. This article explains what's changing, what you'll notice, and how to manage notification volume. | | Details | | --- | --- | | **What's changing** | All devices check in (send a heartbeat) every **5 minutes**. The interval is no longer adjustable. | | **Effective date** | October 13, 2026: | | **Who's affected** | Only accounts that previously configured a custom heartbeat interval. If you received an email from Skykit about this change, your account is one of them. | | **Action required** | None. To manage notification volume, see **Managing Notification Volume** below. | ## What's Changed Skykit devices send a periodic signal, called a **heartbeat**, to let Skykit Control know they are operating normally. Previously, some accounts could set a custom heartbeat interval, and the player and Skykit Control app intervals could be set independently. | | Before | After | | --- | --- | --- | | **Heartbeat interval** | Custom, set per account | Standard **5 minutes** for all devices | | **Player and Control app intervals** | Could be set independently | Always match | | **Interval setting in Skykit Control** | Visible and editable | No longer visible or editable | ## Why We Made this Change When heartbeat intervals differ from the standard, or differ between the player and the Skykit Control app, device status can appear inconsistent across Skykit. For example, a device might show **Online** in Skykit Beam but **Offline** in the Skykit Control device list, or show one status in the list view and a different status in the device details view or the API. A single standard interval ensures that device status is accurate and consistent everywhere you see it: Skykit Beam, the Skykit Control list and details views, and the API. ## What You'll Notice ### Offline Notifications Will Arrive Sooner You can expect an offline email notification roughly **5–15 minutes** after a device actually goes offline. If your account previously used a longer interval, you will likely receive more notifications than you're used to. ### Previously Hidden Issues May Become Visible Longer heartbeat intervals can hide devices that briefly drop offline and reconnect. With a 5-minute interval, these short disconnections are now detected and reported. If devices that previously appeared stable now show intermittent **Offline** events, this usually indicates an existing network or connectivity issue rather than a new problem with the device. To investigate: 1. Confirm the required domains and ports are allowed using [Network Firewall Configuration for Skykit](https://support.skykit.com/docs/network-recommendations). 2. Check whether the affected devices share a network, location, or Wi-Fi access point. The [Wi-Fi Troubleshooting Guide](https://support.skykit.com/docs/wi-fi-troubleshooting-guide) can help with wireless issues. 3. Review the device's activity in the [Event History Tab](https://support.skykit.com/docs/event-history) to see when disconnections occur. 4. Follow the steps in [Troubleshooting Connectivity Incidents](https://support.skykit.com/docs/troubleshooting-connectivity-incidents). If you need help identifying which devices are unstable and why, contact the Skykit support team at [support@skykit.com](mailto:support@skykit.com). ## Managing Notification Volume If more frequent notifications are disruptive, we recommend creating an email rule that routes Skykit notifications to a dedicated folder or label. This lets you review alerts on your own schedule while your device status data stays accurate. Skykit notifications are sent from **Skykit Admin-Console** [**noreply-provisioning@skykit.com**](mailto:noreply-provisioning@skykit.com), with subject lines beginning **Skykit Device Up/Down Alert**. ### Gmail 1. In the Gmail search bar, click the **Show search options** icon. 2. In the **From** field, enter **Skykit Admin-Console** [**noreply-provisioning@skykit.com**](mailto:noreply-provisioning@skykit.com). 3. Click **Create filter**. 4. Select **Skip the Inbox (Archive it)** and **Apply the label**, then choose an existing label or create a new one (for example, "Skykit Alerts"). 5. Click **Create filter**. ### Outlook (Web and New Outlook) 1. Go to **Settings** > **Mail** > **Rules**. 2. Click **Add new rule** and enter a name (for example, "Skykit Alerts"). 3. Under **Add a condition**, select **From** and enter **Skykit Admin-Console** [**noreply-provisioning@skykit.com**](mailto:noreply-provisioning@skykit.com). 4. Under **Add an action**, select **Move to** and choose or create a folder. 5. Click **Save**. In classic Outlook for desktop, right-click a Skykit notification and select **Rules** > **Create Rule**. **Tip:** If multiple team members need these alerts, consider routing them to a shared mailbox or distribution list with one person responsible for review. ## Frequently Asked Questions ### Can I change back to my custom interval? No. To keep device status consistent across Skykit Beam, Skykit Control, and the API, all devices now use the same standard interval. To reduce notification volume, use an email rule as described in **Managing Notification Volume** above. ### Does this affect content playback on my displays? No. This change only affects how often devices report their status. Content scheduling and playback are not affected. ### Will my devices use more bandwidth? The heartbeat is a small status message, and the difference in data usage is minimal. ### I use the Skykit API. Does anything change? Device status returned by the API now matches what you see in Skykit Beam and Skykit Control. ### Why am I suddenly getting alerts for devices that seemed fine? Your previous, longer interval may have been hiding brief connectivity drops. See **Previously Hidden Issues May Become Visible** above, or contact support for help investigating. ### Will I get more control over notifications in the future? Yes. We're building notification and alerting controls into Skykit so you can manage how and when you're notified without affecting the accuracy of your device status data. We'll share more as these become available. ## Related Articles - [Device Status & Intelligence](https://support.skykit.com/docs/understanding-device-status-intelligence) - [Status Tab](https://support.skykit.com/docs/status-tab) - [How do I set up email alerts for device offline and online events?](https://support.skykit.com/docs/how-do-i-set-up-email-alerts-for-device-offline-and-online-events) - [Troubleshooting Connectivity Incidents](https://support.skykit.com/docs/troubleshooting-connectivity-incidents)