In the browser it is. In the official android app it only comes up with a blank screen when I’m using ssl, but since it is in very early development I’m thinking this is a different issue. I’m using https://ip:port as the url, if that matters.
I can’t say I have ever tried https with specifying a port in HassIQ. If you could use the default port of 443 and not specify it, that might be worth a try.
Thanks for gettign back to me. I just tried to go with the default port, but everything behaves the same. I tried both https://ip and https://ip:443. It’s reachable in the browser, but the watch comes up with “-300”. Could the certificate be the problem, since it is not trusted?
I had the same issue and solved it by using DuckDNS - so I guess that it is a certificate issue.
See my previous post from jul 9th
Thanks for the info. That doesn’t look good for me. I don’t want to expose my HA to the internet either, but I don’t think my router supports static host entries. At least I can’t find anything like it. Do you by chance know If this is achievable in a different way, if the router doesn’t have the necessary features?
This thread is awesome (and long 
)
Just ordered my vivoactive 4 to track my sleep, stress level and start to run again.
My TomTom is old…need a rest.
I’m a vivid Home Assistant user, and just found out this app was there, thanks Alan!
Can’t wait to fiddle with it, and maybe even support it somehow, I can code a little.
1 Like
I just saw this app and what to set it up. Reading the thread it mentions password but it appears the app now requires a long live access token. Is this correct? If so, do I create a new token, use an existing token or setup something else?
A long live access token is optional. If you don’t specify one HassIQ will have you auth to your HA instance through your phone initially.
1 Like
Just wanted to add my thanks for this app. It’s not super useful on my fenix 3, but it’s amazing on the wife’s vivioactive 3. Thanks for the great work, much appreciated.
1 Like
So if you get status 0, and 401 what does it mean?
401 mean Unauthorized. Are you using the access token or logging in through your phone?
Through the phone. It is now working. Not sure what changed? It did ask for my username and password several times.
Hi all
I have a Fenix 6 Pro and I’m trying to get hassiq setup. I have a nabu casa subscription and I’ve created a group with some light entities. Running Hassio on a Rpi4.
HassIQ Settings:
Host: Nabu Casa URL
Visible Group: group.garmin (This group is visible in Hassio)
Long lived Access Token: Token created in Hassio,
I get a status:-104.
Any ideas of suggestions please.
Do you have anything in this group.garmin group already added? I mean do you have there some entities?
Hi
Yes, I’ve added 2 light entities and they are visible under the group in Hassio.
Can you see any connection hitting the nabu casa server?
I don’t have Nabu Casa yet, so I don’t know if you can see there anything.
Are you sure the token is correct?
I’ve been using nabu casa successfully since last year sometime so that’s definitely working.
For the token, I’ve generated a new long lived token on my phone, copied and pasted from hassio app to garmin iq app so that I don’t have to type that long token and risk typos.
I’ve tried the above several times. I also tried no token, tried local network IP address. I can access hassio from my phone in browser using local ip, companion app is connecting via nabu casa.
Works very well for me thank you so much, very cool!
Watch is Fenix 5 Plus
I’m connecting via my public accessible (Reverse Proxy on Synology) homeassistant 
@cdrom1028 have managed to work this out with nabu casa. Maybe he can share the config.
In the meanwhile, could you please show me the config screen from Garmin Connect app? Of course obfuscate the private data
