Channel API Deprecation - Chrome OS ?

  • 2
  • Problem
  • Updated 1 year ago
  • (Edited)
EDIT MARCH 21, 2018: Please note that all conversations related to Chrome OS in this Community should be considered obsolete and out of date. As announced in our new Community, Rise Vision is adding support for Chrome OS with a new version of Rise Player for Chrome OS.

To receive updates, make sure to subscribe to the Rise Vision Blog, or join the new Community and post questions.
=====================================================================================================================================================

We received the email today from Rise Vision's Support team about the Channel API deprecation (an action taken on Google's part). We have a sizable fleet of Chrome OS players (unsupported - we know) which have worked FANTASTIC for us. I know there's a few other folks out there who have stayed with the Chrome OS players. A few questions we have:
  • Is this the Sword of Damocles for our CAP players?
  • What are others who are still using CAP planning to do?
  • What will happen on 11/1/17 if our CAP players are still in use?
  • If nobody has a solution, is there interest in pooling resources to modify the CAP player (now open-sourced) to work correctly with the new Messaging Service? 
Photo of Robert Schoneman

Robert Schoneman, Champion

  • 4,990 Points 4k badge 2x thumb

Posted 1 year ago

  • 2
Photo of Alan Clayton

Alan Clayton, Official Rep

  • 8,788 Points 5k badge 2x thumb
Hi Robert,

Thanks for posting. Just to clarify - the deprecation of the Channel API will NOT prevent your Display from showing content.

The Channel API was a technology that provided a persistent connection between Rise Vision Servers and your Display. Earlier this year we introduced a replacement to the Channel API known as the Messaging Service which uses technology under our control. 

While we don't support Chrome App Player, we have taken the steps necessary to ensure our Messaging Service is compatible with Chrome App Player, as well as other legacy versions of Rise Player and 3rd Party Players. 

This means there are steps you can take to update the Displays mentioned in the notice you received to ensure they continue to work as expected once Google shuts down the Channel API on October 31st.

The impact of not updating your Displays before October 31st, and the steps you should take before then, are outlined in this help center article. For convenience, I've copied and pasted the steps to take for Chrome OS below. 

For everyone else, you DO NOT need to take any action unless you receive an email from us specifically stating one or more of your Displays need to be updated. A majority of Displays have upgraded automatically since the Messaging Service was released.

If you did receive notice, please note that Step 2 below applies to Chrome OS only. If your using a different operating system please refer to the help center article


Step 1: 

Please review and confirm the network requirements for Rise Player are satisfied. In order for your Display to be able to use the Message Service, it needs to be able to connect to display-messaging.risevision.com on ports 80 and 443.

Step 2: 

  1. Open the Rise Player Configuration. This can be done by adding the URL, http://localhost:9449/config, to the Schedule the Display is assigned to.
  2. Once the Rise Player Configuration page is opened on your Media Player update the value of "Server:" by selecting the radio button, “Production”.
  3. Then select “Apply”.
Step 3:

You can confirm your Display is updated by checking the Viewer Version shown on Display settings. It should be version 2-01-201705252154 or higher.
          
                
Photo of Robert Schoneman

Robert Schoneman, Champion

  • 4,990 Points 4k badge 2x thumb
Alan,

Thanks for the quick response. I read the help article again and clearly I missed entirely the section about Chrome OS. D'oh! False alarm! 

However, only three of our 20 player IDs were mentioned in the email we received. I looked at all three and they show Viewer Version "2-01-201708081443" which seems to meet the requirements as laid out in the article. Am I missing something (else)? :) 
Photo of Robert Schoneman

Robert Schoneman, Champion

  • 4,990 Points 4k badge 2x thumb
They are indeed. However, there are four (4) other players on the same network, with the same configuration, which show the same Viewer Version. They were not mentioned in the email. 
Photo of Alan Clayton

Alan Clayton, Official Rep

  • 8,788 Points 5k badge 2x thumb
So the Displays you received notice for definitely connected to the Channel API. What caused that I'm not sure. If you could send me the Display ID's to support@risevision.com I'd be more than happy to take a look and see what I can find. 
Photo of Robert Schoneman

Robert Schoneman, Champion

  • 4,990 Points 4k badge 2x thumb
Email sent. Thanks. 
Photo of Alan Clayton

Alan Clayton, Official Rep

  • 8,788 Points 5k badge 2x thumb
Got it. I have a couple priorities I need to knock out and will then review the logs for these Displays. I'll get back to you by end of week. 

Thanks! 
Photo of Robert Schoneman

Robert Schoneman, Champion

  • 4,990 Points 4k badge 2x thumb
Ours now all show View Version "2-01-201710022135" and seem to be working as expected. 
Photo of Wendi Borden

Wendi Borden, Champion

  • 6,028 Points 5k badge 2x thumb
Just to address the third point there.. this is the reply I got in another thread. It looks like most of our players have automatically upgraded, so hopefully we're good!

https://community.risevision.com/rise_vision_inc/topics/important-reminder-regarding-channel-api-shu...


If a Media Player is not upgraded to viewer 2-01-201705252154 or later, it will continue to display content, however when content is changed on a Presentation or Schedule, those Displays will not update automatically and will instead require a reboot. In addition to that the following will no longer function on any Displays not upgraded to the newest viewer:
  • Display status
  • Restart Rise Player
  • Reboot Media Player
  • Alerts