Are there any recommended models of Home Heating Thermostats (Gas) that can be flashed with OpenBeken or similar? Or has anyone flashed one and created a config? This is something I wish to try, as my current Tuya-based unit is rather inflexible with its programmable settings. I would rather buy a new unit rather than dismantle my current one, as I don't wish my current heating to be out of action should the plan not work out.
Hi - I was hoping someone else had already done something of this nature so I could just buy that device. This isn't for experimentation or to see if I can make it work; more just to get my current device off cloud and I feel obk is the easiest way to achieve this. So yes, open to recommendations
Added after 7 [hours] 41 [minutes]:
Do you think it would be possible to replicate the config listed here:
I just wonder if the openrtl supports the DPLDs so I could transfer them over from the Tasmota config. If that doesn’t work out, I can just solder in an ESP32 as they are super cheap
Added after 2 [minutes]:
I just wonder if the openrtl supports the DPLDs so I could transfer them over from the Tasmota config. If that doesn’t work out, I can just solder in an ESP-12 as they are super cheap
Default release does support TuyaMCU so in theory it should work - again just from my experience - I haven't tested that, maybe @insmod can say more or @p.kaczmarek2 ??
Can’t seem to find an ME81H that supports gas boilers that will ship from AliExpress, so I think I’ll buy a replacement Minco one from Amazon, and modify my current one, as that’s a Minco one too.
Added after 1 [hours] 58 [minutes]:
Can’t seem to find an me81h that supports gas boilers that will ship from aliexpress so I think I’ll buy a replacement Minco one from Amazon and modify my current one as that’s a minco one too
Added after 10 [hours] 44 [minutes]:
I have seen some people on this forum have experimented with various thermostats, possibly 2 or 3 different models and I'm wondering how they got on?
Added after 9 [hours] 48 [minutes]:
Took a bit of a gamble as I couldn’t find the any of the ones listed over on the Tasmota site so I bought a cheap Moes unit which has an integrated Beken unit inside. I wonder if I can make this work??
I don't know if OBK provide thermostat card via HA discovery, you will probably have to add it manually via HA config.
I wouldn't recommend ME81H, there are reviews that say that it might die after about a year.
Still, i can provide dpId list if you bought it.
I myself currently use Avatto WT100 (16A, electric heating). Bought two of them without wifi, and then soldered ESP-12F to one and ESP8684-WROOM-01C to another. Have them for about a year.
I’m wondering what to do. The Moes one that arrived today is quite far from the ME81H, whereas my current one is closer to those design- and spec-wise. I’ve had it working for about 2 years now and it’s been fine. I just need one to stand in whilst I work on one of them and try to work things out.
Added after 1 [hours] 17 [minutes]:
This is the Minco Home thermostat I have, I’m hoping it’s quite close to the me81h or can accept an esp12f if required and the dlpds will match up
>>21736146 Since this doesn't look like ME81H, can you provide a backup?
I can extract dpIds from it.
Or share MCU product information (when you start TuyaMCU driver, it should automatically query it. For WT100, it is '{"p":"jaovfquhkmbydxyp","v":"1.0.0","m":0}')
Happy to share my backup; however, I have managed to destroy this board as the pads are very low quality and have come off the board even when just using the lightest of touches to free the Realtek chip. Think I'll find something that is better made.
therein lies the problem i've lost RX, TX and VCC.
Added after 23 [minutes]:
As you can see here pads are all but dead so I had to expose tracks on the board but scraping material away.
It does seem to come up now but naturally this board is no good for normal use in the state it’s currently in.
However one to test with I think maybe. Can provide the back up for dlpds
this is the first time I've got in this deep so forgive my naivety - none of my devices have an MCU involved but if you could do it from the webUI that'd be great. I'm just waiting now to get the config info back as I have another brand new unit to use so i'm glad this half dead one does actually appear to work.
this suggest the mcu is working over tx/rx right? :
Info:TuyaMCU:Received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 CF E9
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 3 type 2-val len 4
Info:TuyaMCU:ParseState: int32 207
Info:GEN:No change in channel 3 (still set to 207) - ignoring
when (if? - I was expecting to see schema ID in extraction but it's null, but your wifi creds are in backup) you paired with Tuya, which of these two is how the device looked in the app?
yellow background but very similar and a bit “older” looking but very similar yes
Thank you for going to the effort of doing that. Would you mind explaining about the key situation etc? As simple as possible so I understand 😂
the second pic is using your factory pin instead of the product key. I thnk there's some preference of order between factory pin and product code. As in, if there's a fac_pin set, then that could mean a different schema is pulled down to the device upon pairing vs just product key. Not 100% sure of the pattern/reasoning.
Added after 2 [minutes]:
anyway, if/when you get OBK up and running you can have it query the TuyaMCU for dpIDs and the key it's using. It just won't have all the values and descriptions you can get from Tuya
This is what the controls looked like in app. Going to try soldering and flashing a new one up (I have a spare similar one at hand) and then see what I can do about this dpid situation - it’s dpID not Dpld right?
New one is all soldered and flashed. Bit of a pain in the butt as the hot air melts the lcd backing and I’m not desoldering the LCD as it’s got about 20 connections.
The Moes one I have is much better built but anyway my next step is to figure out these dplds
Added after 7 [minutes]:
Added after 2 [minutes]:
anyway, if/when you get OBK up and running you can have it query the TuyaMCU for dpIDs and the key it's using. It just won't have all the values and descriptions you can get from Tuya
How do i perform this part? I assume I don’t need to have it all connected up to uart again?
I have a backup of this new unit I’m happy to share again
How do i perform this part? I assume I don’t need to have it all connected up to uart again?
I have a backup of this new unit I’m happy to share again
If your module is soldered back in place and has been flashed with OpenRTL then starting the tuyamcu driver from the web app Logs tab should see the MCU respond in the log box
That's the step insmod mentioned:
insmod wrote:
Or share MCU product information (when you start TuyaMCU driver, it should automatically query it. For WT100, it is '{"p":"jaovfquhkmbydxyp","v":"1.0.0","m":0}')
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 1 (QueryProductInformation) len 49
Info:TuyaMCU:ParseQueryProductInformation: received {"p":"22m2ytawuenfen5b","v":"1.0.0","m":0}
and this is the old "broken" one which you've already confirmed.
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 1 (QueryProductInformation) len 49
Info:TuyaMCU:ParseQueryProductInformation: received {"p":"gw173aldekvpzalg","v":"1.0.0","m":0}
so if not mistaken these keys seem to be Tuyas "method" of having a config in their app, key xy1234 will make the app screen look a certain way and give it certain features. I've noticed that my current "in use" tuya Moes thermostat in the Tuya app entirely diffrent to every other one i've tried albeit with very similar functionality
interesting. so maybe dpIDs above are correct anyway. Not sure what the deal is with the motif in app though.
Additionally, once TuyaMCU driver is running you can send command tuyaMcu_sendQueryState and it should return a list of the dpIDs, so you can at least compare to see if they match what I/we post in json form from Tuya.
The discussion focuses on identifying home heating gas thermostats compatible with OpenBeken (OBK) or similar custom firmware to replace Tuya-based units with limited programmability. Most Tuya devices can be flashed with OBK, but newer models may require additional modifications beyond flashing. The user seeks recommendations for thermostats already supported or easily adaptable to OBK to avoid cloud dependency. A specific interest is in replicating the ME81H thermostat configuration, which uses a Realtek 8710c chip, rather than switching to ESP32. The current thermostat uses a WBR3 chip, similar to the ME81H. There is uncertainty about OpenBeken's support for DPLDs to transfer Tasmota configurations, with a fallback option to solder an ESP-12 or ESP32 module due to their low cost. The default OpenBeken release supports TuyaMCU, suggesting potential compatibility. Due to difficulty sourcing an ME81H with gas boiler support on AliExpress, the user considers purchasing a Minco thermostat from Amazon and modifying their existing Minco unit. An AliExpress link to a potential device for testing OBK compatibility was shared but without clear model identification. Summary generated by the language model.
