You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Note: This is a restricted shell, sudo cannot be used here.# …# Node.js Version: v20.9.0# Node.js Path: /opt/homebridge/bin/node# Plugin Path: /var/lib/homebridge/node_modules# …# homebridge@home:/var/lib/homebridge $
NVM
Used for personal projects management.
It’s not related to Homebridge, sharing it as it's node is in the pi user's path.
# pi@home ~
$ which node
# /home/pi/.nvm/versions/node/v20.9.0/bin/node
sudo apt-get install bluetooth bluez libbluetooth-dev libudev-dev
1.1 Node in the path
Noble installation requires the node binary to be in the path, I assume that the above config can lead to issues and a mess. Any suggestions on how to configure it properly?