Resp = await self._request_handler(request)įile "/usr/local/lib/python3.8/site-packages/aiohttp/web_app.py", line 499, in _handleįile "/usr/local/lib/python3.8/site-packages/aiohttp/web_middlewares.py", line 119, in implįile "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 56, in security_filter_middlewareįile "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 18, in request_context_middlewareįile "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 74, in ban_middlewareįile "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 135, in auth_middlewareįile "/usr/src/homeassistant/homeassistant/components/http/view.py", line 128, in handle 22:43:54 ERROR (MainThread) Error handling requestįile "/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py", line 422, in _handle_request Please report issue for fitbit doing I/O at homeassistant/components/fitbit/sensor.py, line 362: result = _access_token(data.get("code"), redirect_uri) 22:43:54 WARNING (MainThread) Detected I/O inside the event loop. Seems to be a perpetual issue for any number of user, for multiple years, any update? Raise_from_error(params.get('error'), params)įile "/usr/local/lib/python3.8/site-packages/oauthlib/oauth2/rfc6749/errors.py", line 405, in raise_from_error Self.token = parse_token_response(body, scope=scope)įile "/usr/local/lib/python3.8/site-packages/oauthlib/oauth2/rfc6749/parameters.py", line 431, in parse_token_responseįile "/usr/local/lib/python3.8/site-packages/oauthlib/oauth2/rfc6749/parameters.py", line 438, in validate_token_parameters Self.token = self._client.parse_request_body_response(r.text, scope=self.scope)įile "/usr/local/lib/python3.8/site-packages/oauthlib/oauth2/rfc6749/clients/base.py", line 421, in parse_request_body_response Response = (method, url, **kwargs)įile "/usr/local/lib/python3.8/site-packages/requests_oauthlib/oauth2_session.py", line 496, in requestįile "/usr/local/lib/python3.8/site-packages/requests_oauthlib/oauth2_session.py", line 446, in refresh_token Response = _request(*args, **kwargs)įile "/usr/local/lib/python3.8/site-packages/fitbit/api.py", line 90, in make_requestįile "/usr/local/lib/python3.8/site-packages/fitbit/api.py", line 68, in _request Result = self.fn(*self.args, **self.kwargs)įile "/usr/src/homeassistant/homeassistant/components/fitbit/sensor.py", line 271, in setup_platformĪuthd_client.system = authd_er_profile_get()įile "/usr/local/lib/python3.8/site-packages/fitbit/api.py", line 285, in user_profile_getįile "/usr/local/lib/python3.8/site-packages/fitbit/api.py", line 256, in make_request TokenExpiredError: (token_expired)ĭuring handling of the above exception, another exception occurred:įile "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 198, in _async_setup_platformįile "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run Url, headers, data = self._client.add_token(įile "/usr/local/lib/python3.8/site-packages/oauthlib/oauth2/rfc6749/clients/base.py", line 198, in add_token
Please try again" errors while using the website.01:31:28 ERROR (MainThread) Error while setting up fitbit platform for sensorįile "/usr/local/lib/python3.8/site-packages/requests_oauthlib/oauth2_session.py", line 477, in request
#FITBIT CONNECT AN UNKNOWN ERROR HAS OCCURRED UPDATE#
We will update this article as fixes for the issues listed here are released.īug: Unable to scroll to see ingredient data when editing a recipeīug: Language setting on Web not being recognized / Keeps reverting to location's default languageīug: Check-In measurements displayed incorrectly in Reports for members with profiles set to track in kg.īug: Newsfeed posts are not being generated for exercise.īug: Print option not working for Recipes in the Blog.īug: Unable to delete a recipe if the website's language is set to anything other than English.įixed 2/22/22: Some users are seeing "A client side exception has occurred" error after logging in.įixed 2/3/22: Intermittent "Sorry.
If that doesn't resolve things, please send us an email about the issue so we can address it. If your issue is not listed below, please try clearing your browser's cache and cookies, as this may resolve unexpected issues. Please accept our sincere apologies for any inconvenience caused by these issues. Where appropriate, we will note any temporary workarounds. If the issue you're reporting is listed below, it's on our radar and under investigation.
0 kommentar(er)
