New post
0

Remote reboot options?

Avatar
Matt
None
Follow

G'Day all, I've been tasked with automating/scripting some of my organisation's regular digital signage management tasks. One such task is remotely rebooting brightsign devices that have stopped communicating with Appspace.

Other than via the "REBOOT" button within the DWS, (or cycling PoE on the devices' switch port via CLI), are there any other options to trigger a reboot?

I've played around with the SSH terminal on an XT244, though I gather this is only used for logging - not for sending device commands.

Cheers!

Date Votes

8 comments

  • 1
    Avatar
    Bright Scripters

    Control.cloud seems suitable but it does depend on your use-case.

    https://brightsign.atlassian.net/wiki/spaces/DOC/pages/378831527/Remote+DWS+APIs

    Power-cycle via PoE is a good option...

     

  • 0
    Avatar
    Matt

    Ah that's excellent, thank you! I had no idea there was an API for the DWS.

  • 0
    Avatar
    Matt

    ...that works via the BrightSign WebSockets server, so I gather we'd need our devices registered in bsn.cloud for this option to work. I'll take a look into that too, cheers.

  • 0
    Avatar
    Allen H. Porter

    I second the Control.Cloud option.

    I have not played with AppSpace on BrightSign, just Navori on BrightSign.  I am surprised there is no scheduled reboot option.  My preference is always pure BrightSign and I have almost never needed to reboot a player in that situation.

    Can you add a BrightScript to the SD card and have it execute while also running a 3rd party CMS?  That might also be a way to do it.

  • 0
    Avatar
    Matt

    A reboot only resolves our issues about 25% of the time, by my estimation, and it's often only a temporary fix. The most common fault we come across is some kind of corruption of the file system on the microSD (if not a fault with the microSD card itself). Formatting the card from the DWS, uploading a new Appspace package (autorun.zip), and then reconfiguring the device within Appspace is usually the more permanent solution.

    I've had a brief play with registering a device with the bsn.cloud, and my inital impression is that it adds more complication to both the provising process and ongoing support than it'll be worth just to be able to script a reboot via the DWS API. I also can't see a clear way to register devices already in production (running Appspace) to bsn.cloud, though I'm open to learning a solution for that.

  • 0
    Avatar
    Allen H. Porter

    Running as pure BrightSign players it is rare for us to have corrupt SD cards (except when someone uses a cheap SD card).

    My experience with Control.Cloud is about the same as yours.  But I can't see any other way when using another CMS.  We do not have access to the DWS as all of our players are on networks not under our control.  Still figuring out the best way to use it.

  • 0
    Avatar
    Matt

    I can certainly see the value of control.cloud if you don't otherwise have access to the devices. We have network access to our whole fleet across multiple sites, which I guess is why the idea of using control.cloud hasn't come up before now.

    In our case, it's just a shame that BrightSign devices don't have some basic telnet/ssh console commands to control basic functions (such as rebooting the device). It comes very much in handy for our fleet of Crestron touch panels and various other networked AV control system gadgets.

  • 0
    Avatar
    Bright Scripters

    If you are looking for a way to reboot from the local network, the local DWS API might be an option.

    https://brightsign.atlassian.net/wiki/spaces/DOC/pages/1172734089/Local+DWS+APIs#PUT-%2Fv1%2Fcontrol%2Freboot%2F

Please sign in to leave a comment.