NSPanel Pro V4.0.7 Optimized Version Released

No the mini R4 m extreme

Hi,

Why don’t you allow the possibility of adding a shortcut to an application from the NsPanel 120 interface that we installed ourselves (adb mode activated)?

And to launch automatically at startup by putting the interface of your application in screensaver.?

Same thing, the update was blocked because, OK, we opened ADB mode, which is ridiculous. We lose the warranty, OK, we accept it, but blocking updates…

Many more people would buy it.

Hey, I get the frustration, but let’s clear up a few things before we start redesigning Android from the screensaver menu.

NSPanel Pro isn’t a general-purpose tablet. It’s a purpose-built embedded device with a tightly controlled UI layer. Expecting it to behave like a full Android launcher with shortcuts, custom screensavers, and startup app injection is like asking your microwave to run Spotify because it technically has a clock.

ADB mode gives you low-level access, yes! But it’s a developer/debugging tool, not a magic wand :magic_wand: Once you enable it, you’re stepping outside the supported ecosystem. Blocking OTA updates after ADB is not ā€œridiculousā€ - it’s standard practice to prevent firmware mismatches, bricked devices, and support nightmares.

As for launching your own app as a screensaver: that would require replacing core system services, modifying intent handling, and possibly rewriting parts of SystemUI. It’s not about ā€œpermissionā€, it’s about architecture.

NSPanel isn’t locking you out. It’s just not designed to be a playground for launcher experiments. If you want full control, root it, fork it, or build your own firmware. Just don’t expect OTA updates to play along once you’ve gone off-road.

With that in mind, maybe ease off the steam a bit and don’t take it out on the NSPanel Pro developers. It’s not helpful and doesn’t lead anywhere productive. Thank you very much.

2 Likes

I’m very relaxed my friend, everything works very well even rooted!

1 Like

Hello,

What is the reason why the reported problem has not been fixed despite several updates being released?
Current versions are:
App version: V 4.0.10
Os version: 4.0.7
Cube version: 1.13.0

Thank You!

Which one exactly?

Hi, I would like to test new version. Can you add my device to OTA update list?

Device id: 1002139de8

Thank you @LMX and @MichaelLearnsToCode, for rolling out the update to my device - I’m now running v4.0.10/4.0.11 on my NSPanel Pro 86!

The update process was impressively smooth and fast, with absolutely no issues or errors. All my settings and Zigbee sub-devices remained intact, which was a pleasant surprise. I was able to install and set up Home Assistant immediately and without any problems. Overall, very positive experience - though I do have a few questions and observations:

Launching installed apps:
At the moment, it seems I can only open an installed app (e.g., Home Assistant) by going to F-Droid > Manage installed apps > Home Assistant > Open. Is there a quicker or more direct way to launch apps? Ideally, I’d love to open Home Assistant (or any other installed app) directly from the main UI.

Screen timeout while running Home Assistant:
My NSPanel is set to turn off its screen after 30 seconds of inactivity, but while Home Assistant is running, the screen stays on indefinitely. Is there a setting or workaround to make the screen timeout apply while running apps?

Proximity sensor behavior:
I know the NSPanel Pro has a proximity sensor - and I always assumed it would wake the screen when someone is in front of it. This didn’t work for me in v3.x. Will this feature be implemented in v4.x, or is there another app or setting that enables this behavior?

Accessing the dropdown menu while running other apps:
When using apps like Home Assistant, I can’t access the NSPanel’s dropdown menu without exiting the app. Is there a gesture or shortcut that allows opening the menu from within other apps?

Auto-starting Home Assistant:
Is there a way to make Home Assistant start automatically after a reboot?

The eWeLink crew is currently off-duty, probably sipping something cold and ignoring bug reports. So I’ll jump in and tackle your question set. Not to play the know-it-all card, but these points have already done a few laps around the forum.

Yes, the devs are aware of the quirks and hiccups you mentioned. Improvements are in the works, so patience is key - cheering from the sidelines is optional but encouraged. Versions 4.2 and 4.3 are on the roadmap for this year. Meanwhile, 4.1 will likely get a few more updates, just enough for us to grumble and sigh like proper users.

For deeper insights and official wisdom, Monday should bring someone with a badge and answers. Until then, consider this your unofficial but well-meaning dispatch. Regards! :smiling_face_with_sunglasses:

Thanks for all the work you guys are doing on the firmware :slight_smile:

Just some quick questions:

  • Is there any place where changelogs for these updates can be found? 4.0.10 exists, but I can only seem to find release notes for 4.0.7. Even an API endpoint with release manifests would be useful to know so I don’t have to scroll through this forum thread each time :stuck_out_tongue:
  • Are there any plans to upgrade the Android version? I asked SONOFF about a year ago as panels are currently on Android 8 IIRC which is a huge security issue given they’re on WiFi and connected to the cloud, and they mentioned it was being worked on. There’s plenty of work being done on projects like LineageOS to keep older devices supported that could be piggy-backed off of

Hi! Please add 10023a8964

We will publish our roadmap for v4.1.0 , v4.2.0 , v4.3.0 , v4.4.0 tomorrow (Saturday).

The promise has been fulfilled. Even though it’s Sunday in China now.

Thanks for your quick and detailed answer! I can’t wait for v4.2 which seems to fit all my needs for a HA wall panel…

Will you post the roadmap in this thread?

Please refer to NSPanel Pro Roadmap and Co-Created Future for details.

Fully agreed. We will get it done in v4.2.0 firmware which will be released on December 8th, 2025.

Please check out NSPanel Pro Roadmap and Co-Created Future.

Thank you very much for your kind recognition.

Launching installed apps:
Screen timeout while running Home Assistant:
Proximity sensor behavior:
Accessing the dropdown menu while running other apps:

I think above questions have been anwsered in NSPanel Pro Roadmap and Co-Created Future.

Auto-starting Home Assistant:
Is there a way to make Home Assistant start automatically after a reboot?

Yes, you can set Home Assistant companion app as the Home App, aka Launcher right in Home Assistant companion app, just go to Settings -> Companion app -> enable "Allow as home app" -> "Change home app" to Home Assistant. But doing so before v4.2.0 firmware will lose all the goodies NSPanelPro App provides, such as Zigbee hub or router, eWeLink-Remote gateway.

Please can you add my devices?

  • 10023a861d

  • 10026d1c03

Thanks a lot!

Thank you very much for your interest in NSPanel Pro.

We were too busy to develop v4.0.0 firmware and later fix it through v4.0.1~v4.0.10 :sweat_smile: so we haven’t published formal release note. From the feature set point of view, v4.0.x firmware is basically the same as v3.x firmware. One could even argue, v4.0.x firmware lacks several major features of v3.x firmware, for example, Web Shortcuts, Open API.

If you are curious where NSPanel Pro is headed, please take a look at NSPanel Pro Roadmap and Co-Created Future.

Are there any plans to upgrade the Android version? I asked SONOFF about a year ago as panels are currently on Android 8 IIRC which is a huge security issue given they’re on WiFi and connected to the cloud, and they mentioned it was being worked on. There’s plenty of work being done on projects like LineageOS to keep older devices supported that could be piggy-backed off of

The current plan regarding the underlying Android 8.1 OS is to open source it. After that, we may try to upgrade to newer Android OS. But Android OS is a huge system, and we rely on SoC vendors to provide necessary support. Most of the time, we have to use new generation of SoCs to run newer Android OS.

LineageOS is great. I love it, and I am using it. But as you can see on device pages (for example, Xiaomi Mi 8 Lite) of LineageOS, many devices have lost the opportunity to further upgrade due to the lack of support from SoC vendors.

3 Likes

Hey everyone,

I would also like to be added to the list :slight_smile:
Here is my device ID:
10025b2e47

The problems have not ended since I first bought the product. I use the NSPanel86PB model. Version 4.0. I have to restart every day since X was passed. In versions 4.0.6 and 4.0.7, there is a high CPU usage problem after a certain period of time. The panel is not used and no sub-products become inaccessible. After about 12 13 hours, the panel CPU has a problem with rising and it does not improve without cutting off the electricity and turning it on, I have to cut off the electricity of my house.

Still 4.0 10 stuck after 14-16 hours.

@lucian.sander @roberto.foroncelli @faritmf @jgardzinsky Hi, a new version 4.0.x has been deployed to your device. Please go to Settings > About to refresh and obtain the latest version. If you encounter any issues, feel free to contact us.

You’re using NSPanel Pro with firmware 4.0.x and claim that CPU usage spikes after 12–16 hours of inactivity, making Zigbee devices inaccessible. The only fix, apparently, is cutting power to the entire house - which feels more theatrical than diagnostic.

No logs, no rollback attempts, no structured testing. ā€œX was passedā€ remains undefined, and the dramatic framing overshadows any technical insight. If you want help, start with reproducible symptoms and actual data. Otherwise, this reads more like a firmware exorcism than a troubleshooting report.

1 Like