2026-02-12, 08:11 AM
(2026-02-12, 12:32 AM)barnaclebill22 Wrote: I created a PR for one possible solution.Thanks for the attempt.
https://github.com/pypilot/pypilot/pull/267
Parameters in pypilot.conf will override zeroconf. The zeroconf process still runs but you would have to erase the signalk lines in pypilot.conf and restart to get zeroconf to re-scan. I started doing this second modification and I got out of my depth with race conditions so I will leave it to someone smarter (like Claude :-)
I will try it, however now it's successfully providing data to the main Sk server. However, I don't know how, as there was a point that it wasn't, even when I put venus os Raspi down for several days.
So desperate, I activated again the Imu attached to my Mac Arthur hat, which before, when TinyPilot was providing data , was disabled.
After some days, working on another thing, I noticed that I had messages in Sk server log saying something like "there was a new device offering heading, roll, etc" (don't remember the exact words), a message shown in a neverending cascade. That was the TinyPilot back to scene.
So I disabled again the MacArthur Imu and, voila! I got the data flow as before the problem was. But there is no trace in Sk server of anything.
I just got an active deltas Ws connection with my Sk server username which don't know where did it come from. I don't even know what data is generating. Mistery!
One day TinyPilot stopped providing its data again, but maybe due to the fact that these days I'm developing a Sk Plugin and I am restarting Sk server maybe 20 times a day. Now it's OK again.
In the meantime of this story, I also updated twice Sk installer and sk server to the latest version.
If I have the same problem again, I'll try your solution, but for the moment, I won't touch it again.
Thanks a lot for your efforts.

