Getting this error after upgrade:
Logger: aioswitcher.bridge
Source: /usr/local/lib/python3.9/site-packages/aioswitcher/bridge.py:56
First occurred: 17:41:17 (3 occurrences)
Last logged: 17:42:47
received datagram from an unknown source
Your WLED device now provides a select entity that allows you to change the preset. You can use that entity directly.
1 Like
Unfortunately I can’t use the BMW Connected anymore (get failed to connect)
1 Like
after upgrading I can’t use ha, lovelace GUI is defect:
And I have the same issues in the ha android app.
I can’t find anything related in the log.
It looks like ha is working: I get pictures based on motion on telegram. But How to get the GUI back?
A restart doesn’t solve the issue. Maybe this part of the log could be related?
2021-08-04 17:33:09 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook f2c6d8d4301f3397e746747bd0f943610d73a1961b6cbeebec81542c6cb3c1e8 from 192.168.178.126
2021-08-04 17:33:09 ERROR (SyncWorker_7) [homeassistant.loader] Error parsing manifest.json file at /usr/src/homeassistant/homeassistant/components/openuv/manifest.json: Unterminated string starting at: line 8 column 16 (char 238)
2021-08-04 17:33:10 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook f2c6d8d4301f3397e746747bd0f943610d73a1961b6cbeebec81542c6cb3c1e8 from 192.168.178.126
2021-08-04 17:33:10 WARNING (MainThread) [homeassistant.config_entries] Config entry 'FRITZ!Box 7590 (UI)' for upnp integration not ready yet: None; Retrying in background
2021-08-04 17:33:10 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [547641867424] Error handling message: Unknown error
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 25, in _handle_async_response
await func(hass, connection, msg)
File "/usr/src/homeassistant/homeassistant/components/frontend/__init__.py", line 693, in websocket_get_translations
resources = await async_get_translations(
File "/usr/src/homeassistant/homeassistant/helpers/translation.py", line 311, in async_get_translations
cached = await cache.async_fetch(language, category, components)
File "/usr/src/homeassistant/homeassistant/helpers/translation.py", line 221, in async_fetch
await self._async_load(language, components_to_load)
File "/usr/src/homeassistant/homeassistant/helpers/translation.py", line 236, in _async_load
for translation_strings in await asyncio.gather(
File "/usr/src/homeassistant/homeassistant/helpers/translation.py", line 156, in async_get_component_strings
await gather_with_concurrency(
File "/usr/src/homeassistant/homeassistant/util/async_.py", line 170, in gather_with_concurrency
return await gather(
File "/usr/src/homeassistant/homeassistant/util/async_.py", line 168, in sem_task
return await task
File "/usr/src/homeassistant/homeassistant/loader.py", line 536, in async_get_integration
integration = await _async_get_integration(hass, domain)
File "/usr/src/homeassistant/homeassistant/loader.py", line 561, in _async_get_integration
raise IntegrationNotFound(domain)
homeassistant.loader.IntegrationNotFound: Integration 'openuv' not found.
2021-08-04 17:33:17 WARNING (MainThread) [homeassistant.components.onvif] The date/time on the device (UTC) is '2021-08-04 16:33:23+00:00', which is different from the system '2021-08-04 15:33:14.125400+00:00', this could lead to authentication issues
2021-08-04 17:33:23 ERROR (MainThread) [homeassistant.components.switch] Platform fritz does not generate unique IDs. ID E0286D7A042E-wi_fi_aisberg_wlan already exists - ignoring switch.fritz_box_7590_ui_wi_fi_aisberg_wlan
2021-08-04 17:33:55 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook d5df04fa03b95614ff8734fd69c29decab8e70a0493b5681363a460af633faf9 from 192.168.178.138
2021-08-04 17:33:57 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook d5df04fa03b95614ff8734fd69c29decab8e70a0493b5681363a460af633faf9 from 192.168.178.138
Awesome release!
I really hoped that support for Broadlink LB1 would also be introduced 
hopefully next release :sigh:
I had some Utility meter sensors to monitor my energy consumption using Shelly EM and 1PM, “sensor.daily_energy” and “sensor.monthly_energy”. After upgrading to 2021.8.0., all those are gone, and some new sensors appear with “_consumption” at the end, “sensor.daily_energy_consumption”, “sensor.monthly_energy_consumption”. All historical data of the old sensors are gone. Please help advising how to do to get back the history?
Zigbee2mqtt broke, too.
[23:22:59] INFO: Handing over control to Zigbee2mqtt Core …
[email protected] start
node index.js
Zigbee2MQTT:error 2021-08-04 23:23:35: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-08-04 23:23:35: Failed to start zigbee
Zigbee2MQTT:error 2021-08-04 23:23:35: Check | Zigbee2MQTT for possible solutions
Zigbee2MQTT:error 2021-08-04 23:23:35: Exiting…
Zigbee2MQTT:error 2021-08-04 23:23:36: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:102:27)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:123:29)
at Zigbee.start (/app/lib/zigbee.js:67:27)
at Controller.start (/app/lib/controller.js:106:27)
at start (/app/index.js:94:5)
[23:23:38] INFO: Handing over control to Zigbee2mqtt Core …
Thanks
1 Like
A smooth update as usual thanks to all for all the hard work.
A quick question, I have two fans ( Insteon fanlink and sonoff ifan03) both controlled as low, med or high in lovelace. As expected with this update google assistant voice control now only works with a percent fan speed request
Is there a way to still do low, med or high voice control with google ?
1 Like
Please extend documentation on statistics with examples. Could a template sensor be a metered?
1 Like
Was there a change to apcupsd? I see that some of the sensors are no longer available: sensor.usp_model, sensor.ups_status, sensor.ups_time_left are gone.
Getting some weird error after upgrade, reboot doesn’t help. Should I open a bugreport or is it isolated problem?
Logger: homeassistant.setup
Source: components/frontend/__init__.py:285
First occurred: 6:06:21 PM (1 occurrences)
Last logged: 6:06:21 PM
Error during setup of component energy
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 249, in _async_setup_component
result = await task
File "/usr/src/homeassistant/homeassistant/components/energy/__init__.py", line 25, in async_setup
frontend.async_register_built_in_panel(hass, DOMAIN, DOMAIN, "mdi:lightning-bolt")
File "/usr/src/homeassistant/homeassistant/components/frontend/__init__.py", line 285, in async_register_built_in_panel
raise ValueError(f"Overwriting panel {panel.frontend_url_path}")
ValueError: Overwriting panel energy
That is the developer documentation and not related to the template integration.
The template integration currently does not support this feature.
Statistics Graph and Energy Graph does not accept utility_meter sensors as sources. Some MQTT sensors are also not accepted. Does somebody see similar issues?
2 Likes
Eneco Toon sensors not supported in the new energy management system? 
I got the same issue. Actually the sensors created with Utility Meter are not listed in the entities list anymore, new sensors with “_consumption” as postfix added. Eg. before upgrading “sensor.daily_energy”, after upgrading “sensor.daily_energy_consumption”
Yes they are, the official Toon integration of Home Assistant does. It was actually one of the first integration to add support back in May (as I use it myself) 
The Honeywell Total Connect Comfort (US) only detects one of two of my thermostats. I had it manually configured in config.yaml but the new integration takes over and there is no way to detect my 2nd thermostat.
So I’d love to use the new energy reporting! However I’m unable to configure my Aeon Labs DSB09. There are no ZWave(JS) configuration parameters listed, which are needed to setup reporting.
This is the listing from the ZWave JS DB browser:
https://devices.zwave-js.io/?jumpTo=0x0086:0x0002:0x0009:0.0
Where is the best place to report this?
I have a problem with the utility meters too:
2 Likes
Me too. The sensor naming seems to have changed. Stuff is mixed up. Issue with the new energy stuff as well. Utility meter sensors are not accepted. Do wee need a bug report?
2 Likes