When I did my first connection to the NSPanel to internet the update file was downloaded in the root folder. You need to copy that file to a computer and later do the update.
The sonoff will request to reboot when the download is done, that is the moment to extract the update.zip.
I manage to factory reset(by switching on and off for 5 times) multiple times but every time I end up with same firmware 2.1. Is there anything else I can do to downgrade the firmware?
I did a “5 x boot-to-animation” factory reset (do this 5 timer: power up until Sonoff logo animates, unplug and plug in again). Thanks to @alexmpp for mentioning that. I was given version 1.7 after my factory reset.
After decompressing the xposed framework tar (the tar -xvf xposed-v90-sdk27-arm64-beta3.tar command) I deleted the xposed-v90-sdk27-arm64-beta3.tar from the touchscreen’s Download directory. I used the File Explorer app but you can do it from the command line.
After running the flash-script.sh install script I got the expected success message
************************************
Xposed Framework installer zip
************************************
- Mounting /system and /vendor read-write
- Checking environment
Xposed version: 90-beta3
Android version: 8.1 / SDK27
Platform: arm64
- Placing files
- Done
************************************
The first boot will take longer than
usual, please wait a few minutes.
************************************
I have updated webview, and installed companion app,
Everything works great.
I have one problem though - and that is the screen never goes to sleep.
i first thought it was the nspanelTools, but even though i disabled that - it still doesnt go to sleep.
under display settings advanced i have set it to 15 seconds.
i can “trigger” it by sending the power_off key via an ADB command
but i would really like for it to simply turn of the screen when it’s not in use.
please notice that i did remove some of the standard apps - so i dont now if that is part of the reason.
I am looking at getting one or two of these to use as HA dashboards for bedrooms where there is a fair amount to control per room.
The thread is fairly confusing, however am I right in thinking this method should still work with devices that are purchased today? Or have Sonoff now locked the device down so it’s not possible?
do you have a step by step guide how to upgrade the firmware as I can connect to the unit via adb but then how do you upload the new firmware as I am stuck on 1.5 would like just to put it back to stock firmware
Since I seen a few questions about firmware updates after enabling developer mode, I thought I share, since I managed to do this successfully using seaky’s root tool today
Sonoff firmware V2.2.0 (10-nov-2023) and V2.0.0 (12-sep-2023) added Zigbee router mode and Matter support:
Support switching NSPanel Pro from Zigbee gateway mode to Zigbee router mode. Click ‘Device Settings–Pilot Features–Zigbee Mode’ in the APP to enable Zigbee router mode. After switching to a Zigbee router, you need to bind it with other gateways.
Supports as a Matter hub to add Matter-enabled devices to the eWeLink App. Currently supports switches and plugs.
@seaky does not recommend to upgrade firmware above 1.5.0 because Sonoff removed a tons of usefully binaries from system folder. However, with the new functionality introduced by Sonoff, I’m wondering if it would be possible to combine the best of both worlds (HA companion app + the zigbee router/matter functionality) OR is better to stay with version 1.5.0?
I Have a New NSPanel Pro and I update the firmware to 2.20 I cant connect to the panel adb wireless
( GitHub - j-a-n/lovelace-wallpanel: 🖼️ Wall panel mode and photo screensaver for your Home Assistant Dashboards)
and also have an issue with usb connection (i can see the device in the windows device manager)
but when i type the command “adb devices -l” i’m getting “List of devices attachd” with no other details.
" D:\adb>adb devices -l"
List of devices attached
I Have a New NSPanel Pro and I update the firmware to 2.20 I cant connect to the panel adb wireless
D:\adb>adb connect 192.168.1.227
cannot connect to 192.168.1.227:5555: No connection could be made because the target machine actively refused it. (10061)
and also have an issue with usb connection (i can see the device in the windows device manager)
but when i type the command
“adb devices -l”
I’m getting the following:
Hello, how did you do that ? Activating it through eWeLink app by hitting Device ID 8x asks to enable Developer Options, but confirming that does not seem to unlock the panel anyway and I still hit the wall with connections being actively refused. No luck via usb either as adb device is not listed despite being seen in Device Manager as px30_evb. Any hints, please ?