Address in use is pretty clear - you have something else listening. My guess is you didn’t get a complete shutdown of your weewx process before you switched it to shared sockets. That happens occasionally.
Try ‘netstat -lnp | grep 50222’ if you have that installed, or alternately I think it’s ‘ss -tupln’
yep weewx is listening to 50222 but with the driver from Vreihen (before) you could set share and wfpiconsole could also listen to the port. I think python 3 isn’t so nice and/or changed the way how to do this. Might need some code change on Vreihen’s code
Disagree. His driver is rock solid as is weewx and both work fine with python3.
My guess is it’s the piconsole code that isn’t handling shared sockets correctly, considering you have to be running some variant of Peter’s beta (develop branch) code, but I’d have to dig into the code to verify.
I have some time to try to recreate your issue if you can quantify your setup…
What precise os image did you use ? What does /boot/issue.txt contain ?
Which version of weewx and how was it installed (dpkg or pip) ?
Which version of piconsole and how did you install that ?
ok - I can verify that the weewx driver shares the socket ok if you add the switch to your weewx.conf in the correct position…
driver = user.weatherflowudp
share_socket = True
[... and so on...]
The test was to install weewx v5 via pip, which makes running multiple copies easier. I started up one instance and it hears my wfudptools simulator (from the mac mini) just fine. I started a second instance and it ‘also’ listened just fine.
I also started my wfudplistener on the same pi so I had ‘three’ things hearing the UDP broadcasts just fine. Two instances of weewx plus my wfudptools listener.
So I’m pretty convinced weewx is ok. Let me add the piconsole and see what we see…
ok - I can confirm the piconsole is ‘not’ sharing the socket.
I installed the newest console in UDP mode and configured it to match the ST-nnnnnnn my simulator emits. Fired it up and got no data. Shut down the console and see the address in use errors a couple times.
I killed the three things I had listening and sharing the socket (my listener and two weewx instances) and started up ‘only’ the piconsole. It worked fine and displayed the udp my simulator was emitting.
Then I tried to start just my listener on the pi with the piconsole running. Fail - address in use.
So it seems pretty clear to me that the piconsole is ‘not’ opening the listening socket and sharing it so other things can listen to that port too…
[…incidentally - the new console installs ‘very’ quickly on the pi4 using deb-11 raspios so that part works perfectly…]
I’m really not sure I understand what is going on here. I have just retested Bookworm 32 bit on a Pi 3 and I have no problems. I run wfpiconsole start directly from the terminal on the Pi screen and it starts with no issues. I don’t see the Unable to connect to X server issue.