-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
camera.snapshot 'no access to path!' error in 0.65.x #13107
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
Comments
Found a workaround while it gets fixed: create a file with the same name of the snapshot in the same folder. |
kellerza
added a commit
to kellerza/home-assistant
that referenced
this issue
Mar 18, 2018
balloob
pushed a commit
that referenced
this issue
Mar 30, 2018
balloob
pushed a commit
that referenced
this issue
Mar 30, 2018
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Uh oh!
There was an error while loading. Please reload this page.
Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (
hass --version
):0.65.2 and 0.65.30.64.3Python release (
python3 --version
):Component/platform:
Raspberry Pi 3
Description of problem:
camera.snapshot seems to have broken in the
0.65.x0.64.3 release. I was running 0.64.2 and it worked fine untill I updated to 0.65.2, I then received the error 'Can’t write ‘/tmp/snapshot_front_door_1.jpg’, no access to path!'Expected:
Expected it to write to the given path :)
Problem-relevant
configuration.yaml
entries and steps to reproduce:homeassistant user has full access to the /tmp/ folder
Additional info:
Reverting to version before 0.64.3 fixes the problem, it now works as before. I'm now running version 0.64.2 again and it works as expected.
Seem to be related to a fix in the 0.64.3 release:
https://github.com/home-assistant/home-assistant/releases/tag/0.64.3
The text was updated successfully, but these errors were encountered: