Listen to this article:
Why physical output beats mobile notifications
In the era of overflowing email inboxes and endless push notifications, the biggest challenge is getting information under control. Children, like adults, easily overlook another message on their phone. Physical output on paper, however, eliminates the competition for attention. A printed slip lies on the table, can't be swiped away, and has a concrete beginning and end.
This principle is also confirmed by McKinsey's 10/20/70 rule for AI adoption: only 10% of value comes from the model itself, 20% from data infrastructure, and 70% depends on changes in processes and people's behavior. A button on the kitchen counter and paper output are precisely that 70% solution to the problem "my kids never read the emails I send them".
Hardware: thermal printer, buttons, and a small server
The entire build is surprisingly undemanding. The basic setup for three children costs approximately 150–200 USD (approx. 3,400–4,500 CZK). All components are commonly available in Czech e-shops or can be ordered from EU warehouses without customs complications.
List of components
- Thermal printer with Wi-Fi or Ethernet support and ESC/POS protocol. Models like MUNBYN ITPP905 or devices from Xprinter brand are commonly sold for 50–80 USD (1,100–1,800 CZK). It's important to avoid purely Bluetooth versions, which may lose connection.
- Smart buttons compatible with HomeAssistant. Suitable buttons include Aqara, Shelly Button 1, or Zigbee devices with HomeKit support. A set of three buttons can be purchased for approximately 700–1,000 CZK.
- Thermal paper without BPA, BPS, and phenol content. Standard receipt paper contains bisphenols, which can disrupt the endocrine system during prolonged skin contact. Safe alternatives cost about 30% more, but with daily contact with children, this is a necessity.
- Host server in the form of Raspberry Pi 4, older Mac mini, or local NAS with Docker. Raspberry Pi 4 with 4 GB RAM costs around 1,500 CZK and is more than sufficient for this purpose.
- HomeAssistant as a bridge between buttons and the AI agent. The software is open-source and free.
Agent architecture: parent and its children
The most interesting thing about the entire project is not the printer, but the software architecture. The temptation to write one huge prompt for all children at once doesn't pay off. The result tends to be either too generic or too expensive in tokens. The solution is multi-agent orchestration, which the Stanford AI Index 2026 identified as the most significant architectural shift of this year.
The entire system consists of five specialized agents:
- Parent agent (orchestrator) — collects data from the calendar, weather, and lunch menu. Calls shared sub-agents for jokes and facts. Assembles an information package for each child and triggers the appropriate child agent.
- Sub-agent for jokes — selects age-appropriate jokes from the database and records their ID in a tracking file so they don't repeat for 60–90 days.
- Sub-agent for facts — works the same way as the joke agent, but draws from verified sources of interesting facts.
- Child agent for each child — receives its data package and a system prompt tailored to age and reading level. Generates output formatted directly for the printer.
- Rendering and printing service — converts text to a one-bit image optimized for the thermal printer and sends it to the queue.
This structure allows isolating errors. If the weather API fails, other parts of the brief will still print without problems. Each agent also has access only to the tools it actually needs — the principle of least privilege, which should apply even in home projects.
Connecting buttons, agents, and printer
The entire workflow begins with a button press. HomeAssistant captures the event and sends a webhook POST request to the local server with AI agents. It finds the prepared brief for the given child, converts it to an image, and queues it for printing. A second container then communicates directly with the printer via the ESC/POS protocol.
Why split rendering and printing into two separate containers? If the printer loses connection, the brief remains safely in the queue and doesn't disappear. The printing service can then retry attempts while the rendering part remains untouched.
The total delay from button press to printed paper is 2–5 seconds, if the brief was generated in advance. The printer itself prints at a speed of several lines per second.
Output formatting for 58mm printer
A thermal printer with a width of 58 mm holds approximately 32 characters per line. This limitation paradoxically helps: the agent must concentrate information into a concise, readable form. The output is most often rendered as a small HTML page 384 pixels wide, which headless Chromium converts to an image, and then Floyd-Steinberg dithering is applied for smooth transitions in black and white rendering.
A good prompt for the child agent might look like this: "You are the author of a brief for a seven-year-old child with a reading level of 2nd grade. Each line maximum 32 characters. Sequence: WEATHER (1 line), TODAY (max 3 lines), LUNCH (1 line), JOKE (max 2 lines), FACT (max 2 lines). No emojis, no special characters outside ASCII. Total max 12 lines."
No-code path vs. custom code
Not everyone wants to fine-tune Docker containers. For a quick prototype, Make.com can be used, where you just need to set up a webhook, connect an OpenAI API call, convert the output to an image, and send it to the printer's HTTP endpoint. This path takes one weekend and costs approximately 9 USD per month plus API token costs.
A custom Docker stack requires two to three weekends of work, but offers full control over prompts, offline operation, and lower monthly costs (only API consumption, i.e., approximately 2–5 USD for three children). The recommended approach is to start with Make.com, verify that the family actually uses the system daily, and only then invest time in a custom solution.
What this means for Czech enthusiasts
No component is exotic. Thermal printers with ESC/POS protocol are sold in every major Czech e-shop with IT equipment, Aqara and Shelly products are commonly available from authorized dealers, and HomeAssistant has a strong community even in Czech. The only barrier may be connection to Czech school systems — calendars and lunch menus differ from school to school, but most of them allow export in iCal format or at least RSS.
In terms of costs, this is an accessible project. The total acquisition costs fit under 5,000 CZK and monthly operation costs less than a family Netflix subscription. For parents who want to show children the practical use of AI outside of screens, this is an inspiring entry gate into the world of agent automation.
Conclusion
The daily brief project with a thermal printer proves that the greatest value of AI often does not lie in the model itself, but in how its outputs reach people. A physical trigger, paper output, and multi-agent architecture transform abstract technology into a daily ritual. Whether you're a parent looking for a way to involve children in technology, or a developer exploring the boundaries of agent systems, this build shows that the future of AI can smell like thermal paper.
Can the system work without a thermal printer?
Yes. The printer is the most fun output, but not the only one. The brief can be sent by email, displayed on an e-ink display in the kitchen, published to a family Slack, or converted to a voice message for a smart speaker. The agent architecture remains the same.
How do I prevent the agent from repeating the same joke or fact?
Sub-agents for jokes and facts record each selected entry into a local tracking file along with the date. During the next run, the agent loads this file and filters out items used in the last 60–90 days from the candidate list.
Is it safe to give thermal paper to children?
Only if it is bisphenol-free rolls. Standard receipt paper contains BPA or BPS, which can disrupt hormonal balance during prolonged skin contact. Bisphenol-free alternatives cost approximately 30% more and eliminate the risk.
