Raspberry Pi Power Sensor (updated: 2018-07-25) / Use Github for reports in the future

DavidFW1960 · July 24, 2018, 11:32am

ok doesn’t work… I’m going with yours.

ludeeus · July 24, 2018, 11:33am

That platform does not support templates.
You need to add a template sensor for that, and when getting attribute values in templates it is recomended to use this syntax:

value_template: "{{ state_attr('sensor.rpi_power_status', 'description') }}"

klogg · July 24, 2018, 11:37am

Interesting.
Apart from the fact that it is definitely better looking what is the reason it is the recommended syntax? I’m not questioning your authority, far from it, I am off now to change all my occurrences for this far more readable syntax!

Thanks for the pointer.

DavidFW1960 · July 24, 2018, 11:41am

ok here’s what is working…

# RPI Power
  - platform: rpi_power
  - platform: template
    sensors:
      rpi_power_description:
        friendly_name: "RPi Power Status"
        value_template: "{{ state_attr('sensor.rpi_power_status', 'description') }}"
        icon_template: mdi:raspberrypi

ludeeus · July 24, 2018, 11:43am

It will render None if it fails to get the state of the attribute, where states.sensor.rpi_power_status.attributes.description will fail ang give you a “render” error in your log

klogg · July 24, 2018, 1:32pm

I’ve answered my own question about what the zero actually means by the simple method of looking at the code. It always helps… My mistake, sorry.

But @toast having looked at it can I offer a small correction to the throttled text descriptions?

I think

self._description = 'A under-voltage has occurred.'

should be

self._description = 'An under-voltage has occurred.'

and shouldn’t these two

self._description = 'ARM frequency capped has with under-voltage.'
self._description = 'ARM frequency capped has with under-voltage.'

be

self._description = 'ARM frequency capped due to under-voltage.'
self._description = 'ARM frequency capped due to under-voltage.'

I promise I’m not trying to be picky, I really like this component so thank you for writing it.

toast · July 24, 2018, 3:36pm

got a pr for it and merged it so there is an updated version with grammatical fixes

DavidFW1960 · July 25, 2018, 12:35am

Thanks for that!

I made an automation to message me if there is a power problem - basically if the status is > 0
Does this look like it would work?

- id: '1532478833426'
  alias: Power Problem Notification
  trigger:
  - above: '0'
    entity_id: sensor.rpi_power_status
    platform: numeric_state
  condition: []
  action:
  - data:
      message: Power Problem Detected
    service: notify.notify

ludeeus · July 25, 2018, 8:57am

- above: '0'
should be:
- above: 0
Other than that it should work

Why: it expects an int and not a string

DavidFW1960 · July 25, 2018, 9:15am

Thanks for that! FWIW the automation editor put it in quotes.

klogg · July 25, 2018, 9:32am

I’ve got this, it gives slightly more information and I’m using it in an HA persistent notification.

  # Raspberry Pi Power
  - alias: Device - Power alarm
    initial_state: on
    trigger:
    - platform: numeric_state
      entity_id: sensor.rpi_power_status
      above: 0           
    action:
      service: script.notify
      data_template:
        message: >
          # WARNING - There is a power supply problem.

          Status code - {{ state('sensor.rpi_power_status') }}
          {{ state_attr('sensor.rpi_power_status', 'description') }}

ludeeus · July 25, 2018, 9:42am

For those that have made a template sensor to show the description as the state there is now a config option that let you do that without creating a seperate sensor for it.

https://github.com/custom-components/sensor.rpi_power/pull/4

toast · July 25, 2018, 10:21am

merged and updated op

maurizio53 · July 25, 2018, 10:58am

Is this correct? Does it means i have all ok on my rpi?

Which is the meaning of “none” ?

maurizio53 · July 25, 2018, 11:07am

I have this on my group.yaml:

sensor.rpi_power_description
sensor.rpi_power_status

But i get this on my frontend:

Why the same name?

klogg · July 25, 2018, 12:16pm

Edited for typos.

Assuming you have the new latest version (0.0.7) of the sensor, this should work (it is what I have).

sensor:
  # Raspberry Pi Power
  - platform: rpi_power
    text_state: True

group:
  system:
    - sensor.rpi_power_status

automation:
  # Raspberry Pi Power
  - alias: Device - Power alarm
    initial_state: on
    trigger:
    - platform: numeric_state
      entity_id: sensor.rpi_power_status
      above: 0           
    action:
      service: script.notify
      data_template:
        message: >
          # There is a power supply problem.

          Status code - {{ state_attr('sensor.rpi_power_status', 'value') }}
          {{ states('sensor.rpi_power_status') }}

Sunonline · July 25, 2018, 12:25pm

for automation.rpi_power_status

message: "Warning, currently your raspberry pi is {{ states.sensor.rpi_power_status.state }} and {{ state_attr('sensor.rpi_power_status', 'description') }}."

toast · July 25, 2018, 12:35pm

Glad to see so much activity on this thread nice when my first project really comes to life also grad for the pr that people have created on github save me time and makes the component much better.

ludeeus · July 25, 2018, 12:52pm

If you want to use both variants, you need to add it twice.

sensor:
  - platform: rpi_power
  - platform: rpi_power
    text_state: True

note that the entity_id for one of them will be sensor.rpi_power_status_2

DavidFW1960 · July 26, 2018, 12:13am

Awesome work @toast & @ludeeus

Is this automation ok?

- id: '1532478833426'
  alias: Power Problem Notification
  trigger:
  - above: 0
    entity_id: sensor.rpi_power_status
    platform: numeric_state
  condition: []
  action:
  - data:
      message: "Warning, currently your raspberry pi is {{ states.sensor.rpi_power_status.state }} and {{ state_attr('sensor.rpi_power_status', 'description') }}."
    service: notify.notify

May as well be sure…