0.108: Logos, Area Pages, Lovelace Entity Card, Lovelace Map History

Blog
348

Update : managed go back with the wipe and restore function

349

Hi

Was that answer to my version issue? If yes, I have tried with a cleared browser, but no change. That would also not explain, why the cli is reporting the wrong version as last_version.

350

If itā€™s reporting that you are still on 0.107 then your update failed.

351

My Homekit setup was broken. I thought I messed up but it turns out that 0.108.3 fixes my issue. I wasnā€™t able to switch on/off groups or rooms with Siri commands anymore. Now everything is working fine again. Thanks!!!

352

I had to reinstall my venv environment. After that everything works.

353

Regarding hide_entity option being deprecated:

  1. I have many, many warnings in the log like:

2020-04-11 20:47:05 WARNING (MainThread) [homeassistant.components.automation] The 'hide_entity' option (with value 'True') is deprecated, please remove it from your configuration. This option will become invalid in version 0.110

Before the end comes, could the name of the item or the configuration file location be added to the warning message to make it easier to track down?

  1. Is this the same as hidden: true in the entity attributes, and Hide from UI in Customizations? I can find those and, if so, you can disregard the ask in #1. It just could use a better description in the warning for what to look for.

  2. Just because hidden: true no longer has a direct effect in the UI, why is it necessary to purge it from the attributes of all entities? It is possible to configure Lovelace with an entity state filter that references the attribute, somewhat preserving the functionality.

  3. Why doesnā€™t Lovelace honor it as an implicit filter in the first place?

354

Should your request not be implemented before 0.110 arrives, this works from the command line in the config directory:

grep --include=\*.{yaml,py} -rnw "hide_entity"

It will search, recursively, through all files ending with .yaml or .py, in all sub-directories and report the file and line-number containing the matching word hide_entity (or any other word you may wish to find).

2 Likes
355

Itā€™s reporting Iā€™m on 108.3, if you look on the picture, but itā€™s reporting the newest version is 107.7.

356

After upgrading I canā€™t access my Supervisor panel any longer on Hass.io. It throws the following error:

Unable to load the panel source: /api/hassio/app/entrypoint.js.

Restarting the server or rebooting the host doesnā€™t work either. Any suggestions? I already searched the forum but wasnā€™t able to find a fix that solves the issueā€¦

1 Like
357

Beginning with 108.x I began seeing ā€œrequest to pairā€ on my pre-WebOS LG tv pop up every 5 minutes, which does not occur on my newer WebOs LG tv. I have not enabled LG integrations. When I turn off homeassistant the message on the TV stops. Not a biggy, since I just disabled network connection to the TV, which is not needed and stops the pairing request problem.

358

Not sure if anyone responded, but I just had the same issue, it appears there are a few of us:

359

Which version are you upgrading from? Are you using Docker?
If upgrading from a version before 0.107.x, you might want to try this (duplicate instances running in Docker container):
https://github.com/home-assistant/core/issues/32992#issuecomment-604789778

I also had to restore zwave configuration file backups, possibly corrupted by the same issue.

360

Iā€™ve been going crazy trying to figure out why my curtain wasnā€™t moving. Finally thought to check these comments and saw that others are having the same issue.

361

Thanks for sharing this! It was the exact issue I was seeing. I ended up spending almost all of yesterday resetting up my zwave devices :frowning: but I got everything up and running again.

362

I should also mention that the forums are full of people who have this issue after upgrading to 0.107+, with zwave or other integrations. It should be mentioned as a breaking change for docker users.


https://github.com/home-assistant/core/issues/33648#issuecomment-611703069
https://github.com/home-assistant/core/issues/33917#issuecomment-611739015
https://github.com/Swamp-Ig/pizone/issues/3#issuecomment-612316078
https://github.com/mikelawrence/senseme-hacs/issues/3#issuecomment-612309790
1 Like
363

See this. https://github.com/home-assistant/core/issues/33860#issuecomment-612711130

364

Anyone notice that since upgrading to 108 that the CPU utilisation slowly increases over a period of time?

Restarting Home assistant restores the CPU utilisation but then it starts creeping up again.

I rolled back yo 107.7 and CPU utilisation is stableā€¦

1 Like
365

run the install script again. This is due to some issue with wrong permissions in pervious installer scripts.

1 Like
366

Thanks, ill keep an eye on that for a fix.

367

I am getting this error on startup on upgrade. I understand some of the MQTT config items have changed. It looks like it is an old (standalone - ainā€™t broke donā€™t fix) Zigbee2MQTT integration? I did not see anything in Breaking Changes on this.

2020-04-13 08:37:49 ERROR (MainThread) [homeassistant.util.logging] Exception in async_discover when dispatching 'mqtt_discovery_new_light_mqtt': ({'brightness': True, 'color_temp': True, 'platform': 'mqtt', 'command_topic': 'zigbee2mqtt/Standing Lamp/set', 'state_topic': 'zigbee2mqtt/Standing Lamp', 'availability_topic': 'zigbee2mqtt/bridge/state', 'name': 'Standing Lamp'},)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/mqtt/light/__init__.py", line 52, in async_discover
    config = PLATFORM_SCHEMA(discovery_payload)
  File "/usr/local/lib/python3.7/site-packages/voluptuous/validators.py", line 208, in __call__
    return self._exec((Schema(val) for val in self.validators), v)
  File "/usr/local/lib/python3.7/site-packages/voluptuous/validators.py", line 287, in _exec
    raise e if self.msg is None else AllInvalid(self.msg, path=path)
  File "/usr/local/lib/python3.7/site-packages/voluptuous/validators.py", line 283, in _exec
    v = func(v)
  File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 272, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 817, in validate_callable
    return schema(data)
  File "/usr/src/homeassistant/homeassistant/components/mqtt/light/__init__.py", line 30, in validate_mqtt_light
    return schemas[value[CONF_SCHEMA]](value)
  File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 272, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 594, in validate_dict
    return base_validate(path, iteritems(data), out)
  File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 432, in validate_mapping
    raise er.MultipleInvalid(errors)
voluptuous.error.MultipleInvalid: extra keys not allowed @ data['brightness']