Skip to content
This repository has been archived by the owner on Nov 11, 2022. It is now read-only.

Latest commit

 

History

History
193 lines (159 loc) · 6.99 KB

README.md

File metadata and controls

193 lines (159 loc) · 6.99 KB
Raw

Home Assistant Recteq Integration

This is no longer working for me. Seems the protocol has changed but I don't have the time to work on it any more. Sorry gang.

Custom integration for recteq grills and smokers providing a climate entity to control the unit and sensor entities for the probes.

hacs-badge issue-badge pr-badge release-badge commit-badge license-badge commits-badge

NOTE - This isn't supported or approved by recteq at all!

climate

entities

Installation

We recommend you install HACS first, then add https://github.com/pdugas/recteq as a custom integration repository and finally, add the integration from there.

Instead, if you prefer the manual route, you could download a copy of the latest release and unpack the contents into into config/custom_components/recteq/ on your HA machine. Feeling adventurous? Using git clone in config/custom_components/ to pull the project from Github works too.

In either case, you need to restart HS once it's installed. Then you need to configure it.

Configuration

This integration is configured using the UI only; no changes in configuration.yaml are needed. Navigate to Configuration » Integrations and tap the red "+" button in the bottom-right. Search for and select the "Recteq" entry in the list of available integrations to setup. You'll get the dialog shown below. Enter the details for your grill and tap "Submit".

config

Repeat the process if you have multiple grills to control. (ps: I'm jealous!)

See the wiki for info in where to get the IP address, device ID and local key values needed.

The "Force Fahrenheit" option was added for folks who operate HA in Celsius but cook in Fahrenheit. The climate and sensor entities will report tempeatures in Fahrenheit rather than converting them to Celsius when this option is set. The thermostat card will still display °C but the values will actually be °F.

User Interface

The stock Thermostat Card can be used to present the current state of the recteq when it's on. I like to hide it and display a button instead when it's off. I use conditionals like below. The result is shown in the screenshot at that top of this document.

type: vertical-stack
cards:
  - type: conditional
    conditions:
      - entity: climate.smoker
        state: 'off'
    card:
      type: glance
      entities:
        - entity: climate.smoker
          tap_action:
            action: toggle
  - type: conditional
    conditions:
      - entity: climate.smoker
        state_not: 'off'
    card:
      type: thermostat
      entity: climate.smoker
  - type: conditional
    conditions:
      - entity: climate.smoker
        state_not: 'off'
      - entity: input_number.smoker_probe_a_target
        state_not: '0.0'
    card:
      type: glance
      entities:
        - entity: sensor.smoker_probe_a_temperature
          name: Probe-A
        - entity: input_number.smoker_probe_a_target
          name: Target
        - entity: sensor.smoker_probe_a_status
          name: Status
      state_color: true
  - type: history-graph
    entities:
      - entity: sensor.smoker_target_temperature
        name: Target
      - entity: sensor.smoker_actual_temperature
        name: Actual
      - entity: sensor.smoker_probe_a_temperature
        name: Probe-A
      - entity: sensor.smoker_probe_b_temperature
        name: Probe-B
    refresh_interval: 0
    hours_to_show: 8

The third panel above mimics the logic in the app that monitors the probe. I created an input_number named "Smoker Probe-A Target" (min=0.0, max=500.0, step=5.0, mode=slider, unit=°F, icon=mdi:thermometer). Then I added the template sensor below. An automation to send notifications could be added too if desired.

*NOTE - If you're using the "Force Fahrenheit" option, don't set the units on the input_number or HA will try to convert it automagically.

sensor:
  - platform: template
    sensors:
      smoker_probe_a_status:
        value_template: >
          {% if states('climate.smoker') == 'off' or states('sensor.smoker_probe_a_temperature') == 'unavailable' -%}
            undefined
          {% else %}
            {% set target = states('input_number.smoker_probe_a_target')|round %}
            {% set actual = states('sensor.smoker_probe_a_temperature')|round %}
            {% set offset = actual - target %}
            {% if offset > 5 %}Over Temp!
            {% elif offset > -5 %}At Target
            {% elif offset > -15 %}Approaching...
            {% else %}Waiting...{% endif %}
          {%- endif %}

Change Log

  • next
    • Fix for setting target temp when Force-Fahrenheit enabled
    • Moved force-fahrenheit to options.
  • 0.0.4
    • Metric units support
    • Force-Fahrenheit option
  • 0.0.3
    • Added target & actual sensors
    • Sensors and current temperature report "unavailable" when off.
    • Added UI usage to README
    • Bugfixes and cleanup.
  • 0.0.2
    • HACS support
    • README additions
  • 0.0.1
    • Initial release candidate
    • Works for me. Looking for others to test.

License

Copyright (c) 2020 Paul Dugas

See LICENSE for details.

Support

Submit issues for defects, feature requests or questions. I'll try to help as I can.

I am very interested in feedback on this to know whether it's working for others.

Credits

I'm Paul Dugas, paul@dugas.cc. This is my first HA integration so be gentle!

I learned this was possible from SDNick484/rectec_status and based the intial versions of the project on his examples. Much thanks to SDNick along with those he credits; codetheweb, clach04, blackrozes, jepsonrob, and all the other contributors on tuyapi and python-tuya who have made communicating to Tuya devices possible with open source code.