2026-02-05, 03:06 AM
(This post was last modified: 2026-02-05, 03:13 AM by barnaclebill22.)
I have a problem similar to one discussed a couple of weeks ago, where I cloned a Pi root drive and now cannot get pypilot data in SK, no matter what I try.
I have uninstalled and reinstalled several times. I'm installing pypilot from source.
Pypilot appears to be connected to SK:
Feb 04 18:01:57 mastcompass pypilot[2271]: zeroconf addresses ['127.0.0.1', '192.168.68.83'] 2
Feb 04 18:01:58 mastcompass pypilot[2271]: zeroconf exception:
Feb 04 18:01:58 mastcompass pypilot[2271]: e is {'127.0.0.1': ServiceInfo(type='_pypilot._tcp.local.', name='pypilot._pypilot._tcp.local.', addresses=[b'\x7f\x00\x00\x01'], port=23322, weight=0, priority=0, server='pypilot._pypilot._tcp.local.', properties={'version': '0.56'}, interface_index=None), '192.168.68.83': ServiceInfo(type='_pypilot._tcp.local.', name='pypilot._pypilot._tcp.local.', addresses=[b'\xc0\xa8DS'], port=23322, weight=0, priority=0, server='pypilot._pypilot._tcp.local.', properties={'version': '0.56'}, interface_index=None)} 192.168.68.83
Feb 04 18:02:52 mastcompass pypilot[2271]: store_file /home/wjquigs/.pypilot/pypilot.conf 3003.663 imu.gyrobias
Feb 04 18:02:58 mastcompass pypilot[2271]: zeroconf addresses ['127.0.0.1', '192.168.68.83'] 2
Feb 04 18:03:00 mastcompass pypilot[2271]: zeroconf exception:
Feb 04 18:03:00 mastcompass pypilot[2271]: e is {'127.0.0.1': ServiceInfo(type='_pypilot._tcp.local.', name='pypilot._pypilot._tcp.local.', addresses=[b'\x7f\x00\x00\x01'], port=23322, weight=0, priority=0, server='pypilot._pypilot._tcp.local.', properties={'version': '0.56'}, interface_index=None), '192.168.68.83': ServiceInfo(type='_pypilot._tcp.local.', name='pypilot._pypilot._tcp.local.', addresses=[b'\xc0\xa8DS'], port=23322, weight=0, priority=0, server='pypilot._pypilot._tcp.local.', properties={'version': '0.56'}, interface_index=None)} 192.168.68.83
Also, the uid appears to be correct:
grep signalk pypilot.conf
signalk.period=0.5000
signalk.uid="pypilot-71815478698"
This uid shows up in SK->Security->Devices (I approved the access request).
But Data Browser does not show heading or YPR.
Disregard...the one piece I failed to clean up was signalk-token. Deleting this file after stopping the service, rebooting, and clearing signalk from pypilot.conf allowed me to get a new token and receive data. So either delete this thread, or leave it for the next knucklehead... :-)
I have uninstalled and reinstalled several times. I'm installing pypilot from source.
Pypilot appears to be connected to SK:
Feb 04 18:01:57 mastcompass pypilot[2271]: zeroconf addresses ['127.0.0.1', '192.168.68.83'] 2
Feb 04 18:01:58 mastcompass pypilot[2271]: zeroconf exception:
Feb 04 18:01:58 mastcompass pypilot[2271]: e is {'127.0.0.1': ServiceInfo(type='_pypilot._tcp.local.', name='pypilot._pypilot._tcp.local.', addresses=[b'\x7f\x00\x00\x01'], port=23322, weight=0, priority=0, server='pypilot._pypilot._tcp.local.', properties={'version': '0.56'}, interface_index=None), '192.168.68.83': ServiceInfo(type='_pypilot._tcp.local.', name='pypilot._pypilot._tcp.local.', addresses=[b'\xc0\xa8DS'], port=23322, weight=0, priority=0, server='pypilot._pypilot._tcp.local.', properties={'version': '0.56'}, interface_index=None)} 192.168.68.83
Feb 04 18:02:52 mastcompass pypilot[2271]: store_file /home/wjquigs/.pypilot/pypilot.conf 3003.663 imu.gyrobias
Feb 04 18:02:58 mastcompass pypilot[2271]: zeroconf addresses ['127.0.0.1', '192.168.68.83'] 2
Feb 04 18:03:00 mastcompass pypilot[2271]: zeroconf exception:
Feb 04 18:03:00 mastcompass pypilot[2271]: e is {'127.0.0.1': ServiceInfo(type='_pypilot._tcp.local.', name='pypilot._pypilot._tcp.local.', addresses=[b'\x7f\x00\x00\x01'], port=23322, weight=0, priority=0, server='pypilot._pypilot._tcp.local.', properties={'version': '0.56'}, interface_index=None), '192.168.68.83': ServiceInfo(type='_pypilot._tcp.local.', name='pypilot._pypilot._tcp.local.', addresses=[b'\xc0\xa8DS'], port=23322, weight=0, priority=0, server='pypilot._pypilot._tcp.local.', properties={'version': '0.56'}, interface_index=None)} 192.168.68.83
Also, the uid appears to be correct:
grep signalk pypilot.conf
signalk.period=0.5000
signalk.uid="pypilot-71815478698"
This uid shows up in SK->Security->Devices (I approved the access request).
But Data Browser does not show heading or YPR.
Disregard...the one piece I failed to clean up was signalk-token. Deleting this file after stopping the service, rebooting, and clearing signalk from pypilot.conf allowed me to get a new token and receive data. So either delete this thread, or leave it for the next knucklehead... :-)