(You are right. In the past when SignalK had no web ui, openplotter set the configurations for SignalK.
SignalK has developed a good configuration ui today. It is not openplotters job to work against the SignalK web ui.
Openplotter has reduced/reduces/will reduce things which are solved in SignalK.
You are completly free to add/edit/delete a connection on 55557 UDP type SignalK input with the SignalK web ui.
The dashboard of SignalK does show you the connection status.
It isn't a good idea to put all the old connections 55555,55556,55557,55558,55560,55561 into the configuration when most aren't used anymore and produce bad status.
I use 55557 UDP for SignalK and add the connection myself. (We send pure SignalK why should we configure SignalK input outside of SignalK-server with openplotter?)
The port 20220 is for the communication with pypilot afaik. Don't ask me why it isn't 55557.)
Sorry I didn't see that your question was only about documentation. So we should document SignalK better and changes from 1.x to 2.x.
Martin
SignalK has developed a good configuration ui today. It is not openplotters job to work against the SignalK web ui.
Openplotter has reduced/reduces/will reduce things which are solved in SignalK.
You are completly free to add/edit/delete a connection on 55557 UDP type SignalK input with the SignalK web ui.
The dashboard of SignalK does show you the connection status.
It isn't a good idea to put all the old connections 55555,55556,55557,55558,55560,55561 into the configuration when most aren't used anymore and produce bad status.
I use 55557 UDP for SignalK and add the connection myself. (We send pure SignalK why should we configure SignalK input outside of SignalK-server with openplotter?)
The port 20220 is for the communication with pypilot afaik. Don't ask me why it isn't 55557.)
Sorry I didn't see that your question was only about documentation. So we should document SignalK better and changes from 1.x to 2.x.
Martin