This will quickly describe some of the steps needed to get the recteq configured in the latest versions of HA & (Local)Tuya.
If configured, you will be able to:
- Display Current and Target Temperatures, Probe A & B Temperatures
- Turn Smoker on and off
- Set Target Temperature NEW
- HomeAssistant
- Tuya/LocalTuya
- Steps here are for LocalTuya, but should be similar for normal Tuya users
- Tuya IoT Platform
- Recteq Pellet Smoker
- This has only been tested with an RT-700.
- Install LocalTuya into HA as described in their docs.
- Configure the Tuya IoT Platform account. Details described in the LocalTuya docs above.
- Local Keys are hard to find, but the easiest way in the Tuya IoT Platform is by going to:
- Cloud (left-toolbar) > API Explorer
- Navigating the tree to Smart Home Device System > Device Management > Get device details
- Pasting the
device_id
from the previous steps - Reading the JSON Response and looking for
"local_key"
with the corresponding value.
- In HA, configure your first device after loading the integration and connecting the Tuya IoT Cloud Account
- My configuration has never allowed me to use the auto-discover and here it helps because I can configure each
dps
- BE CAREFUL doing the following as there is no chance to edit anything in the Device/Entity after it has been added to HA. You will always need to delete and start from scratch.
- For Power On/Off: Entity Type = switch, ID/DPS = 1
- For Probe A: Entity Type = sensor, ID/DPS = 105, Device Class = temperature, Unit of Measurement = F
- For Probe B: Entity Type = sensor, ID/DPS = 106, Device Class = temperature, Unit of Measurement = F
- For Smoker Temperatures: Entity Type = climate, ID/DPS = 102, Target Temperature = 102, Current Temperature = 103, Precision = 1
- At this point should be have a working device with 4 entities. Now, if you would like to have a working Lovelace Thermostat card, you will need to customize the entity itself via YAML configuration.
- You may also want to customize the entity IDs as it was not something available during set-up.
This is required because the LocalTuya configuration for the entity will not take free-text values and none of the DPS parameters from the smoker itself provide the max/min. We are going to hard-code these. I assume you've never configured a customization before below. If you have, you know where to start :)
- Create a new
customize.yaml
file in the root of the config folder. I use the Visual Code Studio host add-on so this is very easy from within HA. - Include the following in the new
customize.yaml
file, replacing theclimate.smoker_temperature
with the appropriate entity ID:
climate.smoker_temperature:
max_temp: 500
min_temp: 180
- Save the file.
- Open the
configuration.yaml
file and locate a line that stateshomeassistant:
; if this does not exist, add it on a new line at the bottom. - Indent two spaces, and add
customize: !include customize.yaml
and save the file. The added text should be:
homeassistant:
customize: !include customize.yaml
- Restart HA