Another day - another update?
Basically this is a roll back of the previous update from yesterday, since in the meantime HA Core has released the new version 2026.10.4 which include a global fix for the response header size issue caused by the latest changes at GitHub. You can find details in the HA Core PR#188329
Important
You must update your HA installation to 2026.10.4 (or higher) & reboot - before you can update to this new integration version via HACS.
If you don't want to update your HA installation, simply skip this release - all is fine - you will not miss anything.
Too many updates?
I have to admit that I am quite unsure how to handle situations like the current one caused by the change at GitHub - breaking all update processes for all HA users. I am quite confident that some other integration developers are a bit more relaxed when it comes to the situation that there is an breaking issue.
My personal expectation is, that when something breaks that a fix/patch/solution (at least a response) should be provided as soon as possible, even if the own code is not responsible for the issue itself. And how fast is as soon as possible? For me this is less then 24h. Of course there are situations where I do not meet my own 24h-resolution-time expectation - but the 24 in marq24 is an commitment (and not just two random digits in a user name).
I was surprised (this morning) to see that a new HA version has been released - of course if I would knew this 24h earlier, I would not have invested the time to create nine HA integration updates (trying to explain the current situation and the root cause for the release) - might be I should switch to marq48 (but that's already in use by someone else) - so here he is, my alter ego: Mañana, Mañana Matthias, @marq72
Please consider supporting me
Thanks to everybody who have already supported me in the past weeks or month that is really highly appreciated! Sometimes it has been a though journey. To the other users of this integration: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.
If you haven't starred this integration in Github yet - please do so - TIA