Lixee ZLinky crashes Gladys

Vianney · January 22, 2023, 4:32pm

Hello everyone,

Big problem with Gladys since I tried to add the Lixee ZLinky module.
It is well detected by Zigbee2MQTT and I can see it in the Z2M interface. No problem at this level.
On the other hand, as soon as I try to integrate it into Gladys, things get complicated.. It is well detected via discovery. I can integrate it, add it to my device list. However, as soon as I try to save (or perform any operation on it via Gladys), Gladys crashes.. I have the loading icon spinning in a loop and Gladys seems « empty »…

When I look at the logs, Gladys seems to be looping on operations involving the sensor[details=« Logs Gladys »]

{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature drawn_v_a_max_n1 not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.954121846Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature message1 not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.95642981Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature message2 not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.958666941Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature meter_serial_number not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.960582562Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature rms_current_max not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.963160785Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature rms_current_ph_b not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.964999792Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature rms_current_ph_c not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.979539396Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature schedule_h_p_h_c not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.979678459Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature site_id not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.979708406Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature software_revision not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.979756115Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature start_mobile_point1 not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.979784813Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature start_mobile_point2 not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.979812469Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature start_mobile_point3 not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.982060172Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature start_notice_e_j_p not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.984475948Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature status_register not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.986786933Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature stop_mobile_point1 not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.989265417Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature stop_mobile_point2 not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.991605985Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature stop_mobile_point3 not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.994035147Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature tomorrow_color not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.996360142Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature update not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:03.998878782Z »}
{« log »:« 2023-01-22T12:23:03+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature warn_d_p_s not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:04.001247892Z »}
{« log »:« 2023-01-22T12:23:08+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature active_power_max not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:08.034296402Z »}
{« log »:« 2023-01-22T12:23:08+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature active_register_tier_delivered not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:08.037986863Z »}
{« log »:« 2023-01-22T12:23:08+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature apparent_power not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:08.053753496Z »}
{« log »:« 2023-01-22T12:23:08+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature current_date not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:08.057776091Z »}
{« log »:« 2023-01-22T12:23:08+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature current_price not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:08.070534553Z »}
{« log »:« 2023-01-22T12:23:08+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature current_tarif not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:08.073449964Z »}
{« log »:« 2023-01-22T12:23:08+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature current_tier3_summ_delivered not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:08.076166104Z »}
{« log »:« 2023-01-22T12:23:08+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature current_tier4_summ_delivered not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:08.079132451Z »}
{« log »:« 2023-01-22T12:23:08+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature current_tier5_summ_delivered not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:08.081745258Z »}
{« log »:« 2023-01-22T12:23:08+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature current_tier6_summ_delivered not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:08.084635565Z »}
{« log »:« 2023-01-22T12:23:08+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature days_number_current_calendar not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:08.087393371Z »}
{« log »:« 2023-01-22T12:23:08+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature days_number_next_calendar not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:08.090601177Z »}
{« log »:« 2023-01-22T12:23:08+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature days_profile_current_calendar not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:08.093416483Z »}
{« log »:« 2023-01-22T12:23:08+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature days_profile_next_calendar not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:08.096746528Z »}
{« log »:« 2023-01-22T12:23:08+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature drawn_v_a_max_n1 not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:08.099926886Z »}
{« log »:« 2023-01-22T12:23:08+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature message1 not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:08.103602659Z »}
{« log »:« 2023-01-22T12:23:08+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature message2 not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:08.106357445Z »}
{« log »:« 2023-01-22T12:23:08+0100 handleMqttMessage.js:101 () Zigbee2mqtt device 0x00158d000966cb9d, feature meter_serial_number not configured in Gladys.\n »,« stream »:« stderr »,« time »:« 2023-01-22T11:23:08.109563948Z »}
[/details]

I wonder if this is related to the fact that the sensor has many features (I changed my Linky meter from historical to standard)

What can I do to fix this issue? For now, I have unplugged my Zigbee doodle to avoid crashes in Gladys..

pierre-gilles · January 25, 2023, 2:20am

Hi @Vianney and welcome to the forum!

Oh, do you have any other logs in Gladys? These logs are normal, they just indicate that some features of your sensor are not handled by Gladys, but it’s not blocking ^^

Vianney · January 25, 2023, 8:51pm

Hi @pierre-gilles and thanks for the welcome

I don’t have anything else in the Gladys logs. I tried re-adding my Zigbee module (SONOFF ZigBee 3.0 USB Dongle Plus, for reference if needed) and to collect the logs from that moment. I didn’t see anything more than the operations looping as Warnings

On the Gladys interface, it looks like this.. My user changes to User, and in the other tabs it’s impossible to display the content (except the calendar and the explanatory panel on the right in Discussion)

I might run other tests, run top to compare source usage without and with the dongle paired in Gladys
On the Zigbee2MQTT side (via the Z2M interface), everything is OK

cicoub13 · January 25, 2023, 9:08pm

If I remember correctly, @VonOx had noticed that the module was reporting a huge amount of data and that a filter was needed in the zigbee2mqtt configuration.
Maybe that’s related to this

Here Données de consommation compteur Linky - #44 par VonOx

Vianney · January 26, 2023, 8:43pm

Hi @cicoub13,

Thanks for your help.
I tried filtering via the whitelist like in the message from your link. I can filter on the Z2M interface (I used the same whitelist and I get the same results in Expose).

But once back from Gladys, when I try to update it… it starts again, still the same issue.
I retrieved the logs while doing the device update. I have errors in them like this.

{"log":"2023-01-26T20:53:48+0100 \u003cerror\u003e handleMqttMessage.js:98 () Failed to convert value for device 0x00158d000966cb9d: Error: Zigbee2mqqt expose not found on device \"0x00158d000966cb9d\" with property \"current_tier9_summ_delivered\".\n","stream":"stderr","time":"2023-01-26T19:53:48.472190174Z"}
{"log":"    at Zigbee2mqttManager.readValue (/src/server/services/zigbee2mqtt/lib/readValue.js:16:11)\n","stream":"stderr","time":"2023-01-26T19:53:48.472349336Z"}
{"log":"    at /src/server/services/zigbee2mqtt/lib/handleMqttMessage.js:94:31\n","stream":"stderr","time":"2023-01-26T19:53:48.472399438Z"}
{"log":"    at Array.forEach (\u003canonymous\u003e)\n","stream":"stderr","time":"2023-01-26T19:53:48.472426989Z"}
{"log":"    at Zigbee2mqttManager.handleMqttMessage (/src/server/services/zigbee2mqtt/lib/handleMqttMessage.js:86:41)\n","stream":"stderr","time":"2023-01-26T19:53:48.472454332Z"}
{"log":"    at MqttClient.\u003canonymous\u003e (/src/server/services/zigbee2mqtt/lib/connect.js:53:12)\n","stream":"stderr","time":"2023-01-26T19:53:48.472503654Z"}
{"log":"    at MqttClient.emit (node:events:513:28)\n","stream":"stderr","time":"2023-01-26T19:53:48.47253058Z"}
{"log":"    at MqttClient._handlePublish (/src/server/services/zigbee2mqtt/node_modules/mqtt/lib/client.js:1277:12)\n","stream":"stderr","time":"2023-01-26T19:53:48.472581203Z"}
{"log":"    at MqttClient._handlePacket (/src/server/services/zigbee2mqtt/node_modules/mqtt/lib/client.js:410:12)\n","stream":"stderr","time":"2023-01-26T19:53:48.472607921Z"}
{"log":"    at work (/src/server/services/zigbee2mqtt/node_modules/mqtt/lib/client.js:321:12)\n","stream":"stderr","time":"2023-01-26T19:53:48.472657555Z"}
{"log":"    at processTicksAndRejections (node:internal/process/task_queues:77:11)\n","stream":"stderr","time":"2023-01-26T19:53:48.472684117Z"}

I checked and it’s the right device. But why is it trying to retrieve values for a property I didn’t ask for and that’s not exposed (and doesn’t appear in this device’s features for Gladys)?

I’m attaching a screenshot of the device in Gladys. There’s an unnamed feature, which is the relay. I wondered if it could possibly come from there. I tried removing the property from the whitelist; it does disappear in Gladys but the update is still impossible

One point I thought I had mentioned in my previous message. I had already paired it while in HISTORICAL mode on the Linky. At that time it worked fine. I’ve had problems since switching to STANDARD (I tried deleting the device in Z2M and re-pairing it, without success)

VonOx · January 26, 2023, 9:34pm

There’s something weird, updating will just align the features.

But the logs tell us something else.

As indicated in the Lixee doc, did you reconfigure the module after changing the settings? (whitelist and historical mode)

Another thing to check is the firmware version

When you say update, do you mean the green Gladys « Update » button?

Vianney · January 26, 2023, 10:12pm

Hi @VonOx, to answer your questions

Quote
Is it, as indicated in the Lixee doc, that you reconfigured the module after changing the settings? (whitelist and history mode)

If we are indeed talking about the orange button in the device’s Z2M interface, I had doubts that I had done it after removing the Relay feature. So I did it again (+ restarted the Gladys container) but same symptom (log + Gladys)
In the Status tab (in the Z2M UI), however, I do have these fields that are in error in Gladys (current_tier9_summ_delivered etc.). I don’t know if that’s normal (I’m new to Z2M)

Quote
When you say update, do you mean the green Gladys « Update » button?

Yes that’s it, the « Update » button you can see in my previous screenshot

Quote
Another thing to check is the firmware version

Using « OTA Update », I get the

Vianney · January 28, 2023, 8:04pm

I apparently finally managed to solve my problem (I’ll keep monitoring the issue but as of now everything is OK)

I think this might be useful for people working on the project, here are the steps I carried out:

In Gladys, Zigbee2mqtt section and Devices tab:
- Click the « Save » button corresponding to the device
  
  image435×392 9.27 KB
Zigbee Discovery section:
- Click « Update » corresponding to the device
  
  image427×480 9.82 KB

And that fixed my issue.
I should note that before performing these steps, I had set a whitelist and made sure that the exposed parameters were the same as those in Gladys for this device in the Devices section (see my 1st point)

Topic		Replies	Views
Zigbee2mqtt non fonctionnel Configuration zigbee2mqtt	11	36	February 23, 2026
Zigbee2mqtt - services démarrés mais croix rouge pour le lien Configuration	59	1886	May 13, 2023
Plus d'affichage température et d'humidité depis la V.28 Configuration	43	763	October 23, 2023
Bug affichage box - timeout réponse instance locale via Gladys Plus Configuration	34	963	September 7, 2022
[Résolu] Zigbee2mqtt n'est plus opérationnel sur ma config, de façon soudaine Configuration	23	995	December 9, 2023

Lixee ZLinky crashes Gladys

Related topics