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
Is no one using Nmap tracker here? If so, please check if your device_trackers are working? In my setup none is functional. Only one dedicated thread found Nmap stop working within 2 days
Issue is filed in github, only appeared in my config after updating to 108.3. (From 107.5 so might have missed the culprit version,)
Oh man…totally don’t want to go there. But if I have to…how did you do it? Remove zwave config files and start from scratch? And it’s all working smooth?
thanks for checking, good to hear.
not using docker myself, and still none of the device_trackers are working correctly.
in this issue, https://github.com/home-assistant/core/issues/33281 people are reporting the same.
You are on Hassio though right? I think it uses a similar docker image so it might be the same thing. The issue you linked to the original author is on Docker. I am just trying to find the commonality here, because if not all users have it then there must be something else that is common so installation type becomes the next commonality to look at after the integration.
which I used before, but caused some issues with Nmap, and now see all my devices tracked properly again. Both using Nmap tracker and asuswrt. How odd.
Not sure of this is related, but upon install of 108.3 the IPP integration was ‘discovered’ for my Epson printer. I added it, and it did see the cartridges and created sensors, but got no states for the sensors.
Upon restart just now, my cartridges were seen and given their proper states.
I removed the integration in my configuration yaml, removed the integration within HA (configuration -> integrations) and did a factory reset on my zwave stick. I also rebuilt the docker container. Not sure which step actually fixed it. But from looking at the few threads on this issue, it looks like starting in a recent version of HA core, there’s an issue with multiple instances of HA running.
It turns out that there is a "cmd" : "python -m homeassistant --config /config" in the container and by recreating the contain without a cmd: All issues are fixed
