Matt The Horwood@lemmy.horwood.cloud to homeassistant@lemmy.worldEnglish · 2 months ago2024.10: Heading in the right directionwww.home-assistant.ioexternal-linkmessage-square11fedilinkarrow-up1112arrow-down11file-textcross-posted to: lealternative@feddit.ithomeassistant@lemmit.online
arrow-up1111arrow-down1external-link2024.10: Heading in the right directionwww.home-assistant.ioMatt The Horwood@lemmy.horwood.cloud to homeassistant@lemmy.worldEnglish · 2 months agomessage-square11fedilinkfile-textcross-posted to: lealternative@feddit.ithomeassistant@lemmit.online
Please don’t be scared; it is October, Halloween is coming, and so is the next Home Assistant release: 2024.10! 🎃
minus-squareStampela@startrek.websitelinkfedilinkEnglisharrow-up1·1 month agoSimilarly unfortunate situation for me, using the backup didn’t really help. But I DO have the Alexa integration, I guess next time I get HA between reboots I’ll disable that.
minus-squareBluesheep@lemmy.worldlinkfedilinkEnglisharrow-up1·1 month agoIf you’ve got access to the file system I think you could remove the custom component there - can’t exhausted resources if there’s no code!
minus-squareStampela@startrek.websitelinkfedilinkEnglisharrow-up1·1 month agoHad access to cli, restarted HA and quickly disabled the Alexa integration: so far everything is working as intended :)
Similarly unfortunate situation for me, using the backup didn’t really help. But I DO have the Alexa integration, I guess next time I get HA between reboots I’ll disable that.
If you’ve got access to the file system I think you could remove the custom component there - can’t exhausted resources if there’s no code!
Had access to cli, restarted HA and quickly disabled the Alexa integration: so far everything is working as intended :)