Skip to content
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

Node.js v20.9.0 issue on Synology. #1581

Closed
1 task done
psalize opened this issue Feb 1, 2025 · 2 comments
Closed
1 task done

Node.js v20.9.0 issue on Synology. #1581

psalize opened this issue Feb 1, 2025 · 2 comments
Labels
discussion Let's talk about it

Comments

@psalize
Copy link

psalize commented Feb 1, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Describe The Bug

The Ring Plugin was not connecting anymore. Refresh token failed. When trying to reinstall the plug-in, the following error occurred:

Node.js v20.9.0
npm error code 1
npm error path /volume1/homebridge/node_modules/homebridge-ring/node_modules/ffmpeg-for-homebridge
npm error command failed
npm error command sh -c node install.js
npm error A complete log of this run can be found in: /var/packages/homebridge/home/.npm/_logs/2025-02-01T14_33_45_154Z-debug-0.log

Error: Operation failed with code 1.
You can download this log file for future reference.
See https://github.com/homebridge/homebridge-config-ui-x/wiki/Troubleshooting for help.

It seems like, there was a change made to the required node version. Unfortunately, as of now, there is no update for node.js for Synology. Running node.js on Docker didn't help. Installing earlier versions of the ring plug-in didn't work either.

To Reproduce

No response

Expected behavior

The ring plugged in to work with Homebridge on a sinology NAS :)

Relevant log output

Screenshots

No response

Homebridge Ring Config

{
            "refreshToken": 
      "showPanicButtons": true,
            "_bridge": {
                "username": "xx:xx:xx:xx:xx:xx",
                "port": 38711
            },
            "platform": "Ring"
        },

Additional context

No response

OS

Synology DSM 7.2.2x

Node.js Version

20.9.0

NPM Version

7.22x

Homebridge/HOOBs Version

v1.8.5

Homebridge Ring Plugin Version

latest

Operating System

Synology DSM 7.2.2x

@psalize psalize added the bug Something isn't working label Feb 1, 2025
@tsightler
Copy link
Collaborator

I'm not really sure why you believe this is a Node.js version issue. While Node.js is 20.9.0 is a bit outdated, it should be recent enough to work and nothing in the logs you posted indicates an issue with the node version. The error is actually fairly clear:

npm error path /volume1/homebridge/node_modules/homebridge-ring/node_modules/ffmpeg-for-homebridge
npm error command failed
npm error command sh -c node install.js

This occurred trying to install ffmpeg-for-homebridge package which is a critical dependency. You'll need to troubleshoot why you are unable to install this package as there's not enough information to go on here to provide any insight, it just says that running the install.js script failed.

The ffmpeg-for-homebridge package works by running install.js as a post-install step and this script tries to determine the correct ffmpeg binary for your system and then downloads that binary into the ffmpeg-for-homebridge directory. You can also try to manually download the correct ffmpeg binary from the Github releases page and place it there yourself, if the script is failing for some reason.

@tsightler tsightler added discussion Let's talk about it and removed bug Something isn't working labels Feb 1, 2025
@tsightler
Copy link
Collaborator

tsightler commented Feb 3, 2025

@psalize As this is not an issue with the code in this repository, I'm going to close this. I'd suggest if you need help troubleshooting dependency install issues the discussion groups might be a better place. The most common issue for failure of the ffmpeg-for-homebridge install.js script is lack of free disk space as the static ffmpeg binary is quite large these days, and requires as much as 150MB of total free space to download the compressed binary and extract it.

Other reasons for failure are temporary issues with binary downloads from Github, etc. You can always manually attempt to install it via npm at any time.

@tsightler tsightler closed this as not planned Won't fix, can't repro, duplicate, stale Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Let's talk about it
Projects
None yet
Development

No branches or pull requests

2 participants