Hi, I have mentioned the problems and thermostats several times and suggested solutions. Here I addressed the issue of why their scheduler does not work: BUGS HUNTER Part 2 ( That’s my assumption from a programmer’s perspective, only Sonoff knows if it’s a real situation ).
REALLY there are two problems, the first is that even if you turn on the cooling and the conditions are met, it will not do anything unless the thermometer sends new data. Apparently their thermostat processes the data that comes and not the data that it already has.
The second part ignores the settings and sometimes it does not turn off the heating/declaration even if the switch-off temperature is exceeded. There are cases that it also ignores the setting of the value for turning on the heating/cooling.
So far they have not been able to do anything about it. Because of this, CubeOS has to control my heating.
Could you please confirm whether you’re using a central thermostat, or a thermostat created within the eWeLink app?
If you’re using a central thermostat, please let me know the approximate time when the issue occurred, and I’ll check the logs for further investigation.
If you’re using a thermostat created in the eWeLink app, to avoid the logs being overwritten, please submit the logs as soon as possible after the issue occurs:
NSPanel Pro log:
Pull down from the top of the screen → Settings → About → Feedback → Submit
eWeLink App log:
Profile → Help & Feedback → Feedback → Submit Feedback → Make sure “Include Logs” is checked
Once the logs have been submitted, please let me know and I’ll take a closer look.
Hi, I’m using a couple of NSPanel Pro 120 units as the main hubs for managing Zigbee devices; specifically, one of them handles the heating system and several switches located in hard-to-reach places. When I updated to version 4.5.2, I was forced to reconnect all the devices and recreate all the scenes. A couple of days ago, I tried connecting an SNZB-01M to this NSPanel Pro, but it didn’t work properly (it reported a low battery and failed to detect button presses). I see there is a new version available for the NSPanel Pro—version 4.5.3—but I’m terrified to update because I don’t want to go through the nightmare I experienced a few days ago. Could you please explain why the SNZB-01M still doesn’t work on the NSPanel Pro—even though it works perfectly on the ZBBridge-Ultra—and also tell me what to expect from the 4.5.3 update? Are there any known issues that might make me decide against updating? Thanks.
When did you update to version 4.5.2? If it was within the past two days, I can check the logs to investigate why sub-devices required reconfiguration after the upgrade (this is not expected behavior).
The SNZB-01M should already be supported in 4.5.2. Please try re-adding it and then submit the NSPanel Pro logs. I will review them to identify the exact cause.
Regarding the 4.5.3 release notes (Optimizations & Bug Fixes):
Seamless Device Discovery: Improved the Auto Discovery process for Matter-compatible devices, providing a smoother user experience.
Enhanced Screen Management: You can now easily customize, reposition, or remove Matter devices and other locally configured devices across dedicated custom screens. Screen layouts can be freely arranged during setup without affecting the devices themselves.
Accurate Device Syncing: Fixed an issue where certain sub-device types were incorrectly identified. (This does not include SNZB-01M.)
I updated to version 4.5.2 on June 11th, and when I reported the issue to you, you confirmed it was a known bug in version 4.5.1 (which was the version I had updated to first). Now, with the update to version 4.5.3, I want to avoid running into known issues that could be disastrous for my setup. I can confirm that I tried connecting the SNZB-01M multiple times, but the result was always the same: it was recognized immediately, but a few moments later it was gone—disconnected. When I tried reconnecting it, it showed the battery as completely dead (even though it’s a new device), and it didn’t register any button presses. Because of this, I tried using the ZBBridge-U instead, and that works perfectly. Please let me know what else I can try.
Thanks.
Oh, sorry—I just remembered that this issue has already been resolved, so it will not occur in version 4.5.3.
Regarding the SNZB-01M, I can run some tests on my side. When convenient, please try adding it to the NSPanel Pro again. Once the issue occurs, submit the NSPanel Pro logs as soon as possible, and I’ll investigate the cause in detail.