Ok, I solved the problem by enabling the beta features, now it’s updated to 4.3.0. Let’s hope it’s stable and doesn’t cause constant system crashes like version 4.1.5.
i switched the zigbee from router to hub mode , and it did factory reset even on 4.3.0
We have received your logs and will work on locating the issue ASAP.
Hi, Zigbee mode switching optimization requires the latest version of the eWeLink app, 5.22.1 (submitted for Android release on January 12, currently under review). If your phone runs Android, you should be able to upgrade to the latest version in about two days.
i did upgrade today the ewelink app , i will give it a try , btw on router mode im unable to pair with gateway , i reset the unit several times but still failing to pair , also i brought gateway near the unit but still cant be detected , what to do if you got any suggestion ?
My Pro 120 is also.stuck to 4.1.5, It displays that is the latest version.
Hi,
I’ve noticed the 4.3.0 release notes talk about a new feature to access the NSPanel speaker from HA.
What’s the procedure to do that?
Thanks
Good morning,
Unfortunately, this morning I noticed a bug whereby, once the heating program’s end time is reached—in my case, 8:30 AM with a target temperature of 20 degrees (which wasn’t reached)—the boiler actuator doesn’t switch to “off” but stays “on” despite the program ending at 8:30 AM, so it should turn off even without reaching the target. This bug was present before the update, and I circumvented it by using a scene. At 8:31 AM, if the temperature is less than or equal to 20, the actuator turns off. I recreated this scene, and nspanel pro started crashing repeatedly. I sent a feedback.
This is still happening in 4.3. The update didn’t keep the home app that was set up previously (I would say it’s a bug but easy to solve for the user). So the device did restart on the main interface
When setting the Home App from “Home Apps Settings” settings, the HA App is launched, I can see the device in the eWelink App.
I restart the device to be sure the HA App is launched at startup, then I don’t see the device online in the eWelink app (iOS). When I press the Assistive button, the Sonoff the Rubik logo are displayed (system startup ?), then the device is showed online in the eWelink App…
This behaviour is the same on two devices, I’ve got 3 more to test, I’ll keep you updated
The update status issue is solved after updating to 4.3, I think it was a bad update process (don’t remember from which version I updated to 4.2.2)
I think you can only access the speaker volume via MQTT.: there’s still no way for HA to get a media_player from MQTT (the protocol used to communicate between NSPanels and HA)…
You can use the Sonoff LAN custom integration to access the media_player (only with audio files uploaded on the device)… The media_player is a bit unstable: you have to use the devtools to play a sound once before it appear enabled 
1 Like
After switching to router mode, which gateway are you using to add the NSPanel Pro? Could you please submit the NSPanelPro logs from the device screen, and then send your device ID to me separately? Thank you!
Have you already joined the beta testing program to access the internal version? Alternatively, you can send me your device ID separately, and I can add your device to the whitelist to experience the latest version.
How to Apply
Follow these steps to join the Beta Test program:
- Visit the tool page: NSPanel Pro Beta Testing Program
- Log in using your eWeLink account.
- Select the NSPanel Pro device you wish to register.
- Read and accept the risk notice, then submit your application.
- Wait approximately 5 minutes, then go to your device’s
Settings -> About -> Software Updateto check for the latest firmware and install it.
I apologize for the issue. Could you please send your device ID to me separately? I will review the logs and work on locating the problem as soon as possible.
Hi, this relates to our previous discussion. You’ll need to first cancel your previous Home APP settings and set it back to NSPanelPro. Then, use NSPanelPro → APPS → Home APP to configure other applications. For details, please refer to this reply: NSPanel Pro v4.2.0 Officially Released: New Features & Enhancements - #131 by Milk
Regarding the optimization of this setting, we plan to explore new solutions in version 4.4.0, but a suitable approach has not been finalized yet. Thank you for your understanding.
Thanks so.much. I had always assumed that all my NS Panels were registered flr the Beta programme.
Hi @DamienCH
Starting from version v4.3.0, NSPanel Pro not only supports exporting its Zigbee devices to Home Assistant（v4.1.0 Supported ）, but can also export its own features (such as the speaker and ambient light sensor). Here are the specific steps:
- Configure MQTT Broker : Set up via the eWeLink App.
- Navigation Path :
eWeLink App > NSPanel Pro > Device Settings Page > Home Assistant - Sync Devices : Follow the instructions in the App to complete the MQTT Broker configuration. Once successful, NSPanel Pro will automatically sync to Home Assistant, and you can also select which Zigbee sub-devices to sync.
After a successful export, you can now view or control NSPanel Pro and its Zigbee devices within Home Assistant.
Thanks,
Also. Prior to this new version, I had screen sleep set and it was automatically sleeping the screen after like 5 min in HA.
Now it’s showing the clock instead. Is there something to do to still sleep the screen?
It doesn’t. You describe the add‑on as “native”, but in practice it’s just an MQTT bridge that pulls devices from the cloud and exposes them to Home Assistant via MQTT Discovery. It works reliably and follows HA standards, but it’s not a full integration on the level of ZHA, Z2M, ESPHome, or Shelly - everything still goes through an intermediate layer and depends on the cloud.
Please refer to this post for enabling Sleep and Screen saver: NSPanel F-Droid auto start HA - #4 by MichaelLearnsToCode
If you encounter any issue, please let me know.
Thanks,
So indeed it’s NSPanel Pro App selected (thus the clock), but I don’t see a way to actually sleep it instead of opening an app