I suggest that items in screens can be pinned to prevent the order from breaking up due to newspaper items.
Synchronization of areas with NSPP to other NSPP. We have not found any errors yet
4.6.0 Firmware feels smoother. I like the local web control of the NSPanel devices !
I would like to report a bug: i have 2 NSPanels PRO in same house, and the local hostname has been automatically set the same for both https://nspanelpro.local .
A possibility to edit the hostname for each device would be great, and also to implement a variable for simmilar devices, if 2 devices have the same name it adds a number on next one like nspanelpro.local and second one to be nspanelpro2.local .
Device: SNZB-05P, SNZB-03P, SONOFF SNZB-02P ,SNZB-02LD and SNZB-02LD I can’t update it or check if there are updates. It ends with an error, as you can see in the picture.
The problem is with all battery-powered devices.
After this update, it successfully ignores the scene like:
It should have stopped cooling the house 2 hours before sunset; if I hadn’t turned it off, it would still be cooling the house.
https://nspanelpro.local works but I have 3 devices in the house, how do I connect to the rest?
NSPP ID: 1002b3b969
This is a common problem for me too, it normally turns on the LED strip whenever it wants, ignoring scenes. I sent them the logs, hopefully they will fix it as soon as possible.
I set the smart security. I added the trigger device to the Away mode. If it is disarmed it won’t alarm when I open the door. But is still a bug that without setting it also triggers the sercurity.
Hi, is this the type of alarm notification you are seeing?
If so, this notification is triggered when the status of a sub-device changes. You can tap the sub-device card, then go to Notification Management to change the notification method or turn it off.
If this is not the alarm you are referring to, please take a photo of the alert you encountered and send it to me so I can check it.
The stability has improved, and the overall responsiveness is much better. In general, you’ve made significant improvements to the product.
In the web interface, the main feature I’m still missing is the ability to directly control paired device.
So far, I haven’t found any other bugs.
@Jojkoba @Derex At the moment, you can access each device’s web page using either nspanelpro-{device_id}.local or its IP address. This means that each device already has its own unique access address.
That said, your suggestion is a good one. We could consider allowing users to customize the hostname to something more meaningful. I’ll record this as a feature request for our team to evaluate.
Thanks again for the great suggestion!
This message usually appears because the device is in sleep mode. Before starting the OTA update, you’ll need to wake the device manually. After waking it up, the update should proceed normally. Did the OTA update work after you woke the device?
Regarding the issue you mentioned where the scene did not run after the sub-device was updated: I checked the logs and found that the sunset scene was triggered at around 5:50 PM (local time). Could you please check the logs for that scene to see if there is a corresponding record? If there isn’t any record at all, please let me know and I’ll continue investigating.
I can’t answer that, as I have everything up to date. It might be worth considering a feature that automatically updates the devices immediately after waking them up
I don’t know what happened, the heat pump remained on even after the time limit. There is a possibility that it was updated at the time it was supposed to turn off. Since the scheduler you have doesn’t check back to see if the task is completed, it didn’t turn it of.
Where can I find a changelog for this new release?
I tried to import devices from Home Assistant to the NSPanel Pro so I could export them to Matter.
However, the authorization process fails because my Home Assistant instance uses two-factor authentication (2FA). Authentication requires both a username/password and a TOTP (Time-Based One-Time Password) code, but the NSPanel Pro only appears to support username and password authentication and does not provide a way to enter the TOTP code.
As a result, I am unable to authorize the connection and import my Home Assistant devices.
You’ll find the update notes in the eWeLink app, although they’re kept fairly brief.
- Added local web access.
- Expanded compatibility with Zigbee sensor types.
- Fixed some known issues.
For the full release notes, please refer to this forum post. My colleague updates it with the detailed changelog for each new version.
Hi, I did some testing on my side and confirmed that it’s possible to enter the TOTP code even when 2FA is enabled. I recorded a short video showing the complete process, so please take a look.
If you’re still experiencing the issue, you can also send me the specific details of what you’re seeing, and I’ll investigate it further.
thank you , it works for me
You can probably overcome this by making the NSPanel a trusted user in HA. I think this negates the need for 2FA for the panel login only