![\"\"](\"https:\/\/test.itsonix.eu\/wp-content\/uploads\/2026\/05\/iot_quer-745x1024.jpg\" "\\"iot_quer\\"\/")
<\/figure>\n\n\n\nWhat was the starting point for the Circle?<\/strong><\/p>\n\n\n\n Axel:<\/strong> We wanted to do away with the paper lists our employees had been using to sign up for lunch. These lists were used solely for statistical purposes. A digital solution was long overdue.<\/p>\n\n\n\n What has changed since the first version of the project?<\/strong><\/p>\n\n\n\n Axel:<\/strong> The project has been significantly expanded. Originally, the plan was to include only a simple RFID reader without feedback. The device now features a display and a speaker, allowing users to receive immediate feedback. In addition, two buttons enable users to provide verbal feedback on the food, such as its quality or taste.<\/p>\n\n\n\n Another important step was the integration of a rechargeable battery. This makes the system portable, for example, at events or in different office areas.<\/p>\n\n\n\n What was your specific role in the project?<\/strong><\/p>\n\n\n\n Axel:<\/strong> I was responsible for the enclosure and the firmware. The goal was to combine all components into a compact, integrated unit. To achieve this, I redesigned the enclosure using OnShape and customized the firmware based on Tasmota. I focused particularly on controlling the display and speaker.<\/p>\n\n\n\n How did you go about it?<\/strong><\/p>\n\n\n\n Axel:<\/strong> When it came to the firmware, I started out with simple Tasmota rules. That was enough for the basic functionality. When it came to the display, however, the logic quickly became too complex. After a little research, I came across Tasmota\u2019s own scripting language. It\u2019s based on Berry and allows you to create your own mini-apps directly on the device.<\/p>\n\n\n\n One highlight was the automated configuration. When the device is turned on for the first time, the display, speakers, and the entire pin configuration are automatically detected and set up\u2014without any manual setup required.<\/p>\n\n\n\n I used OnShape to design the enclosure. This was new territory for me. I familiarized myself with the software by working through sample models and imported the dimensions of the components to be installed. This resulted in a parametric enclosure that is generated almost entirely programmatically. After the first test prints, we slightly adjusted the shape again to ensure everything was implemented precisely.<\/p>\n\n\n\n Were there any technical challenges involved?<\/strong><\/p>\n\n\n\n Axel:<\/strong> Yes, especially with a display and speakers.<\/p>\n\n\n\n For the speaker, choosing the right PWM channel was crucial. Since Tasmota already uses one channel internally, I had to find an alternative method of control.<\/p>\n\n\n\n As for the display, it was initially unclear which interface would work. Tasmota is currently being switched over to a universal display driver. Using this driver, we were finally able to control the display correctly. The biggest challenge was the pin configuration. The labels on the display did not match those in Tasmota. In the end, the only solution was a process of elimination until everything worked.<\/p>\n\n\n\n Did you ever wonder if the technical approach you chose was the right one?<\/strong><\/p>\n\n\n\n Axel:<\/strong> Not on the hardware side. We made the switch from the ESP8266 to the ESP32 early on, mainly because of the battery support and the larger storage capacity. For development, I used the ESP32-S3 because it offers advanced features and is easier to configure.<\/p>\n\n\n\n On the software side, the simple Tasmota rules would likely have been sufficient for a basic RFID check-in. However, scripting was essential for additional features such as feedback, display, and sound. It enables complex logic, states, and signals without the need to program in C.<\/p>\n\n\n\n However, it's important to be mindful of resource consumption. Animations and time-sensitive processes can overload the system. Nevertheless, scripting has proven to be very reliable. Since the switch, there has been no reason to consider alternatives.<\/p>\n\n\n\n What would you do differently next time?<\/strong><\/p>\n\n\n\n Axel:<\/strong> I would start out using the ESP32-S3. Its resource and pin management is better, and its overall performance is higher. Tasmota's graphics library is very powerful in the embedded field. A low-level approach in C would have significantly increased the effort without providing any noticeable benefits.<\/p>\n\n\n\n Can your experience be applied to client projects?<\/strong><\/p>\n\n\n\n Axel:<\/strong> To some extent, yes. The project was very well received internally because it represents a real improvement. Paper lists are outdated. A simple and intuitive digital solution is much better received.<\/p>\n\n\n\n This knowledge is particularly useful for customer projects when similar hardware or Tasmota is already in use. The most important lesson, however, is that scripting allows complex applications to be implemented quickly\u2014without any in-depth modifications to the operating system. This shortens development cycles and reduces maintenance efforts in the long term.<\/p>\n\n\n\n The Meal Check-In is more than just a digitalization project for everyday work. It is a testing ground for modern embedded development, with a focus on open-source tools, efficient scripting, and user-friendly hardware design. Projects like this foster technological expertise, as well as teamwork and internal innovation.<\/p>\n\n\n\n Experience shows just how effective low-code approaches can be even in embedded environments, especially when flexibility and development time are key factors. This provides a valuable knowledge advantage for similar customer projects.<\/p>\n\n\n\n Related links:<\/strong> Die Digitalisierung allt\u00e4glicher Prozesse ist auch im Unternehmensumfeld ein wichtiger Bestandteil moderner IT-Systeme. Mit dem Projekt \u201eEssens-Check-In\u201c verfolgen wir das Ziel, interne Abl\u00e4ufe effizienter und userzentrierter zu gestalten. Bereits in einem fr\u00fcheren Blogbeitrag haben wir die erste Version des Systems vorgestellt. Dabei handelte es sich um eine einfache RFID-basierte L\u00f6sung zur anonymisierten Erfassung der Teilnahme […]<\/p>\n","protected":false},"author":4,"featured_media":538,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[5],"tags":[],"class_list":["post-534","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-softwareentwicklung"],"acf":[],"yoast_head":"\nConclusion: Internal Projects as a Testing Ground for Smart Embedded Solutions<\/h4>\n\n\n\n
https:\/\/berry-lang.github.io\/<\/a>
https:\/\/tasmota.github.io\/docs\/LVGL\/#using-lvgl<\/a>
https:\/\/github.com\/lvgl\/lvgl<\/a><\/p>","protected":false},"excerpt":{"rendered":"