New device: Moes (Tuya?) ZigBee Thermostat Programmable Temp Controller BHT-002-GCLZBW #4185
Comments
|
Try editing your devices.js like so: then re-pair your device. |
Results in Z2M, how to test? |
|
Thanks @ginkage That certainly produced some results in the log
So that is the default (unrecognised) for TuYa convertors, so maybe not Tuya at all. I got my hands on a Moes zigbee gateway this morning, so also linked it there. Despite getting the transport (network) key It's very,very chatty and its difficult to gather the codes [without experience?] Appreciate the help |
|
Hm... Judging by the modelID, it should've been TuYa, but then again, maybe it does need a special converter to implement. Oh well, at least we tried. |
|
Hi @ginkage, I tried your devices.js update. Here short log after join device Full log here: |
|
@Utyff I've done some further testing, the default log (on failed conversion has been really useful) and have found the following message (DP/data). These are all messages from the Thermostat in response to pressing buttons. Green shaded entries I am certain of, the others I need to confirm further.
|
|
Will look at the toZigbee.js converter next. attached the analysis of tozigbee message content |
|
Hi, @insipiens. I am trying to make some protocol analysis too, but it's my first experience and i have some troubles. I can't catch transport key for decrypting payloads. I've tried many times to pair device with hub, but 'transport key' frame doesn't occur. I ask for advice |
|
You want to search for the "Transport key" identifier in the Info column in wireshark, you can reorder it by clicking the info column header. Attached a screenshot of the process , locating the Transport key in the Info column and then locate the data for the key in the Zigbee security header. You'll need to enter this in the preferences for the zigbee protocol - AES-128 encryption. I would recommend putting "zbee_aps" in the display filter once set up so you see relevant messages for Zigbee Home automation.
|
|
Assuming this can be closed now because changes have been added. Changes will be available in the latest dev branch in a few hours (https://www.zigbee2mqtt.io/how_tos/how-to-switch-to-dev-branch.html) |
|
Is this Opentherm? I couldn't find the information on the website. |
|
Not opentherm, uses just Tuya or Smart life app. Zigbee2mqtt support has been added to the Dev branch and should be in the master at next update |
|
@Koenkk, I have a thermostat for a warm floor BHT-002-GBLZB, in the dev version it was defined as "Moes Room thermostat water / gas boiler (BHT-002-GCLZB)". The difference is that it has 2 temperature sensors: internal and external. |
@poisondima Do you know the DP of the second temperature sensor? I'm sure we can add it and amend the naming to indicate the family instead of a specific model. Not sure how the HA configuration should be amended for a second temperature, if that is a concern... |
|
@insipiens I have only CC2531, I don't have "Moes zigbee gateway". Of course there are no DP codes. Floor temperature is more important than room temperature, since the room already has xiaomi temperature sensors. |
|
There’s an error clause which should show any unknown dp codes, such as a second temperature when the log is set to debug....that should give the code. |
|
@insipiens I got such a log, but there are no errors. |
|
@poisondima , I can make some changes which you can copy. Just a little concerned if your thermostat has different behaviour than mine - without the hub how do you know what functions it has that can be controlled through Zigbee? On mine it seems to have two ontrollable behaviours:
Which of those do you want as the buttons? and which button does what out of the permitted system modes in HS [“auto”, “off”, “cool”, “heat”, “dry”, “fan_only”] The only other function mine has is programming the thermostat but I don't know HA has an interface to do that plus I am sure Z2M cannot handle lengths of hex required. If you're a github guru you could then handle the PR (I'm new to Github) Let me know..... I have changed mine this afternoon so the buttons turn on/off RUNNING, and a preset for PROGRAM Off/ON |
|
Need a switch that will turn the device on and off. |
|
So here is how mine now looks, It's the thermostat when you click the elipse in the top right corner.
I'll do a little more analysis tonight, if you think it looks acceptable I'll share the code changes with you so you can test it. on your second temperature issue I don't know how to proceed without access to your model of thermostat. |
|
@insipiens Where do I get this fix and try it? :) |
|
I'll post it here for you to try later |
|
I have included the surrounding coding for the device as well as the change made, make backups of each file before changing... 3 files need changing, I've arranged the coding sections below as follows. Hope its clear........YAML is very particular about the indentation used. Best of luck :) changed the parameters of the climate configuration section for device BHT-002-GCLZB that generates the HA thermostat file location: opt/zigbee2mqtt/lib/extension/homeassisant.js Added 2 converters to the device.js file - tz.moes_thermostat_mode, tz.moes_thermostat_standby Added the two converters >> moes_thermostat_mode & moes_thermostat_standby |
|
Ah, also....on reading the instructions for mine, but they cover all models, it mentions that the floor temperature can be displayed by holding the temperature down button for 5 seconds. I wonder if that would create the missing DP code in the log? |
|
Thank! Now at least I can turn the thermostat on and off! |
|
I’ll check the preset memory issue, would be a shame for leaving a little left not done. Cheers |
|
What about adding a 10K numeric resistor as External Sensor ? |
|
@insipiens In the device notes I saw the debounce: 1 recommendation to stop spamming. I've implemented it, but it doesn't seem to work.
Any advice is much appreciated. |
Well, a few things to unpack here.
And I get only two messages in the log. |
|
@insipiens thank you very much for your time and feedback. |
|
Has anyone else had the issue of these thermostats crashing? Mine are doing it about once every week or two, when it happens it's always exactly when a temperature change command has been issued. The thermostat then 'reports' a temperature of 6550 degrees C (!) whilst the screen goes blank and the backlight turns on. It goes completely unresponsive after this and requires mains power off-on to fix. I'm pretty convinced it's a communications issue, going to work through resetting them and re-adding to the network, trying them without being connected to zigbee, etc - just interested if anyone else has had this problem? |
Occasionally I had this but not recently and certainly not as frequent as weekly. It was, in my case, some mis-reading of the temp and was easily resolved by setting a new temp. What Z2M version you currently using? |
1.18.1 Unfortunately when they become unresponsive that's it - can't set a new temp or interact with them in any way. Power off-on is the only fix. I have unpaired, deleted all reference to them in states.json, database.db etc. and re-paired. Have also turned off debounce in case that was causing issues. Will see how we get on. |
|
I guess if this has been happening for over a month then it probably won’t be version related. would be interesting to know your findings ....👍 |
|
don't you try to set wrong temp such as .5, 19.5 for ie ? |
Nope. Only integers. |
And between 5-35 °C I suppose. I can only reproduce while setting a wrong temp on my side. |
|
Alasdair, I completely forgot but a PR was submitted in February Koenkk/zigbee-herdsman-converters#2268 I don't know if that is related to your issue, either solves it or otherwise? Insipiens |
I mean, that sounds like exactly the problem! And I wouldn’t have had it fixed until now because I was using custom converters to fix the clock problem. Since recent updates, moving away from custom converters, and re-pairing my thermostats all has been ok (but still less than 48hrs!) EDIT: it crashed again, but that's fine - I'm on Z2M 1.18.1 which uses herdsman-converters 14.0.72. The fix is in 14.0.78, hence why I'm still getting crashes. Z2M 1.18.2 uses herdsman-converters 14.0.102 which includes all fixes plus a load of other nice features so I will be patient for the next release :) |
|
@aegjoyce I have exactly the same problem since a few weeks with my 002GBLZB ... Unresponsive white screen until full reboot via power off :( I'm using the thermostat since #5154 was fixed. The thermostat was stable for about one month and then the crashing has begun. Sometimes daily, sometimes every week... I noticed that the internal temperature Next step was to verify that my heating control script isn't the cause for this. That's why installed another version of this thermostat (002GALZB) next to the other and both thermostats are receiving the same commands. The funny thing is, that the original device never crashed again since the 2nd device was installed. Instead the 2nd device crashes every week... |
|
I’m still on 1.17.1 and it’s fine for me, but is there some specific scenario which seems common to this...such as the temperature sensor reading values outside the normal range? |
|
Btw its always useful to read the release notes for versions - often there can be multiple PRs for a device and if you’re experiencing problems you’re often the best person to try solving it by backing out to a previous working version and experimenting with scenarios that might cause the error this is just a comment and not meant as chiding at all 🙏🏼 |
Hi, is it really so that in the zigbee version of this device the floow temperature is not readable in any way? Does the device still follow it in some way? edit: seems changing the sensor type (IN, AU, OU) will affect which sensor is reported. I was surprised of this as the wifi version reports both. Is it so that not even the Tuya zigbee hub can show both temps for these? |
|
edited I noticed this happening on mine now, oddly it was fine last winter but a few things have changed - newer version of z2m, changed heating automation I created. Happens when the heating timer (a Honeywell programmable timer) switches on the central heating. the thermostat shows -1.9 degrees and is unresponsive. I have to bounce the heating power and then it starts normally. Weird thing is it's inconsistent, some mornings its fine......my initial assumption is the thermostat might be faulty. Z2M wouldn't be at fault and switching the power shouldn't cause an issue unless the device can't handle it.... |
|
I’ve been watching this issue for a while @insipiens and have the same with mine. Tempted to go for a replacement or flash the Wi-Fi model. Like you say there’s no rhyme or reason to the cause of the failure mode except the same symptoms. -2.9°C reported. Backlight on. Screen blank. I’ve got an automation set to trigger a notification in HA on failure so I can power cycle the heating circuit. Not so useful when I’m asleep though. Sometimes it fails multiple times a day, other times it’s weeks or months between. I think there is an increase in failures following increased interaction though. Might be a misnomer though. I’ve got two thermostats, and both have the same issue albeit at separate times. |
|
The crashing issue has not occurred to me yet, but I am slightly annoyed with the temperature changes when those are 'hold/manually' set. It keeps adjusting itself as per the screenshot. The spikes are when I change it manually, and it keeps knocking it down systematically. Does anyone experience the same issue?
Also, I noticed that I cannot get into System Function Settings as per the below: |
|
Not had that issue myself. Mine looks like the attached (30° spikes are caused by an automation when heat is detected as required elsewhere in the house) Is it in manual mode, again, I’ve got an automation to keep it there.
|
Sounds like device does not send update to controller and controller reverts it back to last temp it still holds on the next update 🤔 This coupled with the settings problem makes it sound like a faulty unit? |
I think I figured it out after several hours of testing. There are some issues with the capacitive button as it activates itself randomly. It works perfectly when I turn the 'child lock' ON. The capacitive button in question is the 'arrows down' that activates randomly and for no reason, and it drops the set temperature if it activates too many times at short intervals - 1st to show the set temp and then shortly after to drop it down. As you can see on my graphs, it activates several times in the space of several hours.
This one could be related to something intentionally done by MOES. I noticed I have the latest hardware iteration where the touch buttons controller is on-chip rather than the old version where it was a separate IC. I found the reference in this video https://youtu.be/JPWpryQ2m6I?t=810 The board from 2021 found in the video and my v4 board below: I reckon they disabled access to this function (to enforce buying a hub) or the unit is faulty as you suggested. |
I've also had this exact same issue with my Thermostat, I've been wondering for weeks why it would change modes and temperature all by itself. |
|
@brettcollis2212 I checked Amazon UK and some recent comments are the same. It looks like the latest batch is faulty and should be avoided at all costs. |
|
So the symptom of a faulty unit is that it changes setpoint by itself? Luckily haven’t seen this yet on my devices bought in 10/2022. Is there some serial number or something to identify the faulty batches? |
@odelma So far, I only identified this board and its version written at the top I have one more thermostat to be delivered shortly, and I will check its version and report back. |
I have a small update based on observation:
So, imo poor Moes/Tuya programming, but turning the thermostat off before the heating each night has resolved the problem for me. One gets what one pays for - ha.... image of -1.9 every morning when heating circuit is powered up: |
and others
What happened: Device is not supported
What did you expect to happen: Expected to follow the procedure to add the device and review debug level logs - logs are empty. wireshark output included but outside my experience level to resolve
How to reproduce it (minimal and precise): pair this new device?
Debug Info
Zigbee2MQTT version: 1.14.3
Adapter hardware: CC2531
Adapter firmware version: current (last month)
Moes ZigBee Smart Thermostat Programmable Temperature Controller for Water/Gas Boiler BHT-002-GCLZBW
Device website: https://www.moeshouse.com/collections/smart-thermostat/products/white-zigbee-smart-thermostat-programmable-temperature-controller-zigbee-hub-required-for-water-gas-boiler
User manual: https://support.gw-ec.com/upload/qa/2018/11/19/3019d10504894c7327d18fc07389bbe6.pdf
I've attached the work[?] I did in the attached text file: proforma device.js and resulting outputs etc.
Moes Zigbee Thermostat.txt
Any advice on progressing from here appreciated
The text was updated successfully, but these errors were encountered: