Andrew J.Swan
Andrew J.Swan
> Working as expected, but how to correctly use the trigger? You need to turn on the night mode `night_mode_on`, and this trigger should work.
> But the trigger is not called I checked everything, it should work. What if we add a little feedback? ``` on_night_mode: then: lambda: |- ESP_LOGE("night", "night mode badabum"); id(rgb8x32)->set_clock_color(235,...
I think this switch can be simplified a little and one global variable removed. ``` - platform: template name: "Night mode" id: switch_night_mode icon: mdi:sleep restore_mode: RESTORE_DEFAULT_OFF lambda: |- return...
EspHoMaTriXv2 2023.9.1, ESPHome 2023.12.5 - All work without problem ...
> * EspHoMaTriXv2 version: 2023.7.0 In readme i see: ### 2023.7.0 - removed `set_clock_color` since `clock_screen` and `date_screen` will set color anyway
> since I'm not using other screens at the moment when set_clock_color is called, it deletes the clock screens Its reworked in 2024.1.0 https://github.com/lubeda/EspHoMaTriXv2/blob/8e3f8d73f9196bfe84ba0b8b2dec44b1be4e8765/components/ehmtxv2/EHMTX.cpp#L864-L879
Is this your current TZ, or do you want to register a different one? If different, then according to the documentation: https://esphome.io/components/time/index.html if current: ``` ESPHome tries to automatically infer...
Maybe it makes sense to release 2023.9.1?
@lubeda In my opinion, we have a desynchronization of branches, in `latest` there are some changes, in `2024.6.pre` others, even if you look at the commits, in `latest`, **PR 229,...
IMHO this the most relevant https://github.com/lubeda/EspHoMaTriXv2/tree/2024.12.1