Check. See:
Thank you, full system reboot fixed it
After update I have a lot of loosing connection and hanging up HA. 
My issues with this version. Upgrading from 2022.6 broke my mqtt. Had a silly mistake in my mqtt.yaml file. 2022.6 complained, but mqtt still worked. In 2022.8, it would not run mqtt at all. That was kind of annoying but not my complaint.
In the log file with the error message, it pointed at the include mqtt.yaml line in configuration.yaml. It didnāt give me any clue where in mqtt.yaml the actual problem was. So I had to comment out a bunch of stuff until the error disappeared, and then add lines back in until I found the problem. It also made me comment stuff out like I had an error somewhere else, but there was really only one error in the file.
All good now, and working. Just would have saved me some time if it would have pointed to the real error instead of the include line.
Randy
Right. By default BLEM takes the mean of values received in the period (default 60s). But these differences look too large for that to be the root cause anyway.
Yes they do, which is why I think its an update frequency issue.
I finally figured this out, and only by accident. See here, and remember to restart Home Assistant after reinstalling the integration through HACS. I didnāt see the restart prompt and that added a couple minutes of head scratching:
It also looks like all my sensors need to be renamed.
long ago as a workaround I made some dummy switches in home assistant, exposed them to homekit, then made a rule in my homekit that when an eve device changes status, it changes the status of the dummy switch. Home assistant sees the status of the dummy switch change as well. Has been working flawlessly for 2 years like that for me.
Hi!
I have integrated a Ledvance (Osram) LED Strip with RGB and WW+CW without a problem via Bluetooth into the new Home Assistant version!
But what is not working is the WW+CW part, I can only control the strip in RGB.
Is this a known problem?
Hello,
I tried to use BlueTooth but I get error: āRetrying setup: Failed to start Bluetooth: adapter āhci0ā not foundā. Iām running HA on my Mac using VirtualBox.
Thanks for any help!
What sort of things are people seeing in the new āRepairsā section? I currently have nothing despite my log being full of errors that I havenāt had time to resolve. Iām just surprised that none of the errors have created something for me to ārepairāā¦
1 Like
Same hereā¦ Apparently nothing fixable
Right now it can detect about 25 issues and if a Home Assistant Alert is found that matches your system, it will also show up in the repairs dashboard. There will be more issue detections added in the near future.
5 Likes
They were called āMatti ja Pattiā here in Finland. 
In theirs home country, Czechia, they names are Pat & Mat, which comes from the chess game.
They do not talk, only make noises. The only sentence, they can speak out is: āA je to!ā, what means āItās doneā.
So, when I moved to the Netherlands, I was very surprised, when I saw them on the TV and they were talking, and not called Pat & Mat, but Buurman & Buurman (Neighbor & Neighbor). I actually was a bit disappointed, as the talking was originally left out with a purpose. The childrenās imagination had to be triggeredā¦
This must be the first time Iāve heard Finnish translators getting it right! In Finnish the names relate to chess or games in general. āShakkimattiā, sometimes shortened to āmattiā (also the most common first name) means checkmate and āpattiā means stale mate (among other meanings). AFAIK there were no dialog between the characters. Many Czech childrenās series/movies were popular here back then. Good memories!
P.S. Sorry for another off topic post, just could not resist!
2 Likes
Anyone else having problems with Companionās battery sensors?
Stopped working for both phone (hasnāt update for days) and tablet, sinceā¦
Male audition loves Pat & Mat, female audition cant stand it 
There is a bit of controversy in it - like in the āPotkali se u KolĆnaā ā¦ Sorry for OT, back to great HA project
Running HA as a container in a debian VM on ESXI
So I have installed USBIP on raspberry
Exported the BT
it is visible in the host environment:
Bus 003 Device 002: ID 0b05:190e ASUSTek Computer, Inc. ASUS USB-BT500
/run/dbus is mapped in the container
bluez is installed in the vm
that shall be enough orā¦
Home Assistant Container: The host system must run BlueZ, and the D-Bus socket must be accessible to Home Assistant inside the container.
shall Bluez be installed in the ESXi Host???
I have the same error message (raspberry pi-4, ubuntu-22.04, docker). Were you able to find a workaround/fix?