-
### The problem
This issue is a follow up of the https://github.com/home-assistant/core/issues/106712 issue, apparently solved by https://github.com/home-assistant/core/pull/106738 but seemingly not …
-
### 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"
…
-
### 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
2 months ago
-
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?
I use [Zlinky_TIC from Lixee](https://www.zigbee2mqtt.io/devices/ZLinky_TIC.html) integration in Zigbee2MQTT in Home Assistant.
As you can see in the picture bellow, some par…
-
### 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…
-
It seems that when the tested entity's status contains a space character, the card that should be displayed isn't.
That happens for instance with the following
type: custom:state-switch
entit…
-
### 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.
###…
-
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…