home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.8k stars 30.9k forks source link

spaceapi: sensor values must be numbers, not strings #122252

Open Xiretza opened 4 months ago

Xiretza commented 4 months ago

The problem

The spaceapi integration exports sensors in the following format:

"sensors": {
    "temperature": [
        {
            "name":"Temperature",
            "value":"24.23",
            "location":"inside",
            "unit":"°C"
        }
    ]
}

The spaceapi schema clearly states that the value field must be a number, not a string. This causes the spaceapi JSON exported by the integration to fail validation.

What version of Home Assistant Core has the issue?

2024.7.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

spaceapi

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

spaceapi:
  sensors:
    temperature:
      - "sensor.my_temp_sensor"

Anything in the logs that might be useful for us?

No response

Additional information

No response

mib1185 commented 4 months ago

Hi This is a custom component, which is not maintained by the HA core project. Please report your issue to the maintainer or in the source repository of this custom component. Thx 👍

Xiretza commented 4 months ago

What are you talking about? The source is right here: https://github.com/home-assistant/core/blob/dev/homeassistant/components/spaceapi/__init__.py

home-assistant[bot] commented 4 months ago

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

Code owner commands Code owners of `spaceapi` 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 spaceapi` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


spaceapi documentation spaceapi source (message by IssueLinks)

mib1185 commented 4 months ago

sorry, was confused by the provided link in the description

issue-triage-workflows[bot] commented 1 month ago

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.

Xiretza commented 1 month ago

Unsurprisingly, it hasn't fixed itself, and closing it won't fix it either.