Texting Your Name

In 2018, we added the ability for viewers to supply their first name via text message and have it included in the display. The name immediately displays on the small grid under the clock, and then every 10 minutes or so, a 1-minute sequence is displayed where 13 names are included on the 18’ × 8’ grid. Starting in 2019, viewers can see their spot in the queue using the same website used for voting.

How it Works

1. We use the Twilio service to convert inbound text messages to API calls on our web server.
2. Our web server (python fastAPI) accepts the message from Twilio.
3. The Python code validates the name against a whitelist of valid first names provided by the Social Security Administration.
4. If the name isn’t in the whitelist, a text message is sent to the admin and the sender is notified that the name needs review.
5. For valid names, an MQTT message is generated and sent to both the Clock Controller Service and the xLights Render Service where it will be added to a local queues.
6. The Clock Controller runs a custom C++ program that always drains the queue of names before doing any other greetings or graphics.
7. The xLights Render Service is an Ubuntu container running a Python process and xLights for Linux. The name is added to the queue, and the current queue is always published every 2 seconds so that the web server knows the current status.
8. The xLights Render Service takes the next 13 names from the queue and generates a new xLights sequence file (.xsq) by loading a template with %NAME_1%, %NAME_2%, … %NAME_C% placeholders and doing a simple replace. If there aren’t enough names, it selects a few from the database since the sequence is designed to always play 13 names.
9. Once the .xsq file is generated, the Python process runs xLights -r WISH_Names.xsq to generate the .seq file.
10. As soon as the .seq file is generated, the Python process uses the FPP API to upload Wish_names.seq to the FPP Main Player and sends a signal via MQTT to let the webserver and fppscheduler now that the names are ready.
11. The fppscheduler will schedule this as the next song to play using the REST API of the FPP Main Player.
12. While all this is happening, both the Voting Website and Stats server monitor all traffic and provide updates to both the admin and end users.

Admin Interfaces

The web server also contains an admin page that allows us to remotely monitor the queue. We can remove or add new names to the queue (without going through the name validation). Most of the time, we use this to “add” any valid names that were incorrectly blocked by the name filter. Because of this, we have a one-click “add” button displayed against anything that doesn’t pass the filter.

Source Code

• Web Server
• xLights Render
• Stats Tracker