Zoom presence sensor

BTW if you copied and pasted mine exactly, it won’t work because my binary sensor entity ID is different than yours :grinning_face_with_smiling_eyes:

sensor is on according to the developer view. I did actually copy your sensor but reverted it back and still nothing. stumped!

sorry for the delay, missed your last response. If you are still having trouble, come find me on the HA discord (same username) and DM me. If you can share your screen we can try troubleshooting together

Is it possible to send a home assistant push notification if someone of my zoom contacts has sent me a chat message? (Not in a webinar or meeting)
Thank you

@raman325 I want to install this integration. I have a Zoom app set up already. Unfortunately, when I try to find the package in the HA Add On store it doesn’t come up. I can’t find it under HACS either. I’m probably overlooking something simple, but if you could point me in the right direction that would be awesome.

Sorry just now seeing this. Please open an issue in the repo, I think this is a feature request but I would need to look into it more

It’s in HACS, not an addon. Is it possible you already have the integration installed? Installed integrations won’t show up when you search for them in HACS in the add menu

Sigh It was user error. I get lost in the menus of Home Assistant sometimes. I haven’t installed enough integrations from HACS to understand the flow yet.

I do have another question, though. I managed to get the integration installed in HACS, and then I activated it from Settings > Devices & Services > Add Integration. It took a little trial and error because I used the wrong api keys at first. I sorted that out though and managed to log in with my zoom account.

After this I rebooted and the binary sensor showed up. Unfortunately, it’s showing as “Unavailable”. I tried jumping into a zoom call hoping that would change it but that didn’t work. I think I need to update my configuration.yml with a trigger, but I keep getting errors when I try this. I look through the preceding comments and used those as examples and couldn’t get it sorted out : /

Here’s what I last tried:

alias: 'Zoom event '
description: ''
trigger:
  platform: event
  event_type: zoom_webhook
  event_data:
    status:
      event: user.presence_status_updated
  condition:
  - condition: state
    entity_id: binary_sensor.zoom_odb
    state: 'on'

These are the error logs:

homeassistant.exceptions.HomeAssistantError: The system cannot restart because the configuration is not valid: Integration error: alias - Integration 'alias' not found.
Integration error: description - Integration 'description' not found.
Integration error: trigger - Integration 'trigger' not found.

Ok. My amateur status is evident. I was adding automation related data to the the configuration file. That was clearly a mistake.

I found the source(s) of my issue(s). The biggest mistakes I made occurred when I set up the Zoom App.

  1. You MUST select User-managed app when you create the app. Selecting “Account-level app” changes the Scopes available and messes with other config stuff.
  2. At some point I clicked “Change Now” to Enable Publishing under the Activation section. Don’t do this.

I ended up removing the integration from the core HA integrations, then I removed it from HACS. I recreated the Zoom App more deliberately, and reinstalled everything in HA. Now it works :slight_smile:

Here’s my automation:

- id: '##########'
  alias: Zoom status
  description: ''
  trigger:
  - platform: event
    event_type: zoom_webhook
    event_data:
      event: user.presence.status_updated
  condition: []
  action:
  - if:
    - condition: state
      entity_id: binary_sensor.zoom_###
      state: 'on'
    then:
    - service: notify.persistent_notification
      data:
        message: Entered Zoom Call
        title: Entered Zoom Call
  mode: single

Anyone have trouble validating the event notification endpoint URL in the zoom app? It says I can’t activate my app until this is done, but it doesn’t succeed.

Yep!

Zoom are deprecating the use of the verification token - so after ~October 2023 it will invalidate and the new method must be used. If you go in and alter the app in any way, it will force the new requirements for validation.

The secret token is now to be used as the salt to create an encrypted version of the plainToken.
An update was completed by another contributor (pending merge to the repo). Handle URL validation requests by willscott · Pull Request #64 · raman325/ha-zoom-automation · GitHub