Scheduling content (and playlists) is one of the handiest features inside Fugo. It allows you to select times and days when you want specific content to appear on your screens.

For instance, if you’re using your digital signage to display menu boards at a restaurant, you could use the scheduling options in Fugo to automatically switch between breakfast and lunch displays at a given time every day. You can even use it to display different content on weekdays and weekends.

So, how does the Fugo CMS know what time it is where each of your devices are so that it can work with your schedule properly? If you’re managing your screens remotely, you could even be in different timezones!

Here’s a breakdown of how we detect time, and how we detect date (they’re figured out separately at the moment):

By default, Fugo detects the time and timezone that your device is in by using its IP address. This is an “address” that every device connected to the internet has, which can be used to figure out where on Earth that device is connecting from, giving Fugo the information it needs to figure out what time it is there.

However, there is an option to switch over to use the time set locally on the device. This can be handy if your devices or internet connection makes use of proxies or VPNs, which can re-route your traffic to various locations around the world — which would make accurate scheduling pretty tricky!

1.0 To enable this option, head over to the Screens page of your Fugo CMS account, and click on the screen you want to use local device time for.

1.1 Once you’re looking at the Screen Details page, click the Settings tab.

1.2 From here, it’s just a matter of selecting the Date and Time dropdown, and changing it to Device instead of Automatic.

And you’re done! Any scheduling on this screen will now be based on the local time set on this device. Obviously, it’s important to make sure the time and timezone are set correctly on this device now!

At the moment, we don’t offer the ability to use the IP address of your device to calculate the date. Instead, we default to using the local device date. This is usually not going to be an issue, as most devices automatically fetch their dates from the internet, but if you’re experiencing any strange scheduling sync issues, it’s worth just double-checking to make sure your screen has the correct date set.

We hope that this breakdown of how Fugo manages its scheduling functionality has cleared up any questions you might have! If you’ve still got questions, or you’re experiencing any issues that haven’t been solved here, please don’t hesitate to get in touch with our expert support team by dropping an email through to support@fugo.ai -- they’re always happy to help out.