-
Notifications
You must be signed in to change notification settings - Fork 386
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
homebridge-config-ui-x does not see latest nodeJS installation #2292
Comments
I believe NodeJS is picked up from the path, but I could be wrong. Check out what the homebridge plist shows, it is in the directory |
Hi,
Could I edit the .plist and exchange 22.11.1 with 22.12.0 or would that break something? |
You should be able to just edit the plist - is it generated when you installed homebridge. |
I tried it with no success, it does not see the latest version, even after restarting hb-ui-x and homebridge itself. I found this the wiki and also how to fix it by reinstalling everything. As currently everything is working just fine, I guess, I will just leave it as it is. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been closed as no further activity has occurred. |
Current Situation
Config-ui-x does show in the Status page under System Information that there is currently nodejs v22.11.0 installed and as path Users/USERNAME/.nvm/versions/node/v22.11.0/bin
I installed nodejs with nvm package manager as described on their website for macOS
I manually updated nodejs with nvm and I can see in finder there are two folder under: Users/USERNAME/.nvm/versions/node/ v22.11.0 & v22.12.0
How do I tell homebridge-config-ui-x that there is a newer version downloaded/installed on my Mac?
Logs
No response
Config
No response
Homebridge UI Version
4.65.2
Homebridge Version
1.8.5
Node.js Version
22.12.0
Operating System
macOS
Environment Info
Using hb-service
Raspberry Pi Model
None
The text was updated successfully, but these errors were encountered: