Since that was directed at me, allow me to respond. Let’s put aside for a moment it wasn’t Micro$oft, and it wasn’t consumer end users who were affected. Given their track record, it would appear M$ does better testing before blasting out an update. Yeah. I know. But I did say better, not perfect.
I personally don’t trust automatic updates, and any IT department which allowed Crowdstrike to push them to production machines without in-house testing is foolish.
The fact remains that many end users do trust manufacturers and vendors to push automatic updates, and expect them to work flawlessly. Apparently so do some large IT departments.
And when you thought, that would be the solution - nope!
Imagine this conversation from today:
C: “I read the news about this glitch. Does this affect us?”
S: “No, or do you have a blue screen?”
C: “No, but the news said it’s worldwide?”
S: “Yes, but we were intelligent enough to hold on to that update.”
C: “So this comes up for us next week?”
S: “…”
Except the underlying issue was fixed very quickly and did not affect any devices getting updated later. The problem was to fix the devices already affected. Not sure what your little story was supposed to convey.
hi, passing from 2024.7.2 to 2024.7.3 broke my zigbee2mqtt, i restored 7.2 and loose tuya login, which has btw a stupid way to re-login with a pointless qrcode (security-wise nonsense, user/pass would be normal, maybe 2fa on top). it was like the dongle was not functional (no devices detected on map scan). usually i dig, but i was in a hurry…
we have a solution for this?
updated from 2024.7.2 to 7.3 and lost all of my home-feed cards. code hasn’t changed. didn’t see any breaking changes. haven’t heard anyone else squawk about it. i did the work around for the pop-up cards but can’t figure these out.
HA’s code changed — hence the upgrade. I’m assuming you actually meant you didn’t change your config.
You won’t see third party components mentioned in the release notes. Third party components are your own risk.
Make sure to include your config when you report the issue on the third party repo. Integrations have links to the applicable repos on the integrations page.
what happens to 2024.7.4? neither available via pip nor docker.
that’s not the first time the last release of a month is not released.
I only ever update to the latest monthly version. an update to 2024.8.0 may then fix bugs from 2024.7.3, but also bring new ones. a vicious circle
