Fitbit Integration Broken

DrewXT · June 30, 2022, 1:22am

Hi Folks,

seems that the Fitbit integration has broken since 2022.6.5 or 2022.6.6.

When I try and reconfigure it, I get the following error - I’ve looked into the code for the integration, but can’t see anything that might be causing it (not that I’m a coder by any stretch)

I’ve found a few topics talking about the Fitbit integration being updated, but doesn’t appear like it’s ever happened.

Has anyone else come across this and been able to resolve it?

tom_l · June 30, 2022, 1:28am

It has been reported:

github.com/home-assistant/core

Setting up the Fitbit integration seems broken

opened 07:22PM - 29 May 22 UTC

natbrood

integration: sensor integration: fitbit

### The problem Setting up the Fitbit integration seems to be broken for a few …versions now. Last time I've seen it working was Oct 2021. When adding Fitbit to the sensors in the configuration.yaml does create the fitbit.conf for you. Filling in your id and secret does not seem to change anything. In the past (as well in the documentation) there were persistent notifications telling you what to do. These are not here. So the information of what I'm supposed to do, what url to use, those don't appear ### What version of Home Assistant Core has the issue? core-2022.5.5 ### What was the last working version of Home Assistant Core? core-2021.10.? ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Fitbit ### Link to integration documentation on our website https://www.home-assistant.io/integrations/fitbit/ ### Diagnostics information Log Details (ERROR) Logger: homeassistant.components.sensor Source: helpers/network.py:207 Integration: Sensor ([documentation](https://www.home-assistant.io/integrations/sensor), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+sensor%22)) First occurred: 9:06:39 PM (1 occurrences) Last logged: 9:06:39 PM Error while setting up fitbit platform for sensor Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform await asyncio.shield(task) File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 58, in run result = self.fn(*self.args, **self.kwargs) File "/usr/src/homeassistant/homeassistant/components/fitbit/sensor.py", line 243, in setup_platform redirect_uri = f"{get_url(hass, require_ssl=True)}{FITBIT_AUTH_CALLBACK_PATH}" File "/usr/src/homeassistant/homeassistant/helpers/network.py", line 168, in get_url request_host = _get_request_host() File "/usr/src/homeassistant/homeassistant/helpers/network.py", line 207, in _get_request_host raise NoURLAvailableError homeassistant.helpers.network.NoURLAvailableError ### Example YAML snippet ```yaml sensor: - platform: fitbit clock_format: 12H monitored_resources: - "activities/steps" - "activities/distance" - "activities/heart" - "sleep/timeInBed" - "sleep/minutesAsleep" - "sleep/efficiency" ``` ### Anything in the logs that might be useful for us? _No response_ ### Additional information My guess is that notifications have changed somewhere between Q3 2021 and today. But I could be wrong.

There is a guide here that some have roported success with:

DrewXT · June 30, 2022, 4:40am

yeah, thanks @tom_l - I tried the Multiple Accounts custom component, but it returns the same error, so I wasn’t sure if it were the Integration or something core to Home Assistant…

DrewXT · June 30, 2022, 10:59am

well, that was odd, turns out there was something unexpected with my backup copy of fitbit.conf, which has worked in the past.

all sorted now, but doesn’t explain why the integration broke with an upgrade…

Goalpwr · October 31, 2022, 2:38am

I’m having the same error as you mentioned above but it’s still not working. I was using the multi-account fitbit method as listed here: Home-Assistant/Fitbit - Add Multiple Accounts at main · TheTroubleshooter/Home-Assistant · GitHub so I tried blowing the entire fitbit integration away and starting from scratch but it still pops that error "Failed to call service configurator/configure. unexpected end of data: line 4 column 2 (char 83). @DrewXT what did you do to fix it?

DrewXT · November 27, 2022, 10:07am

At the the I set it up again, and it started working.

It’s just broken again, so I’ve set up MyFitnessPal as a conduit from Fitbit to Garmin, and using the Garmin connect integration to pull the Fitbit data I was pulling directly.

Almost syncs in real time with a free account in MyFitnessPal, and I already use a Garmin Epix2 as my sports watch