OK folks, I just got this working. It’s 2025 now and a lot of the old information and integrations are no longer working, furthermore the default HACS TuyaLocal does not work with my smoker (it’s read only, can’t even turn it on or set the temperature). So for my own benefit (in case I need to do it again or remember what I did) and for others that run into the same issues, I’m going to try to document everything I did. I pulled a lot of inspiration directly from this post. and there’s a lot of information about IDs for different smokers on this GitHub post.
I have a RT-700 (Bull) so all of the information here is specific to the RT-700. Refer to the earlier post for info if you have a different smoker.
I attempted to get this working some time ago, so I already had a Tuya developer account. There are walkthroughs on getting that set up and others that show you how to use a rooted android phone to get your local device keys. I’m going to assume you already have an account and have failed to get the integration working (like me!) and just need the push in the right direction.
So You go to Tuya Smart Developer Center and log in, if you haven’t already. Then open the project. First we need to grab your ClientID and Client Secret
And your UserID
I would recommend you put these somewhere for future reference like 1Password or similar.
OK, now it’s time to install TuyaLocal - BUT!!! Don’t install the one that’s already in HACS - that one doesn’t work. You need to install this integration instead: https://github.com/xZetsubou/hass-localtuya. I liked using the install links in the documentation, made it a breeze!
OK, so you have it installed - time to configure it. Adding the hub using your saved credentials is easy enough, where I ran into problems was when I went to actually configure the smoker. The DPS were not being recognized, I had to put commas in between them: 1, 102, 103, 105, 106. I also found that protocol 3.1 works and 3.3 did not for my particular smoker, so be ready to play around with the protocol too if you have issues.
I had to do this a few times so here is my cheat sheet of IDs and entity names. If you’re “leveraging” my setup, you may want the same entity IDs:
102
Smoker
climate.smoker_set_temp
1
Smoker
switch.smoker_on_off
103
Smoker Actual Temperature
sensor.actual_temperature
°F -- you're going to be pasting this a LOT and °F is not the same as F
105
Smoker Probe A Temperature
sensor.probe_a
106
Smoker Probe B Temperature
sensor.probe_b
You need to configure the temperature control FIRST. This will let you use the DPs as part of the control. In my case, 102 is the target, 103 is current, and 1 turns the smoker on and off. Here are all the settings I changed
FUN FACT! If you do not set the “(Optional) Temperature Unit” to °F - it’s going to assume the numbers are Celsius and convert it into Fahrenheit and suddenly it shows your grill set to 600°F - ask me how I know.
Alright, now let’s go back and set up the smoker on/off button (1)
Now we want a sensor for the current temp (103)
Let’s do Probe A (105)
And Probe B (106)
At least with the RT-700 Bull, you can totally stop here, or if you like, you can configure the other entries. I’m not currently using them on anything but it’s up to you.
Cool. Next it’s time to create a bunch of helpers and then create a dashboard.


















