core icon indicating copy to clipboard operation
core copied to clipboard

Support for binary sensors

Open glibg10b opened this issue 1 year ago • 2 comments

The problem

Boolean values from Netdata show up as "0.0 boolean" or "1.0 boolean" in dashboard cards. These entities don't work properly with cards that color their icons based on state.

Screenshot_20240707_075005_Home Assistant

What version of Home Assistant Core has the issue?

core-2024.6.1

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

netdata

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

glibg10b avatar Jul 07 '24 05:07 glibg10b

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

Code owner commands

Code owners of netdata 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 netdata 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)


netdata documentation netdata source (message by IssueLinks)

home-assistant[bot] avatar Jul 07 '24 05:07 home-assistant[bot]

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.