Devlog #2Today was mostly spent fighting the software rather than the hardware. Arduino Lab turned out to be much more challenging than I expected because many of the libraries I needed were originally written for older AVR-based boards. Fortunately, most of them weren’t completely incompatiblethey usually just required a few small changes to the source code. The catch is that Arduino doesn’t let you modify installed libraries directly, so I had to clone the repositories myself, place them in the correct location within the filesystem, and patch them manually before I could even start debugging. It was frustrating at first, but I ended up learning a lot about how the Arduino ecosystem and its library management actually work under the hood.On the UI side, I experimented with the new Bricks implementation and built a dashboard that displays live sensor readings along with other useful information such as notes and system status. The feature I’m happiest with, though, is the display loop I wrote. Instead of showing a single static screen, the interface now automatically cycles through different pages, making much better use of the limited display space without requiring any user interaction. It feels polished, works exactly as I imagined, and is probably my favorite improvement I’ve made to the project so far.