Zigbee problem with FW 4.4.0

I honestly rarely experienced the reported issues, but I currently do a very basic use of nspp, a couple of thermostats and an mqtt integration with HA in order to simply share device state.

Even the zigbee devices are quite few and the simplest ones, some temperature sensors and a couple of zbmini as actuators for the two thermostats I have.

I stayed away frpm 4.4.0 release at the moment for the reasons I’ve already explaind.

Honestly I think sonoff guys job needs to be appreciated so far, most probably they are simply understaffed for the job sonoff is asking them or maybe not all of them are skilled enough, who knows

Is it just me who has the impression that each version is getting worse and worse? Maybe they should focus less on add-ons and development and instead on ensuring the core functionality works properly? I don’t use HA, mttq, etc. I’d like the basics to work properly. It was ok before, but the newer versions…

2 Likes

Something I told few weeks ago.

Strong foundation and than add “funny” features like HA, MQTT, …

I bought NSPP as thermostat and ZB controller for second part of the house. Thats it.

Yo mi experiencia, a base de muchas pruebas y horas dedicadas me ha llevado a tener todo en el iHOST y los NSPANELPRO trabajando como router, sin añadirlos al iHOST.

Cuando tengo toda la gestión en el iHOST todo funciona y no se desconecta. Cuando tenía dispositivos zigbee en NSPANELPRO era un desastre.

Es lo más estable que he encontrado. Los dispositivos los controlo con Ewelink Cast, (el Cast programado en iHOST) desde los paneles.

Sobre las actualizaciones lo que he notado es que pierdo algunas configuraciones de los equipos. Por ejemplo los ZBMINIR2 estaban programados en modo pulso y después de actualizar los encuentro en modo edge. Al no trabajar tanto con el NSPANELPRO, quizás no puedo opinar mucho.

Tengo varias instalaciones y la verdad que uno lo pasa mal cuando te llaman tantas veces y tú has recomendado el producto. En una de ellas hay 5 NSPANELPRO inútiles después de esa inversión porque se bloquean dos de ellos simplemente con la red wifi, sin añadirles dispositivos de ningún tipo.

Resumiendo, por mí experiencia, nada en el NSPANELPRO y todo en iHOST si podéis. Espero que os sirva de consejo y ayuda

But people don’t buy nspp as a decoration. It’s supposed to work fully without being managed by iHost.

So we agree, it can’t be a decoration and it has to work :smiley: Both for users who do not use very advanced functions and who are completely satisfied with native functions, as well as for advanced users who are expanding their smart home.
But when will this happen?
( My wife is starting to get angry with me because every now and then the light and the blinds don’t work :rofl:)

1 Like

It currently doesn’t even handle basic functions. As an installer, I’m now having problems with functionality everywhere I’ve installed it. Even the latest stable version isn’t fully functional.

That’s exactly what I’m talking about. :smirking_face:
We’ll see what happens next.
For now, zigbee devices are not responsive, they do not execute schedules (some - blinds),(the lighting works).. they do not react to pressing the physical switch the first time, as if after the first touch was just waking up and connecting with NSPP.? … Weird.

Link to videos illustrating the problem
(too big to add)

This would really annoy me. I also have a problem in that I need local control everywhere where there is unstable internet and so NSPP, zbb p and zbb u are completely useless to me.

I installed a combination of iHost and nspp via matter bridge and it doesn’t even work anymore.

On NSPP zb drops and so someone keeps complaining about what I installed.

Where I live in the UK a company called Connexin has installed a ZigBee grid system on lamp standards in my area. It went live in June 2025 and since then my ZigBee temperature sensors are regularly missing the hourly data updates. I have been told that the transmitting power of these lamp standard units is 3 watts which as I understand it is 2.9 watts more than the permitted ZigBee standard. I will not be purchasing any more ZigBee units as a result.

Lo que nunca he acabado de entender, aunque haya evolucionado después de tantas pruebas, es el porque algunos dispositivos de Sonoff no sean compatibles entre ellos, no entre diferentes tecnologías (zigbee, wifi…), si no, hay equipos zigbee que no interactúan entre ellos dentro de la misma marca. Cuando inicie con estos equipos lo compré todo Sonoff sin leer (culpa mía), pero algunos equipos no son compatibles con otros de su marca. Entiendo que quieran hacer los equipos más versátiles y estandar para que se puedan usar en otras plataformas, pero creo que inicialmente se tendría que resolver los problemas internos entre sus propios equipos.

That could interfere with people’s smart meters. Perhaps you could complain to your local council, MP or whichever regulatory body deals with this (possibly OFCOM).

Many years ago devices were installed in my local streetlights which made some types of digital clocks run very fast. They were fine again when they removed them.


Version 4.4. everything disconnected and nothing works… absolute mess…

1 Like

Hello, I have already sent you a private message. I will address this issue for you in a dedicated post. I hope you will cooperate with us in performing some actions. Thank you.

Hello, I have already sent you a private message. I will address this issue for you in a dedicated post. I hope you will cooperate with us in performing some actions. Thank you.

Maybe not an absolute mess, but zigbee devices are unstable, disconnect, don’t perform actions and schedules… They don’t respond to physical buttons for controlling blinds, etc. :wink:

I also experienced that Zigbee devices don’t always respond after an update. The signal strength has changed as well. In the pilot features, I enabled Zigbee turbo mode. Then I restarted the NASPanel Pro, and now it has become more stable.

There was a thermometer where I had to press the button on it once so it would start sending data again, but after that it worked better. Interestingly, the signal strength appears weaker in turbo mode, yet the connection is still more stable.

Try testing it — maybe it will help in your case too.

1 Like

I find it very odd and worrying that my mqtt sync issues got magically fixed on my zbBridge-U about the same time that the staff started replying on forum threads after the vacation. I struggled for a whole week trying everything and resorting to manual reading temperature sensors, closing and opening valves + actuator. I didn’t change anything, no firmware update, no nothing, i didn’t even tried a restart on my HA server or zbBridge-U for a few days. Can anyone check if it got fixed on the NSPP? I don’t want to move again my devices just to find out they don’t work.
Anyone else seen something similar or is just me?

A few days ago, I restored NSPP to factory settings. (What a lot of resetting everything.) It helped! Most ZigBee devices are connected and working. Two are stubborn…ORB 4 keys, and a door sensor. They are visible as disconnected in NSPP, and do not react to the first use - the first opening of the door does not trigger the action, but after it the sensor connects to NSPP and then works for some time. Same with ORB, first press does nothing, but it connects to NSPP, and then it works for some time. Unfortunately, after some time (possibly after activating the screen saver) are disconnected again.


16:30 GMT+2 today and 40 devices started disconnecting one by one after a couple of days with flawless functioning (which came after a nightmare week with nothing working). This is getting wierd. Most of my IoT devices are Sonoff. I invested alot of money into what it seems a very dysfunctional system. Can someone explain what is going on?!