I am reaching out to clarify whether the ChromeOS player is exclusively supported on the Cloud CMS version offered by Xibo.
I attempted to test the ChromeOS player with our on-premise Xibo CMS (v4.2), following the instructions provided in the official documentation. However, when pointing the ChromeOS box to https://<cmsurl>/pwa, the process was unsuccessful and resulted in the outcome shown in the attached image.
Could you please confirm if ChromeOS players are fully supported on the on-premise CMS version, or if additional configuration steps are required? If it is only available on the Cloud CMS version, I’d appreciate further clarification.
Based on my understanding, the CMS is open-source and does not require any licensing unless there’s a need to integrate a professional client, such as Android, Tizen, or WebOS. Following this logic, I assume ChromeOS would follow a similar approach, requiring a license only for the client, not for the CMS itself am i correct ?
You are correct that the CMS is open-source and does not require licensing itself, however the ChromeOS player does require a licence for each display and these are only available via a Plan. The Enterprise plan is required for ChromeOS licensing on self-hosted instances.
I believe the issue here is relevant to having the display not being added to Xibo CMS after launching this url “https:///pwa” as configured from Google Admin Console which results in the error message mentioned.
So I have a self hosted (with Docker) Xibo-CMS. This means i have to order 241x enterprise plans for android in order to be eligible to add ChromeOS players in my Xibo-CMS ?
Thanks everyone, we always listen to feedback and will take your comments on board. I’d like to describe how the ChromeOS player is licensed and explain our position as it stands today.
Xibo for ChromeOS is a commercial player written by Xibo and requires a software licence to use, in the same way as the Xibo for Android, webOS and Tizen player applications. It must be used alongside a ChromeOS Kiosk and Signage upgrade licence (or Enterprise upgrade licence) for Google admin console.
It is distributed from the downloads page on xibosignage.com and the package should be uploaded to your Xibo CMS in Player Versions, and assigned to the Default ChromeOS Display Profile. Using Google Admin console you should then install a Kiosk application via URL pointing to https://your_cms/pwa. It requires Xibo CMS 4.2.0 or later. This is described in our installation documentation.
Currently the only way to buy licenses for Xibo for ChromeOS is via a Plan, and they are included with any plan option. If you want to use a self-hosted CMS with a plan, there are certain requirements, one of which is the enterprise level plan. You are both correct that you would need to purchase an enterprise plan for any ChromeOS display to use Xibo for ChromeOS. The enterprise plan brings a huge list of other benefits as well as the self-hosting benefit.
As you all know, this is a new product, and I would encourage anyone with a potential project involving ChromeOS to get in touch with our team and discuss it.
Thanks Dan for all these details, you’ve done a fantastic job. And it’s really a pleasure to see how Xibo is evolving.
However, I have to admit that licence management with ChromeOs is still a bit unclear to me.
So if I’m Self Hosted, I can’t buy the ChromeOS licence, so I have to go through the Enterprise Plan, which means I’m Hosted
~ 10€ / Player / Month,
then I can buy a ChromeOS Xibo licence under the Enterprise plan
how much does that cost?
Can I transfer this licence to self hosted?
Then I need to connect the Google portal for ChromeOS and pay for the ChromeOS Flex licence for Digital Signage
~ 3 € / month / Player.
Do I understand this correctly in terms of method and cost? Si je comprends bien alors tous les gens comme moi qui sont selfhosted ne peuvent pas passer ou utiliser ChromeOS, tout ça pour ça. Too bad.
Will there be a way to buy ChromeOS Xibo +ChromeOSFlex Digital Signage in SelfHosted one day? Have you thought about this possibility?
Thanks