I have an error message of Fdroid crashing. The good thing is my NS Panel Pro 120 accepts reboots from Ewelink App, the challenge is the reboots are not fixing the problems. Please assist. Device ID: 10023a8cee
Hi, our development team is still reviewing the logs. To help them investigate more effectively, could you clarify a few details about the situation?
- Before the issue occurred, did you perform any specific operations, install new applications, or modify any configurations?
- Have you tried power-cycling the device (unplug and restart), and did that have any effect?
Hi, we have released version 4.2.2 to address this issue. Please check for updates and upgrade to the latest version. If you encounter any problems, feel free to contact us at any time.
Hello, I did not install any applications. I power cycled numerous times without success.
I have opted to reset the NS Panel Pro 120. By the way it is on version 4.1.5 as its out current firmware.
One small bug I noticed ⌠if I try to setup a security code to disarm the alarm on the NS Panel 120 Firmware version 4.22 it does not accept a number starting with 0. So for example if I type 0989 it takes it but simply accepts it as 989
Thank you for your feedback and for bringing this issue to our attention. We will work on fixing it as soon as possible.
Sorry for the issue. Could you please submit a log on the NSPanel Pro device through Top drop-down menu -> Settings -> About -> Feedback -> Submit, and could you also send me the Device ID of your NSPanel Pro?
What exactly are you hoping to achieve this way? The NSPanel Pro isnât an actuator, and Matter doesnât currently support control panels, so it doesnât really make sense . Itâs a bit like trying to register a bicycle as a car: you can give it a go, but nothing useful will come out of it.
When it comes to a control panel, Matter standard simply doesnât define such a role, whereas Home Assistant or eWeLink (CUBE) do, so thatâs where this kind of device actually fits.
I would.like to use the Pro 120 as an alarm control panel that can be used by those who have no direct access to Home Assistant.
The 120 is still not exposing its sensors to Home Aassistant. If I could use matter perhaps I can expose the sensors.
If eWeLink adds native support, Matter will be able to use it - but only within the limits of what the Matter standard actually defines. And hereâs the key point: Matter does not define any role for a control panel or an alarm keypad, so even with native implementation the NSPanel Pro will not become a âMatter alarm keypadâ.
- Sensors: Yes, but only the types that Matter supports. But the NSPanel Pro doesnât actually contain any of those standard Matter sensor types that map to existing Matter sensor roles.
- Panel functions: No, because Matter doesnât support them. Matter has no device category for: control panels, alarm keypads, touchscreen interfaces or general UI devices. So even with native Matter support, the NSPanel Pro will not become: an alarm keypad, an alarm control unit or a UI device in Matter.
Summary:
Yes â native Matter clusters for supported sensor types would make them visible in Home Assistant.
No â Matter cannot turn NSPanel Pro into an alarm control panel, because the standard simply doesnât define such a role.
I saw this nice message on the screen at least 5 times yesterday.
Iâm on version 4.2.2 and it seems this has been successfully fixed.
I have one issue here, potentially with NSPanel Pro 4.2.2.
I use TRVZB valves, one connected to Zigbee bridge (ZBBridge-P, v.2.8.0) and others four to NSPanel.
The one valve connected to ZBB is succesfully updated to v.1.4.1
Others connected do NSPanel are on v. 1.3.0, they report version 1.4.1 available (in eWeLink 5.21, iOS). Once I click âUpdate Nowâ, press âconfirmâ, it says âSuccessâ in 2-3 seconds, but nothing happens.
The only reason I can think of is NS Panel Pro does not send update to valves.
I apologize for this issue. The problem has been addressed in version 4.2.2, which was released on December 17th. This version is currently in internal testing. If you would like to install it, please join the beta program to get the latest build. Alternatively, if you agree, I can directly enroll your device in the beta program for you.
Had identical issue with 6x trzvb and nspanel. After upgrading to 4.2.2, 5 successfully updated, the last one I re-paired, checked for updates through eWeLink Web and after while the last one also updated successfully.
The 120 is still not exposing its sensors to Home Aassistant. If I could use matter perhaps I can expose the sensors.
v4.3.0 will support this feature, please bear with us and wait for approximately three weeks.
OK, my mistake. I tought I have 4.2.2, but there was only update waiting to be installed - as I switched auto-download to off. Updated to 4.2.2 and it is working! Thanks.
This is good news.