Hi, I installed in my sport club TSV DUWO 08 an infoscreen next to the locker rooms.
The scheduled player is working fine with Raspberry Pi Zero W.
Now I’m trying out the power saver plugin.
I hope I can realize in the future some scheduled pages based on data from the central German football portal fussball.de. I want to show current results and create locker room plans.
I have no clue yet what is the best way.
Big thank you to the developers for the really cool project!
cool project, I started a project “ClubTV”, at the moment my idea is to use Browser-Plugin to show results from fussball.de and other sources, not perfect, but a start.
After month we are really happy. Scheduled Player is working fine with a ticker. Maintenance is really easy from home and power saver plugin is great.
I have started to scrape fussball.de with Python to generate a JSON Data Object. Next step will be a plugin for the schedule player and in the end to use the JSON data. But no clue how to start with a simple plugin. Any ideas?
You can have a look at the scroller folder within the schedule player. Say you wanted to create a “scroller” as its own plugin:
my-scroller.node.png file.node.lua file. As your plugin isn’t running as the main content on the screen and instead is called from the schedule player, this file isn’t really needed, so just leave it empty.What happens next depends on whether or not you know how to use the git version control system. If you do, you can use the git based mechanism to push the source code of your package directory to info-beamer.
If you’ve never used git, it’s probably easier to zip all your package files into a single zip file (make sure you directly zip all files, not the my-scroller folder. So the files must be within the top level of the zip archive). Upload this zip file to a location where it’s publicly accessible (aka “you can download it if you know the url”). Then import your new package in info-beamer like this.
At that point you should have your own package in the list of packages in your account. All that you have to do now is to open your existing schedule player based setup. In the left column, click the Add… button and select your new package. Use the name my-scroller for example. This will add your package to your scheduler player based setup. You can now configure the scroller options as well as add your own version of the scroller to any of the pages you configure within the setup.
If you want to modify what the package does (after all, who needs another scroller), open the tile.lua file. This file gets loaded when playback starts. You can remove most of what you see, as it’s scroller specific. What remains is:
local api, CHILDS, CONTENTS = ...
local M = {}
function M.updated_config_json(config)
-- load and react configuration changes made in the dashboard
end
function M.task(starts, ends, config, x1, y1, x2, y2)
for now in api.frame_between(starts, ends) do
-- draw your content on the scroll between the given coordinates
end
end
return M
Let me know if that helps and of course if you have any questions.
Six years later: an update from TSV DUWO 08
Hi everyone,
In 2020, I shared our infoscreen next to the club’s locker rooms. Integrating fussball.de was still an idea. With help from ChatGPT Plus, it has now become an automated system.
Architecture
Club website + Instagram API + fussball.de → hourly Python jobs on my Mac → info-beamer Hosted → Raspberry Pi and screen.
The setup uses the standard HD Image/Video Player with two playlists:
Club news: five website articles and five Instagram posts, sorted together by publication date, with images, carousel slides and short videos.
Football fixtures: upcoming matches, a youth overview, home/away weekend overviews and individual match graphics.
Matchday features
The graphics include club and joint-team logos, date and kickoff time, venue and address, home/away badges, competition type and current league positions where available. Away-match graphics have Google Maps navigation QR codes.
Changes to kickoff times and venues are highlighted, as are cancellations. Each team has one individual slide for its next selected match. Fixtures remain visible until Monday, so weekend information is still available after the games.
The Power Saver keeps fixed weekday training hours. Weekend hours are calculated automatically from home fixtures at our ground, including dynamically discovered youth teams: one hour before kickoff until one hour after the estimated final whistle, rounded to whole hours.
Only changed media is uploaded, allowing the Raspberry to reuse its cache—important with our weak connection. Old unused assets are cleaned up automatically.
WordPress and Instagram exports
We also built a custom WordPress plugin. It receives authenticated uploads and provides fixed public image URLs and shortcodes for team graphics and overview pages. Two WordPress websites update automatically.
The same data generates separate portrait graphics for Instagram posts and Stories, ready for manual posting.
How ChatGPT Plus helped
ChatGPT Plus helped develop the Python scripts and WordPress plugin, refine layouts, write tests and troubleshoot problems. Being able to describe an issue and improve the implementation step by step made a big difference.
The running system itself uses no AI. Ordinary Python programs handle updates, rendering, uploads, cleanup and local notifications. The Mac generates the content; the Raspberry plays downloaded media and can continue playback temporarily offline.
A special thank you to the info-beamer team for the API, fine-grained access controls through ACLs and policies, detailed documentation, and helpful community support. Scoped API permissions let the automation access only the resources it needs. Combined with reusable packages, playlists and local media caching, this provides a flexible foundation for a small club project that has grown considerably since 2020!
Thanks for the follow-up post 
These are the kind of AI projects I’d love to hear more of: Use the existing features to build a seamless integration. I wonder what would have made the task simpler in your case?
I also like that you use the permission system to restrict the automated access as much as possible. These are the kind of use-cases it was designed for and it’s nice to see if use like that!
