Hey guys love the new updates but im still having intermitten offline issues with my nspanel pros and zigbee devices will randomly go offline i submitted a log today idk what the id was tho lol could u guys look into it???also what happend to adding the i host cast dashboard to the panel i cant find it anymore and really liked it any way I can still add it to the panel??? And i have 3 thirdreality zigbee blinds that wont let me control the open close level i will attach a pic Lmk thanks guys keep up the hard work its amazing!
Ihost v2 64 bit Recomendations!
With this last comment, I now understand much better what you meant by the point of view you indicate as âimplicit extensibilityâ. In any case, I insist that this would allow other users and myself to use Zigbee devices from other brands that the NSPP does not currently allow to be configured as sensors and actuators.
Therefore, I would appreciate it if the NSPP team (@JoJo @Milk @MichaelLearnsToCode ) would thoroughly analyse and study the possibility of enabling these âgeneric virtual entitiesâ and thus provide HA users with this manual control.
Otherwise, I will have to continue researching to try to manage everything from HA Companion (âThermostatâ, âSmart Securityâ and âVisual and audible notificationsâ) and leave the NSPP solely and exclusively as a basic screen without any function, because I cannot change the wired magnetic contacts and the rest of the wired installation with Sonoff devices that do not currently exist (I only know of the âFrient Module IOâ device that allows wired devices to be adapted to Zigbee).
Anyway, thank you for your productive and technical comments, and thanks to the great development work of the NSPP team, you are incredible.
Thanks for the explanation. Just to clarify: the idea of using generic virtual entities was something you proposed, and my previous message was simply analysing the implications of that approach from an architectural point of view. I wasnât suggesting that NSPP should implement it - only pointing out that once you introduce generic, userâmappable entities, the panel effectively becomes a universal controller, which is far beyond its intended scope.
Your use case is completely understandable, but itâs also exactly the kind of scenario where HA Companion or a dedicated wallâmounted tablet provides the flexibility youâre looking for. NSPP was never designed to handle arbitrary Zigbee devices, wired IO modules, custom alarm logic or full notification workflows. Expecting the panel to support all of that would shift significant complexity onto users and fundamentally change what the device is meant to be. Most importantly, I doubt the panel is capable, hardwareâwise, of handling what youâre envisioning.
Thatâs why my point was about avoiding this kind of implicit extensibility - not because the mechanism is wrong, but because it turns NSPanel Pro into something it was never intended to become. Itâs like expecting a toaster to be upgraded so it can wash your undies and socks. Technically you could try, but why would you?
1 Like
I understand, but NSPP is sitting in plastic box on the same table like notebook. Wifi antena can be the problem, but anyway, IMHO device should be able to mitigate data/connectivity loss problems.
The reason for sending data is that i control remote house heating with eWeLink and want to have access to historical data to check if everything is OK. House is now used by my 91yo father.
So⌠whatâs the plan here â summon a wizard to handle it?
@jam3 you are right about not asking too much to the current hardware, available resources on nspp are what we can get for the price.
About intended use I think you are less right, tight integration with home assistant was one of promise sonoff took at the 120 model launch and was most probably the main reason that pushed most of us to buy the product, at least it was for me.
Said that, many features we are asking relies primarily on a good mqtt integration with home assistant, I donât think that sharing sensors, voice and some local controls (for example Iâd like to be able to create soft buttons, whose state is visible in HA as an entity and can be used in automations) costs so much in terms of resources and adds much complexity, itâs simply what we are waiting for since the very beginning.
2 Likes
You make some valid points, and I donât disagree with the general direction. Yes â the hardware is limited, and yes â we all knew what we were buying at this price point. That part is simply reality. But regarding the intended use: I understand your perspective. Sonoff did advertise âtight Home Assistant integrationâ when the NSPanel Pro launched, and for many people that was a key selling point. Fair enough.
Still, it would help to clarify what âintegrationâ actually means. From a marketing perspective the term was⌠letâs say used with enthusiasm, which naturally created expectations that no small panel could realistically meet. And letâs be honest â anyone who decides to run Home Assistant should have at least basic technical awareness. HA is powerful, flexible, and about about as beginner friendly as a semiâtruck with a full trailer for a fresh driver. Excellent tool â just not designed for people expecting plugâandâplay magic.
Most HA users understand that devices built for a closed ecosystem (not only eWeLink) wonât suddenly become perfect HA components. If someone lacks the knowledge, staying within a polished ecosystem is usually the wiser choice than assembling a system from many unrelated parts and hoping everything will cooperate. In that sense, the fact that eWeLink even tries to improve local integration is unusual in this industry and deserves recognition.
A different issue is the escalation of expectations â as if Sonoff hardware had been designed specifically for HA. Well, it wasnât! Their business model prioritizes their own platform. Supporting both a closed ecosystem and an open one like HA at the same time is difficult. Wellâknown smartâhome brand Shelly has struggled with this balance and learned the hard way that you canât satisfy both worlds perfectly. The costs are just too high.
Home Assistant is developed by hundreds, if not thousands, of enthusiasts around the world. Their combined resources and creativity are practically unlimited â and even then, not everything works out as planned.
That said, proper MQTT support is not one of those unrealistic requests. Itâs lightweight, doesnât demand miracles from the hardware, and would unlock most of the features people have been asking for since day one. On that part, we fully agree.
2 Likes
Yes, thatâs right, the idea of âgeneric virtual entitiesâ was my proposal, and you are simply explaining the implications it would have from a more objective, broad and technical point of view. But my only intention was for the NSPP team to evaluate it and look at its viability in the future, since the original roadmap indicated that proposals and suggestions could be made.
Furthermore, although your toaster example is very clear, I do not quite see it the same way with the NSPP; I see it more as a possible complement or evolution of the device. V3.# did not contemplate compatibility with HA and all the functionalities it has now. Who knows if the scope of v5.# will be to turn it into a mini universal controller, and this would be a first step.
On the other hand, it is possible that, given my limited knowledge, I do not have as complete or expert a view as you do, and it is possible that you are right in everything you say, but as it would be very useful to me and I think it could also be useful to other people, that is why I proposed this idea for evaluation. In the end, I am just trying (like some other users) to take advantage of the modules already available in the NSPP, but using external sensors and actuators that are not currently compatible with the NSPP.
However, I agree that the NSPP is a device that has already evolved a great deal, and perhaps my proposal exceeds its current intended scope.
In any case, given that user complexity is relative, there could be a section that users can enable if they wish to activate these advanced functions, turning the NSPP into a mini universal controller and thus giving users more flexibility. This is because the device already has many functions that are too complex for my knowledge.
I agree with you. Furthermore, I do not believe that having generic entities consumes a lot of hardware resources, because HA would manage those entities, and the NSPP would only interact with them in the same way as it does with a wireless magnetic sensor, a relay, or a Sonoff smart plug. I believe that managing the Matter functions or the Zigbee hub is more likely to overload the hardware.
But in summary, this idea of âgeneric virtual entitiesâ configured by the user was only a suggestion for the NSPP team to study its feasibility within the scope of this device and thus be able to expand the use of the modules already available to the NSPP with external sensors and actuators that are not currently compatible, although this would lead to implicit extensibility that an expert user could exploit to their advantage. If that is not possible, we will have to look for other more viable alternatives, no problem.
You are absolutely right about that, and the work being done by the NSPP team is truly commendable. The great work they are doing is admirable.
And it is correct that Sonoff hardware is not designed for HA, because they have their own eWeLink ecosystem, but they do have resources and aim to improve compatibility with HA.
I donât think itâs so unfeasible for them to study the possible implementation of these small extra compatibility features, which could open up a wide range of options for the world of HA.
You bet! 
I understand the intention behind your idea, and itâs perfectly fine to propose something for evaluation. Still, thereâs a big difference between what is theoretically possible and what actually fits the scope of the NSPP. Turning it into a âmini universal controllerâ with userâdefined virtual entities would require a whole new architectural layer, not just a small feature toggle. And contrary to how it may seem, even on the Home Assistant side this is not a trivial matter â HA doesnât magically absorb arbitrary custom entities without additional logic, storage, synchronization and maintenance.
Your proposal isnât unreasonable â it simply goes far beyond what this device was designed for. If the team ever finds a way to implement something like that, great. If not, there are - as you know - other tools better suited for that level of flexibility.
Personally, Iâd much prefer the eWeLink dev team to focus on polishing MQTT, because that would bring real, measurable benefits instead of - with all due respect - chasing after fantasy features.
2 Likes
Observed problems:
1. The NSPanel sometimes disconnects - restarting helps. I havenât identified the cause. Symptom: no weather updates, no ability to control the TRVZB thermostat.
2. The TRVZB head device list is limited to 4 item in termostat function.
I have multiple heads and canât switch between them all.
Sorry about the issue. Please submit logs on your NSPanel Pro device via Top drop-down menu -> Settings -> About -> Feedback -> Submit . We will identify the root cause as soon as possible.
Apologies, I need to clarify further: Have you added more than 4 TRVZB thermostatic radiator valves, but in the thermostat interface list on your NSPanel Pro, you can only see 4 of them and cannot view or control the rest?
Thanks for the quick reply.
Sometimes I see all of them, and sometimes 1 or 2 are missing. I canât figure out the situation. All TRVs are connected to one hub (not to ns panel).
Most of the feature requests simply rely on that, once done a reliable mqtt integration itâs a matter to add optional feature like âvirtual entitiesâ, such as my desired âvirtual button/switchâ, which doesnât add complexity to average users, they can simply ignore them, neither should reclaim that much resources.
I think nspp could be both a good central control platform for sonoff ecosystem and a decent multi purpose device for ha.
That will kill any competition for many time
1 Like
Interesting point, but how exactly do you imagine NSPP becoming a âcentral control platformâ for the whole Sonoff ecosystem and a multiâpurpose HA device at the same time? Did you consider that Sonoff might not even have such ambitions? For most HA users NSPP is a niche product, and definitely not the first choice when it comes to control panels.
1 Like
I apologize for this issue. Iâd like to confirm: did you submit the logs from the NSPanel Pro? (Path: Top drop-down menu â Settings â About â Feedback â Submit?) If so, please send me your device ID. I need to retrieve the logs using the ID.
You can find the NSPanel Proâs device ID in the appâs NSPanel Pro details page. Tap the three-dot menu icon in the top-right corner, and the device ID is usually located at the bottom of that page.
If the log submission path you used earlier was incorrect, you can wait for version 4.3.3, which is scheduled to be released today. This version should resolve the issue with Zigbee child devices going offline. If the problem persists after updating, please resubmit the logs and contact me.
Are you referring to previously adding iHost Cast to the NSPanel Pro via the webshortcut method? You can now input the Cast address in the Webpages section (as shown in the image):
Iâm surely not explaining myself well, Iâm not figuring out at all nspp to become a central panel for ha, Iâm more than satisfied if it can share some resources to ha, such as zigbee/bt devices, audio, lux/presence sensor and let me configure virtal buttons in order to drive automations on ha.
My current nspp is located at the floor entrance, it currently drive heating for the whole floor and my best use case is to be used to switch on/off alarmo and garage door (drived by a non sonoff dry contacy relay) when I enter/leave the house.
Those simple features will convince me buy another 4 of them
1 Like
Exactly, @massimo.baschieri.
I have a similar situation to yours. It would be ideal to slightly improve MQTT support using those entities you mention and adding some configurable virtual buttons to interact between the NSPP and HA bilaterally with the NSPP modules or directly with the NSPP screen, as you say.
Although we want to use the âconfigurable virtual entities/buttonsâ for slightly different purposes, the development of the basic idea is the same.
I understand that the desire to turn the NSPP into a more universal control panel probably comes mainly from the fact that you already own one and were hoping for a bit more â after all, thatâs exactly what Sonoffâs marketing promised. The problem, however, is that before we start stacking additional layers of functionality (MQTT, virtual buttons, bidirectional interactions, lights and whistles), itâs worth taking a look at the foundations.
At the moment, eWeLink is still working on the basics, since they havenât quite mastered MQTT payloads yet, especially when it comes to the Zigbee controller built into the NSPP. Thatâs why I believe that before we start piling on new ideas, it would be wiser to give eWeLink some time to sort out the fundamentals. Otherwise, weâll just end up building increasingly complicated workarounds on a platform that simply isnât ready for them.
Iâm not denying that, in theory, you could turn the NSPP into a multiplatform control panel but in practice itâs difficult, inefficient, and there are far simpler and far more stable solutions that already work better today. Just to be clear, I own an NSPP myself and use it every day.
2 Likes