Open incognito1234 opened 5 months ago
To try to move forward in solving this problem, I search the line code which raises the error.
I have found that the line 1021 of file node_modules/zigbee-herdsman-converters/devices/lixee.js
is the bad line:
onEvent: async (type, data, device, options) => {
const endpoint = device.getEndpoint(1);
if (type === 'start') {
endpoint.read('liXeePrivate', ['linkyMode', 'currentTarif'], { manufacturerCode: null })
.catch((e) => {
// https://github.com/Koenkk/zigbee2mqtt/issues/11674
console.warn(`Failed to read zigbee attributes: ${e}`); // <-- Line 1021
});
}
Is this information helpfull ?
I also found that break on connexion can be simulated by stopping zigbee2mqtt.
Thanks
What happened?
After a long break in connexion, lixee attributes are not retrieved anymore even if connexion is restored. The device needs to be repaired to retrieve attributes again.
What did you expect to happen?
When the connection is restored, there should be no errors logged and the attributes should be retrieved successfully.
How to reproduce it (minimal and precise)
npm start
) to get zigbee2mqtt errorZigbee2MQTT version
1.36.0
Adapter firmware version
a003
Adapter
ZLinky_TIC with PiZiGate
Setup
Standalone zigbee2mqtt service on rpi4
Debug log
First start after device configuration and break in connexion
output after npm start command
log after npm start command