Hi Edward, still having issues. All updated to 4.02, but it appears that on one panel it ignores the blueprint. It says Retry 1…2…3… and so on. I dont get it, all looks fine ? Any idea what the issue might be ?
The symbol for climate entity is always visible, at least in my setup.
There is no Stby mode.
This are the available attributes
hvac_modes: heat, off
min_temp: 8
max_temp: 28
preset_modes: eco, comfort
current_temperature: 20
temperature: 19.5
preset_mode: null
battery_low: false
battery_level: 50
holiday_mode: false
summer_mode: false
window_open: false
friendly_name: Wohnzimmer Heizung
supported_features: 17
Is it possible to influence that somehow?
This is not based on attributes, but in the state of that entity. It could be off, heating or idle (it’s set to heat, but as it is above the target temperature, it is in standby and isn’t heating right now). That icon woukd be shown when state is idle.
Try removing that specific panel from you HA devices and then adding again, then go to your automation and make sure the panel is correctly selected.
By the way, have you renamed any entity of this panel?
Not at this moment. Could you please add as a feature request on GitHub?
How are you creating the groups?
I mean, if at the end your entities ar of type group.xxxxx that is not supported, but if you are creating groups of specific domains, that should be transparent to the Blueprint.
Good morning. Yes I rename the panel and entities within it. Also I remove the panel and added it back again. But all old entities keep in the new added one. I guess I need to reset it.if so, how ? Thanks a lot.!!!
Hi @EdwardTFN
Thank you for your replies. I created the group through the groups.yaml, but I am calling an automation through the group… I think there is a problem on my side. I have called the automation thought a script and it is now working…
Can I ask you a question regarding AccuWeather. I do not have the “integration” option as per your instructions, I do, however have the AccuWeather integration installed… Is this correct?
If all elements of your group are from the same domain (light, cover, etc.) I would suggest to create a group using the domain’s constructor instead, as it will in the end be transparent to almost anything you use in Home Assistant.
You can still use yaml to create those: Group - Home Assistant
I’m not sure if I got your question correctly, but if you have AccuWeather under the Settings > Devices & Services area, you are good.
By the way, this blueprint should work with any weather provider, not only AccuWeather. As AccuWeather provides more parameters, you might few your screen a bit empty when using other providers, but it should work anyways.
Hi Guys,
After many attempts, tries and errors, I have finally successfully installed Blackymas blueprint on my NSPanel. It works reasonably well, however I have an issue which I can’t solve.
I’m using HIDDEN WiFi network for my IoT. Every device works well except my NSPanel. I have a few ESPHome devices and there is no problem to connect to hidden network.
It seems that NSPanel cannot connect to hidden network, but once is connected (if i disable Hidden temporarily) there is no problem to stay connected and work as intended. But than, if the WiFi is rebooted, or NSpanel loses power it cannot reconnect again.
This is a portion of my code:
substitutions:
###### CHANGE ME START ######
device_name: "nspkitchen"
wifi_ssid: !secret wifi_ssid
wifi_password: !secret wifi_password
nextion_update_url: "http://192.168.15.30:8123/local/nspanel_eu.tft"
##### addon-configuration #####
## addon_climate ##
# addon_climate_heater_relay: "1" # possible values: 1/2
##### CHANGE ME END #####
packages:
remote_package:
url: https://github.com/Blackymas/NSPanel_HA_Blueprint
ref: main
files:
- nspanel_esphome.yaml # Core package
#- nspanel_esphome_advanced.yaml # activate advanced (legacy) elements - can be useful for troubleshooting
# - nspanel_esphome_addon_climate_cool.yaml # activate for local climate (cooling) control
# - nspanel_esphome_addon_climate_heat.yaml # activate for local climate (heater) control
refresh: 300s
##### My customization - Start #####
##### My customization - End #####
I tried to add to the code : hidden: true or fast-connect: true but non of it is working.
Can you advice what would be the correct syntax here?
Thanks
m.
Please try this:
substitutions:
###### CHANGE ME START ######
device_name: "nspkitchen"
wifi_ssid: !secret wifi_ssid
wifi_password: !secret wifi_password
nextion_update_url: "http://192.168.15.30:8123/local/nspanel_eu.tft"
##### addon-configuration #####
## addon_climate ##
# addon_climate_heater_relay: "1" # possible values: 1/2
##### CHANGE ME END #####
packages:
remote_package:
url: https://github.com/Blackymas/NSPanel_HA_Blueprint
ref: main
files:
- nspanel_esphome.yaml # Core package
#- nspanel_esphome_advanced.yaml # activate advanced (legacy) elements - can be useful for troubleshooting
# - nspanel_esphome_addon_climate_cool.yaml # activate for local climate (cooling) control
# - nspanel_esphome_addon_climate_heat.yaml # activate for local climate (heater) control
refresh: 300s
##### My customization - Start #####
# Connect to a hidden Wi-Fi network.
wifi:
networks:
- id: !extend wifi_default
hidden: true
fast_connect: true
##### My customization - End #####
You can find more like this on the customizations docs: (EN) Customization · Blackymas/NSPanel_HA_Blueprint Wiki · GitHub
1 Like
thanks a lot for advice. I will give a try later on…
Morning all,
I have the following problem 
flashing via espweb several displays, the first worked fine. on the second one all looks good and at the end of the tft upload, it shows a white blank screen. I can flash with no issues a blank file getting the qr code but the regular file doesnt suceed. I have tried as well via ESP Flasher locally, same result.
Any idea how to solve this ? As well, why does one work the next doesnt ?
Edit :
Just seen the log shows :
][nextion:401]: Nextion reported variable name invalid!
Is this an issue ?
thanks all ! Kai
This is a really hard question. I’ve noticed the Nextion library available on ESPHome is quite fragile, so any small delay in your network or http server (Home Assistant?) could cause it to crash. Ans as the latest versions are taking more of the ESP memory, it could be one more factor for issues.
We worked in a new transfer engine with some retries and a better memory management (and better logs), but that still in dev. If you want to try that, change in your yaml, on the remote_package area, from ref: main to ref: dev, flash your panel and try transferring the TFT file again. Please capture the logs and share here as it woukd be easier to troubleshoot with that version.
After finishing that, please change it back to ref: main otherwise you will have version mismatch error.
Yeah, flashing again rarely helps with the TFT transfer.
Not really. The root cause of this is the lack of the right TFT file installed, so the panel is sending commands that are not expected but the current TFT.
2 Likes
Hi,
First off, a big thanks for developing this treasure!
It work real nice for me, after I managed to flash the nextion display via nextion manager.
One question, however, remains: there a updates for esphome quite frequently. After those, there are nspanelfirmware updates. I ran through all of then on HA, but I’m pretty sure I still have 4.0.2 on the panel. I read the few lines on updating and that I have to always update firmware, display, and blueprint at the same time. How do I update blueprint and display? Or more general: how does updating work? Is it just updating nspanelfirmware in HA settings? Or is there more to it, and if yes how do I do that?
Thanks a bunch in advance!
M.
Well, this is a bit more complex than it looks like initially.
Basically, this project is composed by 3 parts, but some of those parts will have “sub-parts”:
Blueprint
It runs on Home Assistant side, driven by an automation where the inputs are set.
It can be splitted in 2 sub-parts:
- The Blueprint itself, which is under /config/blueprint/automations/ - Must be updated every time you update the files from this project. We give a version number for this file and the latest is v4.0.2. You can download it from here.
- The automation with a reference to the Blueprint, which is usually inside
automations.yamland in most cases you don’t have to update unless you wanna change some seftings
TFT file
It is responsible for controlling the display itself, as it have it’s own processing unit and can execute code internally. Again, could be splitted in 2 parts:
3. The firmware (developed by Nextion, will manage the core/low level functionality of the display)
4. Our code containing all the components to be displayed and all the code to be executed at the display level.
We set all the pieces in a HMI file and then we compile it, witch consists of combining the two parts into a TFT file, which could be used by the display. We give a version for those files and the latest is v4.0.2.
Unless you want to customize your screen, you only need the TFT file.
ESPHome
This is also made of two parts:
5. ESPHome base firmware, which contains the basic/core control of ESP32 used in the panel. This have the same versioning as your ESPHome compiler, so the latest is v2023.10.5
6. Our code, which controls the communication between Home Assistant and the display, the relays and buttons in your panel. This is also on the same version as the other files in this project, which is currently v4.0.2.
When you install the ESPHome in your panel, you are sending a merge of these last two parts.
How it works?
When you update any of the parts of this project (1, 4 and 6), you have to make sure the other parts (1, 4 and 6) have all the same version.
The versions are numbered like vX.Y.Z. It’s fine to have different numbers on “Z”, but “X” and “Y” must always be the same between the parts 1, 4 and 6 listed above.
From time to time, you might be updating your ESPHome compiler, which will make the part 5 to be obsolete and then you will get the button to update in the ESPHome dashboard.
When you update that, it will automatically download the latest code for 6 from GitHub. If that haven’t changed, you are all good, however, if the code of 6 was updated, you may have a version mismatch with parts 1 and 4, which have to be manually updated.
The instructions for updating each of those parts are here.
Have this answer helped or just caused more confusion? 
3 Likes
I’m not sure what’s going on here but I’ve found an issue which I can’t imagine is to do with my config, so may have to post it on the github page but was wondering if anyone else has noticed the same.
One of my buttons which is allocated to a fan brings up a media player entity when long pressed instead of bringing up the fan speed controls.
Long pressing “Games Room Fan”
Which version of TFT are you using?
This was fixed on v4.0.2:
Overview of all changes
| Change | Criticality | Page/area | Components affected |
|---|---|---|---|
| Fix incorrect addressing on short press of button02 at buttonpage03 | Critical | buttonpage03 |
TFT (US model only) |
| Fix incorrect service call for Media Player on short press at button pages | Medium | buttonpageXX |
Blueprint |
| Update to customization instructions | Low | N/A | GitHub page (docs) |
| Use UTC for date selection on weather pages | Low | weatherXX |
Blueprint |
| Removed unnecessary refresh of relay’s chips | Low | home |
ESPHome |
I thought it was 4.0.2 but I’ll have to go and check.
EDIT: It turns out that this panel was still running the old ‘advanced mode’ config so I’m guessing the TFT version was wrong. Updating now and will confirm once I get home tonight.
1 Like
Huge thanks for this! Anyone run in to this?
I cant seem to unlock the command/control on the panel. I dont see posts on this or any issues opened so I opened nspanel is not permitted to call Home Assistant services · Issue #1222 · Blackymas/NSPanel_HA_Blueprint (github.com)
Thoughts?
This is related to permissions on your ESPHome configuration.
Please take a look at this: (EN) Alarm Control Panel · Blackymas/NSPanel_HA_Blueprint Wiki · GitHub
1 Like