dependabot-preview[bot] on add-v2-config-file
Upgrade to GitHub-native Depend… (compare)
genebean on 2.1.0
genebean on deepcore2-Suggestions-from-Peter
genebean on master
Correct version file (compare)
genebean on release
genebean on master
Release 2.1.0 Merge pull request #77 from gen… (compare)
genebean on release
Release 2.1.0 (compare)
genebean on master
Finalize enabling 24h time @de… (compare)
genebean on master
Update weather.py Merge pull request #1 from deep… Suggestions from Peter and 1 more (compare)
genebean on deepcore2-Suggestions-from-Peter
Update weather.py Merge pull request #1 from deep… Suggestions from Peter and 2 more (compare)
genebean on 2.0.1
genebean on 2.0.1
genebean on master
Documentation / PyPI updates Merge pull request #75 from gen… (compare)
genebean on 2.0.1
Documentation / PyPI updates (compare)
genebean on 2.0.0
genebean on release
genebean on master
Release 2.0.0 Merge pull request #74 from gen… (compare)
genebean on release
Release 2.0.0 (compare)
genebean on upgrade_script
genebean on master
Updated migration script to mat… Merge pull request #73 from gen… (compare)
Well. Some good news... I realised I probably was running on a lite raspbian install... I made a fresh, full install and got things working. The screen still looks a bit strange. The menu bar stays visible, pushing the weather off screen. Als wind writes just over the weather and is formatted for a bigger screen...
I fixed this for myself by enabling auto-hide of the panel. And I also had to turn off the wind info, since I don't have stations for my region. But the dpi of the 3.5 "display is really too small for this project.
But the dpi of the 3.5 "display is really too small for this project.
That's where I must disagree... These project are extremely suitable for the smaller screens in my opinion! I don't want my hous littered with relative big screens displaying stuff :) But like I said, just my opninion. This one works fine by now :)
I think it will be cool and interesting.
Hi all! I’m preparing for the next phase of PiWeatherRock which includes both a new weather provider and a simpler installation method. To that end, what do you all think about the app being packaged as a Flatpak?
I think it will be cool and interesting.
Thomas Klein: honestly, I’ve never setup the physical buttons, sorry!
Regarding the info screen, you can change the timings from the advanced view of the web based config page that’s at http://<host name>:8888
To quote what I posted to GitHub:
Today I got a normalized data structure created that contains all the bits of the response from Darksky's api that are used in the various bits of my code. The new structure is a dictionary (a hash) with predictable keys. The values are filled in with the data returned from Darksky. The next step is to put this new data structure to use in the existing code. Once that's complete, I'll extract the Darksky bits into a data provider module that simply takes a configuration object or file as input and returns this new data structure. Doing so will mean that any module that can read things such as api keys from the config and returns a dictionary with the needed keys can be used by the core program. This not only lets us create a ClimaCell / tomorrow.io module, but also modules for any other desired data source. That data source could be something region specific to a user or could be one that reads from MQTT. The MQTT angle serves two purposes:
In case you haven't guessed, I'm very interested in scenario 2 above. Don't worry though, I am still going to facilitate using this without Home Assistant.