Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
11.73k stars 1.64k forks source link

Lixee only explose some parameters names but not all #20816

Closed caubios closed 3 weeks ago

caubios commented 7 months ago

What happened?

I use Zlinky_TIC from Lixee integration in Zigbee2MQTT in Home Assistant.

As you can see in the picture bellow, some parameters are displayed with default name MQTT Sensor instead of EAST, EASF01, EASF02, EASD01 & EASD02 as the other parameters (ex CCASN). MQTT Sensor as exposed in HA

Display-wise, looking into MQTT broker, the root commonality between all "MQTT Sensor" displayed in HA seems to be the lack of name root tag inhomeassistant/0xXXXX/{EAST/EASF01/EASF02/EASD01/EASD02}/config (see bellow) No MQTT Name Tag compared to any other parameter (eg CCASN param) MQTT name tag

The only difference I can spot in code base right-now (and I'm a Z2M noob) are :

But i cannot still figure it out why this name tag is not declared in MQTT broker... Any clue? With some i should be able to figure something and try a pull request to fix it!

P.S. : I do not have parameters like EASF03, EASD03, HCHC, etc. exposed as I'm in Standard HP/HC mode with 1 phase only and I'm not producing any power to the grid (aka excluded parameters).

What did you expect to happen?

I would expect all lixee exposed data to declare their name through MQTT in order to have then automatically displayed in Home Assistant. It will ease all the on-screen display and so.

How to reproduce it (minimal and precise)

Running lixee and and MQTT broker viewer should do the trick

Zigbee2MQTT version

1.35.1

Adapter firmware version

0x26670700

Adapter

ConBee2

Setup

Extetnal Mosquitto setup Z2M on Synology Conainer Manager (Synology fork of docker) HA on Synology Conainer Manager (Synology fork of docker)

Debug log

No Debug at this point as I'm not sure which one could be interesting.

github-actions[bot] commented 1 month ago

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days