Darksky API Replacement #185
Comments
|
Some of us are impatient. Any idea how soon, soon is? :-) |
|
The climacell API is different, in that you have to add fields to the query. You also need to pass the cc api key as a http header. The JSON return is pretty easy to parse. |
|
Did you take a look at https://openweathermap.org/? |
|
Open weather is sadly unreliable, with data being up to 2 hrs stale, and sequential polls have regressive time stamps. I kept it in my code, but found that I had to protect from differing time stamps too much. Essentially, the lowest you can poll OW reliably is about once every 10 mins. Even without the timestamp issues, the data is laggy at best. Third column is behind now(): 2020-06-18 08:12:38 PM -0400 info: openweather : 74.44 : 5 : Clouds |
|
I did try to jump onto your fork but im a total amatuer and its melting my brain. I guess I am waiting for this one to update :( |
|
What about weather.gov? https://www.weather.gov/documentation/services-web-api?prevfmt=application%2Fcap%2Bxml&prevopt=id%3DNWS-IDP-PROD-3090928 |
|
OpenWeather API switching guide https://openweathermap.org/darksky-openweather#match |
|
I did do a quick and dirty fix to switch to openweathermap.org in my fork. |
|
I switched to https://github.com/merky1/PiClock because of far more activity. |
|
Keep in mind that my fork forgoes the python aspect, and is managed by a madman... |
|
Has this project died? |
|
If you need an immediate response, my fork is fully operational for the United States. It uses nodejs, so it’s a complete rebuild of the pi, and my forks manager has a bad habit of testing updates in the main branch. Also, my documentation is poor, so it’s really not ready for human use. I have not gotten around to doc‘ing the settings file. That and I’m tied to the US NOAA for forecasting and radar which makes things very US specific. If your brave: https://github.com/merky1/PiClock If you have the PiClock up and running today, I’d say stay until the darksky api turns off. Hopefully there’s enough smart people here to fix that issue. |
|
I vouch for @merky1 repo. I switched and am using it just fine. The settings needs documentation. But everything works. Feel free to contribute, I did a bit. |
|
If you prefer to stick with python my fork implements openweathermap. Just put your owm key on config and follow the standard install directions. |
|
During a discussion in #179, the choice of a new provider was decided. Since then I've been testing that and a few others. That was 2 months ago. My available time has been limited. I've been busy with work, more so than ever before. While that's good news in one respect, my other projects suffer of course. I was also hoping that one of the great followers of this project might take on the changes. This hasn't happened either. Since I have many of these PiClocks running for my friends and family, I will be forced to update it before the API expires in 2021. So, no, its not dead, but progress has been slow. |
|
Good morning Kevin, and the rest of the great peeps following. I wish I could do more, but alas, I am not a developer. I just wanted to state that I appreciate the time that you and others have taken to get the new solution going. |
|
I fully agree. Thanks @n0bel for all your work. |
|
Yes, the PiClock is a fixed asset in my LEGO room ;-) @n0bel I am in no way a solid programmer (well solid al right, but . . . ) Thanks for the so flexible PiClock. |
I Apparently got here a month too late, and didn't get a Dark Sky API key. What's the trick to getting yours running? I like the look of your night mode!. That's basically what I want running 24/7, except using ISO8601 date and time formatting, with seconds, no AM/PM.... |
|
You don't.
…On Sat, Sep 5, 2020, 17:46 captain ***@***.***> wrote:
If your brave: https://github.com/merky1/PiClock
If you have the PiClock up and running today, I’d say stay until the
darksky api turns off. Hopefully there’s enough smart people here to fix
that issue.
I Apparently got here a month too late, and didn't get a Dark Sky API
key. What's the trick to getting yours running?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#185 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGXRTMYVCRGJFWUETQZYEDSEKWR7ANCNFSM4NRYYIAQ>
.
|
|
Get the N4IK fork I created and get an openweathermap key until the main tree is updated correctly.SteveSent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: captain <notifications@github.com> Date: 9/5/20 5:46 PM (GMT-05:00) To: n0bel/PiClock <PiClock@noreply.github.com> Cc: Steve West-Fisher <steve@coastaldatasystems.com>, Comment <comment@noreply.github.com> Subject: Re: [n0bel/PiClock] Darksky API Replacement (#185)
If your brave: https://github.com/merky1/PiClock
If you have the PiClock up and running today, I’d say stay until the darksky api turns off. Hopefully there’s enough smart people here to fix that issue.
I Apparently got here a month too late, and didn't get a Dark Sky API key. What's the trick to getting yours running?
—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
@captain The trick is my fork is not “compatible” with the original, and I have consistently failed to document the settings file, so it takes a higher level of thought right now, being a niche hobby type project. Being stuck at home hasn’t helped. Essentially, wipe your pi with the latest raspian, and the follow the instructions in the install.md. The settings.json is pretty straightforward, but there is no documentation around it. If you want to stay on the python path, then @N4IK is probably the way to go for now. My way leads to ; hades... |
|
Thanks y’all! I got N4IK/PiClock running, figured out how to get weather reports from openweather, but somehow broke python’s ability to use w1thermsensor, which wouldn’tinstall via git but installed fine via apt-get (python -i “import w1thermsensor” claims there is no such file) and I still cannot get dates to display in ISO8601 International Standard format, even when setting locale in Config.py to lt-LT. 😝. I also seem to be missing moon phase information, which is kind of sad. Great work though! Thanks for the ride. I learned a lot. 😄 |
|
Openweathermap doesn't have all the same info as dark sky, I just got what I wanted working, hence my previous "quick and dirty" comment. Glad you got it working!SteveSent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: captain <notifications@github.com> Date: 9/7/20 1:02 AM (GMT-05:00) To: n0bel/PiClock <PiClock@noreply.github.com> Cc: Steve West-Fisher <steve@coastaldatasystems.com>, Mention <mention@noreply.github.com> Subject: Re: [n0bel/PiClock] Darksky API Replacement (#185)
Thanks y’all! I got N4IK/PiClock running, figured out how to get weather reports from openweather, but somehow broke python’s ability to use w1thermsensor, which wouldn’tinstall via git but installed fine via apt-get (python -i “import w1thermsensor” claims there is no such file) and I still cannot get dates to display in ISO8601 International Standard format, even when setting locale in Config.py to lt-LT. 😝. I also seem to be missing moon phase information, which is kind of sad. Great work though! Thanks for the ride. I learned a lot. 😄
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
Does the inside thermometer work on yours N4IK? I’ve determined that in TempServer.py, python3 executes “from w1thermsensor import W1ThermSensor” correctly, but then doesn’t work with some of the other calls, while python works with the other calls, but doesn’t parse “from w1thermsensor import W1ThermSensor” correctly. 🤪 (apparently python3 requires quotations around parentheticals statements to print) I’m really not sure why we are even getting the temperature through this crazy convoluted method of running a Web server just to pass a single number from /sys/bus/w1/devices/[thermometer device number]/w1_slave I have an idea for a cool feature, but I’m barely a hacker, not much of a programmer, so it may take me a while. Here’s my idea, in case anyone else wants to tackle it with me: change the close-up weather window to display video from your front door camera! I was hoping to use the eufy api, but the bastards at Anker locked it down this summer with “privacy enhancements“. I’m Looking into finding a way to access the video stream from a Samsung V6431BN. |
|
I've added some additional info on updating very old Raspbian versions to include dateutil and tzlocal. I have one PiClock that's very old (2015?) that gave me a bit of trouble, so I needed to install those packages somewhat manually. pip was unable to download them from the repository because of old SSL issues. Refer to https://github.com/n0bel/PiClock/blob/master/Documentation/Install.md#updating-on-very-old-raspbian-versions as needed. @GrampDamnpus not sure if you'll need this or not. |
|
I've corrected a problem with Tomorrow.io (wind feels like) |
Thank you so much. Using your and some other help I've been able to get two of my three clocks up and running. The third is much much older, my first one, so this is likely going to help immensely. I'm going to try and get that one going tomorrow. |
|
Hi @SerBrynden you are right - I did not copy the basemap to the radars. In visual studio code I did a config.py file comparison and copied over all the missing code from your dark map config.py and it works! All dark clock with great contrast between map and radar. Thanks for all your help. |
|
Ok ok ok. little slow to the party... So, I updated to latest (ran update script), looked at the code a little and realized that I need a tomorrow.io key, so got one, and created a Going to try some more debugging, but is there anything material I might have missed? I do see this in the logs: |
|
OK, I think I figured it out. My old OWM account only had the version 2.5 service. I added the new 3.0 subscription and it appears to be working now. |
|
@ScottChapman If you saw tio, your version is a couple days old. The latest code has tmapi not tioapi. Similarly it would have handled your old key for owm as well without going to 3.0. |
|
OK, so what do I need exactly? is it either And my old key was definately not working until I added the "One Call by Call" base plan to my subscription. I already had the free plan under professional collections |
|
@ScottChapman You need to pull again. Your version is a day or two older. Other than that you can then choose tmapi or owmapi. |
|
@ScottChapman either API should work. I think the |
|
I actually pulled this morning, after reading some of the commits (which is where I saw the key name, but now see the right name). All set! And thanks! |
|
Cleaned up ApiKeys-example.py to be up to date with the supported keys and key names. Removed 'Sunny' from code 1000 on tomorrow.io code words (its not sunny at night). Removed the entire DarkSky api. |
|
I think at this point I'd better update the main branch PiClock for python3. I'll have to redo install also for newer OS's, as well as add python3 install and dependencies for older OSs in update instructions. |
@n0bel What do you use for code development? For PiClock, I've been using VMware with Ubuntu 22.05 LTS (since it's similar to Raspberry Pi OS Bullseye) and the PyCharm Community IDE. If you've never used PyCharm before, I'd be happy to discuss more. |
|
@SerBrynden For PiClock my dev environment is windows. All my dev tools are set up in a portable fashion, so everything is self contained. I don't usually use the supplied installers for my IDEs and Toolchains, so that I can control where they reside. I have python2 and python3 and many other multiple versions of IDEs and Toolchains residing side by side I use a very very old launcher named PStart, which i use to choose proper environment (paths, sets, etc) I use Notepad++ for everything (with a bunch of handy plugins) This portable style also allows me to have multiple computers syncing my dev environment (I use syncthing for that) so all updates to one simply appear on the other. For final testing I move the code to the target device. With python, it rarely fails on the target device. I have various WSL version 1 environments set up if I really need linux. There of course I use the venerable vi editor. I grew up in unix then windows then linux, so I switch between them easily. |
|
@BertLindeman Pull again. I've just committed changes to correct several function name issues. Config-Example-Berlin works now. |
|
On OpenWeatherMap most of it, but not the day/time in the right forecast squares, but not on tomorrow.io: A small picture on OWM (see left top weather "scattered Cloulds"): On tomorrow.io same as on OWM, but also weather and day/time in the forcast squares is not translated: |
|
working on it. |
|
Commit 8c460ef fixes condition language issue. The change is in Config-Example-Berlin.py which has the language specific table. Still looking at why regional settings aren't working for day names. |
|
Progress. Both OMW and TI weather texts are German.
Thank you, Kevin |
|
I've removed METAR from Config-Berlin-Example. Metar does not currently handle language differences. Current conditions now come from the chosen weather API in that example. I've also corrected two more metric conversion function names. |
So you already fixed: Re pull-ed and all weather texts are OK now for both API's. Just the date/time in the forecasts. (If you want me to open a separate issue . . . ) |
|
@BertLindeman I have no solution for the Day Names being wrong on your PiClock. I've tested two different PiClocks here Raspbian GNU/Linux 8 (jessie), and Raspbian GNU/Linux 7 (wheezy). I had to add de_DE.UTF-8 in raspi-config in each case (It would not work at all if I hadn't) My tests have correct day names in the chosen language. I can only assume its some sort of bug in the particular version of python locale or the OS. |
|
Running on The locales we use needs to be installed, correct. But the date on the top line is translated.... Maybe further tomorrow. Thank you for all the fun you created! |
@n0bel Very nice! You've definitely been doing this longer than I have. ;-) I used PyCharm in an Ubuntu virtual machine when I made the updates to Python 3 and PyQt5. PyCharm would identify all the problems and warnings before running, and suggest fixes. You can also clone repos from GitHub, review changes, and commit them from PyCharm (even sign the commits with a GPG key). It'll also create separate virtual environments for each project. I liked working in Ubuntu because it's close enough to Raspberry Pi OS that I hardly had to install any additional packages other than what's listed in the PiClock install instructions. You can get PyCharm for Windows too. ;-) |
|
This thread has served its purpose. Closing it. I've created a new issue for people arriving here to tell them what to do, and refer to this for background review. #251 |
and others
After a bunch of research carried out by the great people helping with this project, a new provider has been selected, as pointed out in this issue comment:
#179 (comment)
We'll have a new version soon.
The text was updated successfully, but these errors were encountered: