Hi, I’m writing here because I really don’t know if it’s a configuration problem or an Android app problem.
I’ll try to proceed in order:
after the first configuration I tried to use duckdns addon (already used in the past on RPI but not with HA). Everything ok the first 2 days, then problems with remote access. That is, I could access remotely via Chrome with ‘https://myaddressregistered.duckdns.org’ but not via app. Locally the app worked.
to see it remotely I tried (via the Chrome drop-down menu) to do ‘add to home screen’ where I was offered a link or to download an app. trying to download an app took me back to the PlayStore but made me download an app version 1 (?) which in reality still turns out to be a web link. however it worked since I could access it easily via Chrome, but I had no way of configuring the permissions.
I tried removing apps, clearing cache and data and reinstalling, because Companion App disappeared.
I then tried Cloud HA which, I don’t know why, made me download the app again, and during the server search it suggested my duckdns server (of course the URL saved inside the app was the one created by the Cloud). And everything worked perfectly, both locally and remotely.
If I remember correctly two days ago there was an update of the duckdns addon, so I decided to try again, I disabled the Cloud, changed the URLs, checked the logs and everything worked.
Last night I installed the correct app (2025 1.2-full) but I had to log in via Nabu, disable the Cloud, change the URL and finally everything worked again, locally and remotely, Companion App reappeared, all ok.
Today instead I find myself that:
- I can access it remotely from both Chrome and the app without any problems via mydns.duckdns.org:8123;
- locally only access via Chrome with https://myStaticIP:8123;
- if I log in from the app I can’t do it locally, but I have to log in remotely first (disabling wifi) and then, once logged in, reactivate wifi (even though both in /Settings/System/Network and in Companion App the internal URL is configured as the URL used to log in locally on Chrome, and it is https which takes me back to http, otherwise it tells me it expects certificates). When I reactivate wifi after logging in, I can be ‘local’ as I see it through the phone entities on HA.
Sorry, I know it’s very long and detailed but I don’t understand if it’s a bug in the app, a bit of chaos with duckdns, or more simply my configuration errors.
I’m waiting for questions for clarification when your headache has passed…