2022.8: You can fix it!

Blog
428

MusicCast is used by 2249 user (1.7 %)

429

Does anyone know how milestones work? It seems like there are multiple issues that are closed/fixed in milestone 2022.6.8, but none of these have been released yet. Is it because the last issue needs to be closed first?

2 Likes
430

I’ve lost a few sensors (last reboot at the moment). If I restart the phone, they pick up again but other sensors disappear in a few hours (signal strength disappeared before but okay now).
Only seems to be on 2022.8. I can’t pin it down so haven’t raised as an issue.

431

A milestone is just a marker for when something will be released (what release it will be apart of). If the PR has been merged for that milestone then the change is already in the 2022.8 release

432

@crzynik Is your host a Synology NAS? I can not find any way to install bluez on Synology, which means that no matter how I handle dbus, there’s nothing doing
 If you found a way to install bluez on Synology NAS, can you please link? I have been searching for weeks now and reading what I can, but can’t find any resources on this at all.

433

I wondered about similar. Sometimes I guess it unexplainable which PRs are merged into a new release, and which aren’t. Frankly, I still don’t understand it.

1 Like
434

It is not true to say that none have been released. I looked at a simple one that is in that milestone. https://github.com/home-assistant/core/pull/74130

This has been in the release code since 2022.7.0b0

435

If you don’t see a merged PR in a point release (2022.x.##) then unless its pulled it will be in the next major release (2022.y.0).

2 Likes
436

Not sure where to put this
 After this latest update, I have a bunch of zwave devices just going offline and I can’t seem to recover them with a restart or anything. I’ve never had this problem before in the years I have been using HA, so it makes me wonder if it could somehow be related to this release. Anyone else seeing odd things going on with zwave JS in this release?

437

I guess it was wrong of me to assume that none of them were released, but I just wondered how they work.
There’s one Synology fix there that I’m waiting for. And I’m just curious as to when it will be released.
It’s a little confusing when looking at it from the outside when one doesn’t know how the process works.

439

I was on 2022.8.6 and zwave was good. Updated just the Zwave Integration today, and while devices remained online with their status reported, they wouldn’t respond to commands.

Reverting to backup fixed it, but then an upgrade to 2022.8.7 - which seems to include the update - broke it again.

440

Same problem here. But only with my Fibaro dimmers. Qubino works fine. After reverting to zwave.js 0.1.6.5 it all works again.
Maybe it has something to do with the security level? Fibaro devices have “Highest security: S0-legacy” while at the Qubino devices it says “Highest security: unknown”

441

Do you mean 73507? It is certainly released.

442

Hmm
 Okay. I assumed it was not because I have the exact same problem on the current release.

443

@laffer Assumption is the mother of F*** ups. :slight_smile:

Its all available on github. You can see what is in each release. For example the file changed in the PR you pointed to is https://github.com/home-assistant/core/blob/779e020dc439e2cfbc9c3b02bc11043f23ba3500/homeassistant/components/synology_dsm/common.py

If you click on that link, you will see a dropdown labelled ‘dev’ - click on it and choose tags, you then get a list of release numbers, like 2022.8.7. Click on that and you get the code that is in the current release. And as you can see #73507 is the latest change as at that release. In fact you can go back quite a few releases have included #73507.

444

Aha - that’s interesting. Thanks for explaining.

It would be nice if I could compare github with the actual files on the system, but I haven’t been able to find the correct file location for this.

I reported an issue that was resolved with this fix, but it doesn’t work in my scenario.
As soon as I let the NAS through the firewall and allow internet access, it works, and it stops working when the firewall blocks internet access.

445

That depends on your install method.

446

@nickrout Home Assistant OS on an RPi

448

The new bluetooth integration already failed :frowning:

Failed to start Bluetooth: [org.bluez.Error.InProgress] Operation already in progress

Hassos on RPI4 : 30th of august 2020, latest updates applied

Some knows “how to fix this” ?

449

ssh in and type

docker exec -it homeassistant bash
find / |grep synology_dsm

should find it

1 Like