that bug will be fixed today
Hello Everyone,
I managed to flash the NSpanel with the version mentioned in Blakadder’s tutorial but unfortunately, it seems that the temperature sensor is showing unrealistic values (while the temp sensor was working correctly on sonoff firmware).
Thanks again Blakdder for your amazing work!
For those having trouble displaying the widgets on their screen after 2 days of headaches, I found a workaround.
I first followed the instructions here:
Sonoff NSPanel Touch Display Switch (E32-MSW-NX) Configuration for Tasmota
and downloaded the firmware called tasmota32-nspanel.bin from there as well.
But it seems that this firmware is not compatible with the Sonoff NSPanel Tasmota driver v0.46.1. When downgrading to version 10.1.0 using tasmota32.bin from github everything was solved and the driver is working as it should.
Best regards,
Florian
My Kickstarter EU version arrived today…time to get flashing 
I just flashed mine today an have the same results. I have the US version if that makes any difference. I’ll dig into the problem a little. Wanted you to know you’re not alone.
Received it today but should the time update automatically or do i need to send some commands?
Just found out that indeed the latest version not working i have installed 10.0.0.1 and its working
1 Like
How are we suposed to use this code ?
Thanks for the work.
If you’re familiar with ESPHome and the rest of the things you need to use a custom Nextion TFT file, then the only magic here is adding:
external_components:
- source: github://pr#2956
components: ["nextion"]
to your configuration to pull in the updated code.
If you want more detailed instructions, hang on a little bit, I’m in the process of putting together a video.
9 Likes
Can you send link to working version ? 
tasmota-nspanel.bin is now using the correct build options and should work correctly with any version of nspanel.be
3 Likes
It works, thanks a lot Analog1 Temp is not correct, it shows 3.3C, any solution for that ?
Has anyone experienced issues flashing Tasmota onto the nspanel?
I’ve tried a number of times today with no luck.
- Flash using ESP-Flasher (Also tried with Tasmota Web Installer) both are successful.
Attempted to flash tasmota32.bin and tasmota-nspanel.bin - Disconnect UART and reattach screen to back plate
- Connect to Mains Power
- Connect to tasmota ssid
- Browse to http://192.168.4.1
- NSPanel Crashes and reboots (SSID vanishes for a few seconds)
If I do not attempt to load http://192.168.4.1, I am able to continuously ping the device with no issues.
I have also flashed the device using my Bench powersupply incase the USB-Serial was not strong enough. Flashing always shows as successful.
Any ideas what I am missing?
I had the same. I have four switches. It took various attempts per switch before I could login. eventually it worked. I tried logging in using my phone. This had most succes for the last two. I think it might be an issue with available memory since every now and then the interface loaded only half. Another thing I noticed is that sometimes waiting helped and the interface became visible after maybe 30-45 seconds. Keep trying 
Thanks @phaeton, I’ll keep persevering.
I have 19 Devices running Tasmota but this has been the most painful so far. (Its also the first ESP32 device that I purchased)
Same here: this was the most painfull one. I’m now playing with one of the panels and it’s stable and the GUI is stable once included in my network
If you go to the Console on the NSPanel and input:
adcparam 2,12250,10000,3950
It should show the correct temp.
*Note: I did this through trial and error tweaking the numbers to match an external temp reading. US version.
3 Likes
Seem to be stuck in a reboot loop when flashing Tasmota to my NSPanel.
Attempted to flash latest tasmota32.bin, tasmota-nspanel.bin, tasmota32.bin (10.0.0)
@blakadder Would you mind casting your eye over the below serial output?
I am not familiar with the “under the hood” of ESP’s, but I am guessing that “CFG: Loaded, Count 0” is not right. But esp-flasher and esptool suggest that the flash was successful.
[23:04:08]rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[23:04:08]configsip: 0, SPIWP:0xee
[23:04:08]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[23:04:08]mode:DOUT, clock div:2
[23:04:08]load:0x3fff0018,len:4
[23:04:08]load:0x3fff001c,len:1044
[23:04:08]load:0x40078000,len:10124
[23:04:08]load:0x40080400,len:5828
[23:04:08]entry 0x400806a8
[23:04:09]00:00:00 CFG: Loaded, Count 0
[23:04:09]ets Jul 29 2019 12:21:46
[23:04:09]
[23:04:09]rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[23:04:09]configsip: 0, SPIWP:0xee
[23:04:09]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[23:04:09]mode:DOUT, clock div:2
[23:04:09]load:0x3fff0018,len:4
[23:04:09]load:0x3fff001c,len:1044
[23:04:09]load:0x40078000,len:10124
[23:04:09]load:0x40080400,len:5828
[23:04:09]entry 0x400806a8
[23:04:10]00:00:00 CFG: Loaded, Count 0
[23:04:10]ets Jul 29 2019 12:21:46
[23:04:10]
[23:04:10]rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[23:04:10]configsip: 0, SPIWP:0xee
[23:04:10]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[23:04:10]mode:DOUT, clock div:2
[23:04:10]load:0x3fff0018,len:4
[23:04:10]load:0x3fff001c,len:1044
[23:04:10]load:0x40078000,len:10124
[23:04:10]load:0x40080400,len:5828
[23:04:10]entry 0x400806a8
[23:04:11]00:00:00 CFG: Loaded, Count 0
[23:04:11]ets Jul 29 2019 12:21:46
[23:04:11]
[23:04:11]rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[23:04:11]configsip: 0, SPIWP:0xee
[23:04:11]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[23:04:11]mode:DOUT, clock div:2
[23:04:11]load:0x3fff0018,len:4
[23:04:11]load:0x3fff001c,len:1044
[23:04:11]load:0x40078000,len:10124
[23:04:11]load:0x40080400,len:5828
[23:04:11]entry 0x400806a8
[23:04:12]00:00:00 CFG: Loaded, Count 0
For me it was 2C off, but adjusted it a little and now it shows correctly I use EU version
adcparam 2,13470,10000,3950
Thanks a lot
1 Like