Well, I hope you’re not too disappointed with Gladys… even if it’s the module that’s lacking.
And besides, what a crazy idea to have three-phase power
Jokes aside, I’ll pass it through a Lixee TIC DIN rail, single-phase, but it doesn’t change much for retrieving the information.
When the guys installed my Linky meter, I asked them to connect C1 and C2 so that I could then connect these two cables (already present in my electrical box) and thus avoid wireless.
For now, I’m using a teleinfo2mqtt docker, but there is now a dedicated integration teleinfo by @prohand.
Hello, and following my tests. No, I am not at all disappointed with Gladys, on the contrary, I find the application very pleasant both to use and visually. The fact that it is simple is a major asset, compared to these things that are real gas factories, perhaps they do more things, but Gladys is still young. Very bright future.
Then, yesterday, I connected the Lixee to another Linky meter, single-phase, with my raspberry, I had the same thing as at home. Yet, I had indeed deleted the old Lixee. On the other hand, I noticed that it was the same ID 0xx00158d0006206a00. Is this identifier recorded « hard » in the Lixee, or is it created by Gladys?? I think it is important to know.
Well, in any case, the mess is back with the seller, so that I can be refunded. I will take 3 current sensors (at Ali), it will be more practical, even if I do not recover all the information from the Linky, but I also have to modify my fuse box to install all that.
Well, thank you again for your help, and I am still waiting for the update for the Triphasé. You will let me know.
Good continuation to all, and good luck with the development…
The IEEE Zigbee address is a unique 64-bit identifier (in MAC format) assigned to each physical device (bulb, sensor, coordinator) at the time of manufacture. It serves as a permanent ID card.
So it is hardcoded in the Lixee.
Thanks for the information. Do you know if there is a relationship between the identifier and the device model, because in my case, it seems the wrong model was delivered to me. If that’s the case, I will express my dissatisfaction at LIXEE. If you have a link, specifically to the assignment of identifiers,
Good evening to everyone, and thanks for your expertise. Keep it up, it’s great,
Not directly. The IEEE address (0x00158d0006206a00) is read in two parts:
00158d (the first 6 characters) is the manufacturer prefix (OUI). It identifies the Zigbee chip manufacturer, not the product. 00:15:8D belongs to Jennic, now NXP: MAC address 00:15:8D | MAC Address Lookup
0006206a00 is the unique serial number of the chip.
However, the model displayed by Zigbee2MQTT does not come from this address. It is the firmware that announces it at the time of pairing (fields modelID and manufacturerName). A real ZLinky announces ZLinky_TIC / LiXee. Yours announces TS0601 / _TZE284_dikb3dp6, which is a Tuya identity.
This becomes interesting for your claim: the ZLinky actually uses an NXP chip. Your device therefore has a chip consistent with a ZLinky, but firmware that presents itself as a Tuya module. It looks more like a flashing problem than a bad manipulation on your part. And the previous pairing with Tuya Smart cannot rewrite the identity announced by the firmware.
For LiXee, you can therefore highlight:
the IEEE address 0x00158d… (NXP chip, like a ZLinky);
the announced model TS0601 / _TZE284_dikb3dp6 instead of ZLinky_TIC;
the firmware 6000-1017 / 20250923;
the same result on two different Linky meters (three-phase and single-phase), after complete removal in Zigbee2MQTT.
Good evening Bernard, and keep us informed of LiXee’s response!
Hello. It’s really pleasant to be able to talk with competent people, it’s so rare in this virtual world. I will check with the reseller to see what they think. Maybe they are not the origin of the firmware. The correct model (according to the screenshot from « cicoub13 »), would be 0x00158d0005d29ebc, with a firmware ID 4000-0017 20250923 and a definition ZLinky_TIC (v0.0.1).
There you go, thank you for the time spent solving my problem. Have a good day everyone, Bernard
