`Enhancement` Adding Thai localization and fixing broken Thai language.

Aekung commented 1 month ago

Enhancement Summary

Enhancement Adding Thai localization and fixing broken Thai language.

Detailed Description

How can I help in localizing this project for Thai language? I can help translating all the words from English to Thai (one by one) if it means to get my native language supported by the project.
Currently, Thai characters are displayable since it's also included in full charset list. However, it's not being display in a correct way and it's impossible to read. I believe it's due to the letter combination we have in our language and it much like Korean or Chinese where we mix the character up for words with upper and lower letter for vowels and intonations.

Based on the hmi/dev/ui/fonts/CJK/Full Charset.txt, we currently have

"กขฃคฅฆงจฉชซฌญฎฏฐฑฒณดตถทธนบปผฝพฟภมยรฤลฦวศษสหฬอฮฯะัาำ฻฼฽฾฿เแโใไๅๆ๏๐๑๒๓๔๕๖๗๘๙",

which covers all of Thai letters, vowels, intonation marks and numbers. However, when we write word in Thai, we combine these characters in a weird way and not just by ordering the letter from front to back to form a word. This is why the word appear on the display in a weird way when it has an upper or lower letter. For example, "ข ำ" is displayed instead of "ขำ", which is the correct way to write the word.

I think the problem could be both an unsupported Thai character font is being used in the project or the the space between the letter is too much that it causes the letter break.

I tried to look for the font_id or anything that I can use to tweak in the yaml of ESPhome in order to change for to Thai supported Google font but I can't seem to find that in both substitutions: area and anywhere in the esphome/nspanel_esphome_core.yaml. As I'm a newbie in ESPHome, can you please guide me what should I do in order to change the displayed font to the fully supported Thai character from Google Font or how can I make this project 100% compatible with Thai language?

This project is such a great project. Thank you very much for making NSPanel usable for real.

Really looking forward to your reply.

Additional Context

Picture showing how the Thai characters are currently displaying on the NSPanel with the project.

edwardtfn commented 1 month ago

Do you mind splitting those in two different issues (maybe just add a new issue for the display issue)? As those have different complexity levels, it would probably be easier to handle those individually.

edwardtfn commented 1 month ago

For the first request, could you please help the the translation of the following strings (just the part on the right of :)?

        en:     # English
          bytes_per_char: 1
          weekdays:
            mon: Monday
            tue: Tuesday
            wed: Wednesday
            thu: Thursday
            fri: Friday
            sat: Saturday
            sun: Sunday
          weekdays_short:
            mon: Mon
            tue: Tue
            wed: Wed
            thu: Thu
            fri: Fri
            sat: Sat
            sun: Sun
          months:
            jan: January
            feb: February
            mar: March
            apr: April
            may: May
            jun: June
            jul: July
            aug: August
            sep: September
            oct: October
            nov: November
            dec: December
          months_short:
            jan: Jan
            feb: Feb
            mar: Mar
            apr: Apr
            may: May
            jun: Jun
            jul: Jul
            aug: Aug
            sep: Sep
            oct: Oct
            nov: Nov
            dec: Dec
          relative_day:
            today: Today
            tomorrow: Tomorrow
            in_2_days: In 2 days
            in_3_days: In 3 days
            in_4_days: In 4 days
          climate:
            states:
              "on": "on"
              "off": "off"
            heat: heat
          please_confirm: Please confirm
          unavailable: Unavailable
          unknown: Unknown
          no_name: No name
          alarm:
            home: Home
            away: Away
            night: Night
            vacation: Holiday
            bypass: Custom bypass
            disarm: Disarm
          settings:
            reboot: Reboot
            sleep: Sleep mode
            brightness: Brightness
            bright: Bright
            dimming: Dimming
            dim: Dim
          meridiem:
            am: AM
            pm: PM

As a reference, you can take a look at other translations here: https://github.com/Blackymas/NSPanel_HA_Blueprint/blob/e146b1f35dfe38cd8d2da90828695f8a37865b0c/nspanel_blueprint.yaml#L4855

Thanks a lot for your support with this. 😃 I will do my best to have these strings included in the next release.

Aekung commented 1 month ago

Do you mind splitting those in two different issues (maybe just add a new issue for the display issue)? As those have different complexity levels, it would probably be easier to handle those individually.

Will do. Let me finish the translation and I will open another issue for the display.

Thank you.

Aekung commented 1 month ago

For the first request, could you please help the the translation of the following strings (just the part on the right of :)?

I will post the translation for you within an hour.

Thank you.

Aekung commented 1 month ago

        th:     # Thai
          bytes_per_char: 3
          weekdays:
            mon: จันทร์
            tue: อังคาร
            wed: พุธ
            thu: พฤหัสบดี
            fri: ศุกร์
            sat: เสาร์
            sun: อาทิตย์
          weekdays_short:
            mon: จ
            tue: อ
            wed: พ
            thu: พฤ
            fri: ศ
            sat: ส
            sun: อา
          months:
            jan: มกราคม
            feb: กุมภาพันธ์
            mar: มีนาคม
            apr: เมษายน
            may: พฤษภาคม
            jun: มิถุนายน
            jul: กรกฎาคม
            aug: สิงหาคม
            sep: กันยายน
            oct: ตุลาคม
            nov: พฤศจิกายน
            dec: ธันวาคม
          months_short:
            jan: ม.ค.
            feb: ก.พ.
            mar: มี.ค.
            apr: เม.ย.
            may: พ.ค.
            jun: มิ.ย.
            jul: ก.ค.
            aug: ส.ค.
            sep: ก.ย.
            oct: ต.ค.
            nov: พ.ย.
            dec: ธ.ค.
          relative_day:
            today: วันนี้
            tomorrow: พรุ่งนี้
            in_2_days: มะรืนนี้
            in_3_days: ในอีก 3 วัน
            in_4_days: ในอีก 4 วัน
          climate:
            states:
              "on": "เปิด"
              "off": "ปิด"
            heat: ความร้อน
          please_confirm: กรุณายืนยัน
          unavailable: ไม่ปรากฏ
          unknown: ไม่ทราบสถานะ
          no_name: ไม่มีชื่อ
          alarm:
            home: อยู่บ้าน
            away: ไม่อยู่บ้าน
            night: เข้านอน
            vacation: วันหยุด
            bypass: ข้อยกเว้น
            disarm: ปิดระบบ
          settings:
            reboot: รีบูธ
            sleep: โหมดพักหน้าจอ
            brightness: ความสว่าง
            bright: แสง
            dimming: ลดแสง
            dim: หรี่
          meridiem:
            am: AM
            pm: PM

Hope this helps. Really hope to get to see Thai localization in the project soon. Please do not hesitate to let me know if I can still be any help in order to localize this project to Thai language.

Thank you in advance.

edwardtfn commented 1 month ago

This was solved in DEV and will be included in the next release.

Aekung commented 1 month ago

This was solved in DEV and will be included in the next release.

I changed the ref to DEV branch and re-flashed my NSPanel successfully but I couldn't find 'Thai' in the localization of Blueprint Setting Page. Is there anything I must do in order to activate and test these Thai language and make sure everything is working great before the 'main' version update?

Thank you and looking forward to hearing from you.

edwardtfn commented 1 month ago

You have to update the Blueprint also and this is a manual process:

https://github.com/Blackymas/NSPanel_HA_Blueprint/blob/main/docs/different_version.md#for-blueprint-component

TFT also must be update, but this is easy, as you can just press the TFT button to update as you do now.

But please be aware the version on dev is quite broken, so be prepared to return to main after your tests. 😉

Aekung commented 1 month ago

Thanks for the link.

I'll do some testing tonight and will give you feedbacks then swap back to the main branch.

Aekung commented 1 month ago

Tested and the only page I could get to interact with is the front page (Home Screen), I can see the day, which is 'อาทิตย์' just fine but for the date and month, it only shows 20 (which is date) without following by the month. When switching back to English, it shows a complete Sunday, 20/10 though. I think it's because of the max char limit in that text area.

For some reason, clicking on other pages will just return back to Home or not going anywhere. Because of this, I can't check whether other pages on the panel could display everything correctly.

I'm switching back to main now but do let me know if you want me to test anything indev branch.

edwardtfn commented 1 month ago

Ok, I will increase length in some of those common fields...

edwardtfn commented 1 month ago

About not opening the other pages is an issue I'm working on right now and is not related to the language you selected.

edwardtfn commented 1 month ago

I've just tried and the pages are opening... It's slow, but it is opening. Are you sure you cannot open the pages? Could you please share your ESPHome logs?

Aekung commented 1 month ago

I've just tried and the pages are opening... It's slow, but it is opening. Are you sure you cannot open the pages? Could you please share your ESPHome logs?

When I tried navigating to any pages, the screen flickered and came back to home page instantly. However, it did manage to show a climate page in a blink but it was too fast that I couldn't notice anything apart from the temperature bar.

Will re-flash back to dev branch to get the ESPHome logs.

Aekung commented 1 month ago

Re-flashed back to dev branch with dev branch blueprint and latest version of TFT from dev branch. The result is still the same. I can't navigate to any pages as it will just send me back to home in a blink. I also notice the Red HA icon but when I trigger stuff from the physical relay switch (which is bind to turn on/off the fan without wiring anything for real), it could turn on and turn off the fan as normal. I assume that the blueprint links to the Panel just fine (since it also shows Thai language on the date) but I don't know why the HA icon is still showing red.

I should also mention that I'm only using bluetooth proxy addon with the panel as well.

Please kindly find the log enclosed along. I tried to subtract anything that is not relating to the NSPanel so it's easy for you to diagnose.

Thank you.

esphome-nspanel-ha-blueprint.log

edwardtfn commented 1 month ago

Your logs shows the tentative of a service call providing the parameter id, but this parameter is not in use by v4.4.0dev1. Are you sure you are using the latest Blueprint?

Without that, it will flag as missing the blueprint (the reason for the red icon) and this will prevent opening most of the other pages.

Aekung commented 1 month ago

I'm sure it's the right blueprint since I'm using the one from this link

https://github.com/Blackymas/NSPanel_HA_Blueprint/blob/dev/nspanel_blueprint.yaml

If it's not the right one, can you please kindly point me to the right link?

Thank you and looking forward to hearing from you.

Aekung commented 1 month ago

As you can see here, it's all the same version (blueprint included).

Do you think it could be due to other things?

Thank you and looking forward to hearing from you.

Edited: Restarted both HA and NSPanel itself but the problem is still persisted.

edwardtfn commented 1 month ago

Give me a couple of hours and I will change all to dev2, so we make sure you have all the latest...

I will double check the service calls also to make sure it isn't a remaining one using that id as a parameter... We probably have around 150 service calls in the Blueprint. 😩

edwardtfn commented 1 month ago

Please let me know your results with dev2.

Aekung commented 1 month ago

I also see dev3. Should I just jump to dev3 to test or should I test the dev2 for the issue?

Thank you and looking forward to hearing from you.

edwardtfn commented 1 month ago

Yeah, go directly to DEV3. RIght now that is exactly the same as DEV2, but I won't be able to work with DEV2 anymore due to an issue on my laptop.

Aekung commented 1 month ago

I'm putting ref: v4.4.0.dev3 when recompiling on ESPHome but once it's finished, the NSPanel reports ESPHome version 4.3.11 on ESP device page. Should the version bump up to v4.4.0dev3? Have I done something wrong here?

Edited: Re-flashed again and now I'm on v4.4.0dev3. Will report back once I finish flashing the TFT v4.4.0dev3 =)

Aekung commented 1 month ago

It just won't work for me. Still the same. Can't navigate to any pages but home page. HA icon showing red color but it seems to be connected just fine.

I restarted the whole server but it still doesn't help.

edwardtfn commented 1 month ago

Are you still getting the same error messages on Home Assistant logs?

edwardtfn commented 1 month ago

I think I could duplicate the issue you are seeing. I will work in a fix tomorrow morning.

Aekung commented 1 month ago

I think I could duplicate the issue you are seeing. I will work in a fix tomorrow morning.

Sorry for the late reply. I went to bed early yesterday night.

Glad you could replicate the issue. Please let me know if you need me to test anything. I will be more than happy to do so.

edwardtfn commented 1 month ago

Could you please share some logs from ESPHome side when your panel is starting?

Aekung commented 1 month ago

Sorry I wasn't at home yesterday. I will post the ESPHome logs tonight right after I get back home and re-flashed the dev branch.

edwardtfn commented 1 month ago

I've also improved logs on Home Assistant side... 😉

Aekung commented 1 month ago

Here is the ESPHome Log.

5c53de3b_esphome_2024-10-25T06-00-58.775Z.log

As I finished flashing everything to 4.4.0dev4 around 19:40, I don't think I see any useful information in the log at all.

I also enabled the debug log just in case it might help you. I filtered out anything that is not related to the NSPanel but these are only some part of it. I'm not sure if it would be any useful for you. However, I noticed this in the debug log.

2024-10-25 19:56:35.952 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-kitchen @ 10.46.1.55: Sending ExecuteServiceRequest: key: 2759938949
args {
  string_: "bytes_per_char"
}
args {
  int_: 3
}

Does it mean Thai is a 3 bytes per char? Will this be the cause of the problem? Again, this only happen in the dev version and not in a stable release so I think if the bytes per char is the culprit, it should also caused this issue in the stable release as well right?

Here is some part of the ESPHome debug log I extracted.

esphome-debug-log.txt

Hope this helps somehow.

Aekung commented 1 month ago

Wait...

I think, for some reason, I got confused with the log you are referring to. I think I got it now which log you are talking about. I will share the ESPHome device log for you once again later the soonest.

Aekung commented 1 month ago

Here is the log when the panel is starting.

logs_nspanel-kitchen_logs.txt

Please let me know if you want me to get you any other informations.

Aekung commented 1 month ago

Longer version with some errors.

logs_nspanel-kitchen_logs-latest.txt

It seems to be that the boot step stucks at 47% and in pending state. I left it running for longer and it would just not go beyond 47%.

[22:20:20][W][nspanel_ha_blueprint:167]:   Boot steps:  14/30 (47%)
[22:20:20][W][nspanel_ha_blueprint:169]:   State:       Pending

All the errors are spawning up after this point.

edwardtfn commented 1 month ago

Ok. Your boot is completing only 47%. I will look at that when I get home. Probably will need to add more log on the code. 😩

Aekung commented 1 month ago

Thanks. Let me know if I should retest it anytime.

Not sure if any of these errors from the log could give you some clue of what's going on here?

[22:31:05][E][nextion:576]: ERROR: Received numeric return but next in queue "set_component_text" is not a valid sensor type 0
[22:31:35][E][nextion:576]: ERROR: Received numeric return but next in queue "set_component_text" is not a valid sensor type 0
[22:32:05][E][nextion:576]: ERROR: Received numeric return but next in queue "set_component_text" is not a valid sensor type 0

edwardtfn commented 1 month ago

These shows the communication between ESP and Nextion lost it's sync, which indicates the buffer overflow may still happening. 😞

edwardtfn commented 1 month ago

Longer version with some errors.

logs_nspanel-kitchen_logs-latest.txt

It seems to be that the boot step stucks at 47% and in pending state. I left it running for longer and it would just not go beyond 47%.
[22:20:20][W][nspanel_ha_blueprint:167]:   Boot steps:  14/30 (47%)
[22:20:20][W][nspanel_ha_blueprint:169]:   State:       Pending
All the errors are spawning up after this point.

With the latest ESPHome from DEV you should get a number together with this percentage. Could you please share here that number? It is a 32-bit integer indicating the components that completed the boot process. Each bit is one component and the full number will help me identifying which bits are 0 (not completed).

Aekung commented 1 month ago

Noted,

I will pull the log and post it here once I'm back home.

Aekung commented 1 month ago

I can't seem to find that 32bit number but I think what we've got here is pretty much what you want.

[21:03:45][C][script.boot_progress_dump:089]: Boot progress: 43%
[21:03:45][C][script.boot_progress_dump:104]:  - Boot:                 PENDING
[21:03:45][C][script.boot_progress_dump:104]:  - Date & Time:          Completed
[21:03:45][C][script.boot_progress_dump:104]:  - HW Buttons:           Completed
[21:03:45][C][script.boot_progress_dump:104]:  - HW Buzzer:            Completed
[21:03:45][C][script.boot_progress_dump:104]:  - HW Display:           PENDING
[21:03:45][C][script.boot_progress_dump:104]:  - HW Memory:            PENDING
[21:03:45][C][script.boot_progress_dump:104]:  - HW Relays:            PENDING
[21:03:45][C][script.boot_progress_dump:104]:  - HW Temperature:       Completed
[21:03:45][C][script.boot_progress_dump:104]:  - HW Wi-Fi:             PENDING
[21:03:45][C][script.boot_progress_dump:104]:  - Page Alarm:           PENDING
[21:03:45][C][script.boot_progress_dump:104]:  - Page Blank:           PENDING
[21:03:45][C][script.boot_progress_dump:104]:  - Page Boot:            PENDING
[21:03:45][C][script.boot_progress_dump:104]:  - Page Buttons:         PENDING
[21:03:45][C][script.boot_progress_dump:104]:  - Page Climate:         Completed
[21:03:45][C][script.boot_progress_dump:104]:  - Page Confirm:         Completed
[21:03:45][C][script.boot_progress_dump:104]:  - Page Cover:           PENDING
[21:03:45][C][script.boot_progress_dump:104]:  - Page Home:            Completed
[21:03:45][C][script.boot_progress_dump:104]:  - Page Keyboard (Num):  PENDING
[21:03:45][C][script.boot_progress_dump:104]:  - Page Light:           PENDING
[21:03:45][C][script.boot_progress_dump:104]:  - Page Media Player:    PENDING
[21:03:45][C][script.boot_progress_dump:104]:  - Page Notification:    PENDING
[21:03:45][C][script.boot_progress_dump:104]:  - Page QRcode:          Completed
[21:03:45][C][script.boot_progress_dump:104]:  - Page Screensaver:     Completed
[21:03:45][C][script.boot_progress_dump:104]:  - Page Settings:        Completed
[21:03:45][C][script.boot_progress_dump:104]:  - Page Utilities:       Completed
[21:03:45][C][script.boot_progress_dump:104]:  - Page Weather:         Completed
[21:03:45][C][script.boot_progress_dump:104]:  - Versioning:           PENDING
[21:03:45][C][script.boot_progress_dump:104]:  - Base:                 PENDING

Please note that I'm running on your latest dev version of US Landscapte TFT file. No customization has been done to the tft file.

edwardtfn commented 3 weeks ago

Could you please try v4.4.0.dev4 and let me know the results (with logs if still some issue)?

Aekung commented 3 weeks ago

I'm not at home now but I think I can do OTA and paste the ESPHome Device log here for you now, though I won't be able to actually checking the panel whether it's working with any bug. I will be able to do so once I'm back home, which should be by tomorrow.

As of now, give me half and hour and I will come back with ESPHome logs.

Aekung commented 3 weeks ago

INFO ESPHome 2024.10.2
INFO Reading configuration /config/esphome/nspanel-kitchen.yaml...
INFO Updating https://github.com/Blackymas/NSPanel_HA_Blueprint@dev
INFO Updating https://github.com/Blackymas/NSPanel_HA_Blueprint@v4.4.0.dev4
INFO Detected timezone 'Asia/Bangkok'
INFO Starting log output from 10.46.1.41 using esphome API
INFO Successfully connected to nspanel-kitchen @ XX.XX.X.XX in 0.008s
INFO Successful handshake with nspanel-kitchen @ XX.XX.X.XX in 0.116s
[09:43:00][I][app:100]: ESPHome version 2024.10.2 compiled on Oct 30 2024, 09:08:23
[09:43:00][I][app:102]: Project esphome.NSPanel_HA_Blueprint version 4.4.0.dev3
[09:43:00][C][wifi:600]: WiFi:
[09:43:00][C][wifi:428]:   Local MAC: XX:XX:XX:XX:XX:XX
[09:43:00][C][wifi:433]:   SSID: [redacted]
[09:43:00][C][wifi:436]:   IP Address: XX.XX.X.XX 
[09:43:00][C][wifi:440]:   BSSID: [redacted]
[09:43:00][C][wifi:441]:   Hostname: 'nspanel-kitchen'
[09:43:00][C][wifi:443]:   Signal strength: -52 dB ▂▄▆█
[09:43:00][C][wifi:447]:   Channel: 1
[09:43:00][C][wifi:448]:   Subnet: 255.255.255.0
[09:43:00][C][wifi:449]:   Gateway: XX.XX.X.X
[09:43:00][C][wifi:450]:   DNS1: XX.XX.X.X
[09:43:00][C][wifi:451]:   DNS2: 0.0.0.0
[09:43:00][C][logger:185]: Logger:
[09:43:00][C][logger:186]:   Level: DEBUG
[09:43:00][C][logger:188]:   Log Baud Rate: 0
[09:43:00][C][logger:189]:   Hardware UART: UART0
[09:43:00][C][logger:193]:   Level for 'esp32.preferences': INFO
[09:43:00][C][logger:193]:   Level for 'esp-idf': INFO
[09:43:00][C][logger:193]:   Level for 'binary_sensor': INFO
[09:43:00][C][uart.idf:159]: UART Bus 0:
[09:43:00][C][uart.idf:160]:   TX Pin: GPIO16
[09:43:00][C][uart.idf:161]:   RX Pin: GPIO17
[09:43:00][C][uart.idf:163]:   RX Buffer Size: 256
[09:43:00][C][uart.idf:165]:   Baud Rate: 115200 baud
[09:43:00][C][uart.idf:166]:   Data Bits: 8
[09:43:00][C][uart.idf:167]:   Parity: NONE
[09:43:00][C][uart.idf:168]:   Stop bits: 1
[09:43:00][C][template.text_sensor:020]: Template Sensor 'Detailed Entity'
[09:43:00][C][template.text_sensor:020]:   Icon: 'mdi:tablet-dashboard'
[09:43:00][C][template.text_sensor:020]: Template Sensor 'Device Name'
[09:43:00][C][template.text_sensor:020]:   Icon: 'mdi:identifier'
[09:43:00][C][template.text_sensor:020]: Template Sensor 'Notification Label'
[09:43:00][C][template.text_sensor:020]: Template Sensor 'Notification Text'
[09:43:00][C][template.binary_sensor:028]: Template Binary Sensor 'Nextion display'
[09:43:00][C][template.binary_sensor:028]:   Device Class: 'connectivity'
[09:43:00][C][template.number:050]: Template Number 'Buzzer - Gain'
[09:43:00][C][template.number:050]:   Unit of Measurement: '%'
[09:43:00][C][template.number:050]:   Device Class: 'sound_pressure'
[09:43:00][C][template.number:051]:   Optimistic: YES
[09:43:00][C][template.number:052]:   Update Interval: 60.0s
[09:43:00][C][template.number:050]: Template Number 'Brightness - Normal'
[09:43:00][C][template.number:050]:   Unit of Measurement: '%'
[09:43:00][C][template.number:051]:   Optimistic: YES
[09:43:00][C][template.number:052]:   Update Interval: 60.0s
[09:43:00][C][template.number:050]: Template Number 'Brightness - Dimmed'
[09:43:00][C][template.number:050]:   Unit of Measurement: '%'
[09:43:00][C][template.number:051]:   Optimistic: YES
[09:43:00][C][template.number:052]:   Update Interval: 60.0s
[09:43:00][C][template.number:050]: Template Number 'Brightness - Sleep'
[09:43:00][C][template.number:050]:   Unit of Measurement: '%'
[09:43:00][C][template.number:051]:   Optimistic: YES
[09:43:00][C][template.number:052]:   Update Interval: 60.0s
[09:43:00][C][template.number:050]: Template Number 'Timeout - Page'
[09:43:00][C][template.number:050]:   Icon: 'mdi:timer'
[09:43:00][C][template.number:050]:   Unit of Measurement: 's'
[09:43:00][C][template.number:051]:   Optimistic: YES
[09:43:00][C][template.number:052]:   Update Interval: 60.0s
[09:43:00][C][template.number:050]: Template Number 'Timeout - Dimming'
[09:43:00][C][template.number:050]:   Icon: 'mdi:timer'
[09:43:00][C][template.number:050]:   Unit of Measurement: 's'
[09:43:00][C][template.number:051]:   Optimistic: YES
[09:43:00][C][template.number:052]:   Update Interval: 60.0s
[09:43:00][C][template.number:050]: Template Number 'Timeout - Sleep'
[09:43:00][C][template.number:050]:   Icon: 'mdi:timer'
[09:43:00][C][template.number:050]:   Unit of Measurement: 's'
[09:43:00][C][template.number:051]:   Optimistic: YES
[09:43:00][C][template.number:052]:   Update Interval: 60.0s
[09:43:00][C][template.number:050]: Template Number 'Temperature Correction'
[09:43:00][C][template.number:050]:   Unit of Measurement: '°C'
[09:43:00][C][template.number:051]:   Optimistic: YES
[09:43:00][C][template.number:052]:   Update Interval: 60.0s
[09:43:00][C][ledc.output:180]: LEDC Output:
[09:43:00][C][ledc.output:181]:   Pin GPIO21
[09:43:00][C][ledc.output:182]:   LEDC Channel: 0
[09:43:00][C][ledc.output:183]:   PWM Frequency: 1319.0 Hz
[09:43:00][C][ledc.output:184]:   Phase angle: 0.0°
[09:43:00][C][ledc.output:185]:   Bit depth: 15
[09:43:00][C][switch.gpio:068]: GPIO Switch 'Nextion display - Power'
[09:43:00][C][switch.gpio:091]:   Restore Mode: always ON
[09:43:00][C][switch.gpio:031]:   Pin: GPIO4
[09:43:00][C][template.select:065]: Template Select 'Baud rate'
[09:43:00][C][template.select:065]:   Icon: 'mdi:swap-horizontal'
[09:43:00][C][template.select:066]:   Update Interval: 60.0s
[09:43:00][C][template.select:069]:   Optimistic: YES
[09:43:00][C][template.select:070]:   Initial Option: 115200
[09:43:00][C][template.select:071]:   Restore Value: YES
[09:43:00][C][template.select:065]: Template Select 'Wake-up page'
[09:43:00][C][template.select:065]:   Icon: 'mdi:page-next-outline'
[09:43:00][C][template.select:066]:   Update Interval: 60.0s
[09:43:00][C][template.select:069]:   Optimistic: YES
[09:43:00][C][template.select:070]:   Initial Option: home
[09:43:00][C][template.select:071]:   Restore Value: YES
[09:43:00][C][template.select:065]: Template Select 'Update TFT display - Model'
[09:43:00][C][template.select:065]:   Icon: 'mdi:file-sync'
[09:43:00][C][template.select:066]:   Update Interval: 60.0s
[09:43:00][C][template.select:069]:   Optimistic: YES
[09:43:00][C][template.select:070]:   Initial Option: NSPanel EU
[09:43:00][C][template.select:071]:   Restore Value: YES
[09:43:00][C][template.select:065]: Template Select 'Update TFT display - Baud rate'
[09:43:00][C][template.select:065]:   Icon: 'mdi:swap-horizontal'
[09:43:00][C][template.select:066]:   Update Interval: 60.0s
[09:43:00][C][template.select:069]:   Optimistic: YES
[09:43:00][C][template.select:070]:   Initial Option: 921600
[09:43:01][C][template.select:071]:   Restore Value: YES
[09:43:01][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Left Button'
[09:43:01][C][gpio.binary_sensor:016]:   Pin: GPIO14
[09:43:01][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Right Button'
[09:43:01][C][gpio.binary_sensor:016]:   Pin: GPIO27
[09:43:01][C][switch.gpio:068]: GPIO Switch 'Relay 1'
[09:43:01][C][switch.gpio:091]:   Restore Mode: restore defaults to OFF
[09:43:01][C][switch.gpio:031]:   Pin: GPIO22
[09:43:01][C][switch.gpio:068]: GPIO Switch 'Relay 2'
[09:43:01][C][switch.gpio:091]:   Restore Mode: restore defaults to OFF
[09:43:01][C][switch.gpio:031]:   Pin: GPIO19
[09:43:01][C][template.switch:068]: Template Switch 'Touch screen feedback sound'
[09:43:01][C][template.switch:070]:   Icon: 'mdi:volume-high'
[09:43:01][C][template.switch:091]:   Restore Mode: restore defaults to OFF
[09:43:01][C][template.switch:057]:   Optimistic: YES
[09:43:01][C][template.switch:068]: Template Switch 'Wake-up with hardware buttons'
[09:43:01][C][template.switch:091]:   Restore Mode: restore defaults to OFF
[09:43:01][C][template.switch:057]:   Optimistic: YES
[09:43:01][C][template.switch:068]: Template Switch 'Notification unread'
[09:43:01][C][template.switch:091]:   Restore Mode: always OFF
[09:43:01][C][template.switch:057]:   Optimistic: YES
[09:43:01][C][template.switch:068]: Template Switch 'Notification sound'
[09:43:01][C][template.switch:091]:   Restore Mode: restore defaults to OFF
[09:43:01][C][template.switch:057]:   Optimistic: YES
[09:43:01][C][template.switch:068]: Template Switch 'Update TFT automatically'
[09:43:01][C][template.switch:070]:   Icon: 'mdi:file-sync'
[09:43:01][C][template.switch:091]:   Restore Mode: restore defaults to OFF
[09:43:01][C][template.switch:057]:   Optimistic: YES
[09:43:01][C][factory_reset.button:011]: Factory Reset Button 'Factory reset'
[09:43:01][C][factory_reset.button:011]:   Icon: 'mdi:restart-alert'
[09:43:01][C][restart.button:017]: Restart Button 'Restart'
[09:43:01][C][restart.button:017]:   Icon: 'mdi:restart'
[09:43:01][C][homeassistant.time:010]: Home Assistant Time:
[09:43:01][C][homeassistant.time:011]:   Timezone: '<+07>-7'
[09:43:01][C][rtttl:029]: Rtttl
[09:43:02][C][adc:097]: ADC Sensor 'ntc_source'
[09:43:02][C][adc:097]:   Device Class: 'voltage'
[09:43:02][C][adc:097]:   State Class: 'measurement'
[09:43:02][C][adc:097]:   Unit of Measurement: 'V'
[09:43:02][C][adc:097]:   Accuracy Decimals: 2
[09:43:02][C][adc:107]:   Pin: GPIO38
[09:43:02][C][adc:122]:   Attenuation: 12db
[09:43:02][C][adc:141]:   Samples: 4
[09:43:02][C][adc:142]:   Update Interval: 10.0s
[09:43:02][C][psram:020]: PSRAM:
[09:43:02][C][psram:021]:   Available: YES
[09:43:02][C][psram:024]:   Size: 2035 KB
[09:43:02][C][bluetooth_proxy:091]: Bluetooth Proxy:
[09:43:02][C][bluetooth_proxy:092]:   Active: NO
[09:43:02][C][bluetooth_proxy:093]:   Connections: 0
[09:43:02][C][bluetooth_proxy:094]:   Raw advertisements: YES
[09:43:02][C][nextion:138]: Nextion:
[09:43:02][C][nextion:142]:   Device Model:     NX4832F035_011C
[09:43:02][C][nextion:143]:   Firmware Version: 110
[09:43:02][C][nextion:144]:   Serial Number:    118D3401EDDD1E62
[09:43:02][C][nextion:145]:   Flash Size:       16777216
[09:43:02][C][nextion:147]:   Wake On Touch:    YES
[09:43:02][C][nextion:148]:   Exit reparse:     YES
[09:43:02][C][esp32_ble:391]: ESP32 BLE:
[09:43:02][C][esp32_ble:393]:   MAC address: XX:XX:XX:XX:XX:XX
[09:43:02][C][esp32_ble:394]:   IO Capability: none
[09:43:02][C][esp32_ble_tracker:655]: BLE Tracker:
[09:43:02][C][esp32_ble_tracker:656]:   Scan Duration: 300 s
[09:43:02][C][esp32_ble_tracker:657]:   Scan Interval: 320.0 ms
[09:43:02][C][esp32_ble_tracker:658]:   Scan Window: 30.0 ms
[09:43:02][C][esp32_ble_tracker:659]:   Scan Type: ACTIVE
[09:43:02][C][esp32_ble_tracker:660]:   Continuous Scanning: True
[09:43:02][C][mdns:116]: mDNS:
[09:43:02][C][mdns:117]:   Hostname: nspanel-kitchen
[09:43:02][C][esphome.ota:073]: Over-The-Air updates:
[09:43:02][C][esphome.ota:074]:   Address: nspanel-kitchen.local:3232
[09:43:02][C][esphome.ota:075]:   Version: 2
[09:43:02][C][esphome.ota:078]:   Password configured
[09:43:02][C][safe_mode:018]: Safe Mode:
[09:43:02][C][safe_mode:020]:   Boot considered successful after 60 seconds
[09:43:02][C][safe_mode:021]:   Invoke after 3 boot attempts
[09:43:02][C][safe_mode:023]:   Remain in safe mode for 180 seconds
[09:43:02][C][api:140]: API Server:
[09:43:02][C][api:141]:   Address: nspanel-kitchen.local:6053
[09:43:02][C][api:143]:   Using noise encryption: YES
[09:43:02][C][wifi_signal.sensor:010]: WiFi Signal 'RSSI'
[09:43:02][C][wifi_signal.sensor:010]:   Device Class: 'signal_strength'
[09:43:02][C][wifi_signal.sensor:010]:   State Class: 'measurement'
[09:43:02][C][wifi_signal.sensor:010]:   Unit of Measurement: 'dBm'
[09:43:02][C][wifi_signal.sensor:010]:   Accuracy Decimals: 0
[09:43:03][C][wifi_signal.sensor:010]:   Icon: 'mdi:wifi'
[09:43:44][C][script.boot_progress_dump:090]: Boot progress: 50% (868397372)
[09:43:44][C][script.boot_progress_dump:105]:  - Boot:                 PENDING
[09:43:44][C][script.boot_progress_dump:105]:  - Date & Time:          Completed
[09:43:44][C][script.boot_progress_dump:105]:  - HW Buttons:           Completed
[09:43:44][C][script.boot_progress_dump:105]:  - HW Buzzer:            Completed
[09:43:44][C][script.boot_progress_dump:105]:  - HW Display:           Completed
[09:43:44][C][script.boot_progress_dump:105]:  - HW Memory:            PENDING
[09:43:44][C][script.boot_progress_dump:105]:  - HW Relays:            PENDING
[09:43:44][C][script.boot_progress_dump:105]:  - HW Temperature:       Completed
[09:43:44][C][script.boot_progress_dump:105]:  - HW Wi-Fi:             PENDING
[09:43:44][C][script.boot_progress_dump:105]:  - Page Alarm:           PENDING
[09:43:44][C][script.boot_progress_dump:105]:  - Page Blank:           PENDING
[09:43:44][C][script.boot_progress_dump:105]:  - Page Boot:            Completed
[09:43:44][C][script.boot_progress_dump:105]:  - Page Buttons:         PENDING
[09:43:44][C][script.boot_progress_dump:105]:  - Page Climate:         Completed
[09:43:44][C][script.boot_progress_dump:105]:  - Page Confirm:         Completed
[09:43:44][C][script.boot_progress_dump:105]:  - Page Cover:           PENDING
[09:43:44][C][script.boot_progress_dump:105]:  - Page Entities:        Completed
[09:43:44][C][script.boot_progress_dump:105]:  - Page Fan:             PENDING
[09:43:44][C][script.boot_progress_dump:105]:  - Page Home:            Completed
[09:43:44][C][script.boot_progress_dump:105]:  - Page Keyboard (Num):  PENDING
[09:43:44][C][script.boot_progress_dump:105]:  - Page Light:           PENDING
[09:43:44][C][script.boot_progress_dump:105]:  - Page Media Player:    PENDING
[09:43:44][C][script.boot_progress_dump:105]:  - Page Notification:    PENDING
[09:43:44][C][script.boot_progress_dump:105]:  - Page QRcode:          Completed
[09:43:44][C][script.boot_progress_dump:105]:  - Page Screensaver:     Completed
[09:43:44][C][script.boot_progress_dump:105]:  - Page Settings:        Completed
[09:43:44][C][script.boot_progress_dump:105]:  - Page Utilities:       Completed
[09:43:44][C][script.boot_progress_dump:105]:  - Page Weather:         Completed
[09:44:36][I][text_sensor.version_blueprint:112]: Blueprint version: 4.4.0.dev4
[09:44:36][D][script:100]: Script 'send_command' queueing new instance (mode: queued)
[09:44:36][D][script:100]: Script 'send_command' queueing new instance (mode: queued)
[09:44:36][D][script:100]: Script 'send_command' queueing new instance (mode: queued)
[09:44:38][W][nextion:431]: Nextion reported variable name invalid!
[09:44:39][W][nextion:431]: Nextion reported variable name invalid!
[09:46:36][I][text_sensor.version_blueprint:112]: Blueprint version: 4.4.0.dev4
[09:46:36][D][script:100]: Script 'send_command' queueing new instance (mode: queued)
[09:46:36][D][script:100]: Script 'send_command' queueing new instance (mode: queued)
[09:46:36][D][script:100]: Script 'send_command' queueing new instance (mode: queued)
[09:46:38][W][nextion:431]: Nextion reported variable name invalid!
[09:46:46][E][nextion:576]: ERROR: Received numeric return but next in queue "send_command" is not a valid sensor type 0
[09:47:01][D][esp32_ble_tracker:270]: Starting scan...
[09:47:01][E][nextion:576]: ERROR: Received numeric return but next in queue "send_command_printf" is not a valid sensor type 0
[09:47:16][E][nextion:576]: ERROR: Received numeric return but next in queue "set_component_text" is not a valid sensor type 0
[09:47:31][E][nextion:576]: ERROR: Received numeric return but next in queue "send_command_printf" is not a valid sensor type 0
[09:47:46][E][nextion:576]: ERROR: Received numeric return but next in queue "set_component_text" is not a valid sensor type 0
[09:48:01][E][nextion:576]: ERROR: Received numeric return but next in queue "send_command_printf" is not a valid sensor type 0
[09:48:16][E][nextion:576]: ERROR: Received numeric return but next in queue "set_component_text" is not a valid sensor type 0
[09:48:31][E][nextion:576]: ERROR: Received numeric return but next in queue "send_command_printf" is not a valid sensor type 0

Later, it's producing this

[09:50:20][C][nspanel_ha_blueprint:153]: API:           Connected
[09:50:20][C][nspanel_ha_blueprint:161]: ESPHome:
[09:50:20][C][nspanel_ha_blueprint:162]:   Version:     4.4.0.dev3
[09:50:20][C][nspanel_ha_blueprint:163]:   Compiler:    2024.10.2
[09:50:20][C][nspanel_ha_blueprint:168]:   Framework:   ESP-IDF
[09:50:20][C][nspanel_ha_blueprint:173]: Packages:
[09:50:20][C][nspanel_ha_blueprint:175]:   - Core
[09:50:20][C][nspanel_ha_blueprint:181]:   - Bluetooth Proxy
[09:50:20][C][nspanel_ha_blueprint:184]:   - Upload TFT
[09:50:20][C][nspanel_ha_blueprint:205]: Components:
[09:50:20][C][nspanel_ha_blueprint:210]:   - BLE tracker
[09:50:20][C][nspanel_ha_blueprint:213]:   - Bluetooth proxy
[09:50:20][W][nspanel_ha_blueprint:168]:   Boot steps:  15/30 (50% - 868397372)
[09:50:20][W][nspanel_ha_blueprint:170]:   State:       Pending
[09:50:20][C][nspanel_ha_blueprint:171]: Requesting new boot parameters from Blueprint
[09:50:20][D][script:077]: Script 'boot_event' restarting (mode: restart)
[09:50:20][C][nspanel_ha_blueprint:034]: Date & Time:
[09:50:20][C][nspanel_ha_blueprint:035]:  - Time format: %-H.%M
[09:50:20][C][nspanel_ha_blueprint:036]:  - Timezone:    <+07>-7
[09:50:20][C][nspanel_ha_blueprint:360]: UART:
[09:50:20][C][nspanel_ha_blueprint:361]:   Baud rate:   115200 bps
[09:50:20][C][nspanel_ha_blueprint:362]:   Queue size:  0
[09:50:20][C][nspanel_ha_blueprint:366]: Nextion:
[09:50:20][C][nspanel_ha_blueprint:367]:   Queue size:  1
[09:50:20][C][nspanel_ha_blueprint:369]:   Is setup:    True
[09:50:20][C][nspanel_ha_blueprint:376]:   Init:        True
[09:50:20][C][nspanel_ha_blueprint:382]:   TFT:         4.4.0.dev4
[09:50:20][C][nspanel_ha_blueprint:036]:   Free heap:
[09:50:20][C][nspanel_ha_blueprint:040]:     Internal:    63116 bytes (21.4%)
[09:50:20][C][nspanel_ha_blueprint:050]:     PSRAM:     1978091 bytes (94.9%)
[09:50:20][C][nspanel_ha_blueprint:063]: Wi-Fi:         Good (-53 dBm)
[09:50:31][E][nextion:576]: ERROR: Received numeric return but next in queue "send_command_printf" is not a valid sensor type 0
[09:50:46][E][nextion:576]: ERROR: Received numeric return but next in queue "set_component_text" is not a valid sensor type 0
[09:51:01][E][nextion:576]: ERROR: Received numeric return but next in queue "send_command_printf" is not a valid sensor type 0
[09:51:16][E][nextion:576]: ERROR: Received numeric return but next in queue "set_component_text" is not a valid sensor type 0
[09:51:31][E][nextion:576]: ERROR: Received numeric return but next in queue "send_command_printf" is not a valid sensor type 0
[09:51:46][E][nextion:576]: ERROR: Received numeric return but next in queue "set_component_text" is not a valid sensor type 0

It seems like we are getting a bit further now at 50%. Though I'm not sure why the blueprint version is still reporting at dev3 but I've already updated the blueprint to dev4 version and already restarted the automation.

edwardtfn commented 3 weeks ago

Your ESPHome is also reporting v4.4.0.dev3. Re-flashing should fix this issue. ESPHome bootloader keeps 2 copies of the firmware and sometimes it can boot from the partition with the older version. Flashing it again may update the partition with older copy so you will have both updated.

[09:50:20][C][nspanel_ha_blueprint:161]: ESPHome:
[09:50:20][C][nspanel_ha_blueprint:162]:   Version:     4.4.0.dev3

Aekung commented 3 weeks ago

Hi, Sorry for the late reply, I just could go back home to do some more test on it. I did a clean build and now the process seems to be complete at almost 100% (97% so far)

[10:34:01][C][script.boot_progress_dump:087]: Boot progress: 97% (1073741695)
[10:34:01][C][script.boot_progress_dump:102]:  - Boot:                 Completed
[10:34:01][C][script.boot_progress_dump:102]:  - Date & Time:          Completed
[10:34:01][C][script.boot_progress_dump:102]:  - HW Buttons:           Completed
[10:34:01][C][script.boot_progress_dump:102]:  - HW Buzzer:            Completed
[10:34:01][C][script.boot_progress_dump:102]:  - HW Display:           Completed
[10:34:01][C][script.boot_progress_dump:102]:  - HW Memory:            Completed
[10:34:01][C][script.boot_progress_dump:102]:  - HW Relays:            PENDING
[10:34:01][C][script.boot_progress_dump:102]:  - HW Temperature:       Completed
[10:34:02][C][script.boot_progress_dump:102]:  - HW Wi-Fi:             Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Page Alarm:           Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Page Blank:           Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Page Boot:            Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Page Buttons:         Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Page Climate:         Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Page Confirm:         Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Page Cover:           Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Page Entities:        Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Page Fan:             Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Page Home:            Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Page Keyboard (Num):  Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Page Light:           Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Page Media Player:    Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Page QRcode:          Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Page Screensaver:     Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Page Settings:        Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Page Utilities:       Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Page Weather:         Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Versioning:           Completed
[10:34:02][C][script.boot_progress_dump:102]:  - Base:                 Completed

The only process that is still in pending stage is the HW Relay. This is such a big jump from dev3 version.

Great job so far @edwardtfn .

Edited: More than 5 minutes in and the HW Replay is still in Pending stage.

[10:40:20][W][nspanel_ha_blueprint:174]: Boot steps: 29/30 (97% - 1073741695)
[10:40:20][W][nspanel_ha_blueprint:176]:   State:    Pending
[10:40:20][C][script.boot_progress_dump:087]: Boot progress: 97% (1073741695)
[10:40:20][C][script.boot_progress_dump:102]:  - Boot:                 Completed
[10:40:20][C][script.boot_progress_dump:102]:  - Date & Time:          Completed
[10:40:20][C][script.boot_progress_dump:102]:  - HW Buttons:           Completed
[10:40:20][C][script.boot_progress_dump:102]:  - HW Buzzer:            Completed
[10:40:20][C][script.boot_progress_dump:102]:  - HW Display:           Completed
[10:40:20][C][script.boot_progress_dump:102]:  - HW Memory:            Completed
[10:40:20][C][script.boot_progress_dump:102]:  - HW Relays:            PENDING

I think it's safe to assume that HW Relays is the only component that is not working in dev4.

Thank you.

edwardtfn commented 3 weeks ago

Do you have any error message related to this from the Home Assistant side (Settings > System > Logs)?

Aekung commented 3 weeks ago

I can't find any related error message in the logs.

I should add my situation here that I don't use HW Relays with any physical wiring. I only use it as a button to activate another device through the home assistant entity.

edwardtfn commented 3 weeks ago

This is hard to find... Could you please try again with DEV5 where I've tried to improve the loading of relay settings?

Aekung commented 3 weeks ago

I got this error while compiling even with the clean build.

*** [.pioenvs/nspanel-kitchen/src/esphome/components/nspanel_ha_blueprint/ha_components.o] Source `src/esphome/components/nspanel_ha_blueprint/ha_components.cpp' not found, needed by target `.pioenvs/nspanel-kitchen/src/esphome/components/nspanel_ha_blueprint/ha_components.o'.
========================== [FAILED] Took 5.78 seconds ==========================

Do you know what's the cause of the problem?

Edited: It works out of sudden. I can continue flashing and compiling now for some reason.

I will paste the logs here again later.

Thank you very much.

Aekung commented 3 weeks ago

[22:03:28][C][script.boot_progress_dump:087]: Boot progress: 97% (1073741695)
[22:03:28][C][script.boot_progress_dump:099]:  - Boot:                 Completed
[22:03:28][C][script.boot_progress_dump:099]:  - Date & Time:          Completed
[22:03:28][C][script.boot_progress_dump:099]:  - HW Buttons:           Completed
[22:03:28][C][script.boot_progress_dump:099]:  - HW Buzzer:            Completed
[22:03:28][C][script.boot_progress_dump:099]:  - HW Display:           Completed
[22:03:28][C][script.boot_progress_dump:099]:  - HW Memory:            Completed
[22:03:28][C][script.boot_progress_dump:099]:  - HW Relays:            PENDING
[22:03:28][C][script.boot_progress_dump:099]:  - HW Temperature:       Completed
[22:03:28][C][script.boot_progress_dump:099]:  - HW Wi-Fi:             Completed
[22:03:28][C][script.boot_progress_dump:099]:  - Page Alarm:           Completed
[22:03:28][C][script.boot_progress_dump:099]:  - Page Blank:           Completed
[22:03:28][C][script.boot_progress_dump:099]:  - Page Boot:            Completed
[22:03:28][C][script.boot_progress_dump:099]:  - Page Buttons:         Completed
[22:03:28][C][script.boot_progress_dump:099]:  - Page Climate:         Completed
[22:03:28][C][script.boot_progress_dump:099]:  - Page Confirm:         Completed
[22:03:28][C][script.boot_progress_dump:099]:  - Page Cover:           Completed
[22:03:28][C][script.boot_progress_dump:099]:  - Page Entities:        Completed
[22:03:28][C][script.boot_progress_dump:099]:  - Page Fan:             Completed
[22:03:28][C][script.boot_progress_dump:099]:  - Page Home:            Completed
[22:03:28][C][script.boot_progress_dump:099]:  - Page Keyboard (Num):  Completed

Still at 97%. HW Relays seems to still be the problem here.

Everything on the Home Screen loaded up perfectly, chips included. All the chips can also report the right stage. The small buttons on home screen also reflect the state of the devices. However, I will have that Red HA Icon on the screen and it's impossible to navigate to any other pages than the Home Screen.

I think though, as I don't use a fallback function of HW Relays, I don't know why there a [1][1] at the very start of the chips position. I remember not seeing this in the current main version. It just appears this time.

Hope this could bring any light to the problem.

Edited: Forgive my recklessness. I just noticed that the [1][1] of HW Relays was shown on the screen because I enabled Relay 1 and Relay 2 in ESPHome setting. I turned those off and [1][1] is now gone but I still can't navigate to any other pages than the Home page.

Blackymas / NSPanel_HA_Blueprint