Page Comparison

You can look for the sync.checkforcontent.request message received entries in the player's system log (available via the remote DWS) to monitor these events. If the player is disconnected and/or does not accept messages, the server repeats them multiple times with decreasing frequency and eventually stops. The player also checks for missed settings and schedule updates every six hours and retries if it cannot reach bsn.Content, and . It also requests settings and schedule from the server after each reboot.

The BSN.cloud server expects each player to report its status every five minutes. If it does not, then player status is unhealthy (inactive?). The server does not talk to players to check how they are doing.