Each esphome release is packed with new features and suprises (breaking changes), so it is hard to stay up to date for me. Each user can decide which version of esphome he uses. So there is not one combination of esphome, ehmtx and yaml that fits all.
My suggestion is:
Keep esphome up to date with the latest official version!
Which are: Branch 2025.2.0 for esphome 2025.2.0- Branch 2024.12.1 for esphome 2024.12.0-...
For ehmtx use the newest version tag by manually editing the ref tag in the external_componets section in your yaml. Only change your selected ehmtx version if there are compile errors. But expect manual changes to your yaml or even your automations.
The details to each EspHoMaTriX version are on the branch pages
external_components:
- source:
#type: local
#path: EsphoMaTrix/components # e.g. /config/esphome/components
type: git
url: https://github.com/lubeda/EspHoMaTriXv2
ref: 2025.2.0
refresh: 60s
components: [ ehmtxv2 ] With the ulanzi-hardware and esphome 2024.2.0 you have to remove all the rtttl stuff to make things work!!!
The hardware design of the ulanzi isn't perfect. If your ulanzi makes a crazy beeping noise after removinf the rtttl-component you may use this setting to make it silent again.
output:
- platform: gpio
pin:
number: GPIO15
ignore_strapping_warning: true
id: buzzer_pin
See this German tutorial video with information on setting up your display RGB-LED Status Display für Home Assistant mit ESPHome | ESPHoMaTrix.
Another german tutorial video focused on the Ulanzi Smarte Pixel Clock über Home Assistant steuern - Entitäten / Icons und mehr in der Ulanzi
See this nice article about EsphoMaTrix on a Ulanzi TC001 from blakadder.
Short video on Instagram @blak_adder
See these english discussions: Share your projects ESPHOME
It was also mentioned in the blog Building the Open Home and in the home assistant livestream
Or in German: Showroom
THE SOFTWARE IS PROVIDED “AS IS”, use at your own risk!
- blakadder for his contribution (cleanup README.md, fixed sample)
- dbuezas for his fonts infos
- jfurtner for his the on_start_running trigger and a new parameter
- andrew-codechimp for his contribution (display on/off & del_screen "*" & show_clock with 0) and improved blueprint slelection
- jd1 for his contributions
- aptonline for his work on the Ulanzi hardware
- wsbtak for the work on the Ulanzi hardware
- ofirsnb for his contributions
- trip5 for his work on optimized fonts and user support and work on the wiki
- pplucky for his 8x32 GIF animation
- dennisse Auto brightness for the Ulanzi
- hco fixing documentation
- geekofweek fixed sample YAML, cleanup documentation
- joncar fixed scroll small text
- skgsergio who saved this project into 2025
- Everybody who found bugs/issues and reported them!
