BLE-YL01 is spamming network.

[Passific]

What happened?

Several times a day, BLE-YL01 is spamming with updates (noticeable with the last seen constantly updating).
This cause my Zigbee network to saturate and I get some "Fail to deliver message" errors in the logs when it happens.

Using debounce: 2 did not change anything (last seen constantly update, and error messages in the logs).

It even made my NODON SIN-4-RS-20 module (where it is connected to) crash.
I removed the BLE-YL01 from the network 3 days ago, and not a single error since then.

Could rebooting Z2M (as part of docker update for example), send the cluster 0xEF00, attribute 0x03 frame again which cause too many updates? (just guessing)

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

1.40.1

Adapter firmware version

7.4.3

Adapter

Ember

Setup

Docker on Intel N100

Debug log

[2024-09-10 20:32:36] error:    z2m: EventBus error 'OnEvent/deviceMessage': ZCL command 0x7cc6b6fffe6ad296/1 manuSpecificTuya.mcuVersionRequest({"seq":2}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Delivery failed for {"profileId":260,"clusterId":61184,"sourceEndpoint":1,"destinationEndpoint":1,"options":4160,"groupId":0,"sequence":67})

[R3yn4ld]

I have the same error.

Also, I don't know if related but I cannot execute the magic trick to get the value updated after the very first pairing:

The sensor is unusable via Z2M then :(

[aperezva]

The same error, @Koenkk could you see what happen, it was after last update

[CanuckianOz]

@Koenkk this device still doesn't appear to update on the Edge or main Z2M distro. Is it possible that it requires a manual resetting of the backlight_value (to 0, then to 1) similar to the LocalTuya workaround to fetch device updates? If this value were exposed in Z2M, we could set an automation to reset the value as desired.

https://community.home-assistant.io/t/pool-monitoring-device-yieryi-ble-yl01-zigbee-ph-orp-free-chlorine-salinity-etc/659545/18?u=truemana

[Koenkk]

Could you provide the debug log when starting z2m + 5 minutes after this?

See this on how to enable debug logging.

[CanuckianOz]

@Koenkk no problem - here you go:

https://pastes.dev/Oc3DJitDRR

[Koenkk]

It looks that the device is not reachable, try repairing it:

ZCL command 0x08ddebfffe882b82/1 manuSpecificTuya.dataQuery({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))
`

[Passific]

This is almost the same message I got (see my logs in the top message).
But from what I experienced, device does communicate as the « last seen » suggest, and I got some data (not sure about how often though).
I tried to repair it, but each time there was a variable delay in hours before the first meaningful data. So for now it’s in my garage waiting to not crash my Zigbee network…

[Judufu]

Did you manage to fix yours? I have the same problem with mine :/
I dont get spamed, but i dont get any regular updates after the initial pairing..

[CanuckianOz]

No I didn’t. I went back to using tuya local custom integration and their wifi hub, then setting an automation to set and reset backlight_value from 0 to 1 and back to 0 every 5 minutes. It’s the only tuya device I have so a bit of a pain.

[Carrotpro]

Got same problem anyone got a fix yet?

[OE5DRO]

same problem here

[Passific]

I personally gave up on the device. It's a shame given the price tag, but it's really not reliable, plus having all sensors on one device, if it fails you have nothing. And above all, it's not starting this spring, it may not have liked the winter or something...
I'm now starting over with independent sensors.
Good luck anyway, I hope you get more results!

[CanuckianOz]

I haven’t tried to re-pair the device with zigbee, but I have found it to completely reliable running via a tuya gateway and the tuya integration for about 6 months. Takes a little to manually setup but it’s been reporting data consistently.

However, the data isn’t fully reliable. I have a low salt / low chlorine system with auto acid dosing and it’s consistently between 1-2ppm measured, but the device only occasionally shows 0.1-0.4ppm. pH is always about 0.2 higher than measured, temperature about 1.5C higher. Salt PPM is about 200ppm too high but spikes massively randomly once a day.

Basically, I use it to ensure they’re aren’t major swings. The temperature is at least very helpful.

[juslex]

Same problem here