Lint

.github/workflows/validate_clang_format.yml

@@ -0,0 +1,26 @@
+---
+name: Validate C++ (Clang Format)
+
+# yamllint disable-line rule:truthy
+on:
+  push:
+    paths:
+      - '**/*.h'
+      - '**/*.c'
+      - '**/*.cpp'
+  pull_request:
+    paths:
+        - '**/*.h'
+        - '**/*.c'
+        - '**/*.cpp'
+  workflow_dispatch:
+
+jobs:
+  clang-format-checking:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: RafikFarhad/clang-format-github-action@v3
+        with:
+          sources: "esphome/components/nspanel_ha_blueprint/*.h,esphome/components/nspanel_ha_blueprint/*.c,esphome/components/nspanel_ha_blueprint/*.cpp"
+...

ReleaseNotes.md

@@ -76,8 +76,17 @@ or you can use a call to the service `esphome.xxxxx_init_relays` to set it accor
 ## Details of noteworthy changes
 
 ### 1. Transition to ESP-IDF as Default Framework
-As previously announced, we have now transitioned to ESP-IDF as our default framework starting with this release. This change aligns with our commitment to provide a robust and future-ready platform, offering enhanced performance, direct hardware access, and access to the latest developments from Espressif. For those who have prepared for this transition, we look forward to the new possibilities this brings to your projects. For users wishing to continue with the Arduino framework, instructions have been provided on explicitly setting your framework preference. We are here to assist through our community support channels for any questions or assistance needed.
-For the ones previously using the default framework (without any explicity framework especification on your panel's yaml), remember you have to flash your device using a serial cable this time, otherwise you can face some issues.
+As previously announced, we have now transitioned to ESP-IDF as our default framework starting with this release.
+This change aligns with our commitment to provide a robust and future-ready platform, offering enhanced performance, direct hardware access, and access to the latest developments from Espressif.
+
+For those who have prepared for this transition, we look forward to the new possibilities this brings to your projects.
+
+For users wishing to continue with the Arduino framework, instructions have been provided on explicitly setting your framework preference.
+We are here to assist through our community support channels for any questions or assistance needed.
+
+For the ones previously using the default framework (without any explicity framework especification on your panel's yaml), remember you have to flash your device using a serial cable this time,
+otherwise you can face some issues.
+
 More information about this transition can be found in our discussion here: https://github.com/Blackymas/NSPanel_HA_Blueprint/discussions/1756
 
 ### 2. Performance improvements

esphome/nspanel_esphome_core.yaml

@@ -634,7 +634,7 @@ api:
                   id(mui_meridiem)[0] = meridiem[0];
                   id(mui_meridiem)[1] = meridiem[1];
                 }
-  
+
                 // Date/Time colors
                 ESP_LOGV(TAG, "Load date/time colors");
                 id(home_date_color) = esphome::display::ColorUtil::color_to_565(esphome::Color(date_color[0], date_color[1], date_color[2]));
@@ -2308,8 +2308,8 @@ text_sensor:
     name: Version TFT
     platform: nextion
     component_name: boot.tft_version
-    #entity_category: diagnostic
-    #icon: mdi:tag-text-outline
+    # entity_category: diagnostic
+    # icon: mdi:tag-text-outline
     internal: true
     update_interval: never
     on_value: