Confirm the three versions
Run node --version, npm --version, and npx --version only. Report the real result of each command and do not install or upgrade anything.
Verification resultThree versions or the exact command that failed.One Node.js LTS installation supplies Node.js, npm, and npx for the guides that follow. Use the path for your computer, then confirm success with three real versions.
Node.js is the runtime, npm installs packages, and npx runs installers directly. A supported Node.js LTS installation supplies npm and npx too; they are not separate downloads.
You do not need to learn programming here. Success is simply three visible version numbers.
You are done whenYou know that Node.js LTS is the only separate installation.
If it did not workIf another guide asks you to download npm or npx separately, stop and return to this complete path.
If your AI can run commands on this computer, send it the request below. It checks first and does not reinstall a working environment.
Prepare the computer environment required by the Yeelight AI guides. Check Node.js, npm, and npx first, and do not reinstall anything when all three work. If something is missing, install the current Node.js LTS for this operating system using only the official Node.js source or the operating system's package tool; do not add unrelated developer tools. After installation, reopen the command window, run node --version, npm --version, and npx --version separately, and report the real output. If I need to click an installer or approve a permission prompt, pause and tell me exactly what to select. Do not request an account, password, or token, and do not permanently change the npm registry.
This prepares a public runtime and never needs access to a Yeelight account or home. Sanitized interactive demo. It does not read your home or control a device.
You are done whenThe AI reports three actual versions instead of only saying that installation finished.
If it did not workWhen the AI cannot run local commands, continue with the manual operating-system path.
For the clearest path, open the official Node.js download page, choose LTS, and use the system installer: .pkg on macOS or .msi on Windows. The question-mark button on every command block shows where to run a command.
The official installer is the beginner default. Copy a command below only when you already use Homebrew or have confirmed that WinGet works.
brew --versionbrew install node@24 && brew link --force node@24Run the second line only when the first shows a Homebrew version. If an existing link conflicts, do not add --overwrite; inspect the current Node.js or use the official .pkg above.
winget --versionwinget install --id OpenJS.NodeJS.LTS --exactRun the second line only when the first shows a version. If winget is missing, use the official Node.js .msi above.
Download only from Node.js, Homebrew, Microsoft, or the clearly marked third-party mirror. Never disable certificate checks.
You are done whenThe system installer or package manager finishes without asking for a separate npm or npx download.
If it did not workIf you are unsure about architecture: an Apple-chip Mac uses ARM64, an Intel Mac uses x64, and Windows shows x64 or ARM64 under Settings > System > About. The Node.js download page's default recommendation is also a safe choice.
Close the old Terminal or PowerShell window after installation and open a new one so the new PATH is active. Copy only one command at a time.
node --versionnode --version
Interactive demo only. It does not run a command or connect to a device.
npm --versionnpm --version
Interactive demo only. It does not run a command or connect to a device.
npx --versionnpx --version
Interactive demo only. It does not run a command or connect to a device.
You are done whenAll three commands return a version. The numbers do not need to match the examples, and npm or npx does not need the same version number as Node.js.
If it did not workClose the old command window and retry in a new one first. If it still fails, inspect where.exe node on Windows or command -v node on macOS instead of installing several Node.js copies.
Confirm the three versions first. If something fails, send the matching request below to your AI for diagnosis.
Run node --version, npm --version, and npx --version only. Report the real result of each command and do not install or upgrade anything.
Verification resultThree versions or the exact command that failed.Check this computer first. Install the current Node.js LTS only if Node.js, npm, or npx is missing, then verify all three version commands.
Verification resultNo duplicate installation and three real versions at the end.Find the actual locations of Node.js, npm, and npx on this computer. Tell me whether there is a duplicate installation or PATH conflict before changing or deleting anything.
Verification resultCommand locations, duplicate status, and a safe next step.Check whether this Windows computer has WinGet. If it does not, show me the official Node.js LTS MSI path without permanently weakening PowerShell security.
Verification resultWinGet availability and an official installer fallback.Check whether this computer is Apple Silicon, Intel, Windows x64, or Windows ARM64, then tell me which Node.js LTS installer matches it.
Verification resultThe installer type that matches this computer.The Node.js download or installation failed. Check the network, proxy, system time, and certificate message. Prefer an official source or a trusted mainland-China mirror, and never disable TLS or certificate verification.
Verification resultA recovery path that keeps certificate checks enabled.Yes. A supported Node.js LTS installation includes npm, and modern npx is the command runner supplied by npm. Neither needs a separate download.
No. Finish this guide when all three return a version; reinstalling can create an unnecessary PATH conflict.
Close every old Terminal or PowerShell window and open a new one. Installer PATH changes normally become visible only in a new window.
Do not stop here. Download the LTS Windows Installer (.msi) from the official Node.js resource above, or update Microsoft App Installer from the Store and try winget again.
Run where.exe node to list them and do not reinstall again. Keep one intentional version and ask someone familiar with system settings to remove an old PATH entry; this guide never deletes a version automatically.
Try npm.cmd --version first. If it returns a version, npm is installed and Command Prompt can run the later commands too. Do not permanently set the whole system to Unrestricted for one command.
No. The official macOS Installer (.pkg) is the clearest beginner path. Homebrew is only an optional route for people who already use it.
Quit Terminal completely, reopen it, and run command -v node. With no result, rerun the official .pkg using the default location instead of installing through several package managers.
A Mac with an M-series chip is Apple Silicon/ARM64; an older Intel Mac uses x64. On Windows, open Settings > System > About and read System type for x64 or ARM64.
Yes. They are different tools and their version numbers do not need to match. npm and npx commonly show the same or a nearby npm version.
Check the system clock and company proxy first. If the official page is slow, use the clearly marked third-party mainland-China mirror, but never disable TLS, ignore a certificate error, or use an unknown file-sharing link.
An official .pkg or .msi may show a normal operating-system permission prompt. Confirm the publisher and follow that prompt, but do not add sudo to npm commands or send your computer password to an AI.
Get practical setup help, exchange ideas, and follow what is next for Yeelight AI.
Meet other Yeelight AI users and get help with your setup.
Scan with WhatsApp or open the group directly.