You might first want to verify the assumption that you already have proper wind information in signalk by showing the relevant portion (environment.wind.*) of the signalk data browser screen?
Indeed for incoming signalk traffic you don't see anything in the opencpn nmea debug window - because it is not nmea! Bit of a bummer because the debug window was a handy tool, which does not have its equivalent for signalk. To be frank, I have not felt a strong need for debugging the signalk interface, because when data is available in signalk data browser, so far the assumption that is also available in opencpn has held up pretty much always.
Now if the pypilot's port 20220 is the only connection to pypilot, I can imagine your pypilot lacks wind because opencpn does not generate MWV messages out of signalk data. These MWV messages are the ones that pypilot needs to enable the Wind modes. You might have luck checking Forward NMEA in the OpenCPN Pypilot plugin, but I don't think so because it's supposed to forward and not generate messages.
With modern versions of pypilot, I'd suggest hooking pypilot straight to signalk, and bypass the link through OpenCPN altogether. This requires a few actions, all of which are in https://github.com/pypilot/workbook/wiki...k-zeroconf.
Indeed for incoming signalk traffic you don't see anything in the opencpn nmea debug window - because it is not nmea! Bit of a bummer because the debug window was a handy tool, which does not have its equivalent for signalk. To be frank, I have not felt a strong need for debugging the signalk interface, because when data is available in signalk data browser, so far the assumption that is also available in opencpn has held up pretty much always.
Now if the pypilot's port 20220 is the only connection to pypilot, I can imagine your pypilot lacks wind because opencpn does not generate MWV messages out of signalk data. These MWV messages are the ones that pypilot needs to enable the Wind modes. You might have luck checking Forward NMEA in the OpenCPN Pypilot plugin, but I don't think so because it's supposed to forward and not generate messages.
With modern versions of pypilot, I'd suggest hooking pypilot straight to signalk, and bypass the link through OpenCPN altogether. This requires a few actions, all of which are in https://github.com/pypilot/workbook/wiki...k-zeroconf.