flipdot

Go to file

Wiktor Przybylski dbe04fe53e font fix		2024-12-01 22:42:49 +01:00
docs	flipdot photo	2024-11-20 23:09:22 +01:00
.env.dist	mqtt and other stuff to make it similar to departures generator	2024-12-01 22:35:40 +01:00
.gitignore	initial commit	2024-11-20 23:09:14 +01:00
Dockerfile	mqtt and other stuff to make it similar to departures generator	2024-12-01 22:35:40 +01:00
README.md	initial commit	2024-11-20 23:09:14 +01:00
app.py	font fix	2024-12-01 22:42:49 +01:00
apply_env.sh	mqtt and other stuff to make it similar to departures generator	2024-12-01 22:35:40 +01:00
requirements.txt	mqtt and other stuff to make it similar to departures generator	2024-12-01 22:35:40 +01:00

README.md

HSWroFlipdotWeather

Proof of concept of Hackerspace Wrocław shitposting infotainment platform service, that is currently knocking straight to PixelRaspi running on Flipdot Raspi Zero.

Environment Variables

To run this project, you will need to add the following environment variables to your .env file

OPENWEATHER_API_KEY LOCATION_ID LUFTDATEN_CLOSEST_SENSOR

for communicating with openweather and luftdaten

FLIPDOT_API
FLIPDOT_SLOTS - default for HSWro instance is 15

for your PixelRaspi

there is also .env.dist file that you'll find useful that would have all of the above data.

Deployment

To deploy this project after tweaking Dockerfile to fine-tune crontab inside, run

  docker build -t flipdot-weather .

and then

  docker run -d --env-file .env flipdot-weather .

Roadmap

Now it shoots straight to REST api on the flipdot raspi, but plans are to throw the rendered boards into the MQTT stream, and write a interface subscribing on the MQTT stream and shooting requests to the flipdot, and also orchestrator, that would decide what is to be shown. Now it's ready to do a harsh cron driven orchestration