New install on Win 11
I have installed Signal K Server on a new Win 11 computer and I cannot install/all plugins.
19 Replies
/all = /add
How do I set up the SignalK server ?
I just realized that the installation kit is with version 18 of nodejs and the latest version of the server requires a minimum of version 20.
I'll try to post an update this weekend...
Using the windows setup. I have been able to successfully install Node Red, NMEA to NMEA and the Simulator plugins. But Victron BLE fails (could be python3 setup) and NMEA Streamer and BT Sensors install but the server will not load after restart.
These could be Node JS 18 or maybe just not compatible with windows ver
'Victron BLE' I've never tried it, but I'd be very surprised if it worked on Windows !
And your SignalK server start in 2.14.0 version with nodejs18 ?
Yes
I saw that and actually went to the web page. I wasn't sure if ver 18 was by design for windows. The web page walks through how to upgrade in linux.
Was your setup done as described here ?
https://github.com/SignalK/signalk-server-windows
Yes. That is how it was setup.
I wrote a short paragraph about updating nodejs.
And it won't happen automatically.
https://github.com/SignalK/signalk-server-windows?tab=readme-ov-file#upgrade-nodejs
And first I need to update the installation kit.
While waiting for the installation kit to be updated, you can downgrade the server version as follows:
I tried downgrading to 2.13.5 but the server wouldn't start. I think I will just wait for the new kit and do a fresh install. That will be the cleanest.
https://github.com/SignalK/signalk-server-windows/releases/tag/v1.3.0
I have just released a new version of the Windows installation kit with nodejs v22.16.0 integrated.
Before proceeding with a new installation, remember to uninstall the signalk service
remove-signalk-server-services.cmd before deleting or renaming your current signalk folder.
https://github.com/SignalK/signalk-server-windows?tab=readme-ov-file#upgrade-nodejs
I've done the minimum checks, but I'm on the train to the boat and I've burn my WiFi quota with the installation tests 😆
I'm sailing on Saturday, but you can give me your feedback and I'll take a look on Sunday.No change. I ran remove-signalk-server-services.cmd. Verified that it was removed in the services app. Removed the .signalk directory. Ran 1.3.0 and verified that it was installed with v22.16 of node.js.
Recap. I was able to successfully install Node Red & Simulator plugins. Victron BLE failed (I think your right it is probably not Windows compatible). NMEA to NMEA, BT Sensors and NMEA streamer install but the server will not come back up after install. If I rename the node_modules directories the server will come back up.
Something else that may help. I have been trying to test by running test VDR files in OpenCPN. Running the file locally I can see that the data is making it to the sever. If I use the simulator plugin to feed signal k data to local OpenCPN I can see the data. If I run OpenCPN on an external computer on the same network there is no data in or out. I can't see signal k data coming from the server and if I run VDR it does not make it to the server. Not sure if that helps or confuses things more.
As for these two BT-related plugins:
- Victron BLE
- BT Sensors
I think there's little chance they'll work on Windows. The Linux and Windows stacks are too different.
For these two other plugins:
- NMEA to NMEA
- NMEA streamer
I would like to have the exact names and messages you have on the server to try to locate the problem.
Actually it looks like the NMEA to NMEA did install.
nmea-streamer
nmea0183-to-nmea0183
I tried to install the BT sensors again and it also failed on some depreciated packages but I agree that it is probably too different to work on windows.
BT-Sensors
Jun 22 07:54:20 POST /skServer/appstore/install/bt-sensors-plugin-sk/1.2.2 200 657.658 ms - 36
Jun 22 07:54:32 stderr: npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
Jun 22 07:54:33 stderr: npm warn deprecated npmlog@4.1.2: This package is no longer supported.
Jun 22 07:54:33 stderr: npm warn deprecated are-we-there-yet@1.1.7: This package is no longer supported.
Jun 22 07:54:34 stderr: npm warn deprecated gauge@2.7.4: This package is no longer supported.
Jun 22 07:56:06 stderr: npm warn cleanup Failed to remove some directories [ npm warn cleanup [ npm warn cleanup 'c:\signalk\signalkhome\.signalk\node_modules\usocket', npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'c:\signalk\signalkhome.signalk\node_modules\usocket\node_modules\node-gyp\gyp\tools\emacs'] { npm warn cleanup errno: -4048, npm warn cleanup code: 'EPERM', npm warn cleanup syscall: 'rmdir', npm warn cleanup path: 'c:\signalk\signalkhome\.signalk\node_modules\usocket\node_modules\node-gyp\gyp\tools\emacs' npm warn cleanup } npm warn cleanup ] npm warn cleanup ]
Jun 22 07:56:06 stdout: added 81 packages, removed 2 packages, and audited 750 packages in 2m
Jun 22 07:56:06 stdout: 58 packages are looking for funding run
npm fund for details
Jun 22 07:56:06 stdout: 26 vulnerabilities (2 low, 16 moderate, 8 high) To address issues that do not require attention, run: npm audit fix To address all issues possible (including breaking changes), run: npm audit fix --force Some issues need review, and may require choosing a different dependency. Run npm audit for details.About
nmea-streamer & nmea0183-to-nmea0183:
I installed and activated both plugins, and this does not prevent the server from starting. I have not noticed any direct incompatibility with Windows.
I think you should contact the developers of the respective plugins.
For nmea-streamer, I think it would be helpful if the developer provided a sample NMEA0183 file, as this would save a lot of time when testing at startup.
You can find your plugin installation logs here:
C:\signalk\signalkhome\npm-cache_logs*.log