Really bummed we can’t use this in the US right now.
1 Like
Great! Glad you managed to find the issue. Enjoy the console.
1 Like
Hi @germy, you can absolutely use the console in the US right now. The only difference is that you can’t get a forecast. A replacement forecast provider is in the works, but isn’t ready to be released yet.
Got it. I misunderstood and thought it wouldn’t work in the US at all. Awesome news!
I’m trying to get piconsole running on a pi3b. I ran the installation command without any issue when when I try to start the console it hangs up right after
Adding station timezone: America/Phoenix
Fresh raspbian buster burn onto the SD card. Nothing else is running. I’m on my wifi network and I can vnc/ssh into the pi.
EDIT: I have a Tempest module that I am trying to setup with piconsole.
Sorry to hear you are having troubles! Can you let me know your station number and I will investigate further. Also, make sure the you have correctly copied your API keys when they are requested.
Station is 18975. the API key for geonames is my username, correct? The other api key for CheckWX i copy and pasted and made sure that it didn’t have any spaces. I tried via SSH as well as VNC into the pi.
Here is the output:
pi@tempest:~ $ wfpiconsole start
===================================================
Starting wfpiconsole configuration wizard
===================================================
Required fields are marked with an asterix (*)
API keys
---------------------------------
Please enter your GeoNames API Key*: [deleted]
Please enter your UK MetOffice API Key:
Please enter your DarkSky API Key (if you have one):
Please enter your CheckWX API Key*: [deleted]
Adding WeatherFlow API Key: [deleted]
Station and module IDs
---------------------------------
Please enter your Station ID*: 18975
Do you own a TEMPEST module?* [y/n] y
Please enter your TEMPEST module ID*: 64919
Do you own an Indoor AIR module?* [y/n] n
Adding height of TEMPEST module: 1.8288
Adding height of SKY module:
Adding height of outdoor AIR module:
Adding station latitude: 32.35014
Adding station longitude: -111.03194
Adding station elevation: 698.94970703125
Adding station timezone: America/Phoenix
It just hangs up there and never advances. I’ve waited for about an hour on this screen before I get impatient.
I also tried to do an update just in case that would help. Restarted the pi a couple times for various things (last time was to flip the screen 180).
That all sounds right. Thanks for sharing the station number. I’ll have a look and see what I can find. It’s quite late for me, so it’ll probably have to wait until tomorrow. Sorry!
Edit: When you signed up for the Geonames API, did you activate “Free Web Services” by logging into your account?
You can check the Geonames API is working by copying and pasting the link below into your browser (you will need to replace [USER_NAME] with your Geonames username):
It should return something like this:
{"geonames":[{"adminCode1":"AZ","lng":"-111.02565","distance":"0.67821","geonameId":5318331,"toponymName":"Tucson National Estates","countryId":"6252001","fcl":"P","population":0,"countryCode":"US","name":"Tucson National Estates","fclName":"city, village,...","adminCodes1":{"ISO3166_2":"AZ"},"countryName":"United States","fcodeName":"populated place","adminName1":"Arizona","lat":"32.35313","fcode":"PPL"}]}
Well I fee like a dummy now. Fixed the geonames and we are good to go!
Thank you so much! I can’t wait to use this software! I look forward to when you release a forcast api for the states.
1 Like
Got my Tempeat unit today, installed this without a hitch, inatallation was super smooth considering i wasnt 100% sure what I was doing.
Just wantes to say thanks so much, this makes it even better than I hoped. Game changing!
3 Likes
Noticed today that lightning is showing strikes but rain information and strike count information isn’t showing.
Edit: reboot fixed, sort of
Can you share what you are seeing in more detail, or a screenshot if possible? Tempest support in the console is new of course, so there are probably still some bugs that need ironing out. Also can you share your station ID with me so I can investigate in more detail.
If you take a look at the 3 hr vs monthly, its showing more during thr 3 hr vs the monthly, which seems wrong. Before i restarted, those numbers were 0. Rainfall box totals seems to have the same issue.
And noticed military time on certain tiles even though 12 hour is selected.
OK I will have a look into the rain/lightning totals. Can you share your station ID?
Good spot re. 24 vs. 12 hour clock. That setting only applies to the real time clock, not the times of max/min pressure and temperature etc. I will get that fixed up
Sorry, forgot to mention station…
Edit: removed id
Thanks for that. I have found the bug and am fixing it now. This behaviour would only happen with a new station that gets a lot of rain/lightning very soon after the station has been setup. Pretty much exactly like yours!
1 Like
Awesome, thanks so much. So much fun to look at!
I had a few more questions, too, if you don’t mind:
Can I ask what the “Feeling hot” data comes from regarding the Temperature (currently only showing outdoor). Im guessing high humidity?
And the sunrise sunset says estimated time until sunset. Why is considered estimated?
Not at all!
This comes from the “Feels Like” temperature, which is calculated from either the Wind Chill (if it is cold and windy), or the Heat Index (if it is hot and humid). If it is neither, that the “Feels Like” is just defined as the current temperature. The “Feeling hot” is set by defined temperature cutoffs than can be altered in the settings under the Feels Like panel
Calculating the time of sunset is actually quite complex as it depends on factors such as elevation, atmospheric pressure, and refraction in the atmosphere. I ignore most of these factors as they only make a minute or two difference, and just write “estimated” instead. That being said, in the next version there will be a new solar/uv panel that removes the “estimated” text completely.
1 Like
Seems I lost my indoor air and log gives this, something I broke ??
[-] Websocket connection open
2020-05-23 17:34:47+0200 [-] Exception in thread indoorAir:
2020-05-23 17:34:47+0200 [-] Traceback (most recent call last):
2020-05-23 17:34:47+0200 [-] File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner
2020-05-23 17:34:47+0200 [-] self.run()
2020-05-23 17:34:47+0200 [-] File "/usr/lib/python3.5/threading.py", line 862, in run
2020-05-23 17:34:47+0200 [-] self._target(*self._args, **self._kwargs)
2020-05-23 17:34:47+0200 [-] File "/home/pi/wfpiconsole/lib/websocket.py", line 439, in indoorAir
2020-05-23 17:34:47+0200 [-] Device = wfpiconsole.config['Station']['indoorID']
2020-05-23 17:34:47+0200 [-] File "/usr/lib/python3.5/configparser.py", line 1230, in __getitem__
2020-05-23 17:34:47+0200 [-] raise KeyError(key)
2020-05-23 17:34:47+0200 [-] KeyError: 'indoorID'
2020-05-23 17:34:47+0200 [-]
and spitting this each run
Exception in thread indoorAir:
2020-05-23 17:37:19+0200 [-] Traceback (most recent call last):
2020-05-23 17:37:19+0200 [-] File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner
2020-05-23 17:37:19+0200 [-] self.run()
2020-05-23 17:37:19+0200 [-] File "/usr/lib/python3.5/threading.py", line 862, in run
2020-05-23 17:37:19+0200 [-] self._target(*self._args, **self._kwargs)
2020-05-23 17:37:19+0200 [-] File "/home/pi/wfpiconsole/lib/websocket.py", line 439, in indoorAir
2020-05-23 17:37:19+0200 [-] Device = wfpiconsole.config['Station']['indoorID']
2020-05-23 17:37:19+0200 [-] File "/usr/lib/python3.5/configparser.py", line 1230, in __getitem__
2020-05-23 17:37:19+0200 [-] raise KeyError(key)
2020-05-23 17:37:19+0200 [-] KeyError: 'indoorID'