ZY-M100-S_1 sensors report every second #19045
Comments
|
This is a TuYa device, these doesn't support to configure reporting. AFAIK there is no way to reduce the reporting interval for these kind of TuYa devices. |
|
I have the same problem, and I suspect it's the reason for my Zigbee network performance issues. Ever since I added I bought 3 identical TuYa mmWave radar human presence sensor from the same AliExpress listing, and when I paired them they were recognised by Zigbee2MQTT as 2 I suspect that the suppliers are mixing different hardware revisions in the same inventory. My solution is to buy a couple of these sensors from different AliExpress listing until I hit |
|
Having the same issues and it is crashing my network. About 50% of my ZY-M100-L are joining as S_1 devices and reporting every second. |
|
I have the same problem, the sensor overloads the network and every 1 second it communicates this information. |
|
I spent a few weeks sifting through several of these sensors, and the "L" type seems to not exist anymore as I suspect it's now an older hardware revision. I gave up on it and replaced one of my offending sensors with the WiFi equivalent. Unfortunately, I have one outside the WiFi range that will have to keep being noisy on the Zigbee network until something new comes to market or there's a firmware update for it. |
|
ok thank you very much for your information. |
|
I had 7 of these on my network and it was crashing (all devices unavailable, z2m UI non-responsive) regularly. I removed all but one and I'm back to stability. |
Any luck with converting to ESPhome? I can only find replacement guides on the WBR3 module (the WiFi version of this sensor) and not the ZT3L chip (Zigbee version). |
Follow the same procedure. All 3 comms modules (WBR3, ZT3L, and ESP-12) support UART for talking with the mmwave module, and all 3 have the same pin layout for the pins you care about (UART TX/RX, VCC, and so on). The result should be identical whether you start with the Zigbee version or the WiFi version. Let us know how it goes for you. |
|
Has anyone tried the new 24Ghz in ceiling zigbee models to see if they have the same problem? |
Yes and yes. Same behavior in terms of once a second update, I won't install the ceiling sensor becasue the mains 110/220 connection is dangerous (connectors with no strain relief and inadequate separation, poor isolation of low and high voltage components). It's a fire waiting to happen. I've just bough 2 athom esphome sensors to play with which are wifi, have both PIR and MM Wave and so far work great. They run on 5v usbc. and the connector is on the back so if you ceiling mount them it's invisible. |
|
I have exactly the same problem here, my ZY-M100-S_1 is reporting every second, apart from that works perfectly, but obviously is not very good for the zigbee network. I have seen that there is a possible update of this wall sensor called WZ-M10024, anybody tested? |
|
Using the 24G (both ceiling and non-ceiling) that are identified as ZY-M100-24G (_TZE204_ijxvkhd0) on zigbee2mqtt and are spanning the zg network every second. |
|
When we are stating these are spamming the zigbee network, is that only when there is no presence in the room it is still spamming? Because I have this that I bought in Sep 2022 https://www.zigbee2mqtt.io/devices/TS0601_smart_human_presence_sensor_1.html#tuya-ts0601_smart_human_presence_sensor_1 When it detects motion, because of the target distance it spams the network every second because it's picking up the human's distance. When no one is in the room it doesn't log anything in Zigbee2mqtt logs. |
|
For the WZ-M100-W it's also spamming when there is no presence detected, every 0.5 seconds a MQTT message is created. See the log example in #20261 |
|
At the bottom of the ZT3L board, there's an SWS pad, allowing it to be flashed with custom firmware using the Single Wire interface. I got a suitable programmer from AliExpress, which was a little pricey for what it does. After some intense desoldering and soldering, I successfully dumped the firmware out of the I don't quite understand this sensor's architecture, but the only remaining place is the MCU on the 4th board, which is the one directly connected to the mmwave sensor. It's an ARM Cortex M23 chip. If somebody knows how to dump and flash its firmware, we can try to revert it back to the older firmware and see if that fixes the issue.
My worry is this approach is way too coarse, and it's possible the older firmware wouldn't work with the newer daughterboards in the newer version of the firmware. |
|
It's a pity that this is so difficult. I wonder whether there is a way to get the configuration |
|
Hello everyone, I wanted to provide an update on the ZY-M100-S_1 sensor's excessive reporting issue. After contacting Tuya, it's evident that the device's frequent reporting is governed by the MCU's firmware, developed using the Tuya MCU SDK. Tuya's module, part of this setup, does not fully support the standard Zigbee 3.0 protocol and is mainly for data transmission. This clarifies that resolving the issue is beyond Tuya's direct scope, as they only supply the networking module, not the device firmware. Consequently, any changes to the reporting frequency would require modification at the firmware level, controlled by the developers who created it. Unfortunately, Tuya could not provide contact details for these developers, suggesting we reach out to the device suppliers or check for contact information on the product packaging. For those interested in a deeper technical dive, Tuya referenced their Zigbee MCU SDK protocol, which might offer more insight into how their modules work: Tuya Zigbee MCU SDK Protocol. |
|
Thank you for these insights. I have spent the last two weeks trying to figure out what was wrong with the network in my new apartment, starting to setup home assistant from scratch multiple times. I have 9 of these sensors, and the network kept failing when more than 5 of these sensors were included. I solved the issue for now by creating a second zigbee network (a Z2M besides the already existing ZHA network) and dumping all the sensors on there. It seems to work (for now). But a more direct solution to the problem (lower update frequency / less chatter) is of course preferable, and it seems this necessarily has to be done via the firmware route (switching to another sensors is not really a viable option for me, because I prepared all the in-ceiling sensors in my new apartment). Is there any way for a custom firmware, or can it only come from the developers? I really hope there is a solution, because - besides the spamming by these sensors - they work great! |
|
Besides spamming the Zigbee network, directly forwarding all messages as MQTT messages also spams the computer network. One could reduce the frequency of issues MQTT messages, e.g., if there have been any changes? I think, this should be possible on the Zigbee2Mqtt handler level. |
I would probably not worry about the MQTT side of this issue. For MQTT server running on the same machine that runs Zigbee coordinator, it's all cheap operations in memory and occasional disk commits. It's peanuts in terms of the overall level of activity of your Home Assistant setup. For MQTT server running on another machine, the TCP protocol is more than capable of handling frequent transmissions at pretty much any data rate, and the same applies to the physical layers (Ethernet and WiFi). I don't think any component in your system or network even notices them. I guess in theory I could see those additional MQTT messages being unnecessary spam, but architecting and writing code and tests to rate limit them is probably way too costly compared to the benefit. The biggest issue is the spam on the Zigbee network. It's way more vulnerable to this problem. If you have 2-3 misbehaving devices like this, they can really clog up the Zigbee network, cause lags and delays. When I had 3 of those senors in my network, doing firmware OTA on any of my other Zigbee devices was basically out of the question. |
|
Anyone able to find any guides on dumping the firmware and modifying it? I have a ton of these devices. At the same time, I ordered a 24Ghz model (MTG235-ZB-RL) with the local switched relay. It is significantly higher quality and a lot safer. It has a power line tie down and plastic cover to protect the power wire screw terminals. Pending installation this week. |
Curious if the TS0225 sensor your getting is any different (in terms of chattiness). Can’t find a lot of info on it, so look forward to your update on that. |
|
Additionally, the 24Ghz model moved the re-pairing button to the front of the unit so that it is not required to pull the unit out of the ceiling and risk getting shocked. As for testing, the original model is spamming every 1-2 seconds whereas this 24Ghz model is bursty at random. Sometimes no updates for up to 1 minute apart and other times it will send 3 messages a few seconds apart. The is a difference in the size though. This model is 60mm wide instead of 55mm. |
|
And with “at random” you mean when there is no presence detected? Overall, the way you describe it, it seems like less messages per minute though, correct? |
|
Even when presence is detected, the messages from this new model are much less frequent. I don't see any impact on accuracy. While it has only been installed for 12 hours, the presence history looks perfect. |
|
It's not a detection problem but it's actually the zigbee chip that transmits fast I bought 20 zy-m100-v1.4 to put on the same network with 40 other devices, the network collapsed almost immediately I thought of a drastic solution silent for 4 seconds https://futuranet.it/prodotto/micro-modulo-timer-programmabile-2-secondi-1000-ore/ Already ordered, I'll try as soon as they arrive do you think damage could be caused with all these resets |
Put the spammy mmWave radars on a separate Zigbee network ... Just add a second Zigbee dongle. |
|
Just got in my hand these ones for replacement. Even they're working very well, the ZY-M100-S_1 are going to a drawer until further workaround is found. |
Hello all, |
|
Buying additional dongle and creating new network is rather not a solution for me :( . It should be fixed on firmware level. A question is to sell and buy suggested replacement or wait... but how long :) |
|
I agree with the sentiment @orzechszek , but wanted a workable solution for now. @victordqa : pretty straightforward, bought a second SkyConnect stick and configured it for Z2M. Put all the chatty sensors on the new network, and kept all my other devices on my old ZHA network. Result: the peace is restored on ZHA where it again is nice and silent, and the sensors are free to shout at eachother over Z2M without disturbing their peace-loving neighbours HA manages both networks and just passes on the relevant information, everybody’s happy … at least funtionally. Me, I’m still somewhat annoyed that I had to bend over backwards to facilitate these buggy sensors but at least it works now |
|
besides the spammy behavior, are you happy with the performance? I have bad occupancy readings (on similar Tuya sensors), they are quite random: I'm using the plugin file (or how is it called). |
|
I’m quite happy with them. They’re not perfect, but I’d say 98-99% perfect with the very rare false positive or false negative. it is important though that you have them on ZHA with the right quirk or on Z2M, as this allows you to finetune their settings (max distance, sensitivity, etc). Also it takes a bit of tweaking with regard to fade time (both device setting and home assistant automation) to make it work as desired. For instance in the bedroom I have a quite long fade time of about 30 secs, in the living room about 20 secs, while in hallway, bathroom and home office about 10 secs. Rule-of-thumb here is the more physically active you are in a certain room, the shorter the fade time can be). |
|
I really like the performance these sensors give. I have tried most of the hilink and dfrobot sensor but I keep coming back to this one sen0521 (ZY-M100) it has the right balence of sensitivity and works best through my ceiling material for the way I like to use mmwave. One thing to note is the fov of the sensors, I notice other sensor may be better at detection and clearing but the fov is poor when mounted in a ceiling position, mostly only work well at about 2-3m where the tuya sensor works well up to about 4m. I was using the zigbee sensors but like so many I purchased a few and after pairing more than 5 my network started crashing, I split my network into 2 and that mostly helped but not 100% solved, I would still wake up to no devices responding. tried multiple sticks but no luck. removing all the mmwave sensors and the zigbee network is rock solid again. so I wnt down the rabit hole of esphome but still wanted these sensors. I found you can cut the mmwave sensor of the tuya board and solder it to an esp32 and for the most part you can use the esphome yaml from the dfrobot sen0395 that so many love. I have made a working config if anyone wants it. I have been mounting these sensors in 3d printed cases abouve my ceiling material in each room completly invisable and powering them over poe cat6 I ran in the roof space. I also connect a pir sensor mounted in the ceiling near the door that triggers just as you enter the room. this is because the pir is instant and reliable for detection. I dont use the mmwave for detection, I use PIR lights on and PIR + mmWave cleared for lights off. this gives me the best of both worlds and makes up a complete fast and 99% accurate presence system in each room. Pics attached.
|
|
Great solution! Can you send me more info about how to do the retro fit? Thanks in advance Cheers |
|
Has anyone tried this already? https://devices.esphome.io/devices/Tuya-ZY-M100-Human-Presence-Sensor |
Hey there, the jist of it is you can buy the sensor new from digikey: |
|
tbh, after multiple attempts models and firmware versions, I just gave up with those cheap Tuya & alike Mmwave sensors reporting every second, more mature versions will probably come next, but in the meantime I ended up with Aqara FP2, 3x the price, but it just works, map and multi-zone features, lux sensor as well, events triggered only upon relevant changes, and great precision. Sure, the "wiring" to MQTT and your custom code is a bit weird (Sensor > HASS Homekit integration > HASS MQTT integration) but even so, it triggers my Hue lightning awesomely fast through MQTT and my Node.js code (< 1 second), needs some initial fine-tuning due to its precision, but then it's reliable. Other current Mmwave sensors I found on benchmarks, Github issues and other end-user feedbacks have either ugly casing or seem just unusable or low-end sensors, for some reason... 🤷♂️ |
I just bought a new device Tuya ZG-205Z/A and as you can see the spam messages are still but less "stormy" |
Here I observed the same, however when the presence is false, he does the stormy again, publishing every second. |
|
Just a word of caution.... MTG275-ZB-RL also has the same problem Screen.Recording.2024-04-11.at.15.28.25.mov |
So, what about this device after almost two months? I have two ZY-M100-24G plus 35 other Zigbee devices in the same network and starting to have stability problems. I'm thinking about buying two of these if you recommend them. |
|
I was having this exact issue with the M100-S_1 and M100-S_2 sensors. My log was being flooded every second by both these sensors. This happened after changing activating the "Last Seen" option under z2mqtt Settings from "Disabled" to "ISO_8601". I wanted to start tracking which devices go offline. Once I disabled the Last Seen option again, my log was back to normal. However the point which I might be missing, based on some of the above comments, is that these sensors must be still flooding the zigbee network, even though they're not showing up in the log? How do I check? |
As far as I know It'll still spamming the network, although disabling the "Last Seen" option will not send that info trough MQTT Please correct me if I'm wrong |
|
How can I tell if the sensors are flooding the network? I don't have anything showing under Logs in Zigbee2MQTT menu in Home Assistant. |
If I go to Logs and filter for "info," I can still see "last_seen" packets being sent through my Zigbee network, even with the option disabled |
|
|
On my Case ("last seen" disabled). Note I have 7 ZY-100 on my network and a total of 60 devices 
|
|
Folks, the Last Seen configuration in Zigbee2MQTT has no impact on the Zigbee layer of your setup. This a dead end. |
|
Call me a naive optimist, but why can't Tuya simply fix this with a FW update? It shouldn't be that much work on their side, and it would fix one of their coolest products. |
I do not remember if it was earlier in this thread or in another, but someone has already asked Tuya customer service this question, and the answer was something like that it was hardcoded in the Zigbee transceiver module - which was not controllable from their Tuya firmware, so it wasn't possible for them to push out an software update to fix it. I assume they will likely just fix it in some new model with other hardware. |
Adi do you mind explaining why I'm not seeing the same behavior on my ZY-M100-S_1 and S_2 ? Z2mqtt Log is almost empty as shown in the screenshot above. |
|
The new zigbee2mqtt no longer shows the information by default in the front end log. This observation is in this month's update. You need to manually activate it. |
At least disabling this will not spam the MQTT broker |
I noticed the same. I do have 3 x M100-S_2 and Z2M started to chrash much more frequently when i enabled the Last Seen option. Might be two issues, both on the zigbee layer and then the communication with the MQTT broker? |
and others
What happened?
The Tuya ZY-M100-S_1 (_TZE204_sxm7l9xa) is reporting its values every second. This values can or can not changes.
Here is an example with values not changing:
What did you expect to happen?
A delay or minimal value change that can be configured in the
Reportingtab.How to reproduce it (minimal and precise)
Pair the sensor and it starts sending data every second or 2.
Zigbee2MQTT version
1.33.0
Adapter firmware version
20221226
Adapter
Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001
Debug log
The text was updated successfully, but these errors were encountered: