ZLinky_TIC : Failed to read zigbee attributes (...) liXeePrivate.read(["currentPrice","currentTarif","message1","message2"] (...)

[MilesTEG1]

What happened?

There is a lot of this error in Z2M:

Warning 2024-05-20 13:43:27Failed to read zigbee attributes: Error: ZCL command 0x00158d0005d25e9d/1 liXeePrivate.read(["currentPrice","currentTarif","message1","message2"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed ({"target":2695,"apsFrame":{"profileId":260,"clusterId":65382,"sourceEndpoint":1,"destinationEndpoint":1,"options":4416,"groupId":0,"sequence":30},"zclSequence":77,"commandIdentifier":1} timed out after 10000ms)


Warning 2024-05-20 13:46:40Failed to read zigbee attributes: Error: ZCL command 0x00158d0005d25e9d/1 liXeePrivate.read(["currentPrice","currentTarif","message1","message2"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed ({"target":2695,"apsFrame":{"profileId":260,"clusterId":65382,"sourceEndpoint":1,"destinationEndpoint":1,"options":4416,"groupId":0,"sequence":97},"zclSequence":14,"commandIdentifier":1} timed out after 10000ms)

I'm using the Zigbee2MQTT Add-on on HAOS, and I tried the Zigbee2MQTT Edge version too. The log provided bellow is grab from the Edge verion.

What did you expect to happen?

No error like this.

How to reproduce it (minimal and precise)

I don't know. Since an update (don't know which one... Z2M, HAOS...) I get this error a lot of time.

Zigbee2MQTT version

1.37.1-1 (I tried the Edge version too, same error)

Adapter firmware version

7.4.3 [GA]

Adapter

HA SkyConnect with ember driver

Setup

Add-on on Home Assistant OS on Intel NUC

Debug log

Z2M-log.log

[scientas]

Hello, i have exactly the same problem...

warning: zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d000638e222/1 liXeePrivate.read(["currentPrice","currentTarif","message1","message2"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed ({"target":39886,"apsFrame":{"profileId":260,"clusterId":65382,"sourceEndpoint":1,"destinationEndpoint":1,"options":4416,"groupId":0,"sequence":17},"zclSequence":84,"commandIdentifier":1} timed out after 10000ms)

What can we do ?

[Coldness00]

Hello, I have same also

[MilesTEG1]

Hello, I'm glad to see that I'm not alone! 😅

But for now there is no fix to come.

@Koenkk Could you look into this problem please? And if needed, how can we help.

Thanks in advance 😊

[Koenkk]

This error means the device doesnt respond, either an issue of the device or a bad network

[MilesTEG1]

Hello, Thanks @Koenkk for your answer. I'm not sur it's a device issue or a bad network.

I don't know how to explain in english what I think. Let's try:

The error show this to be time dout:

liXeePrivate.read([
    "currentPrice",
    "currentTarif",
    "message1",
    "message2"
],

But there is no currentPrice nor currentTarif in the ZLinky-TIC state in Z2M:

{
    "active_energy_out_d01": 26483.617,
    "active_energy_out_d02": 6029.29,
    "active_power": 402,
    "active_power_max": 1711,
    "active_power_ph_b": 558,
    "apparent_power": 689,
    "available_power": 9,
    "average_rms_voltage_meas_period": 230,
    "current_date": "E240527135725",
    "current_index_tarif": 2,
    "current_summ_delivered": 41649.234,
    "current_tarif": "TEMPO",
    "current_tier1_summ_delivered": 38479.083,
    "current_tier2_summ_delivered": 2143.573,
    "current_tier3_summ_delivered": 350.038,
    "current_tier4_summ_delivered": 347.443,
    "current_tier5_summ_delivered": 179.756,
    "current_tier6_summ_delivered": 149.339,
    "drawn_v_a_max_n1": 3431,
    "linkquality": 164,
    "meter_serial_number": "xxxxxxxxxxxx",
    "power_threshold": 9,
    "relais": 0,
    "relais_breakout": {
        "relais1": 0,
        "relais2": 0,
        "relais3": 0,
        "relais4": 0,
        "relais5": 0,
        "relais6": 0,
        "relais7": 0,
        "relais8": 0
    },
    "rms_current": 3,
    "rms_voltage": 229,
    "site_id": "xxxxxxxxxxxxx",
    "software_revision": 2,
    "status_register": "xxxxxxxxx",
    "status_register_breakout": {
        "cache_borne_dist": "ferme",
        "comm_euridis": "activee avec securite",
        "contact_sec": "ouvert",
        "depassement_ref_pow": 0,
        "etat_cpl": "enregistre",
        "horloge": "correcte",
        "organe_coupure": "ferme",
        "pointe_mobile": "AUCUN",
        "preavis_pointe_mobile": "AUCUN",
        "producteur": 0,
        "sens_energie_active": "positive",
        "surtension_phase": 0,
        "sync_cpl": "synchronise",
        "tarif_dist": "index_2",
        "tarif_four": "index_2",
        "tempo_demain": "UNDEF",
        "tempo_jour": "BLEU",
        "type_tic": "standard"
    },
    "update": {
        "installed_version": 1,
        "latest_version": 13,
        "state": "available"
    },
    "warn_d_p_s": 0,
    "current_price": null,
    "message1": null,
    "message2": null
}

Maybe Z2M try to read those by mistake... But I don't know why.

I think it should be current_tarif and current_price.

May it be a Z2M problem?

What do you think @Koenkk?

[Koenkk]

I'm not sure if those are supported, @mildis could you maybe check this?

[mildis]

current_tarif is listed ("TEMPO") current_price, message1 and message2 are at the end with null value whereas it should read

    "current_price": "HP BLEU",
    "message1": "PAS DE MESSAGE",
    "message2": "",

status_register said type is standard which is good.

However, a firmware update seems pending :

    "update": {
        "installed_version": 1,
        "latest_version": 13,
        "state": "available"
    },

but should read

    "update": {
        "installed_version": 13,
        "latest_version": 13,
        "state": "idle"
    },
    "update_available": false

Try to apply the firmware update OTA. If it fails, I suggest you unplug/replug the ZLinky from your Linky. At last, you might want to get in touch with Lixee @fairecasoimeme for advanced help

[MilesTEG1]

Hi, Thanks for your answers.

current_tarif is listed ("TEMPO") current_price, message1 and message2 are at the end with null value whereas it should read

    "current_price": "HP BLEU",
    "message1": "PAS DE MESSAGE",
    "message2": "",

What I tried to say is that Z2M try to get currentPrice and currentTarif but the ZLinky provides current_price and current_Tarif, with a _.

For this, I may have another input to tell.

However, a firmware update seems pending :

    "update": {
        "installed_version": 1,
        "latest_version": 13,
        "state": "available"
    },

but should read

    "update": {
        "installed_version": 13,
        "latest_version": 13,
        "state": "idle"
    },
    "update_available": false

I flashed the ZLinky non-OTA, with a limited firmware: https://github.com/fairecasoimeme/Zlinky_TIC?tab=readme-ov-file#non-ota https://zigate.fr/documentation/mise-a-jour-de-la-zigate-2/

Si my ZLinky have the ZLinky_router_v13_limited firmware

But as the developer @fairecasoimeme said, or at least what I understood, it cannot get OTA update in limited firmware.

So I can't get Z2M to see the real version of the ZLinky. And the ZLinky report the corect version in the "About" section :

Try to apply the firmware update OTA. You think it's possible? How can I achieve this? How can I set the OTA URL? @fairecasoimeme

[MilesTEG1]

Hello, Apparently, the Measurement poll chunk was the faulty one here! It wasn't set, so normaly It should be the default value: 1. But in my case, it was 4, I don't know why.

Si by forcing 1 to this Measurement poll chunk, no more error by timeout.

[incognito1234]

Hello, I have a similar result with a different root cause (break in connexion)

See https://github.com/Koenkk/zigbee2mqtt/issues/22206

The only fix I found is a repairing of the device.

[MilesTEG1]

Hello, I have a similar result with a different root cause (break in connexion)

See #22206

The only fix I found is a repairing of the device.

Hello, That's a radical solution I preferred to avoid 😃 The last time I reappaired the device, It took long enough to get all my data again, because I was obliged to reconfigure it (TEMPO, Standard, Mono-Phasé, so a lot of info to get). Waiting enough time after rebooting Z2M after those modifications.

[incognito1234]

Before repairing the device, you can backup the file data/configuration.yaml and restore it after repairing.

I have no choice in my case since no data is retrieved without this operation.

[RastaChaum]

I've noticed that I'm no longer receiving any data from my Lixee. As a result, I'm seeing the same message in my logs, along with similar messages for other data. I've tried re-pairing, but it hasn't worked. Do you have any workarounds other than re-pairing?

[Coldness00]

I've noticed that I'm no longer receiving any data from my Lixee. As a result, I'm seeing the same message in my logs, along with similar messages for other data. I've tried re-pairing, but it hasn't worked. Do you have any workarounds other than re-pairing?

Did you tried unparing then disconnect lixee 30min and press in the lixee at least 10sec then reboot z2m and activate pearing

[RastaChaum]

I've noticed that I'm no longer receiving any data from my Lixee. As a result, I'm seeing the same message in my logs, along with similar messages for other data. I've tried re-pairing, but it hasn't worked. Do you have any workarounds other than re-pairing?

Did you tried unparing then disconnect lixee 30min and press in the lixee at least 10sec then reboot z2m and activate pearing

Thanks. I try it :

• delete device from z2m
• unplug it
• wait 1 day
• repairing it
• reboot And and..... always KO 😞

[fairecasoimeme]

Hello, Apparently, the Measurement poll chunk was the faulty one here! It wasn't set, so normaly It should be the default value: 1. But in my case, it was 4, I don't know why.

Si by forcing 1 to this Measurement poll chunk, no more error by timeout.

Did you test this ?

[samsam-rolon]

Hello, Same issue here [2024-09-03 13:47:09] warning: zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d0005be8645/1 liXeePrivate.read(["motDEtat"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (no response received (5) waiting for response TIMEOUT) [2024-09-03 13:46:58] warning: zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d0005be8645/1 liXeePrivate.read(["currentTarif"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (no response received (4) waiting for response TIMEOUT)

Hello, Apparently, the Measurement poll chunk was the faulty one here! It wasn't set, so normaly It should be the default value: 1. But in my case, it was 4, I don't know why. Si by forcing 1 to this Measurement poll chunk, no more error by timeout.

Did you test this ?

Yes

[Coldness00]

I have same issue also. I tried changing the Measurment poll chunk from 1 to 4 but without any success I also have a lot of other error. It's the only device with issue on a network of 54 devices...

Other than the error in itself, the device is working fine.

[2024-09-03 17:30:16] warning: zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d000638dcad/1 liXeePrivate.read(["currentDate"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (Timeout - 51876 - 1 - 218 - 65382 - 1 after 10000ms) [2024-09-03 18:25:46] warning: zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d000638dcad/1 liXeePrivate.read(["currentPrice"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (Timeout - 51876 - 1 - 8 - 65382 - 1 after 10000ms) [2024-09-03 18:28:19] warning: zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d000638dcad/1 liXeePrivate.read(["message1"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (Timeout - 51876 - 1 - 96 - 65382 - 1 after 10000ms) [2024-09-03 18:29:10] warning: zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d000638dcad/1 seMetering.read(["currentTier6SummDelivered"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (Timeout - 51876 - 1 - 124 - 1794 - 1 after 10000ms) [2024-09-03 18:29:46] warning: zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d000638dcad/1 seMetering.read(["siteId"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (Timeout - 51876 - 1 - 132 - 1794 - 1 after 10000ms) [2024-09-03 18:31:11] warning: zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d000638dcad/1 liXeePrivate.read(["message2"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (Timeout - 51876 - 1 - 157 - 65382 - 1 after 10000ms) [2024-09-03 18:32:03] warning: zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d000638dcad/1 seMetering.read(["currentTier5SummDelivered"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (Timeout - 51876 - 1 - 183 - 1794 - 1 after 10000ms) [2024-09-03 18:40:16] warning: zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d000638dcad/1 haElectricalMeasurement.read(["activePowerMax"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (Timeout - 51876 - 1 - 215 - 2820 - 1 after 10000ms) [2024-09-03 18:44:53] warning: zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d000638dcad/1 seMetering.read(["currentSummDelivered"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (Timeout - 51876 - 1 - 99 - 1794 - 1 after 10000ms) [2024-09-03 18:47:28] warning: zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d000638dcad/1 seMetering.read(["siteId"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (Timeout - 51876 - 1 - 164 - 1794 - 1 after 10000ms) [2024-09-03 18:49:46] warning: zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d000638dcad/1 haElectricalMeasurement.read(["averageRmsVoltageMeasPeriod"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (Timeout - 51876 - 1 - 206 - 2820 - 1 after 10000ms) [2024-09-03 19:17:53] warning: zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d000638dcad/1 liXeePrivate.read(["currentDate"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (Timeout - 51876 - 1 - 172 - 65382 - 1 after 10000ms) [2024-09-03 19:57:43] warning: zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d000638dcad/1 liXeePrivate.read(["statusRegister"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (Timeout - 51876 - 1 - 149 - 65382 - 1 after 10000ms) [2024-09-03 19:58:06] warning: zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d000638dcad/1 liXeePrivate.read(["drawnVAMaxN1"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (Timeout - 51876 - 1 - 154 - 65382 - 1 after 10000ms) [2024-09-03 20:01:18] warning: zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d000638dcad/1 liXeePrivate.read(["currentPrice"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (Timeout - 51876 - 1 - 241 - 65382 - 1 after 10000ms)

[samsam-rolon]

@fairecasoimeme since the last FW upgrade (14) : no more issue for the moment

[meyxiam]

Bonjour, je suis en version 14 du lixee et j'ai ce problème. Il faut dire que mon lixee est à 50m de mon antenne sonoff, car mon compteur est dehors et je n'ai pas de routeur entre 2. Le LQI est souvent à 0, mais il marque régulièrement "En ligne" et ça fonctionne ! Mais j'ai aussi régulièrement des "Indisponibles". Je n'ai pas encore pris le temps de chercher et je commence tout juste. Je vois que j'ai vraiment bcp d'appels au lixee et qu'il faudrait surement réduire le nombre car ça ne semble pas utile d'avoir un appel toutes les 5 ou 10 sec. J'ai déjà mis des choses en WHITELIST pour limiter le nombre de propriétés. Mais je souhaite en garder un grand nombre. Bref, à suivre...

[2024-10-23 17:16:27] warning: 	zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d0005d24c84/1 liXeePrivate.read(["currentDate","currentIndexTarif","currentPrice","currentTarif"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))
[2024-10-23 17:16:45] warning: 	zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d0005d24c84/1 liXeePrivate.read(["injectedActiveLoadN","injectedActiveLoadN1","injectedVA","message1"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))
[2024-10-23 17:17:03] warning: 	zhc:lixee: Failed to read zigbee attributes: Error: ZCL command 0x00158d0005d24c84/1 seMetering.read(["currentSummReceived"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))

[2024-10-23 17:19:20] warning: 	z2m: Failed to ping 'Lixee ' (attempt 1/2, ZCL command 0x00158d0005d24c84/1 genBasic.read(["zclVersion"], {"timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233)))
[2024-10-23 17:19:41] warning: 	z2m: Failed to ping 'Lixee ' (attempt 2/2, ZCL command 0x00158d0005d24c84/1 genBasic.read(["zclVersion"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233)))

[git-greatguy]

Have same error with reporting some data. I tried to dig in device configuration and found something weird in database (front end show duplicate lines as well).

This happens after I "tune" reporting inverval for specific data. here is revelant extract from z2m db for zlinky

{"cluster":1794,"attrId":258,"minRepIntval":60,"maxRepIntval":900,"repChange":100,"manufacturerCode":null},
{"cluster":1794,"attrId":260,"minRepIntval":60,"maxRepIntval":900,"repChange":100,"manufacturerCode":null},
{"cluster":1794,"attrId":262,"minRepIntval":60,"maxRepIntval":900,"repChange":100,"manufacturerCode":null},
{"cluster":1794,"attrId":264,"minRepIntval":60,"maxRepIntval":900,"repChange":100,"manufacturerCode":null},
{"cluster":1794,"attrId":266,"minRepIntval":60,"maxRepIntval":900,"repChange":100,"manufacturerCode":null},
{"cluster":2820,"attrId":1291,"minRepIntval":60,"maxRepIntval":900,"repChange":1,"manufacturerCode":null},
{"cluster":2820,"attrId":2315,"minRepIntval":60,"maxRepIntval":900,"repChange":1,"manufacturerCode":null},
{"cluster":2820,"attrId":1297,"minRepIntval":60,"maxRepIntval":900,"repChange":1,"manufacturerCode":null},
{"cluster":2820,"attrId":1288,"minRepIntval":60,"maxRepIntval":900,"repChange":1,"manufacturerCode":null},
{"cluster":2820,"attrId":1285,"minRepIntval":60,"maxRepIntval":900,"repChange":1,"manufacturerCode":null},
{"cluster":65382,"attrId":515,"minRepIntval":60,"maxRepIntval":900,"repChange":100,"manufacturerCode":null},
{"cluster":65382,"attrId":516,"minRepIntval":60,"maxRepIntval":900,"repChange":100,"manufacturerCode":null},
{"cluster":2820,"attrId":1293,"minRepIntval":60,"maxRepIntval":900,"repChange":1,"manufacturerCode":null},
{"cluster":2820,"attrId":1295,"minRepIntval":60,"maxRepIntval":900,"repChange":1,"manufacturerCode":null},
{"cluster":2820,"attrId":1295,"minRepIntval":60,"maxRepIntval":900,"repChange":10},
{"cluster":2820,"attrId":1293,"minRepIntval":60,"maxRepIntval":900,"repChange":10},
{"cluster":2820,"attrId":1291,"minRepIntval":60,"maxRepIntval":900,"repChange":10},
{"cluster":2820,"attrId":2315,"minRepIntval":60,"maxRepIntval":900,"repChange":10}],

After i manually remove duplicate lines attrid 1293,1295,1291, and 2311, everything report good again. I dont know if it is a z2m bug or a @fairecasoimeme bug with "specific" tab values ??!??

[fairecasoimeme]

On the firmware side, it's not possible to get a duplicate report. if a config report with same cluster/attribute is send, it update this line. It's not possible to get 2 lines with same cluster/attributes

You can get firmware config report table with a ZLinky reset when you spy debug port

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days