Closed Mariusthvdb closed 2 years ago
frontend documentation frontend source (message by IssueLinks)
Hey there @home-assistant/frontend, mind taking a look at this issue as it has been labeled with an integration (frontend
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
This is from the Pillow update
2021-12-14 09:13:40 ERROR (MainThread) [homeassistant.setup] Setup failed for image: Unable to import component: cannot import name '_imaging' from 'PIL' (/usr/local/lib/python3.9/site-packages/PIL/__init__.py)
which is what? dont think I recognize that in my system ;-)
could this have anything to do with either fontawesome or favicon custom components?
https://github.com/home-assistant/core/pull/61661
I had to install pillow manually to get my dev env to work again
yeah, well I am on OS so will have to wait for a fix... still I dont understand what happened, or why this Pillow has anything to do with the config at all.
I did test adding a person entity via the UI (using Yaml mode but liked to try that bit of config option) and selected an image for that person too. Upon which a new folder in my /config was created: /config/image where 3 maps have been made for the images.
I deleted the person entity after that, and have no other UI configured entity with an image from the ui.
Maybe I should simply delete that /config/image and try again?
Any idea how to reproduce this? For me it works with 8fc69b7242 on Ubuntu 20.04 (clean pull):
script/setup source venv/bin/activate hass -c config
=> Boots without any issues in the log or the frontend.
Also setting up the various picture entities, uploading and cropping an image to an area works.
It seems to be limited to our container-based installations
How to build those? A naive
docker build . -t homeassistant
fails with
base name (${BUILD_FROM}) should not be blank
Also setting up the various picture entities, uploading and cropping an image to an area work
I do remember that was one of the reasons I deleted the UI created person entity: couldn't get the crop function to work, and ended up with black images. Didn't think anything of it at that time, because no other harm done. Now I see the issue ... sorry I didnt mention before.
@Mariusthvdb according to https://github.com/home-assistant/core/issues/61756#issuecomment-993422811 it's a bit more complex and apparently only occurs in containerized environments.
right, not sure about any of this. btw, tried to delete the folder /config/image and update again to todays dev 1214, but it isn't available anymore ;-)
with #61661 is his now solved?
@Mariusthvdb no, unfortunately it is not solved. The change (#61661) that caused this issue (#61756) was reverted but should be re-applied in the future because of security concerns.
Therefore, we first need to find a way to reproduce this.
unfortunately I dont see the update to dev 1214 anymore, so I can not try again. It was the only thing needed to produce the issue ;-)
I do see that I can update from OS:
You have 8.0.dev20211114 installed. Click update to update to version 8.0.dev20211213
which must be a fluke too ...
As written above, it seems only to happen with containerized versions of Home Assistant (https://github.com/home-assistant/core/issues/61756#issuecomment-993422811), but I couldn't find documentation how to build a containerized version of Home Assistant like the official images and the intuitive way doesn't work.
I was able to reproduce this. I was previously running v2021.11.4 of HA on a raspberry pi 3b+ inside of a docker container. I decided to pull and use the latest tagged image (2022.1.0.dev20211214). After building the container, I noticed my frontend of HA wasn't working. Checked the logs, and they are identical to what OP posted.
Running in docker on a pi4 image id c6e1e0ac2abb (I run :latest tags) I get a similar error:
[homeassistant.setup] Setup failed for image: Unable to import component: cannot import name '_imaging' from 'PIL' (/usr/local/lib/python3.9/site-packages/PIL/__init__.py)
[homeassistant.setup] Unable to set up dependencies of person. Setup failed for dependencies: image
[homeassistant.setup] Setup failed for person: Could not set up all dependencies.
[homeassistant.setup] Unable to set up dependencies of onboarding. Setup failed for dependencies: person
[homeassistant.setup] Setup failed for onboarding: Could not set up all dependencies.
[homeassistant.setup] Unable to set up dependencies of frontend. Setup failed for dependencies: onboarding
[homeassistant.setup] Setup failed for frontend: Could not set up all dependencies.
[homeassistant.setup] Unable to set up dependencies of my. Setup failed for dependencies: frontend
[homeassistant.setup] Setup failed for my: Could not set up all dependencies.
[homeassistant.setup] Unable to set up dependencies of map. Setup failed for dependencies: frontend
[homeassistant.setup] Setup failed for map: Could not set up all dependencies.
[homeassistant.setup] Unable to set up dependencies of logbook. Setup failed for dependencies: frontend
[homeassistant.setup] Setup failed for logbook: Could not set up all dependencies.
[homeassistant.setup] Unable to set up dependencies of mobile_app. Setup failed for dependencies: person
[homeassistant.setup] Setup failed for mobile_app: Could not set up all dependencies.
after this I ran :2021.12.1 and everything is starting back up again.
I faced an issue on this release(2022.1.0.dev20211214) too. My installation was complaining about the X-Forwarded-For header and wasn’t recognizing the already working trusted proxy.
I have reverted back to the previous version (2022.1.0.dev20211213) and it’s running fine.
thanks Martin, can confirm this is now resolved. running Home Assistant 2022.1.0.dev20211215 just nicely.
The problem
updated to latest dev https://github.com/home-assistant/core/commits/dev but got a safe mode boot... all kinds of errors like logged below
system returned to 2022.1.0.dev20211213 automatically though so thats ok...
What version of Home Assistant Core has the issue?
2022.1.0.dev20211214
What was the last working version of Home Assistant Core?
2022.1.0.dev20211213
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Frontend ?
Link to integration documentation on our website
https://www.home-assistant.io/integrations/frontend/
Example YAML snippet
No response
Anything in the logs that might be useful for us?
leading up to
and going on after that:
most awkward is this:
and ofc this: