tried both and same result with autostart
Seems to work. I can run the console while simultaneously running my udp listener on the same pi.
@erir - can you recheck your pip3 list ?
It is massive compared to the tiny list you should have.
cd wfpiconsole
source venv/bin/activate
pip3 list
Mine looks like:
pi@pi4jr:~ $ source wfpiconsole/venv/bin/activate
(venv) pi@pi4jr:~ $ pip3 list
Package Version
------------------ ---------
certifi 2023.7.22
cffi 1.16.0
charset-normalizer 3.3.1
cryptography 41.0.4
docutils 0.20.1
ephem 4.1.5
idna 3.4
Kivy 2.2.0
Kivy-Garden 0.1.5
numpy 1.26.0
packaging 23.2
Pillow 10.1.0
pip 23.3.1
pycparser 2.21
Pygments 2.16.1
pyOpenSSL 23.2.0
pytz 2023.3
requests 2.31.0
setuptools 68.2.2
tzlocal 5.1
urllib3 2.0.7
websockets 11.0.3
when adding the source it is shorter
eric@raspberrypi:~ $ cd wfpiconsole/
eric@raspberrypi:~/wfpiconsole $ source venv/bin/activate
(venv) eric@raspberrypi:~/wfpiconsole $ pip3 list
Package Version
------------------ ---------
certifi 2023.7.22
cffi 1.16.0
charset-normalizer 3.3.1
cryptography 41.0.4
docutils 0.20.1
ephem 4.1.5
idna 3.4
Kivy 2.2.0
Kivy-Garden 0.1.5
numpy 1.26.0
packaging 23.2
Pillow 10.1.0
pip 23.3.1
pycparser 2.21
Pygments 2.16.1
pyOpenSSL 23.2.0
pytz 2023.3
requests 2.31.0
setuptools 68.2.2
tzlocal 5.1
urllib3 2.0.7
websockets 11.0.3
(venv) eric@raspberrypi:~/wfpiconsole $
ok - pip list matches. Your dpkg list is slightly different. Looks like you have apache installed and I’m guessing you have weewx there or did at one time. Which version of weewx do you have installed and how did you install it (v4 setup, v5 pip, ?)
v4 and via py installer
I can’t explain any differences in wfpiconsole behavior. The two os are identical except for you installing some weewx prerequisites and me installing ntp and vim. Otherwise package for package a match.
There’s nothing in a pip-installed v4 weewx that will affect whether wfpiconsole works or not.
Only thing I can think of is for me to .tar.gz up my working wfpiconsole tree for you to grab, extract, and try (after dropping in your wfpiconsole.ini file of course). A .tgz is 80 MB if you want to do that.
One more thing more for @peter - the only other thing I can think of is locale settings although I have no idea what that would do to connecting to the wayland server.
can the order of install matter ? I think I installed first weewx and once that was running, wfpiconsole
nope - wfpiconsole runs in its own python virtual environment so it’s totally separate from weewx.
If you’re asking about the shared UDP stuff, Peter has a fix for that in his develop branch that tests ok here. I don’t know what his official procedure for that is but it should ideally be to switch to the develop/beta branch. I did it commandline via ‘cd wfpiconsole ; git checkout develop; git pull’ to catch up my local copy to his develop/beta branch in github.
If you’re asking about the ‘unable to connect to X’ thing, then I have no ideas there unfortunately.
@peter, ok I re install fresh bookworm with only wfpiconsole ? Or would you like I keep it as is for now for the purpose of trying to understand why this happens ?
I’d suggest working one problem at a time…work wfpiconsole first on a clean os and get that working. Once that’s stable we can move on to weewx+UDP.
Can you confirm you are on a pi3 or pi3+ or pi4 ?
That matters. The new os uses Wayland for its windowing subsystem on a pi4 and that is the cause of lots of adventure for some apps. If you’re on a pi3 or pi3+ it uses the old Xwindows stuff which should work more reliably.
(edit - just reflashed a pi3+ with 32bit bookworm, install wfpiconsole, started it in demo mode, and it worked fine the first time here)
I’m at a real loss here. I’m wondering if it is something that is screen specific of maybe hardware revision specific. I don’t know!
Could you try connecting the Pi to a different screen using a different connector (maybe HDMI if you’ve been using a touch screen attached with a ribbon cable?)
This looks like progress? I take it you no are longer getting the X window error on the 27 inch screen?
The blank screen looks like you are using the demo config file? If so, I think I know why it is crashing when you press the menu button.
I have that on the touch screen too and no this is not the demo ini file but a filled one
Ok, so the console starts on both screens, but you don’t see any fields populated?
yep, that’s it, I don’t have the hdmi linked anymore, need it on this mac 
And the console is blank when it is configured to use either UDP or Websocket?
Can you send me a copy of the ini file?
@peter - my pi3+ is working fine on 32bit 10-10-2023 raspios with UDP+websockets vs. my udp simulator. I’m running off the ‘main’ branch and the git logs say it’s commit f3a1a57d. Monitor is a very ancient 24" 1080p using a good HDMI cable if that matters any.
I’m getting very frequent log entries complaining about no data for yesterday etc. but that makes some sense given that it’s a simulated station. I have a station still registered with WF but there is no actual sensor sending them any data. I guess I’d expect the api call to succeed and return either null or zero data, but this is a secondary nit bug for sure…
[WARNING] [request_api ] 2023-11-03 12:26:34 - Today call failed
[WARNING] [request_api ] 2023-11-03 12:26:39 - Yesterday call failed
[WARNING] [request_api ] 2023-11-03 12:26:43 - Month call failed
[WARNING] [request_api ] 2023-11-03 12:26:47 - Year call failed
[WARNING] [request_api ] 2023-11-03 12:27:29 - last_24h call failed