jerome
/
EspHoMaTriXv2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Message malformed: Unable to determine action @ data[‘action’][0]

Browse Source
pull/15/head
LuBeDa 3 years ago
parent 9d07ff7083
commit 2301068e22
2 changed files with 32 additions and 25 deletions
Show Stats Download Patch File Download Diff File

4
README.md
Unescape View File

@ -18,9 +18,9 @@ There are some "RGB-matrices" status displays/clocks out there, the commercial o
- [LaMetric](https://lametric.com/en-US/) commercial ~ €199 - [LaMetric](https://lametric.com/en-US/) commercial ~ €199
- [Ulanzi TC001](https://www.aliexpress.com/item/1005005008682055.html) commercial ~ €50 - [Ulanzi TC001](https://www.aliexpress.com/item/1005005008682055.html) commercial ~ €50
- [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) - [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. 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.

53
copy2esphome/EHMTX_easy_state.yaml
Unescape View File

@ -1,29 +1,29 @@
blueprint: blueprint:
name: |- name: |-
ehmtxv2: show state with unit on on 8x32 RGB-display 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 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 domain: automation
input: input:
ehmtx_device: ehmtx_device:
name: which device to display at name: Which EspHoMaTriX-device to display at?
selector: selector:
device: device:
integration: esphome integration: esphome
trigger_sensor: trigger_sensor:
name: which state to show name: Which sensor state to show?
description: This sensor state will be displayed description: This sensor state will be displayed.
selector: selector:
entity: entity:
domain: sensor domain: sensor
multiple: true multiple: true
default_color: default_color:
name: default text color name: Default text color
description: this is the default textcolor for values within the low and the high value description: This is the default text color for values within the low and the high value (90% white)
selector: selector:
color_rgb: color_rgb:
default: [240, 240, 240] default: [240, 240, 240]
lifetime: lifetime:
name: how many minutes is this screen in the loop name: How many minutes is this screen kept in the loop?
selector: selector:
number: number:
min: 1 min: 1
@ -31,7 +31,7 @@ blueprint:
step: 1 step: 1
default: 2 default: 2
screen_time: screen_time:
name: minimum display time per loop in seconds name: Minimum display time of this screen per loop in seconds?
selector: selector:
number: number:
min: 6 min: 6
@ -39,7 +39,8 @@ blueprint:
step: 2 step: 2
default: 12 default: 12
icon_name: 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.
selector: selector:
select: select:
mode: dropdown mode: dropdown
@ -47,22 +48,24 @@ blueprint:
["error","home_assistant","temperature","lightbulb","music","phone","car","sleep8x32",] ["error","home_assistant","temperature","lightbulb","music","phone","car","sleep8x32",]
default: home_assistant default: home_assistant
use_friendly: use_friendly:
name: use the triggers friendly name in display name: Use the triggers friendly name in display?
description: Add the friendly name of the sensor to the state display.
selector: selector:
boolean: boolean:
default: true default: true
default_font: default_font:
name: true uses the default, false the special font name: Use the default or set false to use the special font.
selector: selector:
boolean: boolean:
default: true default: true
use_colors: use_colors:
name: Use colors based on state values name: Use colors based on state values?
description: If false, the default color will be used.
selector: selector:
boolean: boolean:
default: false default: false
low_value: low_value:
name: below this vaule is a special color name: Below this value use "low color".
selector: selector:
number: number:
mode: box mode: box
@ -71,12 +74,12 @@ blueprint:
default: 0 default: 0
low_color: low_color:
name: Low color name: Low color
description: the color for values below the limit description: The color for values below the above limit.
selector: selector:
color_rgb: color_rgb:
default: [40, 240, 40] default: [40, 240, 40]
high_value: high_value:
name: upper limit name: Above this value use the "high Color".
selector: selector:
number: number:
mode: box mode: box
@ -88,8 +91,7 @@ blueprint:
description: Text color for values above the defined value description: Text color for values above the defined value
selector: selector:
color_rgb: color_rgb:
default: [240, 40, 40] default: [240, 40, 40]
variables: variables:
display: !input ehmtx_device display: !input ehmtx_device
@ -98,17 +100,19 @@ variables:
lo_color: !input low_color lo_color: !input low_color
hi_color: !input high_color hi_color: !input high_color
mode: queued
trigger: trigger:
- platform: state - platform: state
entity_id: !input trigger_sensor entity_id: !input trigger_sensor
action: action:
- mode: parallel
- if: - if:
- condition: template - condition: template
value_template: "{{ not use_colors }}" value_template: "{{ not use_colors }}"
then: then:
- service: esphome.{{ device_attr(display, "name") }}_icon_screen - service: |-
esphome.{{ device_attr(display, "name") }}_icon_screen
data: data:
icon_name: !input icon_name icon_name: !input icon_name
screen_time: !input screen_time screen_time: !input screen_time
@ -133,7 +137,8 @@ action:
entity_id: !input trigger_sensor entity_id: !input trigger_sensor
below: !input low_value below: !input low_value
sequence: sequence:
- service: esphome.{{ device_attr(display, "name") }}_icon_screen - service: |-
esphome.{{ device_attr(display, "name") }}_icon_screen
data: data:
icon_name: !input icon_name icon_name: !input icon_name
screen_time: !input screen_time screen_time: !input screen_time
@ -156,7 +161,8 @@ action:
entity_id: !input trigger_sensor entity_id: !input trigger_sensor
above: !input high_value above: !input high_value
sequence: sequence:
- service: esphome.{{ device_attr(display, "name") }}_icon_screen - service: |-
esphome.{{ device_attr(display, "name") }}_icon_screen
data: data:
icon_name: !input icon_name icon_name: !input icon_name
screen_time: !input screen_time screen_time: !input screen_time
@ -175,7 +181,8 @@ action:
b: |- b: |-
{{ hi_color[2] }} {{ hi_color[2] }}
default: default:
- service: esphome.{{ device_attr(display, "name") }}_icon_screen - service: |-
esphome.{{ device_attr(display, "name") }}_icon_screen
data: data:
icon_name: !input icon_name icon_name: !input icon_name
screen_time: !input screen_time screen_time: !input screen_time

Write Preview
Loading…
Cancel
Save