Hmm, maybe. Depends on the infrastructure they put up. If there is a separate domain for the telemetry, then you can block it. Still no guarantee that it still works though.

The app will need internet access to login though. That really is a cat and mouse game that is not worth your time I’d say.

I regularly comments from users who were not aware or the financial situation. Maybe “we” need to promote it a bit more. But it is 332 per week, not month. At the beginning of the last migration it stood at 40 something, so we at least got some traction.

Thanks for the update and thanks for the work guys, I really appreciate it

Nope, that doesn’t sound right.

I just tried all of your use cases and it works for me every time, HA in the foreground, background, closed; the command changes to the HA app and the right page.

One thing you should check: Android Settings, Apps, Special app access, Display over other apps, -> make sure home assistant is enabled here. If that doesn’t help I’m out of ideas and suggestions for the moment.

I was curious about this so I tested it on my systems. Path refers to the part after your domain. So, if your settings page is available under https://homeassistant.mydomain.com/config/dashboard (check with your desktop or mobile browser to get the exact URL, then you would use “/config/dashboard” as your path setting. Same for any lovelace dashboard, check the URL in your browser, if it is https://homeassistant.mydomain.com/lovelace-mobile/0, then use “/lovelace-mobile/0” as the path argument. lovelace-mobile is the dashboard part, 0 corresponds to the tab.

Hope this helps!

Yup, same here. Let’s put our money where our mouths are. I also cross posted this info to the main feed on the instance I use. We should spread the word.