-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
Sensor device class docs #5219
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
Sensor device class docs #5219
Conversation
|
||
Home Assistant currently supports a wide range of sensors. They are able to display information which are provides by Home Assistant directly, are gathered from web services, and, of course, physical devices. Please check the sidebar for a full list of supported sensor platforms. | ||
|
||
### {% linkable_title Device Class %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The configuration variables generator is pointing device_class
options to /components/%{component}/#device_class
, so there needs to be a title here for the link to work.
@@ -71,9 +71,10 @@ homeassistant: | |||
|
|||
### {% linkable_title Device Class %} | |||
|
|||
Device class is currently supported by the following platforms: | |||
Device class is currently supported by the following domains: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just wondering: I do understand the difference between platforms (sensor.mqtt
for example) and components (sensor
) - or at least I think I do.
But I've also heard the term "domain" a couple of times. Is a domain the same thing as component or rather the name of a component? Which one is preferred to be used?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that we should avoid using domain here. In the user documentation we should stick to "component" and "platform".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🐦
This reverts commit 76b908b.
Description:
To make the frontend icon package a lot smaller, sensors should in most cases now report their icon via
device_class
(if the device class is common). See home-assistant/core#14010, home-assistant/frontend#1115 and home-assistant/frontend#1100Pull request in home-assistant (if applicable): home-assistant/core#14010
Device Class Icons Screenshot
The page includes a screenshot of all supported device classes. If new device classes are added, this screenshot should also be updated. Use this configuration and setup the new device class template sensors to do so:
Checklist:
current
. New documentation for platforms/components and features should go tonext
.