Screenly 26.8.2: Times in the dashboard follow your device's clock

Fri, 14 Aug 2026 00:00:00 +0000

The dashboard ignored how your device shows time, and wasn’t consistent with itself either. Playlist schedules and every time picker were 24-hour, while a screen’s overview and the Screens list showed AM/PM. Whichever you think in, part of the dashboard needed converting in your head.

Times now follow your own device. Set to 24-hour, you see 18:00. Set to 12-hour, you see 6:00 PM, and the time pickers get an AM/PM selector instead of running from 00 to 23. This runs everywhere times appear: playlist schedules, the Screens list, a screen’s overview, your account settings, and the datetime fields in an app’s settings.

Screenly 26.8.2: last_ping is no longer null for a screen that has never connected

Fri, 14 Aug 2026 00:00:00 +0000

A screen’s last_ping used to be null until the screen first checked in, which made null a usable signal for “this screen has never connected”. It is now always a timestamp: screens start with theirs set to when the screen was created, and existing screens that never checked in were given their creation time.

This affects last_ping on the v4 screens resource. The field’s type and the response shape are unchanged, only the values.

If this affects you: an integration treating a null last_ping as “never connected” loses that signal. A screen created in the last four hours can also report Online in its status before the device has ever reached us, because the seeded timestamp is recent. The closest check is comparing last_ping with the screen’s created_at: a screen that has never checked in still carries the timestamp it was created with.

Screenly 26.8.2 | Screenly

Screenly 26.8.2: Times in the dashboard follow your device's clock

Screenly 26.8.2: last_ping is no longer null for a screen that has never connected