-
Bonjour,
Ce post pour demander si d'autres ont l'astuce pour mettre à jour le firmware via OTA avec un taux de réussite élevé...
Depuis la v5 je galère a chaque monté de version pour passer la MAJ, …
-
### What happened?
At least the "Linky acquisition time" feature is missing: https://github.com/fairecasoimeme/Zlinky_TIC#linky-acquisition-time-from-v7
I'm at a loss as to how to implement this i…
ghost updated
1 month ago
-
### What happened?
My Lixee device used to work fine as I was with Energy Supplier Engie with Base offer, then I decided to switch to EDF with Tempo
Since then, I get only feedback value: "Null"
…
-
### The problem
My energy dashboard is reporting negative untracked electricity usage. I don't generate energy, therefore it's impossible.
My global consumption is provided in near real time by a li…
-
### Is your feature request related to a problem? Please describe
I would like to monitor in HA the following expose (status_register_tempo_jour) :
I have the following setup :
### De…
-
Hello,
I have integrated the Lixee dongle on a Sonoff ZBbridge Pro running Tasmota 13.4.0.2, using Z2T to push the Sensor information to MQTT broker. Zigbee integration is successfull and I can `…
-
### 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",…
-
### 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 happ…
-
### What happened?
It was noted that Z2M does not report the correct value when it comes to the firmware version.
Indeed, the latter constantly indicates that the module will be in V1 while it is in…
-
Suite derniere mise a jour j'ai le warning suivant:
Some MQTT entities have an entity name that starts with the device name. This is not expected. To avoid a duplicate name the device name prefix i…