-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
[Bug]: Cannot update from 1.0.8 to 2.0.0 (Error 505) #47
Comments
Did you check this Common Issues pages ? |
There seems that there was a server error with the ffmpeg-for-homebridge dependency yesterday. I too couldn't download the file referenced in your log. Now it works for me. Can you try again? |
I gave it a try right now. |
Could you please specify which homebridge version you're using? The log mentions that it's requiring version 1.3.5 and up. Actually for 2.0.0 you should even need a version > 1.4.1. Maybe you'll have to update this package first. |
I am using 1.4.1 and homebridge docker on a raspberry pi 4 |
Did you already try to completely uninstall the plugin and then do a fresh install with 2.0.0? |
No, I didn't, because I don't want to loose all of my automations... I tried to install 2.0.1-beta3. It works. It is just the 2.0.0 Version which doesn't works. So I will stay on 2.0.1-beta3 until the next stable version... |
can not install the beta.... USER: root npm ERR! code 1 npm ERR! A complete log of this run can be found in: Operation failed. Please review log for details. |
sry I can't reproduce this. For me it installs without any issues. But since this can't be reproduced I don't think we can help you here really. Did you follow any tutorial for homebridge installation? |
This comment was marked as off-topic.
This comment was marked as off-topic.
It seems the plugin is unable to start the ffmpeg process on your system. Did you try to install ffmpeg-for-homebridge globally as pointed out under https://github.com/homebridge-eufy-security/plugin/wiki/Common-Issues section Since this has nothing to do with the original issue I'll delete your posts and we can discuss this further in your other issue #60 |
Hey @Dominik-1980 Since this issue is not relevant for you anymore I'll close this. Please reopen if there are new things to share. For anyone having update problems: There is a new section in Common issues which might help: https://github.com/homebridge-eufy-security/plugin/wiki/Common-Issues |
Is this the same error? I have had the same behavior updating to version 2.0.0. After a long painful process with de-installations, restarts, deleting directories, etc. I´ve got the system running again. Now it all comes up again when I try to install version 2.0.1. -- npm WARN config global npm ERR! A complete log of this run can be found in: Operation failed. Please review log for details.Sorry if I don't see what to do. |
HI @permaMonk can you attach the mentioned log Better still: contact me on discord if you can. |
Don´t know how to contact you directly in Discord. Don´t know how to copy (the contend of) this logfile. |
just drag the file onto the textbox where you're typing your comment here. It will attach the file. |
Drag&Drop not possible. I’m working only with CLI on that RasPi. Can open the log file with nano but unable to mark the whole content, then copy it to paste it in a text file on my PC. Yes I know much to learn about Unix. |
well you log into it using ssh or something, right? Just copy the file via ssh: https://www.simplified.guide/ssh/copy-file |
Yes via ssh. Your link sounds as a big help. I’ll try this later. |
Ok it was a long way. Here it comes - the log file |
Unfortunately it doesn't say exactly what's wrong, or I'm not seeing the issue right away. Anyway the bug seems to be about the FFmpeg-for-homebridge dependency as was already stated by the error message above. You could try a few things (I would suggest from top to bottom to do one step at a time and see if the update then works) all commands will have to be run as root
Try updating after each step and see if it has helped. Let me know ;-) |
I`ll give this a try on the weekend. |
Ok, done. But nothing helped. :( So I´ve deinstalled the plugin and re installed. But same error as before. Now it´s gone - totally. |
I have to admit that I'm longshotting here, but what happens if you'll drop the Does any part of the path mentioned in the error messages even exist? |
You mean the original automated Homebridge-Eufy-security Plugin command “sudo -E -n npm install -g homebridge-eufy-security@latest”? Doing this manually on CLI without -E? btw: What is the function of -E? |
Yep. You can just run that manually on cli and it will do exactly what homebridge tries to do for you.
For me at least a normal |
Btw. you should drop |
So could say this worked. After restart Homebridge needed really long time to come up. A little fine tuning like unbridge the plugin. Replace username / MAC address and port number with the old data was necessary cause with the new data the Eufy Cam Status was not reachable / grey. So happy again - but I'm afraid I'll have to do every future update manually. Now a little bit later get red errors: Sorry for the trouble. |
Which Port did you use? how do I found which port my Doorbell is Using? |
The plugin finds the entries username / MAC address and port number by itself and sets them in its config. I have only overwritten the new values with the entries from the backup of the old config. |
Glad this helped. The error you're experiencing is most likely this one: #14 Am I right to suspect that this only is a log output and doesn't crash the plugin/homebridge? |
You are right - it’s a snippet of the log, no more crashing of the plug-in. I take a look to the #14 thread later. |
What happened?
I can´t update to 2.0.0 because of Error 505 and Permission Denied.... Please see the log below...
`npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { homebridge: '^1.3.5', node: '^14.18.1' },
npm WARN EBADENGINE current: { node: 'v16.15.0', npm: '8.5.5' }
npm WARN EBADENGINE }
npm ERR! code 1
npm ERR! path /homebridge/node_modules/homebridge-eufy-security/node_modules/ffmpeg-for-homebridge
npm ERR! command failed
npm ERR! command sh -c node install.js
npm ERR! Downloading ffmpeg from https://github.com/homebridge/ffmpeg-for-homebridge/releases/latest/download/ffmpeg-debian-armv7l.tar.gz
npm ERR! node:events:505
npm ERR! throw er; // Unhandled 'error' event
npm ERR! ^
npm ERR!
npm ERR! Error: EACCES: permission denied, open '/root/.npm/_ffmpeg_for_homebridge/.download'
npm ERR! Emitted 'error' event on WriteStream instance at:
npm ERR! at emitErrorNT (node:internal/streams/destroy:157:8)
npm ERR! at emitErrorCloseNT (node:internal/streams/destroy:122:3)
npm ERR! at processTicksAndRejections (node:internal/process/task_queues:83:21) {
npm ERR! errno: -13,
npm ERR! code: 'EACCES',
npm ERR! syscall: 'open',
npm ERR! path: '/root/.npm/_ffmpeg_for_homebridge/.download'
npm ERR! }
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-05-28T16_03_29_008Z-debug-0.log
`
The text was updated successfully, but these errors were encountered: