Koenkk / zigbee2mqtt

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

BHT-006GKLZB recognized as Tuya TS0601_floor_thermostat - local_temperature always = 0 degree, name of the day always two days behind on the display #23890

Open gklank opened 2 months ago

gklank commented 2 months ago

What happened?

BHT-006GKLZB connected to the zigbee2mqtt. All running fine, like changing heating temperature, etc. etc.

What did you expect to happen?

I expect the:

How to reproduce it (minimal and precise)

Just link the BHT to the zigbee2mqtt coordinator

I have deleted the device and tried a second time: it's again the same behavior.

Zigbee2MQTT version

1.40.0

Adapter firmware version

20230507

Adapter

CC2652R_coordinator

Setup

single separate docker container

Debug log

log.log

gklank commented 2 months ago

Hi,

first, sorry: the device is without the "L". Correct is: BHT-006GBZB

Tested further...

  1. The identification of the device as shown above - still there.

  2. The thermostate has two temperatures: internal, which is shown in the mqtt server as "device_temperature external, which is shown the the mqtt server as "local_temperature" 2a. in Homeassistant the "local_temperature" is used as the "actual temperature" per default this can be changed in the config session in the mqtt server. just change the entry: "current_temperature_template": "{{ value_json.local_temperature }}", to: ""current_temperature_template": "{{ value_json.device_temperature }}"," 2b. after installing the external sensor the "local_temperature" is showing reasonable temperatures...

  3. wrong name of the day is now the main issue!!!

Regards

Gerhard

gklank commented 1 month ago

Hi,

may be it sounds like an unimportant issue, but it*s really tiring to read "SAT" but it is "MON", and "SUN" but it is "TUE", etc.

Therefore I am doing some try and error in the tuya.js wtih the entry of "fingerprint: tuya.fingerprint('TS0601', ['_TZE200_edl8pz1k', '_TZE204_edl8pz1k']),":

JÍ just put //onEvent: tuya.onEventSetTime, // Add this if you are getting no converter for 'commandMcuSyncTime' on "comment"...

And yes, not surprising after connecting to the zigbee2mqtt the time will not be set, the day of the week is also not set. With that I am able to set time and day per hand - looks like all fine now.

But in my view it is bad work around...

Is there any idea how I can fix this correctly?

From where is the time and day of the week taken?

Regards

Gerhard