Closed WarrenSchultz closed 1 year ago
For a single attribute (as I've been finding out how to do this aswell) You can add an Entity Then add the attribute Throttle there
Had trouble in Entities but eventually figured out it needs to start with a lower case, so throttle, not Throttle which the attribute is listed as.
so add
- type: attribute
entity: sensor.rpi_monitor_weatherhat
attribute: throttle
name: Throttle status
in the Code Editor and you can do it for others as well.
@bsimmo Thank you, I've also added this info to the card README. Asking for your blessing, after the fact, for using your graphic. thanks!
See: https://github.com/ironsheep/lovelace-rpi-monitor-card#example-monitoring-of-specific-attributes
So, I'm new to MQTT, and things have also changed in HASS's MQTT implementation (config YAML to UI), so finding solid answers via Google is a bit challenging right now. :)
I'm interested in surfacing some of the other variables that are currently being sent to HASS, but not directly usable (as far as I understand).
As part of the data block, I get "throttle": [ "Under-voltage has occurred", "Throttling has occurred" ],
(As well as the CPU load averages, temperatures, etc.)
I'd like to be able to pull some of those values into individual sensors, rather than the text block that your Lovelace custom card displays. Is there a way to do that as currently designed, or is that a code change to make additional (state topics?) ? My attempts to achieve this in the configuration.yaml haven't been successful, so any tips would be appreciated.