I’m currently trying to properly integrate a Moes BHT-006 ZigBee Thermostat with my Home Assistant setup using Zigbee2MQTT, but I’m encountering some issues with entity endpoints that I can’t resolve.
I’ve already reached out to Moes support but haven’t received a response yet.
Current Setup:
Connected via Zigbee2MQTT to Home Assistant
Initially tried using Better Thermostat, but experienced unstable behavior
Temporarily removed Better Thermostat to focus on getting basic functionality working
Issue:
When attempting to set the Deadzone Temperature or Max Temperature Limit, the Min Temperature Limit unexpectedly changes to 1°C. Additionally, the current heating setpoint sometimes jumps to 5°C or 45°C.
At the moment, even if I’ve set a current heating point of “20°”, even if it goes down to 18.5 it want restart the heating and stay idle. I need to turn it off and on, or to change the current heating point to 23/24°, to start the heating again.
Here are screenshots of the current configuration:
As someone relatively new to Home Assistant, I would greatly appreciate any guidance from more experienced users on how to make this integration stable and safe.
I don’t own the device, but the device page in Z2M explains what each parameter does.
eg. The jump you’re seeing in Min Temperature Limit is actually the value going from null to 1, which is the minimum value allowed.
I have no idea why you’re seeing those jumps, but I have a feeling it’s because your HA dashboard & your zigbee dashboard are showing different values. Deadzone Temperature is the parameter you would use to ensure heat is called if your local temperature and your temperature are different by X degrees.
What’s weird is that:
HA dashboard shows the deadzone slider all the way to the left (0 or null)
Z2M dashboard shows it set to something like 3
MQTT message shows "deadzone_temperature":null
Maybe it’s because you removed those “similar entries” and that was the first message, before any updates? Can you double check whether the latest messages are identical (and not just similar)?
I had a similar problem with my thermostat. I wanted to try fix it with external converter but without success. Now I use custom firmware from this source tuya_thermostat_zrd and thermostat works as I expected. It has only 1°C step for heat-point etc but it’s nothing serious. Try this.
I see, but the page you linked refers to “Floor Heating Zigbee with custom firmware”, and my Thermostat is not a Floor Heating, but a Gas-Boiler one.
Even if I’ve checked and the ID of the thermostat starts with A4 C1 38 so it should be working.
Installing this firmware made it work better? you are able to set the deadzone temperature? And also the log spamming is a little bit under control now?
Was it difficult to install this firmware? (i see the procedure is quite long)
Unfortunately, I don’t know what the difference is in the firmware for different types of heating.
After installing the firmware, the thermostat’s behavior improved for me. I can set all parameters via Z2M. Especially the dead zone. Unfortunately, only in whole degrees Celsius. As for spamming, I didn’t notice it before, but after the firmware update, it definitely doesn’t happen.
When I tried to install the firmware on the operating system, I was unsuccessful (I have over 70 devices there), but maybe I didn’t do it quite right. Then I used a testing Z2M, which I only use for testing and where it is not active, and the installation went well there. It took about 25 minutes. After installing the firmware and registering it in the original Z2M, the next firmware update went through without any problems.
