-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to import component: No module named 'homeassistant.components.image' (since v3.5.1) #636
Comments
Edit: v3.5.0 works without any issues. Which HA version is needed to run v3.5.1? 2023.7? https://www.home-assistant.io/blog/2023/07/05/release-20237/#image-entities |
You right. Image require newer Hass version. I think this is bad idea. Will fix this in next release. You can use previous version for now. |
Great. Looking forward to an updated version (you'll probably implement a "if availalbe, use it, if not, don't try to implement usage of image entity" check, right?) 🎉 |
@AlexxIT do you have any estimations for the new release containing the fix for this? Thanks. |
You can try latest master version |
Is there a new release? I'm only using HACS. |
You can install it via HACS. Redownload and select master from dropdown |
It's not a release yet. |
So when will you make a release? |
Since updating to https://github.com/AlexxIT/WebRTC/releases/tag/v3.5.1 and doing the first restart of HA after the update (using HACS), I get this on every HA Core start:
Maybe because of #619 looking for this entity type which does not exist on older HA Core versions? If true (just a wild guess): in that case the 3.5.1 update should have been flagged with a "breaking change" notification or listing the minimum needed HA Core version.
By the way there's a typo in the date of https://github.com/AlexxIT/WebRTC/releases/tag/v3.5.1.
The text was updated successfully, but these errors were encountered: