I just found out that coexisting of a nmea tcp/20220 and a signalk tcp/3000 connection to pypilot is that data (e.g., SOG) that you put into pypilot through nmea:20220 comes back through signalk:3000. This becomes visible as two sources for the same path in signalk's data browser *):
![[Image: 185943500-b639634d-ba4f-48d1-9a76-9033ad62fcb2.png]](https://user-images.githubusercontent.com/17980560/185943500-b639634d-ba4f-48d1-9a76-9033ad62fcb2.png)
At first sight this only seems to have the drawback of source data ambiguity. This can be solved by using the signalk Source Priorities feature. But invisible in the UI, there might also be some infinite loop created by this. As it is not visible, it scares me, and without knowing for sure, I am inclined to attribute past problems with signalk's node process going through the roof, and some wifi issues, to this effect.
To prevent or solve this, I have now made the pypilot client device in signalk (Security->Devices) read/only. This way, pypilot might still benefit from any data that becomes available in signalk, but there is no risk of a loop being created.
Of course, this is a temporary solution, only to bridge the time until the pypilot signalk connection is debugged. But some prudence in making the signalk connection read-write might still be advised.
*) note that in this chosen example, the original wind speed is practically 0; pypilot merely seems to round the figure.
At first sight this only seems to have the drawback of source data ambiguity. This can be solved by using the signalk Source Priorities feature. But invisible in the UI, there might also be some infinite loop created by this. As it is not visible, it scares me, and without knowing for sure, I am inclined to attribute past problems with signalk's node process going through the roof, and some wifi issues, to this effect.
To prevent or solve this, I have now made the pypilot client device in signalk (Security->Devices) read/only. This way, pypilot might still benefit from any data that becomes available in signalk, but there is no risk of a loop being created.
Of course, this is a temporary solution, only to bridge the time until the pypilot signalk connection is debugged. But some prudence in making the signalk connection read-write might still be advised.
*) note that in this chosen example, the original wind speed is practically 0; pypilot merely seems to round the figure.