Tuya (Smart Life) Gateway

Why?

Recently I bought a bunch of Flic buttons to interact with my smart home devices. Unfortunately they lack Smart Life integration and the work around is to use IFTT. Recently though IFTT introduced payed plan and free accounts were left with the maximum of 3 actions. Considering that each button has also 3 possible actions: click, double click and hold, I would need a separate IFTT account for each button (what?!) or a paid subscription (no way!).

Luckily Flic supports sending HTTP requests, and this project is to facilitate this and act like a middle man between the buttons and Tuya.

My goal was to make it as lightweight as possible, hence the following functionality:

• authenticate with Tuya IoT via OAuth2
• get device status
• get device functions
• send commands to the device in the request body (this means that those should be correctly formatted JSON, more below)

Setup

1. Register at https://iot.tuya.com/

2. Go to Cloud -- Project -- Create

3. Set your "Project Name", "Description" and appropriate "Industry"

4. Go to Cloud -- API Group and apply the following groups:

   • Authorization Management
   • Device Control
   • Device Management
   • IR Control Hub Open Service

5. Go to Cloud -- Linked Device -- Linked Devices by App Account -- Add App Account

6. Scan the QR code with you Smart Life app (Me -- upper right corner) and confirm link

7. The device_id that is used in the API can be found on Device List tab (make sure to select correct region) or in device details in Smart Life app

8. Go to newly created project page, where "Client ID" and "Client Secret" are available. Add environment variables on your machine (for development purposes) or add them to secrets.env file (they will be applied to the docker image during build).

   • LOGGING_LEVEL = WARNING
   • TUYA_REGION = us / eu / cn / in
   • TUYA_CLIENT_ID
   • TUYA_CLIENT_SECRET

API

Generic Devices

The following methods are available through the gateway:

• Status (GET): http://host:65080/api/v1/device/status?device_id=xxxxxxx
• Functions (GET): http://host:65080/api/v1/device/functions?device_id=xxxxxxx
• Commands (POST): http://host:65080/api/v1/device/commands?device_id=xxxxxxx

In order to figure out what commands are supported by the device, call functions endpoint with the desired device_id. The response will look like this:

{
  "result": {
    "category": "dj",
    "functions": [
      {
        "code": "switch_led",
        "desc": "[\u706f\u5177]\u5f00\u5173",
        "name": "\u5f00\u5173",
        "type": "Boolean",
        "values": "{}"
      },
      {
        "code": "bright_value",
        "desc": "[\u706f\u5177]\u4eae\u5ea6",
        "name": "\u4eae\u5ea6",
        "type": "Integer",
        "values": "{\"min\":25,\"scale\":0,\"unit\":\"\",\"max\":255,\"step\":1}"
      }
    ]
  }
}

In order to send command to the device, send the POST request to commands endpoint with the following:

• Headers: Content-Type: application/json
• Body:
  • Turn device off:

    {
        "commands": [
            {"code": "switch_led", "value": false}
        ]
    }

  • Change device's brightness:

    {
        "commands": [
            {"code": "bright_value", "value": 125}
        ]
    }

IR Devices

The following methods are available through the gateway:

• IR Remotes (GET): http://host:65080/api/v1/ir/remotes?device_id=xxxxxxx
• IR Remote Keys (GET/POST): http://host:65080/api/v1/ir/remote/keys?device_id=xxxxxxx&remote_id=yyyyyyy

Call /ir/remotes endpoint to list IR remotes bound to the IR device, that will include native remotes available for different brands and DIY remotes. Call /ir/keys to get the list of native and custom keys bound to the remote. In order to trigger the IR call the same endpoint with POST method:

• Headers: Content-Type: application/json
• Body:
  • Native:

    {
        "type": "native",
        "key": "<value>"
    }

  • Custom:

    {
        "type": "custom",
        "code": "<value>"
    }

Scenes

The following methods are available through the gateway:

• Homes (GET): http://host:65080/api/v1/homes?user_id=xxxxxxx
• Scenes (GET): http://host:65080/api/v1/home/scenes?home_id=xxxxxxx
• Trigger Scene (POST): http://host:65080/api/v1/home/scenes?home_id=xxxxxxx&scene_id=yyyyyyy

Use /homes endpoint to get the list of homes linked to the user. In order to be able to get the list of scenes and trigger them, user, that is used in "Link Devices by App Account" should be a "Homeowner"

Deployment

NOTE: Update secrets.env before build.

• Clone repo and use provided docker-compose
• Build custom image using prebuilt container from Docker Hub:

version: '3'
services:
  tuya-gateway:
    image: beerhead/tuya-gateway:latest
    restart: always
    container_name: tuya-gateway
    environment:
      - LOGGING_LEVEL=WARNING
    env_file:
      - secrets.env
    ports:
      - '65080:65080'

License

MIT