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?
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.
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.
Why doesn’t Lovelace honor it as an implicit filter in the first place?
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).
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…
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.
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.
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 but I got everything up and running again.
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.
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']
Yes, Agree Broadlink SC1 switches, now either dont work or have a massive delay. RM Pro will not fire any RF commands also. I have downgraded but problem still occurred. Confused also
I am failing to get the map hours to show function up and running.
I have 4 google ids there all shown correctly with their latitude and longitude.
I added the hours option. But no history is shown.
Do I need to activate something else to get this working. Where is the history stored or is it pulled whenever you open the map?
Zigbee2mqtt isn’t an official integration so there wouldn’t be any breaking change listed
There has been some changes to MQTT so your integration may need to be updated
but I got everything up and running again.