Hi.
When i go to Configuration > Home Assistant Cloud, i noticed “Remote Control” being toggled off after the upgrade. When i try to toggle it on, i get a dialog “Unexpected Error:” and OK as option.
“Nabu Casa Account” reports a ‘Connected’ state in the same window.
I signed out, and upon trying to sign in again, i get “Unexpected error: Handler is already defined!”
What could i try to solve this?
just upgraded and have the same issue
I see a RemoteNotConnected error in the logs
I got the same problem. Logged out of both cloud integration and on Nabu Casa website then logging in again on both places and connecting from Nabu Casa. After that it worked normal to connect remotely.
After restart HA the error is back again.
hi there,
I have the same issue here
Same issue here.
Remote Control swith in server configuration does not work either. Message: Unexpected error
Same issue since today in the morning after the upgrade to 0.108.7
This has happened to me since 0.108.5 for some reason, have you tried unlinking the account ----> Restart Home Assistant ----> relinking account? This worked for me to get Nabu Casa working
I did as you suggested and it worked for me. Strange thing is that yesterday it stopped working without me touching anything regarding the configuration. I’ll keep the thing monitored to check if it happens by itself somehow.
As mentioned by HBK1 above - this only lasts until the first reboot - than you have to repeat…
Unfortunately, the 0.108.7 release missed an essential update. 0.108.7 has been pulled and 0.108.8 is currently building and should be available shortly (fixing this issue).
Updating to 0.108.8 solves it thank you!
no problems 
Just here to help out the community by sharing. Everyone here on the Home Assistant Community is very friendly
Wow - you guys are fast - those things can happen
Do I have to downgrade first to 108.6 (as this would be the only option for me at the moment)
I probably just have to be patient? Intel NUC?
It can take up to 2 hours to receive your update
Hi, Any chance as problem above have impact also on remote access configured with Duck DNS?
Not sure from when, maybe Monday I’m not able to access HA via browser or HA app when I’m in home wifi (access via lan IP work), mydomain.duckdns.org:8123 ends with 403:forbidden message
Before everything worked fine, I was able to connect from my home net with IP or my domain.duckdns.org and with duckdns from external access
What can I check?
I find a solution for my case
My external IP was on banned IP list