It is not possible to make a call from an NSPP Gen2 to an NSPP, or vice versa.
Hi. Since this update the only local website the nspanel could access is its web management page. Any other page I try to access it redirects me to the webpage of this new feature..see the attached vid.
Why isn’t it possible to permanently enable SWV via NSPP? It turn off every 30 minutes.
Firmware 4.6.0 forces HTTPS on local IP in Webpages.
It breaks iHost/Cube OS CAST (ERR_CONNECTION_REFUSED). Please fix HTTP support.
Have you considered enabling direct access to CAST via the eWeLink app? My customers want CAST because of its clear interface and simplicity, whereas the eWeLink app is better suited for administrators.
Or perhaps a mobile app that provides access to CAST for NSPP?
Sorry for the inconvenience. We have identified this issue and are currently working on a fix.
In the meantime, please try adding the port number to the Webpages or Home Assistant address. We have verified that including the port number will not cause any connection issues.
Hi, could you please submit the NSPanel Pro logs as soon as possible? Also, would it be possible to record a short video showing your exact settings and the steps you are performing?
Please submit the NSPanel Pro logs as soon as possible (pull down the screen → Settings → About → Feedback → Submit). I will review them promptly.
According to ChatGPT, it’s a safety feature that shuts off the valve within 30 minutes if nothing is flowing through it.
Have you considered the possibility of implementing a CAST feature that allows for mobile connectivity? I am referring specifically to your web-based CASTs.
Actually, this feature is already supported in version 4.6.0. Before making a call, the devices need to be synchronized to each other’s split-screen layout.
I just tested it, and unfortunately it is not possible to directly call an NSPP120 from NSP Gen2. You need to tap the device card on the Gen2 device to initiate the call.
I will report this issue and work on improving the experience as soon as possible.
Oh, I referenced the wrong message earlier. Yes, SWV has its own security mode, which NSPanel Pro cannot support.
Regarding CAST, do you mean controlling SWV or NSPanel Pro through the eWeLink CAST app?
Controlling the NSPP via CAST let me explain. My customers (and others) have a simple CAST interface they can use to control the NSPP remotely. They find the eWeLink app inconvenient and view it merely as a service tool. While it is possible to log in to CAST via a web browser, that method isn’t optimized or practical, as it requires entering a password. The CAST app available on the Google store is designed for tablets; the goal is to simply tap the icon to log in CAST and then control the NSPP from there.
I checked sadly that the Basic gen 5 relay (BASIC-1GS) still not supported. When will it be?
It’s pretty sad that it doesn’t support new devices right away or at least won’t get an update within 1-2 months. We’re talking about a device that’s almost a year old.
It would be important, though, because in addition to the app, it would also be the main control center locally.
My HA is running at port 80..so this will not solve it..so I’ll wait for the update
Hi, this device is already planned for support in the mid-July release. Version 4.7.0 will add support for this device.
You mean eWeLink CAST, right? Currently, it is possible to control arming and disarming from CAST. However, the detailed configuration settings still need to be done through the eWeLink app or the web interface, mainly because CAST is designed as a control panel rather than a configuration tool.
Imean eWeLink CAST, and I think I may have written it incorrectly.
A simpler way to access eWeLink CAST so users can control the NSPP and their devices. For example, through a mobile app that would automatically sign them in to eWeLink CAST.
My customers don’t want to use the standard eWeLink app because they say it’s too confusing and feels like an app designed for service technicians rather than end users.
I believe many other users probably feel the same way.
This is indeed a difficult balance to achieve. The reason the CAST app interface is kept relatively simple is that there are already other platforms available for configuration, such as the eWeLink app and web interface. At the same time, device configuration is also an essential part of the user experience.
I can share a little information in advance: in the next major version of the eWeLink app, there will be a CAST panel feature. It will allow users to select frequently used devices and scenes as widgets and display them on the app homepage (with a display style similar to the current CAST interface). This may also better meet the needs you mentioned.
That’s the right direction. My users want a simple environment widgets, buttons, and nothing else.