(2024-03-17, 11:33 AM)PaddyB Wrote:(2024-03-15, 01:45 AM)PaddyB Wrote: Thnx though it seems rock solid, it's just that opencpn running on the Pi won't send to peer.
Not sure if this should be in bugs or not but for now... http response -1 is about communication errors between machines, I'll keep digging for now, just to recap >> with opencpn running on a laptop, android tablet 6 openplotter V4 on a Pi4 the laptop & tablet will seed to peer to each other but not the Pi.
https://www.cruisersforum.com/forums/f13...ost3881110
Not sure if this is related but I was having an issue with an Yachta wind sensor communicating with SignalK. I tried the hostname of the sensor first "windsensor-0.local" but that wouldn't work for me. With a little help from Newbie 1979 I tried using the WLAN Client IP and that did work for a bit. After a while, it kept dropping the connection while using the SignalK data connections.
Ended up connecting to the sensor in NodeRed with a TCP node and then sending it TCP to 10110. Has been rock solid since.
Seems like there is some type of compatibility issue with SignalK and the Pi5. Lots of weird stuff going on with network connections.