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

Blueprints Exchange
, , , ,
285

Yes, for now it is working great, maybe if I need to update the tft I will run into problems again. But then i know how to fix it.

Thanx again for the help.

286

You shouldn’t have the same problem again. The original settings from Sonoff puts the display on what is called “Protocol Reparse mode” and this is what makes difficult to update the display with ESPHome. That instruction I’ve user above is to use an old PR (from more then 2 years ago) which always disables this mode, so it allows the TFT transfer.
The PR was rejected as this Protocol Reparse mode might be desired in some cases, but we can still take advantage of that code for this initial upload.
The nspanel_blank.tft, nspanel_eu.tft and nspanel_us.tft.tft all have Protocol Reparse mode disabled, so once it is in your panel, that old code is not needed anymore and you shouldn’t have this problem to transfer TFT files until you reflash your device with original Sonoff files.

1 Like
287

I’ve tried to update one of my NS Panels and I have the ESPhome update on the device as shown on the screen as ‘ESPHome: 3.2.2’ and ‘TFT: 3.1.0’. The blueprint has been updated manually but the device is stuck on the “please wait, the process can take several seconds?” screen.

Any tips?

288

Go to the esphome tab hit logs to see if there are any errors

289

You need the Blueprint, ESPHome and TFT all with the same version.

Please download the latest TFT and upload to your panel, then make sure your Blueprint is also the latest.
Latest versions are on the main branch on GitHub: GitHub - Blackymas/NSPanel_HA_Blueprint: This allows you to configure your complete NSPanel via Blueprint with UI and without changing anything in the code

290

Hi! Question, i want to use the US version in my EU home. i can adjust mounting, no issue. power input range is 110/240V, no issue. something else i am missing? reason i want to do this is the bigger screen ( a little)

291

You’re missing the fact that the actual screen size is the same. 3.5”.
Only the us version has bigger borders. But you can just use that one if you like.

293

I have a NS Panel working on all the 3.2.2 versions however when I add sensors to the home screen and set icons for them, the NS Panel shows the first 3 digits of the icon code (copied from here) rather than the actual icon. Am I setting them wrong?

EDIT: turns out you need to copy the SVG code rather than the 4 digit HEX code. (click the ‘U’ on the page I linked to)

294

Please take a look at this post about my experience so far with the EU model vs US model vs US model mounted in landscape.

295

I just noticed the following error in the serial output log when I updated the ESPhome version on an NS Panel from 2023.4.0 to 2023.4.1.

[W][nextion:396]: Nextion reported variable name invalid!

296

We have a known error which could cause this, and I believe it’s already fixed in dev, so it should disappear when you update after the next release.
But it could also be related to different versions between TFT, ESPHome and Blueprint. If everything is on the same version, don´t worry about that message which hopefully will disappear with the next release.

297

hello i’m here with the same problem of going from tasmote nspanel to esphome blueprint but can’t get out of it this stays on the rotating screen like with you have you already gotten out? thanks in advance!

298

It doesn’t seem to have caused any issue with functionality. I’m running 3.2.2 of the firmware, TFT and Blueprint.

1 Like
299

I configured two Chips but they aren’t showing up.

image
image867×502 24.2 KB 

    chip01: sensor.recycling_bin_today
    chip01_icon: 
    chip01_icon_color:
      - 246
      - 250
      - 0
    chip02: sensor.general_waste_bin_today
    chip02_icon: 
    chip02_icon_color:
      - 250
      - 0
      - 0

image
image849×65 3.25 KB

I’m wondering if this is because the state of the entity (general waste bin today) is True rather than On…?

300

That is probably the problem.
What kind of sensor are you using? Which integration?

301

Its a template sensor:

sensor:
  - platform: template
    sensors:
      general_waste_bin_today:
        friendly_name: "General Waste Bin Today"
        value_template: "{{ ((as_timestamp(states.sensor.date.last_changed) - as_timestamp('2019-01-10 00:00:00')) / 86400) | int % 14 < 1 }}"
        entity_picture_template: >-
          {{ '/local/images/general_waste_bin_today.png'}}
302

Could you please share your ESPHome yaml? Please remove any sensitive information (Wi-Fi credentials, etc.) before sharing.

303

Perhaps the Blueprint could be modified to accept True/False as well as On/Off ?

304

Yes, it could be, but I’d love to know more about your sensor (or integration) so we can propose a solution for this in a more robust way. There are million possibilities here and I’d like to understand if the values in the back-end are really “True/False” (it could be “true/false”, for example, and your front-end is “translating” to “True/False”, etc.)
Also, if possible, please go to Developer Tools, select the tab “State” and look for your entity which provides True/False.
Please send a screenshot if possible.

305

It’s just a template sensor based on dates.

image
image838×87 4.18 KB

1 Like