Issues with Sonoff SNZB-03 motion sensor

Is there anyone here with a X and/or FB account who is willing to poke the Sonoff people by addressing this issue?

Since so many people are experiencing false positives which makes these devices useless, I wonder if they are aware of this problem.

By referring to this topic as well to the post from @francisp with the similar topic on Hubitat, I would think they cannot ignore this.

I would propose a GitHub (media) project to get this Sonoff motion sensor further technically analysed and improved, something like this:

Perhaps that will then draw Sonoff’s attention to really start to improve this device.

I had another 2 ‘drop of the Zigbee network’ events during last 24 hrs.

Each time I recycled (‘Off-On’) de power on the respective SNZB-03 sensor. And each time after that, this sensor came properly ‘online’ again on the Zigbee network within ca 5-10 sec and works fine again.

So, what is happening here? Why is the sensor dropping off the network and why does it quickly function fine again after reboot of the power?

Anyone any idea?

Next experiment I may do is soldering a slightly longer antenne wire to the SNZB-03.

I think there is enough information/proof in this thread (plus the one that Francis links to) that there seems to be a problem with these devices.
Normally I would be in favor of trying to get to the bottom of this kind of problem, not in this case.
The reason: I tried to get something done by contacting the manufacturer without any meaningful response.

In the past I did have another problem with a device and the manufacturer of it is active on this forum, so they addressed it immediately.
It’s their product, they make money out of it so maybe they are more active when the problem is out in the open.

I fully agree with you. In this case unfortunately Sonoff / ITEAD is not very responstive to (consistent) customer/product complaints regarding their SNZB-03 sensor.

Is this the typical Chinese manufacturer behavior to not really respond to customer product complaints or think: “the product is not perfect/high quality, but it is cheap, so customers just have to accept that the quality is too low / the device is Not (!)-fit-for-purpose”?

Thus to get this product really perform better there are 3 options:

  • Continue raising customer complaints at Sonoff/ITEAD, at large scale.
  • start a large ‘blame and shame’ campaign regarding the SNZB-03 via large (FD, Reddit, etc) social channels.
  • Or start a joint research/experiment project with a few smart techies via a GitHub project to try to identify the root cause and define a solution for the unsatisfying performance of the SNZB-03 sensor.
1 Like

The other manufacturer I was talking about is also Chinese and there are also a lot of non-Chinese companies that have a bad reputation when it comes to after sales support.

My main reason for getting these SNZB-03’s was it’s size.
That they are amongst the cheapest is a plus but I would even have payed/ordered more if they were reliable.

We all know that a single, non-public, complaint is easier to ignore then a public one.
In this case they would be confronted with many cases about the same problem which could draw a lot more attention of anyone in that company and buzz on the net.
I would even just inform them in the first place to give them the opportunity to respond.

By posting the fact that basic functionality like not only responding when needed (false positives) and not falling from the network, you make it very simple.
The fact that this device seems also to be falling from the mesh regularly is also a PITA for those experiencing this, but that could start discussions about coordinators, integrations, smart home platforms, … which could make it more difficult to get any support.

I don’t have an account on any of those platforms (and want to keep it that way), otherwise I would have done it myself.

The 2 SNZB-03’s I have in use have never fallen of the network, more then a year in use. The problem I have that one of them gives false positives, that is why the third one I have stays in its box and does not get installed.

I agree with your remarks!

I believe the only way we get this SNZB-03 device improved, if we can find someone to open (and drive) a complaint campaign via a FB group, Reddit, or at a dedicated Sonoff/ITEAD user forum to really increase the attention at Sonoff/ITEAD, that they really must improve de product quality, since it otherwise is going to hurt really hard their own Sales.

Other option is that perhaps a few very technical people at this Home-Assistant forum would be interested and keen to work together in a GitHub project to really get to the bottom of the SNZB-03 issues and find a solution.

Perhaps someone at this forum capable and willing to drive this?

I am myself not technical enough for this.

It’s not a bad idea at all, it would take away the responsibility of a commercial company to investigate one of it’s products on which they make money out of you and me.

A first good test would probably to put a Sonoff ZBBridge together with 2 or 3 SNZB-03’s (preferably hard-wired powered with a solid power adapter) in a big fully closed box in a room you do not enter for 2-3 days. And then see if you experience false motion triggers or ‘falling of the Zigbee network’ events.

If you then experience those unexpected events, then this would proof directly that the issues are not caused by the local environment but by the Sonoff hardware, firmware on the device or on the ZBBridge coordinator or by the Sonoff Could everything always is connected to.

1 Like

I just reached out as well with a note to our GitHub friends:

Customer complaint raised at Sonoff via GitHub forum member:

A lot of bad press as well on Amazon regarding these poor performing motion sensors:

——-

Update 29 Sep:

Hi Gents, have a look!!!

Is there shortly a new Sonoff Zigbee motion sensor coming to town??

They have registered for FCC approval:

https://fccid.io/2APN5SNZB03P/Internal-Photos/Internal-Photos-6757006

https://fccid.io/2APN5SNZB-03P

The bad thinks about this new version of the Sonoff motion sensor likely coming to the market either end this year or in 2024, are:

  • It looks like this version also runs on only 1 CR 2450 battery.
  • Output power Zigbee transmitter is only: 2-3 mW

So, although perhaps this new SNZB-03P may have improved stability, etc it still will probably perform unsatisfying in daily use due to short battery life and limited Zigbee range (due to the 2-3 mW)

——-

A further addition on the ‘classic’ SNZB-03, regarding reducing ‘false positives’:

Hi

I also have these SNZB-03 sensors and just like everyone else i am experiencing massive problems.

I dont have a Sonoff bridge, i run them via the blue skyconnect dongle but i was wondering if some of these problems could be fixed with a firmware update, i dont know what firmware they run and if there are any updates though ?

Thinking of just scrapping these and replacing them with Hue sensors, they seem to work okay if i read it right in this thread.

Does anyone know if it is possible to use Hue sensor without a bridge, i really dont want another power hog in my house, and i have more than enough bridges for a lot of stuff already :slight_smile:

Additional question.

Did someone try the SNZB-03P they now advertise, with a bigger battery that should last for 3 years and faster detection.

Hi, the problems have nothing to do with the coordinator so changing it will not solve anything about these badly constructed motion sensors.