Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Apr 29 2021 20:58

    dependabot-preview[bot] on add-v2-config-file

    Upgrade to GitHub-native Depend… (compare)

  • May 14 2020 01:16

    genebean on 2.1.0

    (compare)

  • May 14 2020 01:16

    genebean on deepcore2-Suggestions-from-Peter

    (compare)

  • May 14 2020 00:00

    genebean on master

    Correct version file (compare)

  • May 13 2020 23:58

    genebean on release

    (compare)

  • May 13 2020 23:58

    genebean on master

    Release 2.1.0 Merge pull request #77 from gen… (compare)

  • May 13 2020 23:58

    genebean on release

    Release 2.1.0 (compare)

  • May 13 2020 23:57

    genebean on master

    Finalize enabling 24h time @de… (compare)

  • May 13 2020 23:55

    genebean on master

    Update weather.py Merge pull request #1 from deep… Suggestions from Peter and 1 more (compare)

  • May 13 2020 23:19

    genebean on deepcore2-Suggestions-from-Peter

    Update weather.py Merge pull request #1 from deep… Suggestions from Peter and 2 more (compare)

  • May 13 2020 03:02

    genebean on 2.0.1

    (compare)

  • May 13 2020 03:02

    genebean on 2.0.1

    (compare)

  • May 13 2020 03:02

    genebean on master

    Documentation / PyPI updates Merge pull request #75 from gen… (compare)

  • May 13 2020 03:01

    genebean on 2.0.1

    Documentation / PyPI updates (compare)

  • May 13 2020 02:58

    genebean on 2.0.0

    (compare)

  • May 13 2020 02:14

    genebean on release

    (compare)

  • May 13 2020 02:14

    genebean on master

    Release 2.0.0 Merge pull request #74 from gen… (compare)

  • May 13 2020 02:13

    genebean on release

    Release 2.0.0 (compare)

  • May 12 2020 01:03

    genebean on upgrade_script

    (compare)

  • May 12 2020 01:03

    genebean on master

    Updated migration script to mat… Merge pull request #73 from gen… (compare)

Peter Hofman
@deepcore2
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...
Peter Hofman
@deepcore2
IMG_20210326_160431_8.jpg
IMG_20210326_160426_4.jpg
IMG_20210326_160436_5.jpg
To add to this... I use the 2.5"tft display
Peter Hofman
@deepcore2
That would be 3.5"
Peter Hofman
@deepcore2
It crashes...
Mar 26 17:44:00 raspberrypi python3[1255]: pygame 1.9.4.post1
Mar 26 17:44:00 raspberrypi python3[1255]: Hello from the pygame community. https://www.pygame.org/contribute.html
Mar 26 17:44:00 raspberrypi python3[1255]: X Display = :0
Mar 26 17:44:00 raspberrypi python3[1255]: Framebuffer Size: 480 x 320
Mar 26 17:44:00 raspberrypi python3[1255]: Traceback (most recent call last):
Mar 26 17:44:00 raspberrypi python3[1255]: File "/home/pi/PiWeatherRockWind/piweatherrock/runner.py", line 213, in check_forecast
Mar 26 17:44:00 raspberrypi python3[1255]: self.my_weather_rock.get_forecast()
Mar 26 17:44:00 raspberrypi python3[1255]: File "/home/pi/PiWeatherRockWind/piweatherrock/weather.py", line 150, in get_forecast
Mar 26 17:44:00 raspberrypi python3[1255]: self.wind = requests.get(url, headers = headers).json()
Mar 26 17:44:00 raspberrypi python3[1255]: File "/usr/lib/python3/dist-packages/requests/models.py", line 897, in json
Mar 26 17:44:00 raspberrypi python3[1255]: return complexjson.loads(self.text, **kwargs)
Mar 26 17:44:00 raspberrypi python3[1255]: File "/usr/lib/python3/dist-packages/simplejson/init.py", line 518, in loads
Mar 26 17:44:00 raspberrypi python3[1255]: return _default_decoder.decode(s)
Mar 26 17:44:00 raspberrypi python3[1255]: File "/usr/lib/python3/dist-packages/simplejson/decoder.py", line 370, in decode
Mar 26 17:44:00 raspberrypi python3[1255]: obj, end = self.raw_decode(s)
Mar 26 17:44:00 raspberrypi python3[1255]: File "/usr/lib/python3/dist-packages/simplejson/decoder.py", line 400, in raw_decode
Mar 26 17:44:00 raspberrypi python3[1255]: return self.scan_once(s, idx=_w(s, idx).end())
Mar 26 17:44:00 raspberrypi python3[1255]: simplejson.errors.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
Mar 26 17:44:00 raspberrypi python3[1255]: During handling of the above exception, another exception occurred:
Mar 26 17:44:00 raspberrypi python3[1255]: Traceback (most recent call last):
Mar 26 17:44:00 raspberrypi python3[1255]: File "/home/pi/PiWeatherRockWind/pwr-ui", line 26, in <module>
Mar 26 17:44:00 raspberrypi python3[1255]: main()
Mar 26 17:44:00 raspberrypi python3[1255]: File "/home/pi/PiWeatherRockWind/pwr-ui", line 22, in main
Mar 26 17:44:00 raspberrypi python3[1255]: runner.main(config)
Mar 26 17:44:00 raspberrypi python3[1255]: File "/home/pi/PiWeatherRockWind/piweatherrock/runner.py", line 81, in main
Mar 26 17:44:00 raspberrypi python3[1255]: self.screen_switcher()
Mar 26 17:44:00 raspberrypi python3[1255]: File "/home/pi/PiWeatherRockWind/piweatherrock/runner.py", line 186, in screen_switcher
Mar 26 17:44:00 raspberrypi python3[1255]: self.check_forecast()
Mar 26 17:44:00 raspberrypi python3[1255]: File "/home/pi/PiWeatherRockWind/piweatherrock/runner.py", line 216, in check_forecast
Mar 26 17:44:00 raspberrypi python3[1255]: self.my_weather_rock.log.exception(
Mar 26 17:44:00 raspberrypi python3[1255]: AttributeError: 'Weather' object has no attribute 'log'
Mar 26 17:44:01 raspberrypi systemd[1]: PiWeatherRock.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:44:01 raspberrypi systemd[1]: PiWeatherRock.service: Failed with result 'exit-code'.
Mar 26 17:44:06 raspberrypi systemd[1]: PiWeatherRock.service: Service RestartSec=5s expired, scheduling restart.
Peter Hofman
@deepcore2
The boolean 12hour_disp does not do anything. I have 24 hour whatever I set it. I want 24hr, so that is not the problem, but the switch should work.
dronix27
@dronix27

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.

image.png
dronix27
@dronix27
image.png
ciprian288
@ciprian288
small update: I added icons for low resolutions and time repair for 12 hours https://github.com/ciprian288/PiWeatherRock-Windguru-Holfuy
Peter Hofman
@deepcore2
Will seek for the auto hide. In general I never use GUI's on a pi :) But things start to look perfect...
IMG_20210327_110931_2.jpg
IMG_20210327_110935_8.jpg
IMG_20210327_110941_6.jpg
I hope the hide will move the display up for the - now - missing pixels.
Peter Hofman
@deepcore2
To have it gone all the time:
sudo vi /etc/xdg/lxsession/LXDE-pi/autostart
Comment out:
@lxpanel --profile LXDE-pi
IMG_20210327_112015_7.jpg
IMG_20210327_112021_2.jpg
IMG_20210327_112026_3.jpg
Peter Hofman
@deepcore2

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 :)

strommsarnac
@strommsarnac
I'm trying to install PiWeatherRock from Win10x64, using elevated PS and followed the steps on the install page. I'm getting the error code Could not find a task named "piweatherrock::pisetup". I see where Marcel got it last year too, but it looks like his solution was to use Ubuntu instead of Win10. Is there an updated Win10 method I'm missing?
Peter Hofman
@deepcore2
I try to get info on station 56 on windguru, but that crashes the software??? 1050 works fine...
ciprian288
@ciprian288
on your windguru favorite station link it must contain 'station' like this https://www.windguru.cz/station/XXXX
ciprian288
@ciprian288
wind data is taken from real time stations not from forcast stations
Peter Hofman
@deepcore2
Every day you learn something. I just copied the final digits without "seeing" the url difference. Thanks!
jnmmoore
@jnmmoore
How do I uninstall this from my Pi?
mbaranak
@mbaranak
I apologize in advance for what is probably a stupid question but... I'm a newbie. I've got everything installed on my pi via windows and I have the http://mylittlepi.local:8888/ page running. However, I have no idea what it wants for an API Key or how I get it. Can anyone offer some advice?
1 reply
mbaranak
@mbaranak
Hmmm. I figured out where to get the API but I have a feeling this project is DOA
1 reply
genebean
@genebean:technicalissues.us
[m]
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?
dronix27
@dronix27

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.

Peter Hofman
@deepcore2
It would be great. I am not bale to havea working version a while :(
5 replies
genebean
@genebean:technicalissues.us
[m]
https://piweatherrock.technicalissues.us/docs/ should have what you need. Let me know if you have issues though
genebean
@genebean:technicalissues.us
[m]
BTW, Matrix clients such as FkuffyChat can be used and are way better than the Gitter client:
https://matrix.to/#/#PiWeatherRock_community:gitter.im
Thomas Klein
@dodas2277:matrix.org
[m]
Hello, I have a Raspberry Pi Model B Rev 2p. This has 3 buttons that are not programmed. Is there a solution here to assign the 3 screens (daily forecast, hourly, forecast info screen) to each of them. The screens are currently jumping back and forth on a timed basis. Thanks in advance. Thomas
genebean
@genebean:technicalissues.us
[m]
Hi Thomas Klein! I think you should be able to assign the keyboard shortcut for each screen to a button.
mbaranak
@mbaranak
Hi Gene. I had PiWeatherRock installed years ago and loved it. I can find no equal. But I'm not a programmer and can get lost. I tried to install this again last fall but couldn't get a working API. Is there one now? Are the installation instructions in the document current? Either way, thanks for doing this in the first place. It really rocks. It rocks..... It.... I guess that was a Dad joke....
genebean
@genebean:technicalissues.us
[m]
mbaranak (mbaranak): glad you liked it! If you still have your old api key then you can reinstall and still use it. If not then, unfortunately, it does work right now because new keys are not offered by darksky. I do have a plan for migrating the program to a new weather provider, I just haven’t gotten to it. Procrastination keeps getting in the way.
Thomas Klein
@dodas2277:matrix.org
[m]
Hi Gene, unfortunately I haven't been able to control the GPIOs (12, 16 and 18) yet. Do I have to define the GPIOs in config.py or in config.txt? Does anyone know? So in the way dtoverlay gpio-shutdown gpio_pin=12,active_low=1 and then in weather.py with if MODE == 'd' or GPIO.event_detected(12)? Thanks in advance for your answer.
Thomas Klein
@dodas2277:matrix.org
[m]
Hi, it takes much longer for the info screen to appear for me than switching between daily and hourly. How can I set the same time for all screen changes? Thanks!
genebean
@genebean:technicalissues.us
[m]

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

Thomas Klein
@dodas2277:matrix.org
[m]
Hello Gene, OK, I'll try the web based config page. Thank you for the fast answer!
genebean
@genebean:technicalissues.us
[m]
My pleasure Thomas Klein!
genebean
@genebean:technicalissues.us
[m]
I thought I’d also share here that I’ve finally resumed working on this. I’m posting updates to genebean/PiWeatherRock#48 as I go
mbaranak
@mbaranak
I'm excited to hear that. I just tried DAKboard last weekend and was NOT impressed.
genebean
@genebean:technicalissues.us
[m]
What turned you off to it?
mbaranak
@mbaranak
Hard to read. Not focused on weather. Honestly, I've never seen any layout that is as simple and effective as yours by a WIDE margin. Plus they wanted you to pay for it.
genebean
@genebean:technicalissues.us
[m]
Ahh, gotcha. Thanks for the complement too.
genebean
@genebean:technicalissues.us
[m]

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:

  1. An instance of this program could read from an api and populate topics in MQTT. Additional instances of this program spread around your house could then read from MQTT without worry of hitting the api's rate limits.
  2. Home Assistant could be configured to query an api for weather data, be it from tomorrow.io or a personal weather station, or both. It could then publish those readings to MQTT via the MQTT Statestream integration. This program could then utilize what's been published locally by Home Assistant without also needing to talk to the same source(s).

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.