Moes BHT-002 Thermostat with updated model ID TZE204_xalsoe3m

Device Requests
1

I purchased this thermostat as it was listed as compatible with deCONZ. Whilst this is true, the hardware has been updated and as such, the “manufacturename” is not listed in the DDF. The device currently loads as a smart plug.

The trouble is, as I’m in Home Assistant with the official add-on, I cannot upload a modified version of the current DDF to include the new manufacture name as add-ons are now sandboxed.

Seems like a simple fix to me as hardware functionality is identical.

For info - the current listed hardware is:

“manufacturername”: [
“_TZE200_ztvwu4nk”,
“_TZE200_ye5jkfsb”,
“_TZE204_aoclfnxz”,
“_TZE200_u9bfwha0”

The new one is:

“_TZE204_xalsoe3m”

Thanks.

2

The problem is we need tests, tuya is making clone of clone and some model can be different.
If you can’t edit the DDF, you can create a new one using the deconz tool Deconz Toolbox
And load it using Phoscon (need to restart it after)

Remember you need to edit 2 lines

  "manufacturername": [
    "_TZE200_ztvwu4nk",
    "_TZE200_ye5jkfsb",
    "_TZE204_aoclfnxz",
    "_TZE200_u9bfwha0",
    "_TZE204_xalsoe3m"
  ],
  "modelid": [
    "TS0601",
    "TS0601",
    "TS0601",
    "TS0601",
    "TS0601"
  ],

But from that I m reading, you have a new device, eg your device use the dpid 50 for heatpoint and the DDF is using the dpid 16.

Seems like a simple fix to me as hardware functionality is identical.

All is possible with tuya, you can have same device visualy, buy the same day, at same seller but 2 differents devices.

3

I did try this - it uploaded fine to Phoscon, but the device didn’t take the DDF after hot-reloading or restarting.

What did work was using SSH from Home Assistant whilst deCONZ was still running and then using nano to edit the current DDF. That worked. It’s now showing all of the correct parameters and I can turn it on and off.

What isn’t right is the heat set point, as you mention. Will try changing it to the value you suggested. It’s also not showing the current temperature and seems to randomly cycle through presets.

So I guess I’m 60% there…

Any further suggestions?

4

Yes, if you can do that, you can edit the file, and use the “hot relaod” feature in the DDF editor.
But next time you will restart deconz you will loose your changes.

but the device didn’t take the DDF after hot-reloading or restarting

Do you have the GUI ? if yes you take a look, right clic on the node, then edit DDF, on the editor title bar you will see the path/title.
The DDF can have a typo.

The model “_TZE204_xalsoe3m” use

  • the dpid 16 for local temperature
  • the dpid 2 for mode (only auto-manu)
  • the dpid 39 for child lock
  • the dpid 50 for heatpoint

Don’t see something for preset … if you device have it, try to change it manualy on the device and look on deconz log the request send by the device.

5

Yes - I noticed the changes didn’t hold. What I did to work around it was do the edits using SSH/nano, then open the DDF editor in the deCONZ UI and save it in the default location (then hot-reload). It now sticks after restarting.

Thanks for the dpid values - I’ll try it with those tomorrow and let you know. Happy to help with testing if you let me know what you’d need.

6

We need tests ^^, your procedure is fine for that.
Even it’s not persistent, after that you will be able to load it using the PR, so you will have it persistent.