That is a real bummer 
Yeahā¦ I know. I really appreciate the work youāve put into this and this just sucks. Our attorney communicated with theirs and pleaded our case, but we werenāt successful.
2 Likes
Hi @sudeepban / @rohan / any others following this thread,
Per Rohanās most recent comment regarding AccuWeatherās legal dept. not allowing us to make calls to their API via this app, I have opened a PR (based on @sudeepbanās initial work on the āTime & Tempā app referenced in this comment) which introduces other weather APIās that Tidbyt users may select. Just trying to contribute to the community and support Sudeep as I really love the work he began with this app and would love to see it merged into the tidbyt/community repo as an app available to be used on our Tidbyts. 
Let me know your thoughts!
1 Like
This is really great stuff, appreciate the effort and hope youāre able to get it through! If that works for the current conditions app, perhaps a similar approach could be used for the previous AccuWeather 3 day forecast app that was removed.
I am curious about how the quality of the weather data compares from the different sources youāre pulling from. I think OpenWeather was what the stock Tidbyt weather app used which gave some pretty questionable results?
Thanks! You are the visionary and really appreciate your initial effort!! Iām hoping we can get this approved as well.
Unfortunately, I do not think we can make API calls to AccuWeather for any app that we care to submit to the Tidbyt Community. @rohanās response would indicate that this is due to some type of legal reasons, so Iām not sure all of the details there.
I added several other open APIās that have free/paid models, and do not know of how their accuracy compares to AccuWeather. Would be nice to get this merged in so the community (worldwide) can test. The one thing I do know about weather APIās in general are that generally-speaking, one isnāt the ābestā in comparison to others. Iāve found that sometimes, one weather APIās data models will return better/more-realistic data based on certain geographic areas vs. others. So, to me it makes sense to have a revision like this latest PR where we allow the Tidbyt user to choose which weather API they would like to use.
Also, I went ahead and renamed the app to āTime & Weatherā as it seems a bit more fitting to the overall functionality of the app. Cheers!
1 Like
Just had a chance to try out the new Time & Weather app, Iām loving it! Thanks so much for your effort on this @kaffolder7 ! Itās so nice to be able to select from different services and configure different weather attributes to cycle through, really good stuff.
1 Like
Youāre very welcome @sudeepban ! I started with your excellent PR, simply made adjustments, then began working through getting several other weather APIās integrated that should have more-lenient integration requirements. Did some research on which services are most-accurate and also included a couple āhyper-localā ones as well (e.g. Tomorrow.io). Either way, unless any of these weather APIās change their free allotments, I have hardcoded all TTLās to stay within the calls/hr. limits.
Also, I included the free OpenWeather 2.5 API (e.g. the existing/default forecast API). I believe they are retiring this āfreeā API and moving towards their newer One Call API 3.0 sometime this summer. Iāll try to keep an eye on it and remove the deprecated 2.5 API code from the Tidbyt app once this API has been retired. OpenWeather One Call 3.0 still has a free 1,000 daily request limit which should suffice for frequent-enough updates.
Iām considering adding maybe a few more selectable/optional metrics in as well with some of the supporting weather API services, but havenāt gotten there yet. (e.g. pollen count, ozone, wildfire smoke index, etc.)
1 Like