Thanks for the update. Are there any plans on updating Android on the 120-type anytime this year?
Yes, we have plans to launch the new version of the 120-type in 2026.
1 Like
Sorry for the late reply. I conducted a test and encountered the same issue you described. This may be related to the NSPanelPro’s system. Please allow me some time to investigate further. Thank you for your understanding.
Microphone and speaker capabilities will be enabled in version 4.4.0 (scheduled for February 9th), supporting their use within Home Assistant.
Why is it that when I synchronize the TRVZB with Apple Home via the NSPanel Pro Matter hub (4.3.3), they appear both as valves and as switches, as if they were two separate devices? Is there a solution to this?
Hi @Milk , I have submitted feedback log yesterday in the late evening. Than I switched Display - Auto-Lock to “Never” (was 5 min) and Screen Saver is also Off. It solved the issue. Will add printscreens from eWeLink app.
Hope it helps (Device ID: 10022022ca)
Btw, panel is in the bedroom, so it is not the best solution. But at least, it is solution for days when I am not on site.
Could you please provide specific screenshots, the NSPanelPro device ID, and the logs(Top drop-down menu → Settings → About → Feedback → Submi) to me? I will check them ASAP.
I played around with some features of the API with v4.3.3. Playing RTSP stream triggered by API seems not to work (NSPanel Pro API). I got always a “404 Not Found” as response.
No matter what I send as the request body, I always get a 404. Other API calls are working fine. I haven’t tried this API call before updating to v4.3.3, so I don’t know if it is working in earlier versions.
Anyone else ever tried this API function?
I tried it as well, with exactly the same results you had. I even gave Matter a shot — it technically worked, but with the protocol’s limitations it was… let’s say, only marginally useful. Then I focused on MQTT and somehow survived three iterations of their ‘development’ firmware. Unfortunately, the dev team never really got a handle on things. Add to that a variety of charming little Zigbee stack issues, and the whole process dragged on unbearably long. It really feels like their ambitions outgrew the team’s actual capabilities. I’m still rooting for them and I’ll keep an eye on their progress, but personally I’m done. Enough is enough.
In the end I gave up, moved the TRVZB over to ZHA, and dismantled the NSPP entirely. It’s now heading into the hands of a representative of the younger generation of IoT enthusiasts. Let him struggle with it for a while.
1 Like
Does version 4.3.3 still have Zigbee sub-device offline issues? I will check the logs ASAP to identify the cause.
Yes im doing another log for u now it happendvagain when I wokup and wont reconnect my main nspanel lmk thanks only restarting it seems to fix thos but its amnoying….
Have u checked the issue with the slider not working for zigbee blinds saying they need to be set with a remote first I sent pictures a while ago about that?
every time i reboot nspanelpro , i get this error at home assistant , bearing in mind that i use the nspanelpro in zigbee router mode
Ya mine does that too probuably a bug does everything still work with mqtt?
yes nspanelpro still appearing at ha mqtt , also the paired as router
This device comes with a remote control. Before using it in the APP, you need to calibrate the remote control first.
Please locate the corresponding remote control and follow the instructions to set it up.
I have tried thier just ir remotes it makes no difference thier is no calibration on them to set
I have sent you a detailed tutorial via private message. Please check.
Really? How can anything be paired through MQTT?