Thanks for adding instructions to the post. I’ll likely be coming back for it later after I get another Recteq. Hopefully this summer.
Thank you so much! I got mine up this weekend.
Recteq 1070 ID/DPS below
Device on/off = 1
Target Temp = 101
Current Temp = 102
Probe A = 104
Probe B = 105
2 Likes
@mclever
Thanks for the awesome input here. This is amazing!
My climate.smoker_temperature comes back as Unavailable while everything else seems to be flawless. Target and Actual did show up for a bit before I set the max and min, but now nothing. I’ve seen other reports of this, but no solutions. Did you run into this at all?
Having issues getting tuya (iOS) to pair with my recteq. I am holding down the wifi button on the controller but it never shows in the app.
any ideas?
Thank you
I’m not a pro here, but there are a few things I can say:
Make sure your wifi is 2.4gHz. I’ve heard people say you should temp disable your 5.0 while doing this pairing, but I read that after I got mine up.
Keep trying-- It took me about 20 attempts 
My climate.smoker_temperature comes back as Unavailable while everything else seems to be flawless.
I’m running into this similar right now, I’m seeing Unknown for my climate entity. Looking at the entity history, I see the temperature values getting properly displayed over time, but the entity itself shows nothing.
Did you ever find a solution?
Forgot I had this in config too
template:
sensor:
- name: smoker_probe_a_status
state: >
{% if states('sensor.smoker_probe_a_temperature') != unavailable %}
{% set target = states('input_number.smoker_probe_a_target')|int %}
{% set actual = states('sensor.smoker_probe_a_temperature')|int %}
{% set offset = actual - target %}
{% if offset > 5 %}Over Temp!
{% elif offset > -5 %}At Target
{% elif offset > -15 %}Approaching...
{% else %}Not Cooked Enough{% endif %}
{%- endif %}
- name: smoker_probe_b_status
state: >
{% if states('sensor.smoker_probe_b_temperature') != unavailable -%}
{% set target = states('input_number.smoker_probe_b_target')|int %}
{% set actual = states('sensor.smoker_probe_b_temperature')|int %}
{% set offset = actual - target %}
{% if offset > 5 %}Over Temp!
{% elif offset > -5 %}At Target
{% elif offset > -15 %}Approaching...
{% else %}Not Cooked Enough{% endif %}
{%- endif %}
2 Likes
Is there a template for input_number as well? Mine shows up as unavailable.
Just noting for my smoker, the inputs needed were slightly different. Guessing this could vary for each model.
RT-410 for the ID/DPS
On/Off: 1
Smoker Temp: 102
Target Temp : 101
Probe A: 103
Probe B: 104
I’m still getting mine set up but when I do device debug from Tuya IoT Platform I got these values for my smoker so wanted so save someone the time.
B380X
2 switch (ON/OFF)
101 set point (250) - in F
102 actual temp (100)
103 probe temp (0)
104 min feed rate (20)
105 temp adjust (0)
106 power failure (on/off)
107 ignite failure (on/off)
2 Likes
I’ve got a Recteq 590, and found a way to dump all of the available data points along with their supported values via the Tuya API (API Explorer > Device Control > Query Things Data Model). Lots of interesting stuff in here, some of which I’ll never use but neat that it’s there.
Short summary:
2: Switch
101: Set point
102: Actual temp
103: Min feed rate
104: Probe A
105: Probe B
106: Temp adjust
107: Temp unit
108: Power failure
109: Ignite failure
110: RTD Failure
111: Probe A arrive
112: Probe B arrive
113: Actual low deviate
114: Actual high deviate
115: Probe A setpoint
116: Probe B setpoint
117: Actual float range
And finally, here’s a JSON dump of the full list of data points, along with their supported values & types:
1 Like
Latest localtuya update breaks the control of my 700, haven’t figured out why yet
Did you get this working? I have not updated the Local Tuya integration and am now leery to do so after seeing this.
Was able to get it to work again by reconfiguring cloud api account on latest version
1 Like
I’ve been trying to get this going for a few days. Today, I was able to get the sensors connected initially, however after they initially connected and reported back they stopped and became unavailable. I have a Stampede RT-590 But all of the DPS numbers were the same as yours @mclever. So, I followed your configuration to a T. Now on the entities screen the entities report back “Not Provided”. The logs show Disconnected - waiting for discovery broadcast. When I setup the device I configured it under protocol version 3.3 as nothing else would work. I did not configure the “DPIDs to send in RESET command” field. I did not know if that was something I should do or not.
only protocol 3.3 would work for me this is how each modify device screen looks for me, hope this helps
and after making changes I did need to restart HA, the localtuya integration wouldn’t reload for me
I had an issue where most of my entities read in just fine, but for some reason, my set temp and actual temps never read in correctly. So here’s a tip for anyone else in the situation:
Instead of following the normal instructions provided at the beginning of this thread (step 5 to be specific), don’t set up your smoker temp(s) as climate. Instead, set up your Set Temp as a Number type and your Actual Temp as a Sensor. You can no longer use a typical climate card to adjust and view your set/actual temp, but you can easily drop in a number input card and a gauge card. A little extra work, but so much better than just seeing “Unavailable” on a climate card.
I got this working via LocalTuya today on my RT-B380X, and just now found this thread. I tried to document my whole process in this gist which might be helpful for others which run into trying to do this in the future. Last year when I tried to use this repo I wasn’t able to get it working. LocalTuya made it pretty easy IMO and I was able to confirm my grill’s DPs match contractcr’s.