You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A while ago, maybe a year ago, this integration stopped working for me. I've come back to it occasionally. Today I discovered something interesting, and it correlates with a change in my use of Zoom at around that time.
I'm able to install the integration and manually POST nonsense to <base url>/api/zoom and see it in HA dev tools listening for zoom_webhook. However actually entering and exiting a meeting doesn't seem to ever trigger the aforementioned event.
Turns out that for some reason Zoom doesn't update presence status if you're using the PWA (web app - in my case in Chromium on Linux). It does on the other hand work exactly as expected if I use the macOS desktop client.
Anyone investigating this might find the Zoom call logs helpful. I can see the presence status changing in there as well with each /v2/chat/<etc> call at response.presence_status.
Is there any other API property/scope this integration could use that doesn't have this limitation?
The text was updated successfully, but these errors were encountered:
Thanks for the integration!
A while ago, maybe a year ago, this integration stopped working for me. I've come back to it occasionally. Today I discovered something interesting, and it correlates with a change in my use of Zoom at around that time.
I'm able to install the integration and manually POST nonsense to
<base url>/api/zoom
and see it in HA dev tools listening forzoom_webhook
. However actually entering and exiting a meeting doesn't seem to ever trigger the aforementioned event.Turns out that for some reason Zoom doesn't update presence status if you're using the PWA (web app - in my case in Chromium on Linux). It does on the other hand work exactly as expected if I use the macOS desktop client.
Anyone investigating this might find the Zoom call logs helpful. I can see the presence status changing in there as well with each
/v2/chat/<etc>
call atresponse.presence_status
.Is there any other API property/scope this integration could use that doesn't have this limitation?
The text was updated successfully, but these errors were encountered: