Originally I subscribed to Nabu Casa for ‘remote access’ and also for ‘my Alexa/Google devices to gain access to my Home Assistant entities and scripts’.
Since then, my HA instance is remotely accessible via DDNS custom domain + Nginx reverse proxy at: HTTPS://hassio.mycustomdomain.com.
Question #1:
Do I still need Nabu Casa if I don’t use its remote access capability anymore and still want my Alexa/Google devices to access my Home Assistant entities and scripts?
Everyone in my family has Home Assistant Companion installed on their Android mobile devices. Their mobile apps connects to: HTTPS://hassio.mycustomdomain.com
All respective Refresh Tokens for our mobile devices look normal (see below screenshot) with the exception of my personal mobile phone with a weird Refresh Token that doesn’t identify itself correctly: https://home-assistant.io/androidinstead ofhttps://hassio.mycustomdomain.com
Question #2:
How do I fix my mobile phone’s HA Companion app so it identifies itself in a normal fashion just like all my other mobile devices? Why is this even happening?
Q1: subs to Nuba casa are used to support the project and development so it’s good to keep them going, however more importantly to your question, for google and or Alexa integration you can set them up manually but it’s a massive ball ache to get working and maintain it, where as with nabu case it’s a 30 sec switch of a button and it’s all maintained for you.
Q2: is that not simply a local network login rather than a remote login from your phone?
Q2: I have all the mobile devices configured the same way… they allow authentication as a Trusted Network whether from a public IP or internal. This is the only mobile device that I’m forced to use an explicit local login as opposed to a Trusted Network. I’ll try to reset the app per @aceindy 's advice to see if that fixes this issue.
