How to hide Native Room Control (NRC icon) with an "events only" statement in the JSON

[joe_0855]

In the "Room Controls for Zoom Rooms" page where JSON examples are provided (Room Controls for Zoom Rooms), ther's a note in the "Rules" section that says the following:

• Room controls users can specify "events only" in their JSON configuration to hide unnecessary room control interfaces. When this field is specifically defined in the JSON, the Native Room Controls UI will not appear on the Zoom Rooms controller. In deployments using both NRC events and Zoom Apps, the Room Controls button directly launches the Zoom App interface without showing empty room control page.

I am using the JSON to trigger states based on meeting start/stop actions, but I don't want to see the "Native Room Controls" icon on the touch panel, since I am using a Zoom App as my primary control interface.

According to the note, I should be able to add an "events only" in the JSON to hide NRC (Native Room Controls). Has anyone done this successfully before and if so, could you please provide an example JSON profile that demonstrates usage? Thank you!

[bstrelko]

Also curious about this and yes, I can confirm that it is not documented anywhere in Zoom's KB (are you even a little bit surprised??) - I would recommend raising a support ticket and see if someone at Tier III+ can talk to someone on the product team and get you an answer.

[joe_0855]

Thanks for your response bstrelko! Once I get an answer, I'll post an update.

[bstrelko]

Any update, @joe_0855 ? 

[joe_0855]

Hi @bstrelko, I submitted a support ticket a few weeks ago and they are still looking into it. As soon as I get a solution, I'll post it. Thanks for asking!

[eliasg]

I am also looking into this; I attempted with Zoom Support to gather further information but was unfortunately unable to get any info as they deemed this as a "configuration-related and not within the scope of your account’s Developer Support Plan".

Will be keeping an eye on this thread for updates.

[bstrelko]

Hilarious and totally expected. This is very clearly not Developer-side based on the fact that it exists in non-dev documentation - I love how quickly Zoom Support (generally Tier 1-2) is to use that line.

[eliasg]

It looks like the Zoom Support article has been updated to include an example of the "events only" JSON configuration.

See KB0064072 article again.

There's a sample JSON file below the article and shows the below snippet:

  "adapters": [
    {
      "model": "GenericNetworkAdapter",
      "ip": "tcp://10.100.*.*:4998",
      "ports": [
        {
          "id": "display",
          "name": "Display",
          "methods": [
            {
              "id": "power",
              "name": "Power",
              "command": "powerOn=%\r",
              "params": [
                {
                  "id": "on",
                  "name": "On",
                  "value": "1"
                },
                {
                  "id": "off",
                  "name": "Off",
                  "value": "0"
                }
              ],
              "type": "actions"
            }
          ]
        }
      ]
    }
  ],
  "styles": [
    "zr_event_only=true",
    "display.icon=icon_tv"
  ]
}

I tested this - but the "Native Room Controls" still appears on the Zoom Room Controller alongside another Zoom App.

Either an additional comment or detail is missing -- this doesn't seem to provide the "events only" interface behavior they're describing.

[joe_0855]

Thanks for the post @eliasg! When I add the style section and the "zr_event_only=true" statement, it actually removes my "Room Controls" icon from the bar on the left. At that point, there's no way for me to see my Room Control App to pull up my interface. I'll add this to my open ticket and hopefully hear something soon.

[bstrelko]

Sounds like this may actually be working as intended. Gotta love the inconsistency between the KB article's use of 'events only' (plural) and syntax of 'event_only' (singular) - classic Zoom documentation!

Will try this out tomorrow with a Q-SYS + NRC deployment and see what happens.