-
-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug
Panel not Connecting to Blueprint
#2457
Comments
I believe the issue is due to the double dash ( |
Same issue with my NSPanel. Dash from the name removed, the problem persists... Started after upgrade of Esphome and HaaS , both in Docker. TFT,script,esphome all upgraded to latest version 4.3.12. go to Developer Tools, tab "Actions" and start typing "esphome.nspanel", then select one of the services -> seems all nspanel entries are empty...
haas log:
log:
|
Now please remove the integration related to this panel and add it back. Reconnect the Panel's device to Home Assistant:
|
Thanks, I've done exactly this+ removed and installed the automation to HA again but no luck..problem is still there... NSPanel is visible and working in Home Assistant, but the automation is still broken... Logger: homeassistant.components.automation.nspanel_configuration NSPanel Configuration: Error executing script. Service not found for choose at pos 3: Action esphome.nspanel_command not found |
Further details: Diagnostic section of NSpanel in HaaS |
In the device's page (Settings > Devices and Services > ESPHome) please check what is shown as “device name” on the “Diagnostics” area. |
Device Name
nspanel
út 21. 1. 2025 v 9:35 odesílatel Edward Firmo ***@***.***>
napsal:
… In the device's page (Settings > Devices and Services > ESPHome) please
check what is shown as “device name” on the “Diagnostics” area.
Also, could you please share your panel’s yank? Please hide any sensitive
info before sharing.
—
Reply to this email directly, view it on GitHub
<#2457 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK4O455V6IJ6W2UYC6IFVR32LYBEJAVCNFSM6AAAAABVFU4M5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBTHE3TCNBYGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Ok, so please go to Developer Tools, tab "Actions", and type "esphome.nspanel". Please let me know which services are listed (a screenshot should be fine). |
[image: image.png]
[image: image.png]
[image: image.png]
[image: image.png]
[image: image.png]
[image: image.png]
út 21. 1. 2025 v 10:32 odesílatel Edward Firmo ***@***.***>
napsal:
… Ok, so please go to Developer Tools, tab "Actions", and type
"esphome.nspanel". Please let me know which services are listed (a
screenshot should be fine).
—
Reply to this email directly, view it on GitHub
<#2457 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK4O45ZV74X2FUIP3WLXZAT2LYHZ3AVCNFSM6AAAAABVFU4M5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBUGE2TQMZWG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I cannot see the images. 😞 |
No problem, seems I found the issue:
https://community.home-assistant.io/t/2023-2-esphome-deprecated-api-password-how-to-update-to-encryption-key/528886
After I've update the api: part all works fine :-)
Thanks for your help!
Adam
út 21. 1. 2025 v 10:53 odesílatel Edward Firmo ***@***.***>
napsal:
… I cannot see the images. 😞
—
Reply to this email directly, view it on GitHub
<#2457 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK4O456EO3GMU343NXYRGX32LYKKFAVCNFSM6AAAAABVFU4M5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBUGIYDQNRZGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
TFT Version
4.3.12
Firmware Version
4.3.12
Blueprint Version
4.3.12
Panel Model
EU
What is the bug?
I installed my first Panel according to the Guide, Updatet tft an made Sure als Components are on the Same Version, but i always getting a Blueprint Version mismatch Error.
Already deleted Everything and stated over, but no change

Steps to Reproduce
No response
Your Panel's YAML
ESPHome Logs
Home Assistant Logs
The text was updated successfully, but these errors were encountered: