2022.8: You can fix it!

o dear, never experienced this before:

nothing much else to relate that to than updating to 2022.8.4… keeps auto rebooting.
this is a mini pc, w 8/129GB mem and 500Gb m2 nvme data disk

unless… its a new Zwave sensor causing havoc:

UnicodeEncodeError: 'charmap' codec can't encode character '\u2082' in position 1051442: character maps to <undefined>
2022-08-14 17:56:46.050 ERROR (Recorder) [homeassistant.components.recorder.core] Error while processing event EventTask(event=<Event state_changed[L]: entity_id=sensor.co2_living, old_state=<state sensor.co2_living=801.0; state_class=measurement, unit_of_measurement=ppm, device_class=carbon_dioxide, friendly_name=Mco Multilevel: Carbon dioxide (CO₂) level Living

in recorder for a CO2 sensor device…

changing the name doesnt help though…

When i toggle a Shelly with a physic button, i have a lag to see his new state and input in HA…
Don’t know if it is related to the last update…

What do you mean by downloaded from new repo, can you share more details?

its not 2022.8.4. Its recorder choking on unicode characters. Issued that before, and now have a new experience:

deadly.

@Sand @Jc2k I kept the BLEM integration active so I put the sensors from that on one card and the same sensors but from the new integration on a second card and put them both side by side to see if the new integration would display the same data accurately. After comparing both I’ve noticed that the BLEM integration will display the data the same as the Flower Care app but the new integration seems to always be a little off. I don’t know if it’s getting old/late data or wrong data. I think it’s old/late data because it’s always close to the correct data. I have not had a chance to compare histories yet. Here is a screenshot. The left cards are using the older BLEM integration and the right cards are using the new integration. You can see the differences in data…

Well i found where was my problem : CoIot mcast.
Don’t know if it is related or not with the lastest update but if i enter ip:port instead of mcast, it’s working like before.

That’s why there is documentation, to follow so that shit works.

1 Like

Check the update frequency. If its stopped updating entirely, try turning BLEM off. If that doesn’t work try running BLEM in active mode. If that doesn’t help try a different (non realtek) bluetooth adapter.

If its updating frequently, but with wrong data, raise a ticket on GitHub. It’s the same parser as BLEM though, so this is all kinds of unlikely. I think BLEM does more smoothing of the data potentially, otherwise they should be the same.

By far the most common problem with the new bluetooth stack is that lots of dongles are very crashy with BlueZ. Which is one of the things we can do least about.

2 Likes

Just a question has anybody else lost the multiple options when call services that used to be available in the visual automation editor?

Or have I changed a setting somewhere?

Just used to be a nice quick way to do an automation on ur phone when sat on the sofa

Any help would be awesome?

Same here, but only after yesterday’s update to 8.5.

Logger: aiohttp.server
Source: components/speedtestdotnet/config_flow.py:74
First occurred: 08:38:47 (1 occurrences)
Last logged: 08:38:47

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 82, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 136, in handle
    result = await result
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 215, in post
    return await super().post(request)
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 73, in wrapper
    result = await method(view, request, data, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 70, in post
    result = await self._flow_mgr.async_init(
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 222, in async_init
    flow, result = await task
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 249, in _async_init
    result = await self._async_handle_step(flow, flow.init_step, data, init_done)
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 359, in _async_handle_step
    result: FlowResult = await getattr(flow, method)(user_input)
  File "/usr/src/homeassistant/homeassistant/components/speedtestdotnet/config_flow.py", line 74, in async_step_init
    self._servers = self.hass.data[DOMAIN].servers
KeyError: 'speedtestdotnet'

Speedtest integration is no longer working after 2022.8.5. I’m getting the following message on the Speed Testy integration screen:

Retrying setup: HTTP Error 403: Forbidden

I can’t find anything in the logs. HELP!!!

EDIT: OMG! It’s worse. The latest update broke my ZHA setup and nothing works anymore. Reloading from my 3 am backup (shame I lost 16 hours of data!!)

2 Likes

I’m getting an error trying to update to 8.5. Says no host internet connection when there is. Seems like this happens every few core updates. Anyone have a quick fix?

My ZHA is working fine on 2022.8.5.

1 Like

I seem to be getting a lot like this. Did I f-up something or is this something worth putting on git?

Logger: root
Source: runner.py:119
First occurred: 14:13:21 (65194 occurrences)
Last logged: 19:41:19

A message handler raised an exception: 'org.bluez.Device1'. Traceback (most recent call last): File "/usr/local/lib/python3.10/site-packages/dbus_next/message_bus.py", line 668, in _process_message result = handler(msg) File "/usr/local/lib/python3.10/site-packages/bleak/backends/bluezdbus/manager.py", line 746, in _parse_msg condition_callback() File "/usr/local/lib/python3.10/site-packages/bleak/backends/bluezdbus/manager.py", line 658, in callback self._properties[device_path][defs.DEVICE_INTERFACE][property_name] KeyError: 'org.bluez.Device1'

I was able to resolve mine by going to the terminal or through ssh and running “ha core check” and then “ha core upgrade”

It installed the update and rebooted itself and when it came back up it was installed and everything seems to be working fine so far.

There have been issues submitted about this in the frontend repo

And this happend!
How can I fix it? Restart didn’t help.
Screenshot 2022-08-17 at 09.52.02

Did you create a Git issue for this? I’m having the same in 2022.8.5, otherwise I’ll create an issue

I’ve seen this error a few times as well. It seems to occur after updating HA Core with the patch builds. Restart the host machine (not just HA) and it should fix it.

2 Likes

no sorry, feel free to do so please… ;-0

1 Like