I’m also very frustrated about the TFT issues…all my NSPanel always update fast and OK using Tasmota, all of them never update using this blueprint project here. So I have always to serial flash them to tasmota for the tft update.
Very very annoying and I guess it will eventually make me stay with Tasmota for good. I really like this project, but its not running reliable in the long term.
Just wonder whats the difference between Tasmote and this solution is, and why it cannot be fixed. Thanks, Jo
Git the following error code today, anyone can help?
The automation “NSPanel Configuration” (automation.nspanel_configuration_4) has an action that calls an unknown service: esphome.nspanel_send_command_font_color.
Where/how to set the esphome.nspanel_send_command_font_color
Looks like you have updated ESPHome but not the other components.
When you restart your panel you have a blue boot screen where the versions are shown. Please take a look there and let us know the versions for TFT, ESPHome and Blueprint.
Based on the error message I believe you have Blueprint v3.x trying to communicate with ESPHome v4.x.
My suggestion would be to update everything to the latest version (currently v4.0.2).
I really understand your frustration. I’m investing quite a lot of my free time on this project and it is extremally frustrating when I see people being blocked not due to mistakes, but for limitations in the platform where I don’t really have that much control.
But I have to admit this was never been in the top of my priority. I’ve seen people complaining about this here and there, but as I do dozes of those transfers every week (I try all the new feature with 3 different TFT files in the same panel) and the system works pretty well for me (I do have rarely cases where it fail, but then I try again and it just works), but as the TFT files are getting bigger, we are using more of ESPHome memory, etc., I can see people getting more of those cases and I see they are getting frustrated.
I don’t know really what is the root cause. It’s hard to compare to Tasmota, as we use distinct drivers to communicate to the device, but certainly there are something there that requires some attention. Unfortunately we are not getting the attention from ESPHome team (we are reporting this issue since at least an year ago with no answer).
I believe there are thing I can do and I will invest some time on that. Could be reducing the file size or memory consumption (maybe with minimal UI compromise or just review some redundant or inefficient code), or looking on things this guide from Tasmota does differently that I don’t know if was tested before (baud rate, etc.).
I will invest some time at that…
Be aware of just updating the new ESP32home firmware.
I was on the old NSP blueprint and old TFT file and I Just updated ESPhome firmware from 2023.8.3 to 2023.9.0.
After the update of ESPhome I installed the firmware on my NSP. Result…. blue screen.
Tomorrow I will try to do a full update including the TFT.
Updated ESPhome to 4.0.2 and now some of the entities on the button page dont load correctly. The buttons are non functional and just show a red exclamation. The funny thing is it only happens to 6 of 8. the other 2 show up just fine. They are all switches so I am at a loss as to what is going on. This worked fine on 4.0…
That is correct, but I just wanted to say that you need to be aware that HA has update ESPHome to 2023.9.1 and if you update your ESPHome to the latest version, it automatically has impact on the NSPanel. So after the ESPHome update you must also update your NSPanel (and some people have problems with the NSPanel update)…
Just updated one of my NSPanels to the 4.02 patch release. Most functions seems to be working, but I have one “issue”:
The display turns black after the Timeout Dimming (set to 20seconds) although the slider " Display Brightness Dimdown" is set to 70%.
No. The upload shouldn’t take more than 15 to 20 minutes. If after half an hour it still far from the end, just interrupt that and try again.
Those life-long transfers always fails at the end. In fact, the display is disconnected from ESPHome and isn’t receiving anything. Unfortunately ESPHome is pretty bad on detecting this state.
It was 20 seconds, but after setting the Timeout Sleep to 0 seconds, the display doesn’t turn off.
The only thing is that is doesn’t go to dimmed mode.
I assumed that the setting “ Timeout dimming” was used to dim the display to the level as specified in the setting “Display brightness dimdown”
