Nothing else running on it. Guess I’ll just need to wipe it and reinstall. Thanks for your help!
Anyone else having trouble with this on the latest version? I’ve just built two consoles (and I LOVE the functionality) but the autostart isn’t working. If I reboot I just get the regular Rasbian GUI. I can SSH in, run “wfpiconsole autostart-enable” again and it gives me the green check marks but then it still doesn’t autostart when I reboot.
Is there something I can look for to troubleshoot this?
Hi @seth! Glad you are enjoying the console and sorry you’re having problems with the autostart. It has always been the most flaky part of the programme, but I’ve never been able to work out why. Can you copy and paste the contents of your wfpiconsole.service file here?
Looks like the working directory and user fields are filled in but otherwise the same as the Git version.
[Unit]
Description=WeatherFlow PiConsole
Wants=network-online.target
After=network-online.target
[Service]
ExecStart=/usr/bin/python3 -u main.py
WorkingDirectory=/home/pi/wfpiconsole/
StandardOutput=inherit
StandardError=inherit
Restart=no
User=pi
[Install]
WantedBy=multi-user.target
OK, that’s looking good. Just to confirm:
- Is the console installed in this directory:
/home/pi/wfpiconsole/? - Does the command
which python3return/usr/bin/python3? - Are you using the
piuser? - What Raspberry Pi model and version of Rasbian are you using?
==
Edit: can you also run
systemctl status wfpiconsole.service
and let me know what you see on the screen?
Looks like it is crashing when it tries to run the auto version. Tries to connect to the Weatherflow servers and then exits. My guess is that’s a timing issue with the WiFi link not yet being online when the app starts.
I just plugged in an Ethernet cable and the autostart works gloriously, so that lends credibility to the theory.
Is there a way to hold off on the auto-start until the network is established or to do a retry rather than just fail out of the routine? I can poke around a little but Python is very much not my language of choice.
● wfpiconsole.service - WeatherFlow PiConsole
Loaded: loaded (/etc/systemd/system/wfpiconsole.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2019-09-22 12:06:21 EDT; 4h 29min ago
Process: 421 ExecStart=/usr/bin/python3 -u main.py (code=exited, status=1/FAILURE)
Main PID: 421 (code=exited, status=1/FAILURE)
Sep 22 12:06:20 wxSeth python3[421]: 2019-09-22 12:06:20-0400 [-] return session.request(method=method, url=url, **kwargs)
Sep 22 12:06:20 wxSeth python3[421]: 2019-09-22 12:06:20-0400 [-] File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533, in request
Sep 22 12:06:20 wxSeth python3[421]: 2019-09-22 12:06:20-0400 [-] resp = self.send(prep, **send_kwargs)
Sep 22 12:06:20 wxSeth python3[421]: 2019-09-22 12:06:20-0400 [-] File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646, in send
Sep 22 12:06:20 wxSeth python3[421]: 2019-09-22 12:06:20-0400 [-] r = adapter.send(request, **kwargs)
Sep 22 12:06:20 wxSeth python3[421]: 2019-09-22 12:06:20-0400 [-] File "/usr/lib/python3/dist-packages/requests/adapters.py", line 516, in send
Sep 22 12:06:20 wxSeth python3[421]: 2019-09-22 12:06:20-0400 [-] raise ConnectionError(e, request=request)
Sep 22 12:06:20 wxSeth python3[421]: 2019-09-22 12:06:20-0400 [-] requests.exceptions.ConnectionError: HTTPSConnectionPool(host='swd.weatherflow.com', port=443): Max retries
Sep 22 12:06:21 wxSeth systemd[1]: wfpiconsole.service: Main process exited, code=exited, status=1/FAILURE
Sep 22 12:06:21 wxSeth systemd[1]: wfpiconsole.service: Failed with result 'exit-code'.
~
OK that makes sense. Once you are certain the WiFi is up and running, can you try running the command sudo systemctl start wfpiconsole.service and let me know if it starts? If the WiFi is the only problem then that should work. If it doesn’t start, run systemctl status wfpiconsole.service again and let me know the output.
Also, can you let me know your raspberry pi version?
It starts up fine manually once the wifi is established. And there’s a bit of flexibility as one of our two has auto-started now with the connection coming online faster than the other (closer to the router, I suppose??) but the other still not.
The Pi is a 3 B+ running v10 of the software (cat/etc/os-release) and kernel 4.19.66-v7+ #1253 (uname -a).
Loving the concept and will be heading to the store for another Pi box this weekend. (I have 3, but they’re dedicated to other stuff, good thing they’re cheap!).
Quick question? Have you given any thought to using an adidtional Air unit for the inside temperature/humidity? (or a Sense hat?) WF’s tech people told me the hub can handle up to 16 sensors, but not how to get them to display. I guess I could go buy the ecobee, but I already have a networked thermostat I’m happy with. I haven’t seen (for a very preliminary look) instructions for getting the ecobee pointed at the software, are there instructions?
Thanks!
After update mine will still not auto start. I can run the auto start command and it will start but the the unit is powered off then back on it does not start the pi console also pi console is not showing current wind speed or direction
@seth - Did the update solve your autostart problems? Please do let me know either way.
@clevenger7778 - Sorry you are now having issues with the autostart. Can you reboot your Raspberry Pi, wait a couple of minutes and then run the command systemctl status wfpiconsole.service. Copy and paste the output here. As for the wind speed and direction, please start the console manually with wfpiconsole start and paste the terminal output here. Also, if you could share a picture of the console that would help to pin down what the issue is.
@scott.ferguson - Thanks for checking out the console! I hope you like it. Allowing a second Air unit to to be used as the indoor sensor is definitely on my road map, but it remains quite an edge case at the moment as not many people have two Airs. I will definitely get round to it though! As for Ecobee support, I’m afraid there aren’t any instructions and I don’t plan to support this functionality. I don’t own an Ecobee personally, so it would be impossible to ensure the console remains stable. Another member of the community did integrate Ecobee functionality though, and you can see all the changes that were made to the code here: Add support for integrating with Ecobee Smart Thermostats to obtain indoor temp/humidity by andy-cooper · Pull Request #1 · peted-davis/WeatherFlow_PiConsole · GitHub. Feel free to hack the code as much as you want, but just be aware that updates I push may overwrite your changes if you are not careful. Hope this helps!
I will see if I can get that info tonight. Auto start has never worked for me.
Sorry for the delay in testing…out of the country for a bit.
The updated version still did not work, but I’ve since managed to tinker such that it does. I adjusted
StartLimitInterval=500
StartLimitBurst=100
and also removed
restart=no
from the wfpiconsole.service file. I’m not sure which of those fixed it, but now it does appear to autostart properly.
Re wind speed/direction, that tile in my display flickers somewhat often now when updating the data, with the circle for wind direction occasionally disappearing then coming back. Minor annoyance but not a deal breaker.
No worries - glad you managed to get it to work. I’ll incorporate the changes you made into the next update.
The flickering issues are due to the graphics memory split and can be easily fixed by increasing the amount of memory available to the graphics. See this post for details: Announcements & Updates - #617. You might need to reboot after making the changes.
@peter I don’t use the autostart but there is a setting in the raspbian “raspberry pi configuration” called “network at boot” that has a check box for “wait for network” (you probably already knew this
I really don’t know what it does.Just throwing it out there.
P.S. The install on the pi3 was flawless!
Thanks,
Chuck
Good spot! I knew it was there, but never thought about using it. I think I need to do some experimenting…
Remember we need to see a 10-page report of “what I did on my summer vacation” when you return !
If you use Twitter and you don’t mind a shameless plug, you’ll be able to see what we are doing here: Twitter @HotWaterOnIce ![]()
don’t let them Triple Dog Dare ya !!!
