2023-08-02, 08:48 PM
HW: RPi4 OP3/64bit SignalK 2.0.0.
I also have same sort of problem, at least the error generated by the reinstall: "FAILED Command npm config get prefix ...exit status 7" is the same as jvadell has.
In my SK/Instrumentpanel there is also a notification "newVersion", which paints the edges of the boxes in glaring yellow so that Instrumentpanel is useless in night sailing. I have tried get rid of the alert but seems to be impossible.
Tried also to update to the next version of the SK 2.1.0, but the update failed generating the above mentioned error.
So after reading this thread I cleared the browser cache (Chromium/.../More Tools/Clear browsing data -All time).
Then I run Openplotter/Signal K Installer/ Reinstall Signal K.
It failed with the same error code (npm config...) as before, but this time also the SK/Instrumentpanel deleted my second page totally and left to the first page datetime, cog and position. The edges were of course in yellow and the "newVersion" alert on.
Any ideas ?
I also have same sort of problem, at least the error generated by the reinstall: "FAILED Command npm config get prefix ...exit status 7" is the same as jvadell has.
In my SK/Instrumentpanel there is also a notification "newVersion", which paints the edges of the boxes in glaring yellow so that Instrumentpanel is useless in night sailing. I have tried get rid of the alert but seems to be impossible.
Tried also to update to the next version of the SK 2.1.0, but the update failed generating the above mentioned error.
So after reading this thread I cleared the browser cache (Chromium/.../More Tools/Clear browsing data -All time).
Then I run Openplotter/Signal K Installer/ Reinstall Signal K.
It failed with the same error code (npm config...) as before, but this time also the SK/Instrumentpanel deleted my second page totally and left to the first page datetime, cog and position. The edges were of course in yellow and the "newVersion" alert on.
Any ideas ?