- [AWTRIX](https://awtrixdocs.blueforcer.de/#/) (project has been discontinued after more than 4 years now in August 2022)
- [AWTRIX](https://awtrixdocs.blueforcer.de/#/) (project has been discontinued after more than 4 years in August 2022)
- [Pixel It](https://docs.bastelbunker.de/pixelit/) (project is under active development)
- [AWTRIX-Light](https://github.com/Blueforcer/awtrix-light) From the developer of Awtrix, optimized for the Ulanzi TC001 Hardware
- [AWTRIX-Light](https://github.com/Blueforcer/awtrix-light) From the developer of Awtrix, optimized for the Ulanzi TC001 hardware
The solutions have their pros and cons. I tried some and used AwTrix for a long time. But the cons are so big (in my opinion) that I started an esphome.io variant. Targeted to an optimized Home Assistant integration, without paid blueprints and the need of MQTT.
ehmtxv2:show state with unit on on 8x32 RGB-display
description:This blueprint is triggered by a state change. If the state is between certain values it will be displayed with special colors or no state change will be displayed
ehmtxv2:show state with unit on 8x32 RGB-matrix
description:This blueprint is triggered by a state change. If the state is between certain values, it will be displayed with special colors or no state change will be displayed
domain:automation
input:
ehmtx_device:
name:which device to display at
name:Which EspHoMaTriX-device to display at?
selector:
device:
integration:esphome
trigger_sensor:
name:which state to show
description:This sensor state will be displayed
name:Which sensor state to show?
description:This sensor state will be displayed.
selector:
entity:
domain:sensor
multiple:true
default_color:
name:default text color
description:this is the default textcolor for values within the low and the high value
name:Default text color
description:This is the default text color for values within the low and the high value (90% white)
selector:
color_rgb:
default:[240,240,240]
lifetime:
name:how many minutes is this screen in the loop
name:How many minutes is this screen kept in the loop?
selector:
number:
min:1
@ -31,7 +31,7 @@ blueprint:
step:1
default:2
screen_time:
name:minimum display time per loop in seconds
name:Minimum display time of this screen per loop in seconds?
selector:
number:
min:6
@ -39,7 +39,8 @@ blueprint:
step:2
default:12
icon_name:
name:the icon
name:The icon associated to this state screen?
description:If you use additional icons in your YAML, you have to add them to this blueprint.