Thanks, but in my case, i use the tv backlight with wifi. the only way i see is via the cloud. Hope, there will be a fix for govee
Mee too… After updating today, the custom ecowitt integration stopped working for me, but if I go through the “official one”, it still displays “Config flow could not be loaded: {“message”:“Invalid handler specified”}” as it has always done… So why is the integration there if it doesn’t work? Or is it some other specific problem that just some people have?
The problem is that the OpenRGB hasn’t been updated over 2 years and the AIMP for well over 4 years. So not much i can do, also what changed in the main code that broke so many integrations? Python version? There isn’t any mention of this in the breaking changes section of the 2025.1 release. I always read it before updating but i thought this update won’t break anything, but i was wrong…
I have a Meross thermostat (mts200) but it was detected by the homekit integration when i first installed it, and that did everything I needed.
You may want to stick with Meross cloud, but Homekit might be a viable alternative for you if you’re stuck.
Probably time to say goodbye to AIMP. The dev is not active.
The OpenRGB dev is still around though. Open an issue and see what happens.
For anyone having trouble with HACS a new version (2.0.2) has just been released that should fix things.
not yet, but in preparation
Nooooo way?!? Who the … was thinking that local backups need encryption without possibility to decrypt?? Is that really the case? That’s so…not nice
Backups stored in the cloud, yes encryption is good. But local in same (for me) /usr/share/hassio for folder…
same here! I am using only Manual backups. Latest version introduced more mouse clicks and unnecessary setup. Not to speak of forced encryption for Manual backups…
i have restore to old Version because these two ingtegrations dont work after Update to 2025.1:
Same advice:
Looks like there is already an open issue for the Tuya ( ) integration with a forked repository listed that does work.
The other one seems unmaintained.
I’ve found in the logs on HA version 2024.12.5 that it dropped a warning “Entity media_player.aimp (<class ‘custom_components.aimp.media_player.AIMP’>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use…” and “Entity None (<class ‘custom_components.openrgb.light.OpenRGBDevice’>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature.EFFECT|17: 21> …”. But again these are only warnings and not errors immediately noticeable, I think a HUGE improvement to UPDATES would be to display what is changed and what will be affected in the next version PRIOR to updating, just go over the integrations with the affected things and say that it won’t work with the next version. I think this SHOULD be addressed soon because many integrations are old and can be updated prior to updating a HA instance and not after with a broken integration. This would be a much nicer way to handle updates.
To be fair to the HA team that warning has existed on your system for 6 months.
i tried it to install, and it worked !!! dont know why, but it is working, thanks for your suggestion
Guess what? We did that with an MQTT change sometime last year. The repair did not go over well with the entire community. There was a large backlash, so things for developers will remain in the logs and out of the UI.
But a pop-up warning would be nice anyway before the update takes place, because let’s be honest many people don’t have time to look at the logs.
please read my last response.
I agree 100%. Most likely, when I really need the backup I will be unable to find the encryption key. To alleviate this, I will try to store the encryption key together with the back thus making it pointless. In addition, this will likely make it harder to automate verification of backups.
I am sure that there are people who are much more structured than me and who have an organized way to store such keys. They are the same people who would never forget their root/admin password because they have it written down. However, people like me need a way to deal with security and the kind to security that works best for me is physical security. I will store the backup on physical media in my house and trust that that will make it secure.
Question: if the backup is encrypted, let’s say you install HA on another hardware, is it possible then to restore?
I haver never ever before seen an update with so much broken. “KEBA” is part of HA and broken too. My point was the 2025.1 seems to be hasted through or simply include way to many changes. I’m fully aware of what HACS is, but also believe HA should respect how important HACS are for HA to be the success it is.