SONOFF NSPanel Smart Scene Wall Switch with integrated Nextion HMI touchscreen display support in Tasmota?

[Hedda]

Can the Tasmota firmware for ESP32 be made to fully support the display in ITead's SONOFF NSPanel with Nextion touch-screen display?

The reason for the request is that "SONOFF NSPanel Smart Scene Wall Switch" (Kickstarter campaign by ITead) is apparently based on an ESP32 and a Nextion touch screen display.

https://www.kickstarter.com/projects/sonoffnspanel/sonoff-nspanel-smart-scene-wall-switch/

UPDATE! Developers discovered that SONOFF NSPanel specifically uses Nextion Discovery 3.5” NX4832F035 screen type part:

https://nextion.tech/datasheets/nx4832f035/

https://www.tkqlhce.com/click-100155210-13913691?url=https%3A%2F%2Fitead.cc%2Fproduct%2Fnx4832f035-nextion-3-5-discovery-series-hmi-touch-display%2F

blakadder wrote: "With this discovery we confirm it is possible to upload custom GUI created in Nextion Editor."

https://nextion.tech/nextion-editor/#_section1

As I understand all Nextion displays as their own integrated microcontroller unit (STM32GO ARM Cortex-M0+ 64MHz Onboard MCU Processor) so that will off-load most of the heavy lifting work and all text and graphics, animations, etc. are created using Nextion Editor software, and then then the project files/assets are uploaded directly into the Nextion screen. The screen then has serial commands mapped to UI elements and can be sent and received from ESPHome firmware to control it.

https://nextion.ca/portfolio-items/nextion-iteadlib-and-esp32-step-by-step/

https://nextion.ca/tutorials/

https://nextion.tech/faq-items/iteadlib-arduino-nextion-library/

https://github.com/itead/ITEADLIB_Arduino_Nextion

https://www.youtube.com/watch?v=FSRx8h8iBnk&ab_channel=AndreasSpiess

https://www.youtube.com/watch?v=eI-4_QyVenw

https://diyi0t.com/arduino-nextion-display-tutorial/

To also add an easy-to-use UI for file upload to Nextion displays to Tasmota could maybe base it on something like this ESPNexUpload? 😃

https://github.com/Nredor/ESPNexUpload

[Jason2866]

There will be probably no integration of the iteadlib. Tasmota supports already LVGL. There are plans to support openHASP via LVGL. SONOFF NSPanel is planned to be supported from Tasmota

[Hedda]

SONOFF NSPanel is planned to be supported from Tasmota

Suggest that you write a short mail to "Jeri Shi" jerry.shi@itead.cc, "Stan Li" Stan.li@itead.cc, and "Daniel Zhan" daniel.zhan@itead.cc telling them who you are and ask them nicely if they would be willing to send you a prototype or preview sample unit in advance of them shipping general availability of the Kickstarter early-bird units, maybe even be so bold and ask them to also send some units to a few more fellow Tasmota developers. I am sure that they would appreciate it if some of the popular open-source firmware projects could already support it before it gets shipped to end-users.

[barbudor]

Oh, do you think that since Tasmota exists there hasn't been any contact between Sonoff and Tasmota developpers or Theo ?
Nevertheless when Tasmota developpers want something, they are getting it whether it's given or paid from their own money :D

[Hedda]

OK cool.

Read that openHASP is a fork of HA SwitchPlate HASPone and that both are existing firmware for Espressif microcontrollers which does not look to rely on iteadlib library and yet apparently support Nextion/TJC/STM32F4 HMI touchscreen / scene display controllers and ESP32 or ESP8266. openHASP at least instead rely on the lvgl graphics library.

https://github.com/HASwitchPlate/openHASP

https://haswitchplate.github.io/openHASP-docs/

https://lvgl.io

https://community.home-assistant.io/t/openhasp-an-mqtt-driven-touchscreen-scene-controller/300853

https://github.com/HASwitchPlate/HASPone

[blakadder]

Teardown: https://blakadder.com/nspanel-teardown/

As for the protocol used to talk to the screen - its a custom one. We need someone to capture the traffic when a firmware update is made to see how the screen is initialized and put into upload mode.

Nextion screens have a different design philosophy and will not work with LVGL and therefore openHASP

[mkaatman]

Hey @blakadder would you mind expanding a bit more on the philosophy part? Curious where using lvgl gets hung up

[blakadder]

Hey @blakadder would you mind expanding a bit more on the philosophy part? Curious where using lvgl gets hung up

Mostly on the part that you cannot use it without reprogramming the screen STM32

[Hedda]

FYI, ITead has now posted specific IO (Input-Output) definition documention for Sonoff NSPanel in a new Kickstarter campaign update:

https://www.kickstarter.com/projects/sonoffnspanel/sonoff-nspanel-smart-scene-wall-switch/posts/3328417

"From the feedback, there are backers who want to use NSPanel in their projects, so we share the documents below to help users better DIY firmware. If you are interested, please check the document below"

Nextion HMI Project Upload Protocol specifications:

https://nextion.tech/2017/12/08/nextion-hmi-upload-protocol-v1-1/

[Hedda]

FYI, there is some interesting discussion in Home Assistant community forum about hacking this Sonoff NSPanel:

https://community.home-assistant.io/t/sonoff-nspanel-smart-scene-wall-switch-by-itead-coming-soon-on-kickstarter/332962/

HA-TB303 also have also collected quite a lot of information on this site similar to blakadder:

https://espthings.io/nspanel

Also, the community at the unofficial Nextion/TJC chat room on Discord have been making some discoveries about its display:

https://unofficialnextion.com/t/welcome-to-the-unofficial-nextion-tjc-user-forum/8

[blakadder]

already hacked and fully controlled with Tasmota

[barbudor]

We want to see the video of it in action (don't forget the T logo :D)
Great hacking job 👍

[Hedda]

Nice!

What about uploading files project files to SONOFF NSPanel integrated Nextion display and flashing firmware of that Nextion display?

Do you think patched will be submitted and available in upstream Tasmota32 before ITead ship their Kickstarter units to its backers?

[blakadder]

Support is for the NSPanel and its built in features.

Uploading custom project files to Nextion is not a part of it but should be possible in the future. Its just serial protocol but requires a finished project file first.

@barbudor not happening with default project

[Hedda]

FYI, blakadder posted that he is trying to replicate the original default firmware but using MQTT to be able to integrate it in HA.

Everything neatly laid out here for hacking it and configuring Tasmota and blakadder said will be updated as support progresses:

https://templates.blakadder.com/sonoff_NSPanel

As mentioned before, also be sure to check out his teardown as an introduction to the hardware:

https://blakadder.com/nspanel-teardown/

[m4dm4rtig4n]

Hello,

I have juste receive my NSPanel and follow blakadder tutorial, but NSPanel constant boot loop :/
Any Idea ?

I have :

• Flash with "tasmota32-nspanel.bin".

• Apply Template :
  {"NAME":"NSPanel","GPIO":[0,0,0,0,3872,0,0,0,0,0,32,0,0,0,0,225,0,480,224,1,0,0,0,33,0,0,0,0,0,0,0,0,0,0,4736,0],"FLAG":0,"BASE":1,"CMND":"ADCParam 2,64000,10000,3950 | Sleep 0 | BuzzerPWM 1"}

• Check if Module 0 is selected

• Upload nspanel.be and create autoexec.be with concent :
  load("nspanel")

But NSPanel always bootloop and reset to factory.

[julesbike]

I had the same problem - I also just flashed with regular tasmota and I can get that half working. I can login and get MQTT working but I am not able to change anything on the display.

I get the following error in the console:

00:00:00.003 HDW: ESP32-D0WD-V3 
00:00:00.079 UFS: FlashFS mounted with 288 kB free
00:00:00.207 CFG: Loaded from File, Count 57
00:00:00.222 QPC: Count 1
00:00:00.318 BRY: Berry initialized, RAM used=3849
00:00:00.343 BRY: no 'preinit.be'
00:00:00.351 Project tasmota - NSPanel Version 10.1.0(tasmota)-2_0_1_1(2021-12-08T14:50:20)
00:00:00.778 BRY: Exception> 'syntax_error' - /autoexec.be:4: 'persist' undeclared (first use in this function)
00:00:00.779 stack traceback:
00:00:00.790 	<native>: in native function
00:00:00.791 	<unknown source>: in function `load`
00:00:00.792 	<unknown source>: in function `load`
00:00:01.328 WIF: Connecting to AP1 ASUS Channel 3 BSSId D0:17:C2:D7:A4:10 in mode 11n as nspanel-3972...
00:00:05.352 WIF: Connected
00:00:05.611 HTP: Web server active on nspanel-3972 with IP address 192.168.0.169

I wonder whether something has changed on the latest shipped NSPanel

[julesbike]

Just got it to work....strange. I got it running with regular tasmota with the error above. Then I did an OTA upgrade to tasmota32-nspanel.bin and that rebooted working fine.

[Jason2866]

Not strange since tasmota32-nspanel.bin is a older version (before the changes in berry)

[blakadder]

This seems more related to possible changes in Berry since the persist function seems to fail.

Try the new nspanel.be with import persist line

[julesbike]

I havent tried but the OTA upgrade seems to get round this. Thanks for your work I have this running nicely with Openhab using MQTT. Great to have a small always on screen to run scenarios.

[binaryhellstorm]

Flashed my NSPanel with Tasmota successfully and have in integrated into HA. But i can't seem to get it to pair with the Ewlink app anymore to set the time and location info. Has anyone else has this issue?

[ascillato]

Ewelink is not compatible with Tasmota. Once you flash Tasmota, Ewelink won't connect anymore to your sonoff device.

[ascillato]

time and location info must be set using Tasmota commands: https://tasmota.github.io/docs/Commands/

use the Tasmota console for that

[binaryhellstorm]

Perfect, thank you!

[ilyavolodin]

time and location info must be set using Tasmota commands: https://tasmota.github.io/docs/Commands/

How about temperature units? I tried running SetOption8 1 command and it's accepted but UI still shows Celsius.

[bmangodt]

Hello all!
I've been having issues installing Tasmota on my NSPanel. I've followed the guide by @blakadder to the letter and I still can't get it to work fully. Here's what I've tried and done so far:

• Attempt 1: Installed via the web installer. Flashing works. Uploaded config and checked if Module 0 is selected. The analog temperature is reading negative and the nspanel.be is not being loaded. Commands like "Latitude", "Longitude" aren't working and the display is not showing weather or time. Will post console logs when I try to install it once again.
• Attempt 2: Installed via ESP-flasher with the provided tasmota32-nspanel.bin from @blakadder GitHub. Same issues as mentioned in attempt 1.
• Attempt 3: Flashed using ESP-flasher to Tasmota32 version 10.0.0. Applied the template and the temperature of Analog1 is now reading correctly. Commands are working but no change on display when I enter timezone or location. And when I upload a version of nspanel.be I get this error in the console:

00:00:00.741 BRY: Exception> 'type_error' - value 'nil' does not support subscriptable
00:00:00.743 stack traceback:
00:00:00.743 	<unknown source>: in function `main`
00:00:00.747 	<unknown source>: in function `load`
00:00:00.751 	<unknown source>: in function `load`
00:00:00.756 	<unknown source>: in function `main`
00:00:00.760 	<unknown source>: in function `load`
00:00:00.765 	<unknown source>: in function `load`

Has anyone had similar issues or knows a fix to these issues? Thanks in advance!

[Jason2866]

@bmangodt Please change the OTA URL to https://github.com/tasmota/install/raw/main/firmware/unofficial/tasmota32-nspanel.bin
and do a upgrade.

[bmangodt]

@Jason2866 I tried that and I get the same result as in my first attempt. Analog1 temperature is negative (see image) and the display just shows 0 values. The full output of the console is:

00:00:00.003 HDW: ESP32-D0WD-V3 (PSRAM)
00:00:00.102 UFS: FlashFS mounted with 288 kB free
00:00:00.210 CFG: Loaded from File, Count 45
00:00:00.226 QPC: Count 1
00:00:00.321 BRY: Berry initialized, RAM used=3813
00:00:00.347 BRY: no 'preinit.be'
00:00:00.354 Project tasmota - Tasmota Version 10.1.0.3(tasmota)-2_0_2(2021-12-30T17:13:02)
00:00:00.127 BRY: successfully loaded 'autoexec.be'
00:00:01.853 WIF: Connecting to AP1 REDACTED Channel 6 BSSId REDACTED in mode 11n as tasmota-0CB1F0-4592...
00:00:03.875 WIF: Connected
00:00:04.154 HTP: Web server active on tasmota-0CB1F0-4592 with IP address 192.168.1.253
19:38:42.150 RSL: INFO1 = {"Info1":{"Module":"NSPanel","Version":"10.1.0.3(tasmota)","FallbackTopic":"cmnd/DVES_0CB1F0_fb/","GroupTopic":"cmnd/tasmotas/"}}
19:38:42.164 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-0CB1F0-4592","IPAddress":"192.168.1.253"}}
19:38:42.169 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU"}}
19:38:42.182 RSL: RESULT = {"POWER1":"OFF"}
19:38:42.184 RSL: POWER1 = OFF
19:38:42.186 RSL: RESULT = {"POWER2":"OFF"}
19:38:42.188 RSL: POWER2 = OFF
19:38:44.684 QPC: Reset
19:38:46.682 RSL: STATE = {"Time":"2021-12-30T19:38:46","Uptime":"0T00:00:10","UptimeSec":10,"Heap":185,"SleepMode":"Dynamic","Sleep":0,"LoadAvg":178,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":38},"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"REDACTED","BSSId":"REDACTED","Channel":6,"Mode":"11n","RSSI":72,"Signal":-64,"LinkCount":1,"Downtime":"0T00:00:04"}}
19:38:46.725 RSL: SENSOR = {"Time":"2021-12-30T19:38:46","ANALOG":{"Temperature1":-8.5},"ESP32":{"Temperature":63.9},"TempUnit":"C"}

[Courty40]

Go to the console window and type this:

AdcParam1 2,19000,10000,3950

The ADC on the new ones is wrong

Courty

[bmangodt]

@Courty40 Thanks! That solves one issue. The problem with nspanel.be not loading is still present unfortunately...

[bananajoe86]

Try this....
To load the driver on startup you can either:
change the filename to autoexec.be

[bmangodt]

@bananajoe86 Trust me, I tried that. The console just says: "successfully loaded 'autoexec.be" and that's it. No time, no weather, no nothing on the display

[sq9myx]

I have the same problem as bmangodt
, only zero on the display

[bmangodt]

Great to hear I'm not the only one having issues here.
I still have no idea what's going on or why it's just not loading the nspanel.be...

[ginger-ha]

hey, i had the same problem.

i changed the line in the autoexec from "load("nspanel")" to "load("nspanel.be")"

[bmangodt]

@ginger-ha HOLY... you my guy, are a genius. Weird that just changing the nspanel.be to autoexec.be doesn't work... but this does? Maybe the devs need to have a look at it anyway

[peepshow-21]

So, I understand that in it's basic form, this allows us to interact with 3 screens built into the device. Home, Thermostat and Buttons.
However we can't change these or link from these to new screen. If we want to make changes we need to dump all those and start with a blank screen and build all custom ones. Is this correct?

I watched a few youtubes on this;
https://www.youtube.com/watch?v=D-zgtylBKUc
and it seems you build a group of screens and package them as a file. you then send this to the screen and reboot and it unpacks the file and installs the screen.

These guides are not specifc to the NSPanel though. I would like to try and do some custom screens but not clear how to do it on this device and how those screens interact with tasmota, So I have a few questions.

1. Assuming I have built a custom package with new screens in, how would I install this on the device?
2. Can I make a backup of the current screens in the unit and restore them, so I can switch back and forward while keeping tasmota on. I guess I could reflash the whole stock firmware, but that would mean I need to keep taking the thing apart to reflash tamsota all the time. You really want to just keep tas and switch between custom and stock screens.
3. If new screens are installed with new buttons and widgets, how would I send command and receive event from these into the tasmota?

Probably have lots more, but those are the main ones I and think of now.

A really simple example of the process with a simple screen with one button, going thought that whole process by someone that knew what they were doing would be a great start for the rest of us!! :)

[peepshow-21]

I don't think you can. Is that not a tool for using on something other than an NS with tasmota? I'm not sure it's relevant here. I'm looking at doing it using what's already installed on the tasmota version, which would be a berry script. That is c code which a variation of would need compiled into the tasmota firmware. If it can be done the way I'm looking at, it would not need anything compiled into the core code, it would just be a berry script that would need copied to the device. For me, easier. If it works.

[mkaatman]

I know it's a pain but you could temporarily flash esphome to have easy access to upload a tft if need be and then flash back. Chris masto has some videos on YouTube.

[r00li]

Well luckily there is already a solution to do all of this in Tasmota - https://github.com/peepshow-21/ns-flash
That's how I flashed my completely custom UI and made it work. In the end it was pretty easy

[peepshow-21]

If you don't want to write a whole HMI yourself, but want access to a pretty full featured one that you can control directly with json commands (over mqtt) there is also an option for that I'm working on
some example screens at bottom of first post here;
https://community.openhab.org/t/sonoff-nspanel-setup/131770/1

[mkaatman]

It looks great but I've got the u.s. version! I've been trying to write my own but I find the nextion editor frustrating.

[peepshow-21]

anyone tell me exactly what I need to do to make the buzzer 'buzz' when the execute the buzzer command? Currently it's clicks. @blakadder said about changing the template, just wasn't clear to me exactly what I needed to do.

[redguyz]

Put in console:
buzzerpwm 1

That's it. The buzzer should work now.
Change the tone, if you wish, with pwmfrequency 2000 (for example)

[wifi75]

hello I have nspanel with tasmota firmware, ho I can set my correct location?
i tried by command type Latitide and longitude but not work, why?

[MeyerFam]

Are you trying to get the correct weather info? If so, try the 'set_weather (your location)' from the console.

[wifi75]

you trying to get the correct weather info? If so, try the 'set_weather (your location)' from the console.

hELLO, can you send me correct line command please?

[MeyerFam]

I assume that you already sent the 'NSPLocation' command from the Blakadder guide: https://templates.blakadder.com/sonoff_NSPanel.html like this:

For weather updates, use this:

[peepshow-21]

It's not got a great weather service built into the tasmota side for doing this. It didn't work for me either for my location, it's very hit and miss. It was an excellent first attempt to get something going when it was first done, but not good for serious use. I'd suggest looking at some other way to use the NSPanel now. You can either look at doing your own berry script or changing the exiting one to look at a better weather service that does know where you are. I initially changed it to look at openweather instead. Or, as I would do (but I'm bias)... replace the stock screen firmware with something better and more customisable like NxPanel, or one other the other custom HMI's that others have done. Using the stock firmware really isn't getting anywhere near the most out of this device. IMHO.

[jonackey]

Did anyone happen to back up the original firmware? I'm trying to revert but made the mistake of not backing up before loading ESPhome firmware

[mkaatman]

A couple of us tried to reflash the stock firmware from some of the images going around and we weren't able to do it. Or rather, we were but it seemed like the device was locked to the firmware it came with.

…

On Wed, Feb 23, 2022 at 9:04 PM jonackey ***@***.***> wrote: Did anyone happen to back up the original firmware? I'm trying to revert but made the mistake of not backing up before loading ESPhome firmware — Reply to this email directly, view it on GitHub <#13347 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACDIW6JDU3A2GV3BRWCYQDU4WN5XANCNFSM5F2GIFGA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[Jason2866]

All stock firmwares from sonoff are device locked (probably via MAC address).
No stock firmware from a other device will work without a correct done patch.

[jonackey]

Thanks for the feedback! Second option, does anyone have the TFT for the US version? I managed to find one on discord, but its the TFT for the EU version which doesn't allow for orientation change. I couldn't find a way to force it in the custom firmware.

[mkaatman]

ns-panel.zip

[peepshow-21]

Need to be clear on what's asked. There are two parts to this, the ESP firmware and the Nextion firmware. The post from @mkaatman is the TFT firmware for the Nextion. There is no issue there, you easy swap to and from that with stock and custom. But if you want to true stock, you need original Nextion and original ESP. The Nextion has no clue of mac address, so i doubt that was what was being referred to. I've also kept tasmota on and never wanted to revert that, so I don't know the answer. But maybe it's that firmware that was being referred to.

[Ulrar]

Hi,

I've tried flashing my new NSPanel with both the generic tasmota and the nspanel specific one through the web installer just now, and got the same behavior on both.
I get a boot loop, with this repeating :

ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DOUT, clock div:2
load:0x3fff0030,len:184
load:0x40078000,len:12352
load:0x40080400,len:2912
entry 0x400805c4

00:00:00.002 HDW: ESP32-D0WD-V3 
00:00:00.016 UFS: FlashFS mounted with 312 kB free
00:00:00.022 CFG: Loaded from NVS, Count 2
00:00:00.025 FRC: Some settings have been reset (2)
00:00:00.102 BRY: Berry initialized, RAM used=3930 bytes
00:00:00.125 Project tasmota - Tasmota Version 11.0.0(tasmota)-2_0_2_2(2022-02-12T14:14:12)
00:00:00.233 WIF: WifiManager active for 3 minutes

Any idea what could be causing this ? Same behavior when using ESPHome too, it reboots with no info as soon as it tries setting up wifi.

[Jason2866]

This is the standard Tasmota behaviour. NO bootloop. You can connect to Tasmota AP under IP 192.168.1.4

[Ulrar]

Sorry I could have been clearer, that message repeats endlessly immediately, not every three minutes.
It takes about a second for it to get to that state then repeat. I also don't see a new network pop up, but that's not surprising since it doesn't stay on wifimanager at all

[Jason2866]

Can not reproduce

13:11:25.287 CMD: reset 1
13:11:25.297 MQT: stat/sonoff-362330/RESULT = {"Reset":"Reset and Restarting"}
13:11:26.282 CFG: Use defaults
13:11:29.047 APP: Restarting
ets Jun  8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:344
load:0x40078000,len:13064
load:0x40080400,len:3484
entry 0x400805d0

00:00:00.002 HDW: ESP32-D0WDQ6 
00:00:00.106 UFS: FlashFS mounted with 280 kB free
00:00:00.146 CFG: Loaded from File, Count 2
00:00:00.155 QPC: Reset
00:00:00.297 BRY: Berry initialized, RAM used=4153 bytes
00:00:00.320 Project tasmota - Tasmota Version 11.0.0.4(tasmota)-2_0_2_1(2022-03-15T21:08:24)
00:00:00.889 WIF: WifiManager active for 3 minutes
00:00:01.521 HTP: Web server active on tasmota-362330-0816 with IP address 192.168.4.1
00:02:17.543 WIF: Connecting to AP Jason_Home_WLAN as tasmota-362330-0816 ...
00:02:27.022 WIF: Connect failed with AP timeout
00:02:48.700 WIF: Connecting to AP Jason_Home_WLAN as tasmota-362330-0816 ...
00:02:59.880 WIF: SSId1 Jason_Home_WLAN: Connected - IP Address 192.168.2.159
00:03:14.410 APP: Restarting
ets Jun  8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:344
load:0x40078000,len:13064
load:0x40080400,len:3484
entry 0x400805d0

00:00:00.002 HDW: ESP32-D0WDQ6 
00:00:00.156 UFS: FlashFS mounted with 280 kB free
00:00:00.251 CFG: Loaded from File, Count 5
00:00:00.267 QPC: Count 1
00:00:00.580 BRY: Berry initialized, RAM used=4153 bytes
00:00:00.607 Project tasmota - Tasmota Version 11.0.0.4(tasmota)-2_0_2_1(2022-03-15T21:08:24)
00:00:01.378 WIF: Connecting to AP1 Jason_Home_WLAN in mode 11n as tasmota-362330-0816...
00:00:04.510 QPC: Reset
00:00:06.607 WIF: Connect failed with AP timeout
00:00:07.446 WIF: Connecting to AP1 Jason_Home_WLAN in mode 11n as tasmota-362330-0816...
00:00:15.013 WIF: Connected
13:15:09.214 HTP: Web server active on tasmota-362330-0816 with IP address 192.168.2.159
13:15:10.229 RSL: INFO1 = {"Info1":{"Module":"ESP32-DevKit","Version":"11.0.0.4(tasmota)","FallbackTopic":"cmnd/DVES_362330_fb/","GroupTopic":"cmnd/tasmotas/"}}
13:15:10.243 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-362330-0816","IPAddress":"192.168.2.159"}}
13:15:10.246 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":3}}
13:15:15.109 RSL: STATE = {"Time":"2022-03-16T13:15:15","Uptime":"0T00:00:24","UptimeSec":24,"Heap":158,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":24,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":45},"Wifi":{"AP":1,"SSId":"Jason_Home_WLAN","BSSId":"88:C3:97:B1:1D:56","Channel":4,"Mode":"11n","RSSI":66,"Signal":-67,"LinkCount":1,"Downtime":"0T00:00:17"}}
13:15:15.137 RSL: SENSOR = {"Time":"2022-03-16T13:15:15","ESP32":{"Temperature":56.7},"TempUnit":"C"}

[Jason2866]

Tested the NSPanel firmware with a ESP32 since i do not have the NSPanel

[Ulrar]

Right, there's probably something wrong with mine but I don't know what. I can flash it all I want but everything just restarts when getting to the wifi step, could it be defective ?

[Jason2866]

Have you assembled the device and powering via mains? If yes the device is defect. If no do that.

[Westcott1]

Yes, you get this boot loop if just powering the ESP32 with 3.3v and the Nextion ribbon cable disconnected.
Either re-assemble, or power with 5V through the 8-pin header with the panel connected.

[Ulrar]

I couldn't try it in wall because sadly I have no neutral wires anywhere, I'll have to get an electrician in.
But I figured it, my serial adapters 5v mode doesn't quite get there and only outputs 4.9v, which isn't enough. I swapped it for a proper breadboard power supply in 5v mode and it all booted up cleanly, that was it.
Thanks for the help ! Now to try and find an electrician that isn't all booked up for 3 months

[charlesmerlen]

Hello, I've Tasmotarised my NSPANEL (EU) and somebody have the original .hmi file to understand how it's made on the Nextion Editor ?
I need to change the Date Format due to use dd/mm in France.

Cheers

[sfromis]

Did you check my suggestion shortly after you asked on Discord?

[charlesmerlen]

Yes, I've tried to swap value and as you see, it isn't correct. I need to find the original HMI project to change the date format.

[rbswift]

Did you check my suggestion shortly after you asked on Discord?

What was your suggestion on Discord please? I'd like to do the same for Australia

[sfromis]

My suggestion did not appear to work.
https://discord.com/channels/479389167382691863/800751039283200050/955765294624833566