Have to gather all the errors I get with this new release, but there are many. Now the panel is no longer functioning. Reporting unknown services: esphome.nspanel_set_component_color, esphome.nspanel_send_command_text_printf and esphome.nspanel_page_home.
And the other problem that occurs is Nextion reported variable name invalid, this is a recurring error every 10 minutes.
You probably have a version mismatch.
Could you please take a look at the different versions shown on the boot screen?
I woukd suggest you update all the parts (ESPHome, Blueprint and TFT) to the same version.
Reboot does not say a lot, only top line version 4.2.6 then a line with esphome and it says retry #1. then no version.
Doing a full new re-install now, hope it will solve this problem.
Allas no even more problems, now I get after the TFT update, System data error! on the screen.
Update!
It would be nice if there is also an option for the Blank.TFT in update TFT in settings devices. As always the buffer or memory of the panel often is too full to except the next update, so there is the need to first do the Balnk page update then do the final european TFT update.
After the blank TFT route and then the European TFT second update all things seemed to work again.
Problem solved, but it is apain in the arse, guess it drives you up the wall too sometimes Edward.
Hi,
I have 2 Nspanels and I am very happy with the work provided by Blackymas.
I also have a 10" tablet in my office to display my dashboard. Not always responsive…
I’m looking for how to dedicate a screen for HA (I can’t find much…) and on Aliexpress, I came across this product (different sizes) :
Not sure what your goal is. It’s a little off topic. This is an android device. You can not flash this with esphome.
I think you should be able to load a webpage and create a HA dashboard.
Today I tried to start my first NSPanel project.
But I have different problems/ errors.
The first one, if I try to configure my first blueprint automation, blueprint is not able to see my nspanel name, the field is empty.
Blueprint version = v4.3.8
And I guess my second problem is maybe related to the first one.
Not able to flash my nspanel, I get following error:
INFO ESPHome 2024.5.5
INFO Reading configuration /config/esphome/test.yaml...
INFO Detected timezone 'Europe/Brussels'
INFO Generating C++ source...
INFO Compiling app...
Processing test (board: esp32dev; framework: espidf; platform: platformio/[email protected])
--------------------------------------------------------------------------------
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
- framework-espidf @ 3.40407.240606 (4.4.7)
- tool-cmake @ 3.16.9
- tool-ninja @ 1.10.2
- toolchain-esp32ulp @ 2.35.0-20220830
- toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch5
Reading CMake configuration...
-- The C compiler identification is GNU 8.4.0
-- The CXX compiler identification is GNU 8.4.0
-- The ASM compiler identification is GNU
-- Found assembler: /data/cache/platformio/packages/toolchain-xtensa-esp32/bin/xtensa-esp32-elf-gcc
-- Check for working C compiler: /data/cache/platformio/packages/toolchain-xtensa-esp32/bin/xtensa-esp32-elf-gcc
-- Check for working C compiler: /data/cache/platformio/packages/toolchain-xtensa-esp32/bin/xtensa-esp32-elf-gcc -- broken
-- Configuring incomplete, errors occurred!
See also "/data/build/test/.pioenvs/test/CMakeFiles/CMakeOutput.log".
See also "/data/build/test/.pioenvs/test/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-xtensa-esp32/bin/xtensa-esp32-elf-gcc"
is not able to compile a simple test program.
It fails with the following output:
Change Dir: /data/build/test/.pioenvs/test/CMakeFiles/CMakeTmp
Run Build Command(s):/data/cache/platformio/packages/tool-ninja/ninja cmTC_8fc56 && [1/2] Building C object CMakeFiles/cmTC_8fc56.dir/testCCompiler.c.obj
[2/2] Linking C executable cmTC_8fc56
FAILED: cmTC_8fc56
: && /data/cache/platformio/packages/toolchain-xtensa-esp32/bin/xtensa-esp32-elf-gcc -mlongcalls -Wno-frame-address CMakeFiles/cmTC_8fc56.dir/testCCompiler.c.obj -o cmTC_8fc56 && :
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/liblto_plugin.so: error loading plugin: /data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/liblto_plugin.so: cannot open shared object file: No such file or directory
collect2: error: ld returned 1 exit status
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:381 (__project)
CMakeLists.txt:3 (project)
========================== [FAILED] Took 7.32 seconds ==========================
It is working well, but the icon doesn’t refresh.
So I created an automation to reload the blueprint:
alias: NSpanel Reload by moonphase
description: ""
trigger:
- platform: state
entity_id:
- sensor.moon_phase
condition: []
action:
- service: automation.trigger
entity_id: automation.nspanel_configuration_m
mode: single
The automation trigger and is working, but the icon doesn’t change .
When I reload the blueprint manually, it also doesn’t change.
The only way to refresh (change) the icon is to use the “Save” button in the blueprint.
Is there a way to do this from an automation? (or any other way?)
This is why I’m asking you to create a new issue there.
On your screenshots I cannot see your full yaml neither your full logs. Navigating to your previous messages here, I see your yaml, but as it isn’t formatted, it’s hard to understand. And the interface here doesn’t allows to someone else format your yaml.
I’m trying to find the issue with the limitations here, as I always do, but I couldn’t find where it is failing, yet, and this is why I’m asking to report a new issue in GitHub and try making my life a bit easier on this troubleshooting.
If for some reason you don’t want to use GitHub instead, we can keep trying here… It’s just way less efficient.