so ive been messing around with a raspberry pi zero w for the past few weeks trying to get it to automatically pull my wsjtx log and push it to qrz and lotw without me having to babysit it. got it mostly working but the timing is all screwed up, like it'll push the same qso twice sometimes or just miss a batch entirely. im running a little python script that watches the adif file for changes using watchdog library and then parses the new entries. feels like the file locking is the issue but i honestly dont know enough about how wsjtx writes to that file to know if im racing it or what.

also totally unrelated but while i was at it i wired up a little 128x64 oled to show my current band and mode pulled from flrig via xmlrpc. that part actually works great, the pi talks to my linux box over the local network and updates every 5 seconds. whole thing runs off a usb port on the back of my radio desk.

anyway if anyone has done something similar with the log syncing piece id love to know how you handled it. i feel like im reinventing the wheel here

yeah the wsjtx adif file thing is a known pain. the program doesnt close and reopen it cleanly every time, it kind of appends in chunks and if your watchdog fires mid-write you'll get a partial record or duplicate depending on how your parser handles it. what i ended up doing was not watching the file at all — instead i just poll it every 60 seconds and keep a local sqlite db of qso timestamps i've already pushed. anything new in the adif that isnt in my db gets uploaded, nothing gets sent twice. bit of a hack but its been running solid for like 8 months now on a pi 3b i had sitting in a drawer.

the xmlrpc flrig thing is a great idea btw, i never thought to throw an oled on there but now i kind of want to. what display driver you using, the ssd1306 with luma.oled or something else?

I did something similar about a year ago but with an Arduino Mega handling the physical side — buttons, rotary encoder, that kind of stuff — and the Pi doing all the network heavy lifting. They talk over serial and it works pretty well once you sort out the baud rate and get some proper handshaking in there. I tried doing everything on the Pi and the GPIO latency for anything timing sensitive was annoying me, so the hybrid approach made more sense for my use case.

For the log upload problem honestly look at cloudlog or even just the built in LOTW tqsl command line tool, you can script tqsl directly and it handles duplicate checking on its own. Might save you from having to roll all of that yourself. Though if you're doing it as a learning project then obviously carry on, half the fun is figuring it out the hard way.