Sonoff NSPanel Blueprint - Configure your own custom NSPanel easy via a Blueprint

bkbartk · March 18, 2024, 6:53pm

Yes it is possible.
Those screens are just dumb devices managed bij 1 ha instance.
Most ga instances do not have a screen. You can have one big screen. But before spending a lot of money on devices. I would suggest start with one and if you know what it does decide if you need more.

EdwardTFN · March 18, 2024, 7:23pm

github.com

Blackymas/NSPanel_HA_Blueprint/blob/4ff219075e2a9d8b69259eefbe7d03cb4a2ce47b/docs/error_compiling.md

# Compiling Errors Guide

The most common cases for compiling errors are related to build files needing to be cleaned up and the lack of resources on your ESPHome compiler host.
These are our suggestions for both cases:

## Clean-up build files

Go to your ESPHome Dashboard, click the 3-dot menu related to your device and then "**Clean Build Files**":

![image](https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/dev/docs/pics/esphome_dashboard_clean_build_files.png)

## Limited resources on ESPHome compiler host
### Free Up Server Resources

1. First, please check the available memory of the ESPHome compiler host. 4GB of memory are recommended if you are installing ESPHome as a Home Assistant add-on. 
Therefore, a RasPi 4 with 4GB RAM is the minimum if you are using a Raspberry Pi. 
A manual installation requires at least 2GB of memory and 500MB of swap space or 3GB of memory. 
With less memory the compiler will crash!

2. Add the following to your device's YAML to reduce resource usage (this may slow down the compilation process):

This file has been truncated. show original

EdwardTFN · March 18, 2024, 7:24pm

This is a know bug, which was already fixed in dev and will be released very soon.

makai · March 18, 2024, 7:25pm

Maybe this is your issue:

github.com/esphome/issues

ESP32-IDF framework fails to compile on ARMv7

opened 12:08PM - 21 Feb 22 UTC

DanteBC

integration: esp32

### The problem Ever since updating to ESPHome 2022.2.x my ESP32-C3 fails to …compile on my ARMv7 docker installation. ### Which version of ESPHome has the issue? 2022.2.1+ ### What type of installation are you using? Docker ### Which version of Home Assistant has the issue? 2022.2.8 ### What platform are you using? ESP32-IDF ### Board ESP32-C3 ### Component causing the issue _No response_ ### Example YAML snippet ```yaml esphome: name: esp01c3 platformio_options: board_build.flash_mode: dio esp32: board: esp32-c3-devkitm-1 variant: esp32c3 framework: type: esp-idf sdkconfig_options: CONFIG_COMPILER_OPTIMIZATION_SIZE: y logger: api: ota: password: "xxx" wifi: ssid: ххх password: ххх manual_ip: static_ip: 192.168.88.112 gateway: 192.168.88.1 subnet: 255.255.255.0 output: - platform: ledc pin: GPIO20 id: gpio_20 light: - platform: monochromatic output: gpio_20 name: "Test light" switch: - platform: gpio pin: GPIO3 name: "Onboard LED" ``` ### Anything in the logs that might be useful for us? The compilation fails with the following output: ```txt Reading CMake configuration... -- The C compiler identification is unknown -- The CXX compiler identification is unknown -- The ASM compiler identification is unknown -- Found assembler: /data/cache/platformio/packages/toolchain-riscv32-esp/bin/riscv32-esp-elf-gcc -- Check for working C compiler: /data/cache/platformio/packages/toolchain-riscv32-esp/bin/riscv32-esp-elf-gcc -- Check for working C compiler: /data/cache/platformio/packages/toolchain-riscv32-esp/bin/riscv32-esp-elf-gcc -- broken -- Configuring incomplete, errors occurred! See also "/data/esp01c3/.pioenvs/esp01c3/CMakeFiles/CMakeOutput.log". See also "/data/esp01c3/.pioenvs/esp01c3/CMakeFiles/CMakeError.log". fatal: not a git repository (or any parent up to mount point /) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). CMake Error at /data/cache/platformio/packages/tool-cmake/share/cmake-3.16/Modules/CMakeTestCCompiler.cmake:60 (message): The C compiler "/data/cache/platformio/packages/toolchain-riscv32-esp/bin/riscv32-esp-elf-gcc" is not able to compile a simple test program. It fails with the following output: Change Dir: /data/esp01c3/.pioenvs/esp01c3/CMakeFiles/CMakeTmp Run Build Command(s):/data/cache/platformio/packages/tool-ninja/ninja cmTC_fc39c && [1/2] Building C object CMakeFiles/cmTC_fc39c.dir/testCCompiler.c.obj FAILED: CMakeFiles/cmTC_fc39c.dir/testCCompiler.c.obj /data/cache/platformio/packages/toolchain-riscv32-esp/bin/riscv32-esp-elf-gcc -march=rv32imc -o CMakeFiles/cmTC_fc39c.dir/testCCompiler.c.obj -c testCCompiler.c /bin/sh: 1: /data/cache/platformio/packages/toolchain-riscv32-esp/bin/riscv32-esp-elf-gcc: not found ninja: build stopped: subcommand failed. CMake will not be able to correctly generate this project. Call Stack (most recent call first): /data/cache/platformio/packages/framework-espidf/tools/cmake/project.cmake:311 (__project) CMakeLists.txt:3 (project) ``` ### Additional information **Addition**: It is still possible to compile the firmware using an older toolchain version. You need to add the following lines to the config: ```yaml esphome: name: ${device_name} platformio_options: platform_packages: - framework-espidf @ 3.40300.0 esp32: board: esp-wrover-kit framework: type: esp-idf platform_version: 3.4.0 ``` **Update:** At the moment all versions of toolchains older then [8.4.0+2021r2-patch5](https://registry.platformio.org/tools/espressif/toolchain-riscv32-esp?version=8.4.0%2B2021r2-patch5) are deleted from platformio repository. **Prior solution doesn't work anymore!** At the moment the only way to mitigate this issue is to use esphome on any other platform (a desktop for example) and compile for esp32-c3 and esp32 from there.

EdwardTFN · March 18, 2024, 7:25pm

I cannot answer more questions here until someone else publishes something.

EdwardTFN · March 20, 2024, 8:20am

v4.3.1 - Ensuring Compatibility with ESPHome v2024.3.0 and Enhancing Stability · Blackymas/NSPanel_HA_Blueprint

Patch v4.3.1 focuses primarily on ensuring full compatibility with the latest ESPHome v2024.3.0 IP address format changes, crucial for the smooth compilation and operation of the NSPanel project. This timely update addresses critical compatibility issues, alongside implementing key bug fixes and optimizations. It underscores our ongoing commitment to enhancing stability and ensuring a reliable experience for all NSPanel users, keeping pace with the evolving ESPHome ecosystem.

v4.3.1 - Ensuring Compatibility with ESPHome v2024.3.0 and Enhancing Stability · Blackymas/NSPanel_HA_Blueprint

sparkydave · March 21, 2024, 3:12am

I’m curious about the IP address change that you mention in the change log. I didn’t see anything about that in the ESPhome breaking changes. I take it this is a backend thing that isn’t seen by us with the YAML config?

EdwardTFN · March 21, 2024, 6:16am

They don’t call “breaking change” when it isn’t changing the way you have to set via yaml. When you write code in lambdas, you are in your own. We do have probably thousands of lines of code there, and one of those lines was isung a function that was changed. So, it was a change, breaking our solution.

leotantantan · March 21, 2024, 9:52am

Thanks for advising, it’s working perfectly now, but I just got another issue. If I type in Chinese in the label area, a bunch of characters cannot be properly displayed. For example, “床头灯” only shows “头灯”, and “衣帽间” only shows “间”.

Anyway, this blueprint is awesome! Great job!

Qyles · March 22, 2024, 12:39pm

Hi guys, congrats for this proyect.

Ive been using nspanel flawless for a month. I am trying now to change the password of my wifi. Is there any option? I try to update it via secrets in esphome but it says password is incorrect.

Thank you very much

EdwardTFN · March 22, 2024, 1:30pm

Please take a look at this: NSPanel_HA_Blueprint/docs/howto.md at e263047b157822f8018c42e583a9d5f0b2ba5ab4 · Blackymas/NSPanel_HA_Blueprint · GitHub

EdwardTFN · March 22, 2024, 1:32pm

On your device’s page (Settings > Devices and Services > ESPHome), which value is shown for “Display charset” in the Diagnostic area?

leotantantan · March 22, 2024, 9:49pm

It shows number 1

10der · March 23, 2024, 8:17am

hi!

why after hardware reboot (power off → power on) the version of esphome aways rollback to prev version
after fw a new version ok, after hardware reboot again - old version and stuck on boot screen

thank you!

oolesh · March 23, 2024, 11:47am

hello i can’t update the TFT from v 4.2.5 to the newer version .how can i fix it please
and yes i did clean build files…

EdwardTFN · March 23, 2024, 12:46pm

In the drop down “Update TFT display - Model” above, please change from “NSPanel US” to “NSPanel US (CJK languages)”, then press “Update TFT display” to update your screen with the file supporting Chinese, Japanese and Korean (CJK) charset.

EdwardTFN · March 23, 2024, 12:50pm

Could you please share your ESPHome logs from when you press the upload button to the moment your panel restarts (and a few seconds after that)?

If possible, please create a bug report in GitHub with this info. It’s much easier there.

oolesh · March 23, 2024, 1:24pm

OMG finally i fixed it after 3 hours.but now it’s working great .my mistake was the Update TFT display - Baud rate was at 921600 i changed it to 115200.okay thank you so much.

EdwardTFN · March 23, 2024, 4:07pm

921600bps shouldn’t be an issue. That is the baud rate to be used when transferring TFT and it’s OK that you use something different than 115200bps.
I will investigate that.

leotantantan · March 23, 2024, 11:29pm

I can’t believe I missed this option. Fantastic, it’s working perfectly now. You’re a superhero.