0.116: Entities card row editor, restore snapshots and performance metrics

Blog
325

AD was in the release notes - You’ll want to read them but basially comment out config.yaml and then re setup through the integration.

326

.116 I am getting the same - Dropping out of order packet 6000 times in 30 minutes of clock time and time stamp overflow detected.

327

Why not just let your super cheap little RPi be dedicated to HA? What I mean is that they are SO cheap and use such little power that surely you can have a second one for Raspbian to do whatever else it is you want to do…? It will save you a lot of headaches and time wasted when HAOS works very well without jumping through hoops to upgrade.

3 Likes
328

Care to name some examples?

You can still install Home Assistant in Docker (Home Assistant Container) or Home Assistant Supervised on top of Raspbian.

329

I don’t know why but, after the update to 0.116, my system monitor gauges stopped working and turned into following yellow background alerts:

  • Entity is non-numeric: sensor.processor_use
  • Entity is non-numeric: sensor.disk_use_percent
  • Entity is non-numeric: sensor.memory_use_percent

Notifications tab reports that:

The following integrations and platforms could not be set up:

  • sensor.systemmonitor

Please check your config.

And my config is:


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

…everything worked perfectly up to release 0.115
Any idea guys?
Thanks

Solution is here: 0.116: Entities card row editor, restore snapshots and performance metrics - #330 by anon43302295
…and the reason why is here: 0.116: Entities card row editor, restore snapshots and performance metrics - #334 by tom_l

330

Process requires an argument (for which process to monitor)

1 Like
331

Well, not for all the processes (ref. to following specific link and check the table):

systemmonitor

332

The table lists an argument as mandatory for the process option. You have none.

1 Like
333

Oh yes… I’ve misunderstood mf_social reply and I’m very sorry for that.
Problem solved guys.
What I cannot understand is why it stopped working with release 0.116… Is this a brand new requirement?

Thanks for your help.
Cheers

1 Like
334

Yes the release notes had this to say:

System Monitor

Not really a breaking change, since the overall logic did not change. Arguments that were previously mandatory for sensors of this integration are still mandatory and optional arguments remain optional.

However, we now enforce those mandatory arguments to be present, since otherwise this integration creates entities that cannot do anything, e.g., the sensor for IPv4 addresses cannot do anything if no network interface is specified from which to take the IP.

If the integration fails to load, check the log to see which arguments are missing in your configuration. The documentation also has been updated to clearly show which arguments are mandatory.

See: 0.116: Entities card row editor, restore snapshots and performance metrics - Home Assistant

Please mark mf’s post as the solution to assist others with this issue when searching.

2 Likes
335

What did you do exactly. I´m currently stuck here.

336

Why not just let your super cheap little RPi be dedicated to HA?

If that were the case, i would have several Pi devices - not such a good strategy!

  1. One possibility might be to provide a useful guide for the installation (HA with Python 3.8 and Pi, see Installation - Home Assistant)
  2. We could wait and skip all updates until python 3.8 is deployed with raspberry OS
  3. Best strategy: HA supports python 3.7 until python 3.8 is available with raspberry OS

Btw. will the instructions be updated?

337

Or
4. Install Home Assistant Container
5. Install Home Assistant Supervised on top of Raspbian

2 Likes
339

A guide to upgrade is included here 0.116: Entities card row editor, restore snapshots and performance metrics

Perhaps you could put the contents in the community guides section of the forum.

340

anyone else seeing all Bluetooth devices being not_home only?
have I missed a breaking change anywhere…?
not sure if this happened after updating to 116.xx or supervisor maybe.

2020-10-22 12:33:45 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/bluetooth_tracker/device_tracker.py", line 177, in update_bluetooth
    await perform_bluetooth_update()
  File "/usr/src/homeassistant/homeassistant/components/bluetooth_tracker/device_tracker.py", line 140, in perform_bluetooth_update
    devices = await hass.async_add_executor_job(discover_devices, device_id)
  File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/bluetooth_tracker/device_tracker.py", line 57, in discover_devices
    result = bluetooth.discover_devices(
  File "/usr/local/lib/python3.8/site-packages/bluetooth/bluez.py", line 26, in discover_devices
    device_id = _bt.hci_get_route()
OSError: [Errno 19] No such device

filling the logs

341

Hi,
there is a problem with the last HassOs 4.14 that broke the bluetooh on raspberry pi 3 only.
This is fixed in the new version 4.15.

342

thanks! glad to hear its not me :wink:
dont see the release yet, so guess we’ll have to wait a bit more? or would it be safe to issue a cli command

343

Have a look here:

But i don’t know how to install in hassio! The upgrade is still not notified to me…

344

no it’s not there yet:

Schermafbeelding 2020-10-22 om 13.26.22

345

You should be able to upgrade with:

ha os update --version 4.15