e-Paper VS epaper-dashboard

I had some issues with the Waveshare method under the "C" heading, but was able to get the "Python" set of instructions to work properly and run the test on my display. If you really do have a G-variant display, then the line "python3 epd_2in13g_test.py" in the last set of instructions should run a full cycle on your display cleanly (real-time clock counting for about 10 seconds at the end) before clearing and giving you command of the terminal again. If the test hangs at any point, its not the right test for your display and you will probably have to go through the rest of the [Github tests](https://github.com/waveshareteam/e-Paper/tree/master/RaspberryPi_JetsonNano/python/examples) until you find the most current one that works.

I ported the Waveshare V3 Python code to Rust. This had a similar outcome, perpetually waiting for the busy pin. The only thing that worked was clearing the display (filling the memory with 0x00/FF): it was blinking a few times in the init() - clear() - sleep() loop. Pixels have never become black/white, though.

Then demo for your eink display from waveshare GitHub and get that working first, any issues and we’ll try to help you troubleshoot.

Following Waveshare's Wiki, I think this is their Python driver/test code for the Raspberry Pi: https://github.com/waveshare/e-Paper/blob/master/RaspberryPi_JetsonNano/python/lib/waveshare_epd/epd3in52.py

I’d follow up on this path, it sounds like even their code may have issues with it: https://github.com/waveshare/e-Paper/issues/15

I ended up including their shared library and using their python API to control the screen, as found on waveshare/e-paper repo

sample code for arduino here - https://github.com/waveshare/e-Paper

Python scripts: these scripts actually retrieve the data and print it on the display. I heavily relied on the existing Waveshare Python libraries to figure out how to print text/images on the screen. The rest is essentially just requests to get data from various APIs (I used Open Weather Map, Pi-Hole, SEPTA, newsapi.org, and Wordnik). I set up cron jobs on the Pi to run the normal refresh script every half hour and to start the Node server on startup.

With the internet connection sorted and the repository cloned and tested, it was time to create a minimal viable product. This was more or less taking the example code and extracting the valuable bits, giving it a smaller footprint and easier to navigate layout. This simpler version has been tagged for your viewing pleasure.