pvvx/ZigbeeTLc

Thermometers keep requesting OTA according to Zigbee2MQTT ("Device '...' requested OTA")

JayFoxRox opened this issue · 0 comments

Here are some logs from Zigbee2MQTT (1.34.0 commit: aae7312); zStack12 Coordinator revision 20211115.

According to this, my 9 LYWSD03MMC thermometers (called T1 - T9) "requested OTA" very frequently.
Each of them is running 3001-0117 (20231215).

I'm not sure if this is poor wording in Z2M or if the devices themselves actually request the OTA. If they do, I believe the 5 minutes is a bit excessive?
I tried to figure out if these are actually from the devices and there are a 3 different calls to ota_queryStart which might be responsible?

<...>
2024-01-24 20:14:14Received Zigbee message from 'T4', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":18296833,"imageType":522,"manufacturerCode":4417}' from endpoint 1 with groupID 0
2024-01-24 20:14:14Device 'T4' requested OTA
2024-01-24 20:14:15Responded to OTA request of 'T4' with 'NO_IMAGE_AVAILABLE'
2024-01-24 20:14:20Received Zigbee message from 'T9', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":18296833,"imageType":522,"manufacturerCode":4417}' from endpoint 1 with groupID 0
2024-01-24 20:14:20Device 'T9' requested OTA
2024-01-24 20:14:20Responded to OTA request of 'T9' with 'NO_IMAGE_AVAILABLE'
2024-01-24 20:15:20Received Zigbee message from 'T7', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":18296833,"imageType":522,"manufacturerCode":4417}' from endpoint 1 with groupID 0
2024-01-24 20:15:20Device 'T7' requested OTA
2024-01-24 20:15:20Responded to OTA request of 'T7' with 'NO_IMAGE_AVAILABLE'
2024-01-24 20:15:49Received Zigbee message from 'T1', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":18296833,"imageType":522,"manufacturerCode":4417}' from endpoint 1 with groupID 0
2024-01-24 20:15:49Device 'T1' requested OTA
2024-01-24 20:15:49Responded to OTA request of 'T1' with 'NO_IMAGE_AVAILABLE'
2024-01-24 20:16:10Received Zigbee message from 'T2', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":18296833,"imageType":522,"manufacturerCode":4417}' from endpoint 1 with groupID 0
2024-01-24 20:16:10Device 'T2' requested OTA
2024-01-24 20:16:10Responded to OTA request of 'T2' with 'NO_IMAGE_AVAILABLE'
2024-01-24 20:16:32Received Zigbee message from 'T5', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":18296833,"imageType":522,"manufacturerCode":4417}' from endpoint 1 with groupID 0
2024-01-24 20:16:32Device 'T5' requested OTA
2024-01-24 20:16:32Responded to OTA request of 'T5' with 'NO_IMAGE_AVAILABLE'
2024-01-24 20:16:40Received Zigbee message from 'T6', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":18296833,"imageType":522,"manufacturerCode":4417}' from endpoint 1 with groupID 0
2024-01-24 20:16:40Device 'T6' requested OTA
2024-01-24 20:16:40Responded to OTA request of 'T6' with 'NO_IMAGE_AVAILABLE'
2024-01-24 20:16:55Received Zigbee message from 'T3', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":18296833,"imageType":522,"manufacturerCode":4417}' from endpoint 1 with groupID 0
2024-01-24 20:16:55Device 'T3' requested OTA
2024-01-24 20:16:56Responded to OTA request of 'T3' with 'NO_IMAGE_AVAILABLE'
2024-01-24 20:19:14Received Zigbee message from 'T4', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":18296833,"imageType":522,"manufacturerCode":4417}' from endpoint 1 with groupID 0
2024-01-24 20:19:14Device 'T4' requested OTA
2024-01-24 20:19:15Responded to OTA request of 'T4' with 'NO_IMAGE_AVAILABLE'
2024-01-24 20:19:20Received Zigbee message from 'T9', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":18296833,"imageType":522,"manufacturerCode":4417}' from endpoint 1 with groupID 0
2024-01-24 20:19:20Device 'T9' requested OTA
2024-01-24 20:19:20Responded to OTA request of 'T9' with 'NO_IMAGE_AVAILABLE'
2024-01-24 20:20:20Received Zigbee message from 'T7', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":18296833,"imageType":522,"manufacturerCode":4417}' from endpoint 1 with groupID 0
2024-01-24 20:20:20Device 'T7' requested OTA
2024-01-24 20:20:20Responded to OTA request of 'T7' with 'NO_IMAGE_AVAILABLE'

"Ota" is not bound to the coordinator either, and there's no reporting configured for "Ota" either.
I have 11 other zigbee devices, and none of them show up here (or not as frequently ~ 5 minutes).
Is this a bug?

Personally, I'd also prefer to push OTA whenever I want them and not when the devices deems them necessary. I'm not sure how zigbee OTA works in this regard, but I'm surprised the device asks at all - I thought the coordinator was responsible.