I just want to mention home assistant update has broken ecowitt yet again it worked flawless for my self for 3yrs one of the most reliable in my home assistant setup. Then when it broke on an update I read it was due to being made better. When it was made better after an update it stoped working for 5weeks caused me to have to change my automations then there was a new update that made it work. But then there was an update that made it not work then a few days later made it work then another up date that made it not work then another update and yup it’s not working again. I just feel an update should only be introduced if it works maybe try it out first then release it.
It’s been a week and ecowitt has still not been working I wouldn’t say it was BETTER maybe crap I’d say
The Core integration has been flawless for me with the exception of during 1 minor rev a month or so ago.
I heard the custom integration from someone on GitHub is not well maintained and breaks often. Is that what you are using? Did you load yours thru the HACS interface?
The HACS Integration that worked perfectly in the past with about 50 entities does not work at all any more.
The core Integration has only some of the sensors and most of them are ‘not available’ as entities. I.e. there is no entity for the outdoor temperature, only the feels like temperature. Indoor temperature exists as entity but is not available etc
Did I do anything wrong? I have no clue what to do now - All my automations are broken but I do not want to change them all if there is any chance that the HACS integration will work again in the future.
Just updated the Core of HA to 2025.12.0, and ended up with seven repairs needed on the Ecowitt integration. Anyone else had this issue with this new core update?
Link here, for those who want to follow along the discussion:
Weird. I just trialled adding state_class: measurement to a couple of the entities (using configuration.yaml), restarted homeassistant, and now there are no errors being flagged. Perhaps something was changed / updated already?
Reading github issue reads like an intentional change gone wrong.
No sufficent warning before change and different assumptions about the usage of the entities.
