Failed to read zigbee attributes: Error: Cluster 'liXeePrivate' has no attribute 'motDEtat'

[RastaChaum]

What happened?

Noted in the logs, this recurring message appears:

"Failed to read zigbee attributes: Error: Cluster 'liXeePrivate' has no attribute 'motDEtat'"

What did you expect to happen?

This message should not be encountered, as it suggests the presence of a coding issue.

How to reproduce it (minimal and precise)

No specials configurations. This is the default setup

Zigbee2MQTT version

1.36.1

Adapter firmware version

20230507

Adapter

zStack3x0

Setup

Docker installation on raspberry PI 2B

Debug log

Docker Z2M version REPOSITORY TAG IMAGE ID CREATED SIZE koenkk/zigbee2mqtt latest 60a241badfae 3 weeks ago 104MB

Lixee details Constructeur Modèle Date du firmware Version du firmware LiXee ZLinky_TIC 20230214 4000-0013

[RastaChaum]

The message in question occurs each time information is retrieved, accompanied by the following message:

zlinky config: historique, single_phase, false, H PLEINE/CREUSE
Failed to read zigbee attributes: Error: Cluster 'liXeePrivate' has no attribute 'motDEtat'

[ghostsam45]

same issue

2024-05-03 17:47:50 Failed to read zigbee attributes: Error: Cluster 'liXeePrivate' has no attribute 'motDEtat'

Version de Zigbee2MQTT [1.37.0] commit: [46f34c8] Type de coordinateur ConBee2/RaspBee2 Révision du coordinateur 0x26780700

Lixee ZLinky 20230214

[ceduderino]

same issue

2024-05-03 17:47:50 Failed to read zigbee attributes: Error: Cluster 'liXeePrivate' has no attribute 'motDEtat'

Version de Zigbee2MQTT [1.37.0] commit: [46f34c8] Type de coordinateur ConBee2/RaspBee2 Révision du coordinateur 0x26780700

Lixee ZLinky 20230214

same configuration, same issue

[Koenkk]

@mildis Could you maybe check this ?

[mildis]

Well, to my understanding, motDEtat is tied to Linky legacy mode. If there’s a mismatch between Linky mode and how Lixee try to parse data, this might occurs.

@RastaChaum @ceduderino @ghostsam45 Are your Linky in standard mode or « historique » (legacy mode) ? Does forcing the Lixee parameter to the correct value instead of « auto » helps ?

[ceduderino]

Well, to my understanding, motDEtat is tied to Linky legacy mode. If there’s a mismatch between Linky mode and how Lixee try to parse data, this might occurs.

@RastaChaum @ceduderino @ghostsam45 Are your Linky in standard mode or « historique » (legacy mode) ? Does forcing the Lixee parameter to the correct value instead of « auto » helps ?

My Linky is in "historique" mode. I have now forced the Lixee "Linky mode" parameter to "historique", but I get the same message. 2024-05-04 12:49:11Failed to read zigbee attributes: Error: Cluster 'liXeePrivate' has no attribute 'motDEtat'

[mildis]

@ceduderino Do you have a line like "zlinky config: historique, single_phase, false, H PLEINE/CREUSE" ?

[ceduderino]

@ceduderino Do you have a line like "zlinky config: historique, single_phase, false, H PLEINE/CREUSE" ?

I have no such thing in the log (I am logging at info level). But my configuration.yaml is as follows:

friendly_name: ZLinky_TIC
measurement_poll_interval: ''
kWh_precision: 3
linky_mode: historique
energy_phase: single_phase
tarif: Historique - BASE

[BAKSLASH971]

hello , i have the same problem

[mildis]

Well, I see nothing obvious in the code and as I'm using the Standard mode, I can't help. Maybe @SilentT-FR who implemented this can help. Also, have you tried to rollback to koenkk/zigbee2mqtt:1.36.1 to see if the problem is still here ? Or at least logged ?

[RastaChaum]

"Hello everyone, I've just reviewed your responses. I am currently in auto mode with koenkk/zigbee2mqtt:1.36.1. Before making any changes, I checked my logs again. To my surprise, I no longer see that message since the morning of April 28th. I don't recall making any modifications that day. However, I did turn off my electricity meter a few times while working on my radiators. This could potentially have affected the Lixee module. This is a rough guess, but it might be worthwhile for @ceduderino or @ghostsam45

[ghostsam45]

Well, I see nothing obvious in the code and as I'm using the Standard mode, I can't help. Maybe @SilentT-FR who implemented this can help. Also, have you tried to rollback to koenkk/zigbee2mqtt:1.36.1 to see if the problem is still here ? Or at least logged ?

looking in the logs of version 1.36.1, I did not have this error

[BAKSLASH971]

No error log with 1.36.1

[remidebette]

Reading the latest release notes, is this issue fixed by https://github.com/Koenkk/zigbee2mqtt/issues/21825 ?

[lecourtb]

Same issue with Z2M 1.38.0, "historique" mode, triphasé, measurement poll chunk = 1