Hi everyone, the latest beta update for NSPanel PRO has been released today. You have to enroll to the beta update again via NSPanel Pro Beta Testing Program .
I would like to see that this time, everyone will provide feedback about this update on a SINGLE TOPIC, could be this one. So we all can track the issues in one single place.
Can we have the changelog please @Milk ? And thank you for the update ! I bet you guys had a lot of work on it.
I will start with the first feedback about this BETA update, and i will provide more as i test:
There are 2 options now on the proximity sensor: Proximity Sensor & Wake on Proximity. - While activating both options i could see that the popping (click) sound is still happening while approaching to the panel (when proximity is triggered)
When on firmware 4.4.6 and performing a device factory reset, it reverts back to 4.4.0 . Before when reseting it was staying on the same version.
Thank you very much for creating this dedicated thread to discuss the issues with version 4.4.6. We also truly appreciate your understanding and support for our team.
This was an oversight on our part. The fix for this issue was planned for version 4.4.6, but the finalized code was unfortunately not merged into this release. If you don’t mind, you can temporarily turn off the system touch sounds. Alternatively, we can deploy a dedicated hotfix version for everyone to address this specific problem.
Since we performed a firmware upgrade starting from version 4.4.0, performing a factory reset will no longer revert the device to a version prior to 4.4.0.
If you encounter any other issues, please feel free to point them out here. We will do our best to investigate and address them as quickly as possible.
Regarding Scene Switch R5 - repaired it again, set scenes and it still sends “fantom” button presses. So it switches lights on its own. I hade to press Ch6 at the and, which does nothing, but you can still see “presses” through the night. log send.
Do you mean that the logs for clicking on channel 6 on the page were all triggered automatically by the device itself, and no one actually clicked on it?
Hi, I’ve checked the logs. This issue occurs because when the NSPanel Pro goes offline and then comes back online, it re-reports the current status of the R5 device. This is being interpreted as a button press, which results in extra entries in the log and unintended scene triggers. The problem is related to the R5 device, and we’re still working on it. I’ll update you as soon as we have a resolution.
OK, thank you. I can confirm that in recent days my wifi connectivity (rulal area) seems unreilable. But had no time to investigate where the issue is.
Anyway, IMHO the communication protocol should be able to handle dropouts like this, so my setup is actually a great testing ground for your investigation.
1.I cannot sync NSpanel pro itself to HomeAssistant/Mqtt，the reason may be there is no Zigbee sub devices. But I need to control panel from hass, light on the screen by human sensor. 2. When add a Scene in the ewelink app， in the action part， if I chose to NsPanel Pro to show video， cannot select my RTSP camera. (device id 100208599d).
Hi, if there are no sub-devices under the NSPanel Pro, you can still control the NSPanel Pro’s own capabilities after connecting it to Home Assistant (as shown in the image). Regarding the presence sensor you mentioned — I’m not sure if you meant that you want the NSPanel Pro screen to light up automatically when someone approaches. If that’s the case, you can enable the wake‑on‑Proximity feature.
For RTSP, please try playing the stream again. If it fails, promptly submit the NSPanel Pro logs (I’ll check them as soon as possible). You can also try downloading VLC from F‑Droid and entering the RTSP address to see if it plays properly.
You are not alone. I too are getting random presses from my R5W switch 3 single press that sets off a scene that turns on all the outside lights in the middle of the night when I’m asleep. Shows in the logs but no one pressed the switch.
