Can this be added please?

1. URL from Nabucasa
2. Port is default 8123
3. generated in HA
4. API activation means in config only: "api:"
   correct? Does not work for me.

title says it all really :)

i use a lot of button entities to trigger stuff, would be awesome if i could press them on my watch!

New to fitbit, and no idea how the fitbit environment/API(s) work, but was excited to see your app pop up.

I think I've configured everything correctly:
My settings are:
URL: https://something.duckdns.org
PORT: 443
Token: myrandomlonglivetokenhere
Not sure how to debug, but there's no error just:
Home Assistant N/A

I also don't see any errors in my HA logs. I've tried with an internal IP, with/without the port, and with/without the protocol. I've also set up the prequisites in your readme. Honestly haven't looked to deep, so very possible I am missing how it's all wired together, but in companion/index.js won't that Token always be pulling the hard coded global at the top?
else if (evt.key === "entities") { sendData({key: "clear"}); JSON.parse(evt.newValue).forEach(element => { fetchEntity(address(), Token, element["name"]); }) }

i read the guide on https://dev.fitbit.com/build/guides/publishing/ but i cannot figure it out.

Connection Error showing on screen of the Sense watch.
In the app settings I have the https://1234567.xyz domain listed that I access HA from.
The port is left blank and I have added a single entity name to test with so far. A freshly created token has been pasted into the app as needed.
I do also have "api:" in my configuration.yaml file
What else might be causing the connection error?

Hey,
I am unable to connect to my HA. I am running Home Assistant 2023.1.2 and own the Fitbit Sense.
I was able to connect to the api via
curl -X GET -H "Authorization: Bearer eyJhbdKo..." -H "Content-Type: application/json" http://192.168.178.96:8123/api/
but HA-Remote always returns a connection error.

App settings:
URL:
http://192.168.178.96
Port:
8123
Token:
eyJhbdKo... and so on

Regards
Jannik

Hey @smirko-dev, could you please remove hardcoded 8123 port in api calls? I'm using nginx for ssl termination and expose default ssl 443 port outside. I tried to configure URL in the app as https://host:port but obviously it does not work

Hey Mirco, thats me again with another feature idea (does not know how to set a 'feature' label for a new issue).

I saw that my configured entity list (10 positions at the moment) has a random sort order in watch app - I suspect this is results from first get first serve, so whenever I run the app on the watch there is in fact no sorting mechanism applied for the entity list.
It would be nice to initially create an array of entities within companion app (fetchEntity) that is connected to some kind of ID (sort key) and always fetched with this order. I wish every time I run the app to have the same entity order (could be the order from settings list or at least to sort by entity name).
What do you think?
Cheers

Hi,

I just wanted to ask if maybe something has changed over last two years in regard to being able to connect via nabu casa or a local HTTP?
I'd love to use the app, but no way Im gonna do local https, too many complications :(

It would be amazing if I could enter the id for my hive thermostat
And it then show the temperatures

Even better it allow me when clicking the entity to turn it up or down with maybe up or down arrows?
(I already have a script which I click which turns the hive onto boost for 30mins)

I haven't even really used the app yet--I
just wanted to say Thank You for spending your time building it... It's definitely needed!

I've created a long access token, set my url, port and new token,
then added a single switch entity
BUT the app says connection error
BUT HA also keeps saying access is denied then after 3 tries opening the app on my watch
HA bans me from logging in for 5mins?