This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
OpenPlotter 4 roadmap
Remove "/en/":

https://openplotter.readthedocs.io/latest/
https://openplotter.readthedocs.io/4.x.x/
https://openplotter.readthedocs.io/3.x.x/
https://openplotter.readthedocs.io/2.x.x/
Reply
Hello,
I know it is a lot of work in progress here and I also want to thank you again for the whole team's effort.
One question: can you estimate a release date for the stable GPIO app?  I'm interested about seatalk 1 support because I'm still having this kind of equipments and I intend to make the switch from OP3/Rpi4 to OP4/RPi5
Thank you
- SV Haimana
Reply
Hi R
Old issue not solved. A new try to discuss.
New image again: v4 downloaded today: 2024-06-19 OpenPlotter v4... on a Rpi4.
Still the same npm? trouble.
SignalK can't update or show "Appstore" contents or whatever where npm is needed.
Openplotter Signalk Installer also not functional as before. (time out)
I did nothing more on first start up than changed key board to SE, changed host name to RPi4 and a new password. (local wifi country not set since I'm using a wired net.)
I tested to reinstall npm including nodejs.
result:
npm -v: 10.8.1
nodejs -v: v18.20.3

It's the same behavior on my Rpi400 and Rpi5

Håkan
Reply
(2024-07-07, 03:34 PM)Hakan Wrote: Hi R
Old issue not solved. A new try to discuss.
New image again: v4 downloaded today: 2024-06-19 OpenPlotter v4...  on a Rpi4.
Still the same npm? trouble.
SignalK can't update or show "Appstore" contents or whatever where npm is needed.
Openplotter Signalk Installer also not functional as before. (time out)
I did nothing more on first start up than changed key board to SE, changed host name to RPi4 and a new password. (local wifi country not set since I'm using a wired net.)
I tested to reinstall npm including nodejs.
result:
npm -v: 10.8.1
nodejs -v: v18.20.3

It's the same behavior on my Rpi400 and Rpi5

Håkan
I also tried to use a v3 image. The same result. No Signal k update possible.
I tried to reinstall npm. Broken packages:

Code:
pi@RPi4:~ $ sudo apt install npm
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
libnode72 : Conflicts: nodejs-legacy
nodejs : Conflicts: npm
E: Unable to correct problems, you have held broken packages.
pi@RPi4:~ $
Reply
How are your devices connected to the internet? You have just downloaded the image and gone straight to update and it's broken? Is that correct
Reply
The openplotter v4 is downloaded and used to make an image by Raspberry pi imager. The card is mounted and the Rpi4 is started as normal.
It's wired connected to the Internet. The same result if a wifi is used. Internet connection is working.
npm/nodejs is not working so any SignalK update is not working.
Reply
(2024-07-06, 09:52 AM)sebba Wrote: Hello,
I know it is a lot of work in progress here and I also want to thank you again for the whole team's effort.
One question: can you estimate a release date for the stable GPIO app?  I'm interested about seatalk 1 support because I'm still having this kind of equipments and I intend to make the switch from OP3/Rpi4 to OP4/RPi5
Thank you

I may have been too optimistic about a quick fix for Seatalk1 on Raspberry 5. My first attempt failed and I'm afraid we should ask for help here because this shouldn't delay more important things. Any ideas...?
Reply
(2024-07-08, 06:43 PM)Hakan Wrote: The openplotter v4 is downloaded and used to make an image by Raspberry pi imager. The card is mounted and the Rpi4 is started as normal.
It's wired connected to the Internet. The same result if a wifi is used. Internet connection is working.
npm/nodejs is not working so any SignalK update is not working.

This is a really strange issue because no one else reported something similar. Could you open a new thread for this issue? Did we already have one?
Reply
(2024-07-08, 07:44 PM)Sailoog Wrote:
(2024-07-08, 06:43 PM)Hakan Wrote: The openplotter v4 is downloaded and used to make an image by Raspberry pi imager. The card is mounted and the Rpi4 is started as normal.
It's wired connected to the Internet. The same result if a wifi is used. Internet connection is working.
npm/nodejs is not working so any SignalK update is not working.

This is a really strange issue because no one else reported something similar. Could you open a new thread for this issue? Did we already have one?

My Signal K also doesn't update anymore. The web UI pretends everything is working (update being installed - ... - please restart) but on a restart I find myself with the same version as before. Could only track down some checksum errors on the npm downloads so far and assumed that this as a temporary glitch (caching issue for example). Hence no report here so far. 
Also: Everything still working fine in v4. It's just the updates.
Reply
(2024-07-09, 11:00 AM)tsr Wrote: My Signal K also doesn't update anymore. The web UI pretends everything is working (update being installed - ... - please restart) but on a restart I find myself with the same version as before. Could only track down some checksum errors on the npm downloads so far and assumed that this as a temporary glitch (caching issue for example). Hence no report here so far. 
Also: Everything still working fine in v4. It's just the updates.

Is there anything in the server log after you try to update?
Reply


Forum Jump:


Users browsing this thread: 4 Guest(s)