Mine is running and no webostv.conf in the configuration folder… So it is somewhere else.
Question:
- What to do with the “newly discovered” Philips Hue bridges? Note they are already discovered…
Almost a flawless upgrade! 
1 Like
This works for me too…and I’d even tried putting commas at the end of each line - I just hadn’t removed the {} around each line individually.
Thanks!
@Vasco @WhistleMaster @KennethLavrsen I think this issue is the result of me normalising bridge id, which groups unique id are based on. I didn’t reflect on this affecting entity unique ids, this should have been a breaking change or done in a different way. I haven’t verified this though
3 Likes
Same here, two new hue bridges discovered. But only one already discovered one is active in my network. Any advices or workarounds? Should I just press “IGNORE” then? 
Read the google assistant docs for how to setup the service account. It also talks about what services it provides.
I have a few https://www.home-assistant.io/integrations/light.group/ type light groups also. And mixed with non-Deconz lights. I did not get any duplications of those.
I swear that section wasn’t there a few hours ago when I last looked! Thanks!
That section was there for a few releases actually. Ever since report state was added 
It is just easy to miss as it is part of the install steps.
The HEOS integration doesn’t work anymore. My devices were unavailable → I removed the integration and wanted to re-add it via Lovelace, but HEOS is not available as an option…
Hi, i have the same problem since the update
How would you do the delete? There is no delete button for single entities in the integrations page.
After updating from 103.5 to 104.0 Home assistant entities cannot connect to mqtt service. It is starting and therefore clients are able to connect that are external clients to HASSIO. Am using HassOS 3.8 with the Mosquitto broker addon.
I get the following in the logs
Mosquitto log:
1579204435: New client connected XXX.XXX.XXX.XXX
HA log:
2020-01-16 19:42:20 ERROR (MainThread) [homeassistant.components.mqtt] Failed to connect due to exception: [Errno 110] Operation timed out
2020-01-16 19:42:20 DEBUG (MainThread) [homeassistant.components.mqtt] Subscribing to owntracks/#
2020-01-16 19:42:20 ERROR (MainThread) [homeassistant.setup] Error handling when_setup callback for mqtt
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 307, in when_setup
await when_setup_cb(hass, component)
File "/usr/src/homeassistant/homeassistant/components/owntracks/__init__.py", line 144, in async_connect_mqtt
context.mqtt_topic, async_handle_mqtt_message, 1
File "/usr/src/homeassistant/homeassistant/components/mqtt/__init__.py", line 442, in async_subscribe
encoding,
File "/usr/src/homeassistant/homeassistant/components/mqtt/__init__.py", line 842, in async_subscribe
await self._async_perform_subscription(topic, qos)
File "/usr/src/homeassistant/homeassistant/components/mqtt/__init__.py", line 878, in _async_perform_subscription
_raise_on_error(result)
File "/usr/src/homeassistant/homeassistant/components/mqtt/__init__.py", line 985, in _raise_on_error
"Error talking to MQTT: {}".format(mqtt.error_string(result_code))
homeassistant.exceptions.HomeAssistantError: Error talking to MQTT: The client is not currently connected.
I get the same in the logs after commenting out:
configuration.yaml
#owntracks:
# max_gps_accuracy: 200
# waypoints: true
# mqtt_topic: "owntracks/#"
# events_only: false
# waypoint_whitelist:
# region_mapping:
# shed: home
# office: work
In Developer tools > MQTT I try to publish a topic but get the following
unable to call service mqtt/publish. Service not found
was working before upgrade.
Thanks!
Same here. Did you find a fix?
I am also seeing an issue with MQTT after the upgrade. I have tried to adjust settings (TLS on/off, using FQDN/IP/localhost) but have not been able to find a workaround.
All my deconz connected devices are dead. Their entities are showing as unavailable.
They have not been duplicated; they are just not seen by HA, although they are functioning perfectly in Phoscon. What can I do? Should I delete the entities from HA? Will they then be rediscovered?
When you see the list of devices - click on the one that you believe is the old one (normally the first of the two). Then you see the page that lists all entities that are associated with the device. For a deconz group there is only one.
Then clock on the gearwheel icon. The pop-up should show a delete link in the lower left corner. It will only available if the entity is in status unavailable which the old group will be.
And it is the same for renaming the _2 entity. Instead of delete you update the entity name by removing the _2 and hit update in the lower right corner
I with there was a similar delete function for the device but we can only rename devices which is the gearwheel in the top right of the screen when you have opened a deconz device
1 Like
Nope, ended up ditching the automated view and customized my lovelace ui
This is what worked for me:
- uninstalled and reinstalled Mosquitto broker addon, then
- deleted entry
MQTT: <IP Address>in Configuration > Integrations. At some point maybe after I restarted HASSIO I went back to Configuration > Integrations, and “Mosquitto: configure” appeared near the top. Clicked on configure, confirmed Enable discovery (not sure if this is the exact wording) and clicked through rest of wizard.
It is now working, try step 2) first as step 1) didn’t make any initial difference in fixing issue. If step 2) doesn’t work then try step 1) & 2).
After updating to 0.104.1 I’m seeing the following error which wasn’t in 0.104.0:
Log Details (ERROR)
Thu Jan 16 2020 23:16:19 GMT+0000 (GMT)
extra keys not allowed @ data['0']
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 134, in handle_call_service
connection.context(msg),
File "/usr/src/homeassistant/homeassistant/core.py", line 1204, in async_call
processed_data = handler.schema(service_data)
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['0']
It doesn’t look like a config error but has anyone else come across this? I’m not sure what extra keys its referring to.