Denys Dmytriyenko
Denys Dmytriyenko
@rpcme any updates?
Same error here. I've tried multiple different options - my.homeassistant.io, NabuCasa Cloud URL and even Cloudflare Tunnel, nothing works. I do have Webhook working from my bed sensor though, but...
> Right, I just debugged this and made a fix for it. You probably have to renew your client secret for it to work again. @joostlek thanks for fixing it!...
@joostlek Aargh, I'm a complete moron! Somehow I missed that. Thank you! BTW, just using `https:///auth/external/callback` didn't work and gave the same error, but `https://my.home-assistant.io/redirect/oauth` worked fine after a redirect...
Well, the documentation does say if the My integration is disabled, use the FQDN `` for the redirect. But it doesn't specifically say those are mutually exclusive - I was...
Thanks for reopening it after our discussion on G+ I understand the previous fix was to not enable the auto speakerphone on startup. And I can confirm that the volumes...
Also, this entity cannot be assigned to an Area, as it lacks a unique ID and gives an error when trying to do so.
Yes, still the same for me.
So, this issue may be specific to Uptime Kuma running locally as an Add-in on Home Assistant OS (https://github.com/hassio-addons/addon-uptime-kuma). And I had the same issue on 2 separate HA instances,...
Just upgraded to HA Core 2024.04.0 and lost 85% of assigned Areas for Uptime Kuma sensors/services, even on a separate Docker container independent of HA... :(