0

BrightAuthor Connected first-time player setup takes many networked player refreshes to connect

I've been setting up a handfull of XT2145 devices over the past few weeks, and one issue that keeps repeating itself across every device (with varying severity) happens during first-time connection to the player via local network.

After setting up each player with their local network provision, when i get to the publishing step and select Type > Local Network, the players with no previous published content (first-time publish/setup) are greyed out with the message "Access to xxx.xxx.x.xxx denied".

After entering the correct credentials, the message changes to "Failed to connect to xxx.xxx.x.xxx ". 

I have:

  • Turned off wifi & bluetooth
  • Connected my pc and the player through the same ethernet port setup
  • Hard- & soft-rebooted the player
  • Restarted & reconnected the BA connected app

And yet:

  • The "Access denied" / "Failed to connect" messages continue
  • Refreshing momentarily shows the player active, and then greyed out with the "Access denied" message
  • The big issue: Repeated refreshing and entering of credentials (about 7+ times in a row) sometimes fixes the issue and lets me connect, but sometimes it takes a half-hour troubleshooting process of restarting devices, refreshing, re-entering credentials, restarting devices ... and so on ... to finally be able to publish a presentation locally to a player.

After doing this tedious process for the first time - the players never misbehave again. Even after reprovisioning the player. Even after a factory reset. I've read the post about an almost identical issue, but thought i'd revive the general topic here.

Am I missing critical information, or is this a recognized issue?

1 comment

  • 0
    Avatar
    Frederik

    Update:

    I've now had the first case of a player that refuses to connect, and tried just spamming the refresh button 10+ times in a second or so.

    • This forces the player connection and the checkbox button to stay visible for long enough to successfully publish a presentation. However, doing it like this means defaulting back to the "Access denied" message after every published presentation.

    This issue is repeatable across multiple computers. Of the 5 devices set up these past 2 months only one of them didn't feature this issue.

Please sign in to leave a comment.