isaa-ctaylor / ha-controller Goto Github PK

Says it on the tin!

This issue is for the purpose of tracking the development of brightness controls.

Hello.
I've done all the steps outlined... Have the app on my Sense, have the token and https access to my HA installation. But... The app is not connecting, just says "Phoning home..." on the screen. So I'm guessing step two, enabling Home Assistant API is not actually done. I've looked at the support pages but don't understand what needs to be done to enable the API. Can you provide some direction?

This issue is for the purpose of tracking the development of error displays

Describe the bug

I'm not entirely sure this use case is supported :) I have an instance of home assistant running on a "local" network. It's just my home network, so it's in 192...*. The long story is that it's running on a Kubernetes cluster, and the service is a Node with a port accessible only from the same network. I generated SSL certificates for this HA instance (to enable encrypted traffic), and this certificate is installed on my phone. I can access my HA from my phone with the official app.

To Reproduce

• I entered the url in the app settings: 192.168.0.103:8123
• I entered a freshly generated long-lived token
• I enabled the home assistant API (at least I think I did...) by adding api: at the end of my config, and I restarted the HA instance
• I installed the app on my fitbit sense and tried to open it. It just says "phoning home"
• My phone is connected to the wifi and the wifi is setup on my watch too

Expected behavior

I expected the app on the watch to go past the "phoning home" screen

Smartphone (please complete the following information):

• OS: Android

Fitbit device (please complete the following information):

• Device: Fitibit sense

This issue is for the purpose of tracking the development of coloured light support.