| Ticker for the door | |
|---|---|
 | |
| Participants | |
| Skills | 1337 Skillz, coding |
| Status | Operational |
| Niche | Infra |
| Purpose | Electronics, fun, world domination |
| Tool | No |
| Location | Zaal 2 |
| Cost | |
| Tool category | Electronics |
Ticker for the door Property "Tool Image" (as page type) with input value "File:{{{Picture}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. {{{Picture}}} {{#if:No | [[Tool Owner::{{{ProjectParticipants}}} | }} {{#if:No | [[Tool Cost::{{{Cost}}} | }}
Door ticker is a small 64 by 32 HUB75 led matrix along with a small ESP32 board by Brian Lough. It’s located near the front door of the space to let people know when there are people in the space, or tell them to wait when they ring the door bell.
It can also display a scrolling text via the command !dticker text. Useful for example if you want to tell a PostNL delivery worker to just put the parcel down in front of the space.
The ticker should be able to reconnect and/or restart itself may a wifi disconnect or mqtt sever restart happen. If needed, it can be rebooted via HASS.
It also will change the display brightness depending on the ambient light. So the display remains a bit easier to read when the sun is shining, and not blinding during the night.
Display States
It has the following display states:
Nurds Are In
When the space is open
Een Moment
Displayed when the doorbell is being rang, the choice for Dutch is because the majority of those who would ring our doorbell are Dutch speaking. (Thuisbezorgd etc).
Er is Niemand
Displayed when the doorbell is being rang but the space is closed.
It will also display if it’s failing to connect to MQTT or Wifi.
Extras
It can also display the current time, straight from our own time server. This option is toggable via HASS.
Controlling the options.
Aside from the !dticker command on IRC, it also exposes a few options to HASS. You can access this by devices > mqtt > doorticker.
Of note
Previous the display was only running the !dticker code while being controlled from a python script docker container on Erratic. The script would send the rgb values of the pixels over UDP. This was called Pixelvloed.
With this new iteration, it is all contained on the esp32 itself. Making now full use of both the cores, where core 1 handles all the primary tasks such as mqtt and wifi, while core 2 is used to render the output to the led panel.