Updated to 0.63.2 - system monitor load sensors have disappeared :P

As the title suggests the load_/1m/5m/15m have all disappeared :frowning:

They are no longer reported in the states table (under win 10) and therefore don’t appear in my groups.

Config in sensors.yaml…

- platform: systemmonitor
  resources:
    - type: disk_use_percent
      arg: c:\
    - type: disk_use
      arg: c:\
    - type: disk_free
      arg: c:\
    - type: disk_use_percent
      arg: d:\
    - type: disk_use
      arg: d:\
    - type: disk_free
      arg: d:\
    - type: disk_use_percent
      arg: g:\
    - type: disk_use
      arg: g:\
    - type: disk_free
      arg: g:\
    - type: disk_use_percent
      arg: q:\
    - type: disk_use
      arg: q:\
    - type: disk_free
      arg: q:\
    - type: memory_use_percent
    - type: memory_use
    - type: memory_free
    - type: swap_use_percent
    - type: swap_use
    - type: swap_free
    - type: load_1m
    - type: load_5m
    - type: load_15m
1 Like

I have already read that and changed the values accordingly as can be seen in my post above, the sensors are not listed in the state table :frowning:

State table for sensor.l*

image

Just noticed this amogst the multiple other errors in my log…

File “C:\Users\MyPc\AppData\Local\Programs\Python\Python36\lib\site-packages\homeassistant\helpers\entity_platform.py”, line 197, in _async_add_entity
yield from entity.async_device_update(warning=False)
File “C:\Users\MyPc\AppData\Local\Programs\Python\Python36\lib\site-packages\homeassistant\helpers\entity.py”, line 327, in async_device_update
yield from self.hass.async_add_job(self.update)
File “C:\Users\MyPc\AppData\Local\Programs\Python\Python36\lib\asyncio\futures.py”, line 327, in iter
yield self # This tells Task to wait for completion.
File “C:\Users\MyPc\AppData\Local\Programs\Python\Python36\lib\asyncio\tasks.py”, line 250, in _wakeup
future.result()
File “C:\Users\MyPc\AppData\Local\Programs\Python\Python36\lib\asyncio\futures.py”, line 243, in result
raise self._exception
File “C:\Users\MyPc\AppData\Local\Programs\Python\Python36\lib\concurrent\futures\thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “C:\Users\MyPc\AppData\Local\Programs\Python\Python36\lib\site-packages\homeassistant\components\sensor\systemmonitor.py”, line 181, in update
self._state = os.getloadavg()[0]
AttributeError: module ‘os’ has no attribute 'getloadavg’e[0m

Works fine on dev

sensor:
  - platform: systemmonitor
    resources:
      - type: disk_use_percent
        arg: /
      - type: disk_use
        arg: /
      - type: disk_free
        arg: /
      - type: disk_use_percent
        arg: /
      - type: disk_use
        arg: /

Can’t help with installations on Windows.

You haven’t got the load sensors listed :stuck_out_tongue:

- type: load_1m
- type: load_5m
- type: load_15m

Yeah, some of my sensors disappeared on the upgrade, they seemed to be the ones that were not as per the listed entity state names. The names have changed and they now are listed as those names so I had some changes in sensors and more in customisationa
I definitely use the sensor.load_5m and that’s how it now appears and the entity name I use to define it
Mutt

I am not using a lot but what I got is working properly, just had to use the new entity name:

 - platform: systemmonitor
   resources:
   - type: disk_use_percent
     arg: "/home"
   - type: memory_use_percent

Yeah, I didn’t post the whole sensor configuration.

Mine are still not working and I am using version 0.63.3, not sure why do we release half baked things that breaks already working environment?

The version number should tell you all you need to know. This is not a final release product. We are Beta testers, using free software, and giving back by posting our problems and solutions on this forum.

Give <===> Take

Your sensors are still working, just their names have changed.
Look at the states page under Developer Tools to find the new names.

New names include

sensor.processor_use
sensor.memory_use_percent
sensor.disk_use_percent

I can’t remember which, but one of them inexplicably has an underscore at the end of the name.

Maybe it will be fixed in 0.66.0 :smile:

1 Like