System monitor - no entities

Hey,
Since last HA update it seems like all the entities from system monitor stopped working.
I removed and added the addon, but now it just shows no entity.

Is it only me? Do I have to do something else? Was working fine before the update.

Thanks!

1 Like

No, same here. I had system monitor configured in YAML, and a couple of days ago it became an integration… At first, it showed all the sensors, but Unavailable, then I removed the integration and added the integration again, and since then there’s no devices or entities.

Haven’t found anything yet that would solve my problem.

Did you remove the yaml lines?

On RPI4 it works fine. One service and over 300 entities to choose from.

Yes, right after the import. And this afternoon I updated to 2024.1.1

yes, the lines are now deprecated.

Yep, exactly what happened to me.
Was also showing this message on the card details before I reinstalled the integration.
image

Are you running HA in a VM as well?

Could it be that duplicate entities have been made?

Same for me.

Removed my .yaml sensors and reinstalled the sensor integration, and now there are no entities at all.

Get this log error:

Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:360
Integration: Sensor (documentation, issues)
First occurred: 11:21:46 (3 occurrences)
Last logged: 11:23:24

Error while setting up systemmonitor platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 360, in _async_setup_platform
    await asyncio.shield(task)
  File "/usr/src/homeassistant/homeassistant/components/systemmonitor/sensor.py", line 393, in async_setup_entry
    disk_arguments = await hass.async_add_executor_job(get_all_disk_mounts)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/systemmonitor/util.py", line 22, in get_all_disk_mounts
    usage = psutil.disk_usage(part.mountpoint)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/psutil/__init__.py", line 2012, in disk_usage
    return _psplatform.disk_usage(path)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/psutil/_psposix.py", line 177, in disk_usage
    st = os.statvfs(path)
         ^^^^^^^^^^^^^^^^
BlockingIOError: [Errno 11] Resource temporarily unavailable: '/media/NasRouter'

Same here, on generic x86-64

Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:360
Integration: Senzor (documentation, issues)
First occurred: 11:03:46 (5 occurrences)
Last logged: 11:23:08

Error while setting up systemmonitor platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 360, in _async_setup_platform
    await asyncio.shield(task)
  File "/usr/src/homeassistant/homeassistant/components/systemmonitor/sensor.py", line 393, in async_setup_entry
    disk_arguments = await hass.async_add_executor_job(get_all_disk_mounts)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/systemmonitor/util.py", line 22, in get_all_disk_mounts
    usage = psutil.disk_usage(part.mountpoint)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/psutil/__init__.py", line 2012, in disk_usage
    return _psplatform.disk_usage(path)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/psutil/_psposix.py", line 177, in disk_usage
    st = os.statvfs(path)
         ^^^^^^^^^^^^^^^^
BlockingIOError: [Errno 11] Resource temporarily unavailable: '/media/Hudba'

Ah, the trace might explain why a bit. I have hundreds of entities, many of them relating to disks. If the new UI based version is loaded when these are not available (yet?) and crashes, you might have what you experience. Did you file a bug report?

I bugged a report, but they closed it linking that issue:

That issue is now closed as well, but relates to another issue about getting disk usage

maybe that’s is stopping system monitor from starting.

I also got the message about having to remove systemmonitor from config.yaml and restart.

I got the above errors re shared disks - but re-entering the username and password to the share fixed the problem (in System > Storage). EDIT fixed for a while only :frowning:

I have found the System monitor integration which states " All entities are disabled by default, you need to enable the entities that you wish to use." and lists several of the available sensors. Looks good.

Adding the integration, and selecting it indicates that there are “No devices or entities” (which is what was stated in the documentation), so click on [configure] to add the sensors I want.

To be presented instead with options that (to me) are meaningless

Even adding all of these, submitting and restarting HA still indicates “No devices or entities” :frowning:

Hello, Same issue. No entities

1 Like

Same issue for me, i have 2024.1.2

Can confirm the bug of having no sensors showing in UI after 2024.1 upgrade is related to NAS (for me at least).

In logs I get the same “Error while setting up systemmonitor platform for sensor”, which is caused by “get_all_disk_mounts” failing with the error:
BlockingIOError: [Errno 11] Resource temporarily unavailable: ‘/media/MyCloud_Media’

For some, removing the Network storage solves the issue.
However, I do not want to remove my Network storage, so I’ll wait for this fix:

Same for me, I am unable to use system monitor.
Try to remove and re-add the integration, with no luck (and no “visible” error).
In the log I have the error related to mounted folder.
Remove mounted folder is not possible, so I think I will wait the fixed , that was merged into dev 2 days ago (6 january).

And same for me too…

Same for me.

i also have this same problem, but if i remove all my network shares then system monitor works fine.
then i went to add one network share back in and system monitor stopped working again. i need my shares so system monitor has been removed only problem now is that the old way in yaml no longer works either.
frustrated.