Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to add FastDotCom integration #98341

Closed
Quentame opened this issue Aug 13, 2023 · 4 comments
Closed

Unable to add FastDotCom integration #98341

Quentame opened this issue Aug 13, 2023 · 4 comments

Comments

@Quentame
Copy link
Member

The problem

Can't add the fastdotcom integration, check logs and yaml below.

Disabled my AdGuard filtering.
Living in France.
Running in a container on a NAS.

On SpeedTestDotNet, I also get #85375 and #80290, maybe it's linked

What version of Home Assistant Core has the issue?

core-2023.8.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

fastdotcom

Link to integration documentation on our website

https://www.home-assistant.io/integrations/fastdotcom

Diagnostics information

No response

Example YAML snippet

fastdotcom:
  scan_interval:
    days: 1

Anything in the logs that might be useful for us?

Logger: homeassistant.components.sensor
Source: components/sensor/__init__.py:595
Integration: Capteur (documentation, issues)
First occurred: 17:05:38 (2 occurrences)
Last logged: 17:05:39

Error adding entities for domain sensor with platform fastdotcom
Error while setting up fastdotcom platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 591, in state
    numerical_value = int(value)
                      ^^^^^^^^^^
ValueError: invalid literal for int() with base 10: 'unknown'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 510, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 750, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1004, in add_to_platform_finish
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 746, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 808, in _async_write_ha_state
    state = self._stringify_state(available)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 752, in _stringify_state
    if (state := self.state) is None:
                 ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 595, in state
    raise ValueError(
ValueError: Sensor sensor.fast_com_download has device class 'data_rate', state class 'measurement' unit 'Mbit/s' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: 'unknown' (<class 'str'>)

Additional information

No response

@home-assistant
Copy link

Hey there @rohankapoorcom, mind taking a look at this issue as it has been labeled with an integration (fastdotcom) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of fastdotcom can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign fastdotcom Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


fastdotcom documentation
fastdotcom source
(message by IssueLinks)

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@Quentame
Copy link
Member Author

Not stale

@Quentame
Copy link
Member Author

Quentame commented Dec 8, 2023

Solved with 2023.12.0
Thanks !

@Quentame Quentame closed this as completed Dec 8, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Jan 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants