Raspberry Pi 4 Model B temperature

MarkB1 · June 12, 2020, 7:15pm

I take it you have tried refresh, restart and clear cache?

my lovelace config.

cards:
  - cards:
      - entities:
          - sensor.rpi_cpu_temperature
        font_size: 75
        line_color: red
        line_width: 8
        show:
          average: true
          extrema: true
          fill: fade
          icon: true
          name: true
          points: true
          state: true
        type: 'custom:mini-graph-card'
      - entities:
          - sensor.disk_use_percent
        font_size: 75
        line_color: blue
        line_width: 8
        show:
          average: true
          extrema: true
          fill: fade
          icon: true
          name: true
          points: true
          state: true
        type: 'custom:mini-graph-card'
    type: horizontal-stack
  - cards:
      - entities:
          - sensor.memory_use_percent
        font_size: 75
        line_color: red
        line_width: 8
        show:
          average: true
          extrema: true
          fill: fade
          icon: true
          name: true
          points: true
          state: true
        type: 'custom:mini-graph-card'
      - entities:
          - sensor.processor_use
        font_size: 75
        line_color: blue
        line_width: 8
        show:
          average: true
          extrema: true
          fill: fade
          icon: true
          name: true
          points: true
          state: true
        type: 'custom:mini-graph-card'
    type: horizontal-stack
  - cards:
      - columns: 3
        entities:
          - sensor.ha_uptime
          - sensor.hacs
          - sensor.installed_version
          - sensor.last_boot
          - sensor.last_boot_date_time
          - sensor.latest_available_version
          - sensor.rpi_power_status
          - sensor.rpi_uptime
          - sensor.tasmota_current_version
          - binary_sensor.updater
          - sensor.uptime
        type: glance
    type: horizontal-stack
title: SYSTEM MONITORING
type: 'custom:vertical-stack-in-card'

MarkB1 · June 12, 2020, 7:36pm

what is sensors.yaml?

4walls · June 13, 2020, 1:39am

Yes, I did the refresh and cache clear etc. Still didn’t work.

Sensor.yaml is just split out from configuration.yaml with an include statement.


group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
panel_iframe: !include panel_iframe.yaml
switch: !include switches.yaml
cover: !include cover.yaml
sensor: !include sensors.yaml
ios: !include ios.yaml

MarkB1 · June 13, 2020, 6:56am

Reinstall of custom mini-graph-card via HACS, I am running v0.9.3 ?

Other than that I’m stumped, try opening an issue.

Regards,

4walls · June 14, 2020, 7:46am

Ok, thanks. It’s strange because it worked for a while then suddenly stopped. I have reinstalled all the HACS cards and still no graphing.

4walls · June 16, 2020, 5:37pm

This fixed it:

slim0287 · August 13, 2020, 11:29pm

Just a few days ago, HACS updated [custom-components/sensor.rpi_power](https://github.com/custom-components/sensor.rpi_power) to version 0.2.0. The breaking change was that the rpi_power sensor went from sensor: to binary_sensor:. I did the changes recommended on the Github page (changes to configuration.yaml plus change lovelace cards and automations from sensor.rpi_power_status to binary_sensor.rpi_power_status.) Unfortunately after restarting the server, I get a Notification that “Platform error binary_sensor.rpi_power - No module named 'custom_components.rpi_power.binary_sensor” and the System Monitoring Card from @MarkB1 still does not show “RPi Power Status” (little yellow triangle indicating the entity isn’t available, see below).

This is frustrating because rpi_power is in fact in the custom components directory, and I did exactly what the rpi_power GitHub told me to do. There is no binary_sensor.rpi_power in the entities list. Any ideas?

MarkB1 · August 14, 2020, 7:17am

See the folllowing.

https://github.com/custom-components/sensor.rpi_power/issues/45

Just checked my own as i am not experiencing this.

I manually installed 0.1.5 and it still works fine for now, might not in future, will cross that bridge when I get to it.

slim0287 · August 14, 2020, 11:19am

Thanks. I used the process proposed by regystro:

This brought the integration to 0.2.0 and it works. So, if you want to upgrade to 0.2.0, it appears to be a working process.

CaptainSweatpants · August 26, 2020, 4:12am

Could you post the steps? seems that link gets the good ol 404 now.

MarkB1 · August 26, 2020, 6:19am

I had to manually download the zip and extract the files into

config.yaml

binary_sensor:
  
  #=======================
  #=== Raspberry Pi Power
  #=======================

  - platform: rpi_power

CaptainSweatpants · August 26, 2020, 8:25am

I used HACS to install it, maybe that’s my problem. I set it up as a binary sensor but still got that error.

I’ll try manually downloading the files and moving them over.

kiwipaul · September 21, 2020, 9:02am

I am getting the error afer I set this up using HACS

Platform error binary_sensor.rpi_power - No module named 'custom_components.rpi_power.binary_sensor'

When i check the configuration and I am reasonably sure that I have the files in the right place, the yaml references from above etc.

Any other thoughts?

stevevanhoyweghen · September 25, 2020, 7:57pm

Still the same here as well … Entity not available: binary_sensor.rpi_power_status
I reverted back last month. Now tried again. Still not working.
Uploaded with HACS seems to be the breaking issue …
I remember there was a discussion with the developers mentioning this was done to migrate it into HA. But I cannot find back this discussion anymore.

So need to revert back to the previous version again …

MarkB1 · September 26, 2020, 7:24am

Hi,

I have not installed via HACS, All I did is download the zip archive from the Github page, extract and copy the
folder custom_components/rpi_power to

My updated YAML code.

sensor:

#==================
#=== System Sensors
#==================

  - platform: command_line
    name: RPi CPU Temperature
    command: "cat /sys/class/thermal/thermal_zone0/temp"
    value_template: "{{ value | multiply(0.001) | round(2) }}"

  #===========================================
  #=== Latest Tasmota firmware version
  #===========================================

  - platform: command_line
    name: Tasmota Current Version
    command: "curl -s https://github.com/arendst/Tasmota/releases/latest | cut -d'\"' -f2 | rev | cut -d'/' -f1 | rev"
    scan_interval: 86400

  #==============================
  #=== Installed hass.io version
  #==============================

  - platform: version
    name: Installed Version
    source: local


  #================================
  #=== Latest Available HA Version
  #================================

  - platform: version
    name: Latest Available Version
    beta: false
    image: raspberrypi4
    source: hassio


  #=============================================
  #=== Last boot time, Disk, memory & CPU usage
  #=============================================

  - platform: systemmonitor
    resources:
      - type: last_boot
      - type: disk_use_percent
        arg: /
      - type: memory_use_percent
      - type: processor_use


  #===================
  #=== System Up Time
  #===================

  - platform: uptime

  - platform: template
    sensors:

      #==========================
      #=== Home Assistant uptime
      #==========================

      ha_uptime:
        friendly_name: HA Uptime
        value_template: >
          {% if states('sensor.uptime') == '0.0' %} 
            Just restarted...
          {% else %}
            {% macro phrase(value, name) %}
            {%- set value = value | int %}
            {%- set end = 's' if value > 1 else '' %}
            {{- '{} {}{}'.format(value, name, end) if value | int > 0 else '' }}
            {%- endmacro %}
            
            {% set weeks = (states('sensor.uptime') | int / 7) | int %}
            {% set days = (states('sensor.uptime') | int) - (weeks * 7) %}
            {% set hours = (states('sensor.uptime') | float - states('sensor.uptime') | int) * 24 %}
            {% set minutes = (hours - hours | int) * 60 %}

            {{ [ phrase(weeks, 'week'), phrase(days, 'day'), phrase(hours, 'hr'), phrase(minutes, 'min') ] | select('!=','') | list | join(', ') }}
          {% endif %}

      #=========================================
      #=== Raspberry Pi last boot date and time
      #=========================================

      last_boot_date_time:
        friendly_name: Last Boot
        value_template: >
          {% set date = as_timestamp(states('sensor.last_boot')) | timestamp_custom('%d') %}
          {% set date = '{:01}'.format(date | int) %}
          {% if date in ('1', '21', '31') %}
            {% set date = date ~ 'st' %}
          {% elif date in ('2', '22') %}
            {% set date = date ~ 'nd' %}
          {% elif date in ('3', '23') %}
            {% set date = date ~ 'rd' %}
          {% else %}
            {% set date = date ~ 'th' %}
          {% endif %}

          {{ as_timestamp(states('sensor.last_boot')) | timestamp_custom('%H:%M on %a') }} {{ date }} {{ as_timestamp(states('sensor.last_boot')) | timestamp_custom('%b %Y') }}

      #=========================
      #=== Raspberry Pi Up Time
      #=========================

      rpi_uptime:
        friendly_name: RPi Uptime
#        entity_id: sensor.time
        value_template: >
          {% set up_time = as_timestamp(now()) - as_timestamp(states('sensor.last_boot')) %}

          {% set minutes = (up_time // 60) | int %}
          {% set hours = (minutes // 60) %}
          {% set days = (hours // 24) %}
          {% set weeks = (days // 7) %}

          {% set minutes = (minutes % 60) %}
          {% set hours =  (hours % 24) %}
          {% set days = (days % 7) %}

          {% macro phrase(value, name) %}
                    {%- set value = value %}
                    {%- set end = 's' if value > 1 else '' %}
                    {{- '{} {}{}'.format(value, name, end) if value | int > 0 else '' }}
          {%- endmacro %}
                    
          {% set text = [ phrase(weeks, 'week'), phrase(days, 'day'), phrase(hours, 'hr'), phrase(minutes, 'min') ] | select('!=','') | list | join(', ') %}
          {% set last_comma = text.rfind(',') %}
          {% if last_comma != -1 %}
            {% set text = text[:last_comma] + ' and' + text[last_comma + 1:] %}
          {% endif %}
          
          {{ text }}

    
### BINARY SENSOR  ###

binary_sensor:

  #=======================
  #=== Raspberry Pi Power
  #=======================

  - platform: rpi_power

johny_mnemonic · September 27, 2020, 5:12pm

Yeah. Looks like the author @swetoast broke it for 0.2.0 version and when people complained he told us, that he is not going to fix it as this is the last version which he is now integrating into HA (in this broken state).
And as probably more people complained about such move, he went on and disabled “Issues” section on Github. Fine chap, isn’t he?

MarkB1 · September 27, 2020, 5:21pm

It works if you install it as I mentioned above, don’t install with HACS use manual method.

A tad unfair to the author in my opinion…

johny_mnemonic · September 27, 2020, 8:39pm

Maybe. It is his creation, so he has full right to also break it. That’s true.

But why disabling “Issues” section in the repo?
Even if he has no intention to help people to make that broken version working, there are others that provided hints and guides how to make it work. And having it right there in the repo would be much better than here in the forum.

Ali-Almarri · October 10, 2020, 11:38am

Hi ,
What is the difference between these integrations ?
1- https://www.home-assistant.io/integrations/rpi_power/

And

2- https://github.com/custom-components/sensor.rpi_power

vojtechkoval · March 6, 2021, 11:26pm

It should be under binary_sensor section. See:

 binary_sensor:
   - platform: rpi_power
     text_state: True