Last Updated on2020-01-08 09:19:34

Tuya Panel Kit Template is the best practice of device control panel engineering, including the basic framework of the development panel, this document will introduce What templates do for us, and how we need to develop a brand new panel project based on templates.

Run start

Please refer to the previous quick start article

Detailed template

Detailed directory

├── .babelrc             // babel configuration file
├── .eslintignore        // Configure which files don't need eslint
├── .eslintrc.js         // eslint configuration file
├── .gitignore           // Configure which files don't require git
├── .npmrc               // npm configuration file
├──            // Project information, including but not limited to project name, productId, author, description, etc.
├──     // Android entry
├── index.ios.js         // IOS entry
├── index.js             // Android portal (for compatibility)
├── package.json         // npm dependency management
├── rn-cli.config.js     // metro configuration file
├── src
│   ├── components       // Place each reused functional component used in the project
│   ├── composeLayout.js // The package handles some `device events` and` device information` needed inside the panel
│   ├── containers       // Place each page-level component of the project
│   ├── i18n             // Place Multilingual Profile
│   ├── main.js          // The project entry file, inherited from `NavigatorLayout`, passes some necessary configuration, such as background, topbar, etc., by overriding the` hookRoute` method. Override the `renderScene` method to control route forwarding.
│   ├── redux            // Place some code related to redux
│   ├── res              // Place local resources, including pictures, svg path, etc.
│   └── utils            // Some common functions that will be used inside the panel
└── yarn.lock

Detailed composeLayout

In simple terms, there are three things that the higher-order function composeLayout does for us;

  1. When the panel is initialized, composeLayout processes the originaldevInfo and initializes the redux store.

  2. When the panel is running, composeLayout listens to events related to device changes and updates the correspondingredux store in real time.

  3. The incoming component is connected to the redux store.

import _ from "lodash";
import PropTypes from "prop-types";
import React, { Component } from "react";
import { Provider, connect } from "react-redux";
import { TYSdk, Theme } from "tuya-panel-kit";
import {
} from "./redux/modules/common";
import theme from "./config/theme";

const TYEvent = TYSdk.event;
const TYDevice = TYSdk.device;

 * @param {Object} store - redux store
 * @param {ReactComponent} component - The component that needs to be connected to the redux store, which is usually main
const composeLayout = (store, component) => {
  const NavigatorLayoutContainer = connect(_.identity)(component);
  const { dispatch } = store;

   * The `device data change` event is monitored here,
   * Whenever the dp point data is changed, the changed dp point status will be updated to `redux` synchronously.
   * Similarly, when the device information is changed, the changed device information value will also be updated to `redux` synchronously.
  TYEvent.on("deviceDataChange", data => {
    switch (data.type) {
      case "dpData":

   * The `Network State Change Event` event is monitored here,
   * Whenever the device information is changed, the changed device information value will be updated to `redux` synchronously.
  TYEvent.on("networkStateChange", data => {

  class PanelComponent extends Component {
    static propTypes = {
      // eslint-disable-next-line
      devInfo: PropTypes.object.isRequired

     * If `devInfo` already exists when the panel is entered (it usually exists)
     * This will call setDeviceInfo to process the original devInfo and put it into `redux`
     * If `devInfo` does not exist when the panel is entered,
     * Then getDeviceInfo will be called asynchronously to get the processed `devInfo` and put it into` redux`
    constructor(props) {
      if (props && props.devInfo && props.devInfo.devId) {
        TYDevice.getDeviceInfo().then(data => dispatch(devInfoChange(data)));
        // eslint-disable-next-line
      } else if (props.preload) {
        // do something
      } else {
        TYDevice.getDeviceInfo().then(data => dispatch(devInfoChange(data)));

    render() {
      return (
        <Provider store={store}>
          <Theme theme={theme}>
            <NavigatorLayoutContainer />

  return PanelComponent;

export default composeLayout;

Detailed main

Simply put, there is only one thing that the MainLayout entry component does for us;

  1. Inherited NavigatorLayout to help the panel manage multiple pages internally.
import _ from "lodash";
import React from "react";
import { TYSdk, NavigatorLayout } from "tuya-panel-kit";
import composeLayout from "./composeLayout";
import configureStore from "./redux/configureStore";
import Home from "./containers/Home";
import { formatUiConfig } from "./utils";

console.disableYellowBox = true;

 * Generate a store through the built-in store configuration method of the template.
export const store = configureStore();

class MainLayout extends NavigatorLayout {
  constructor(props) {
    console.log("TYSdk :", TYSdk);

   * @desc
   * hookRoute can do some control processing for specific routes here
   * @param {Object} route
   * @return {Object} - Some control values provided to the parent container layout of the current page component
   * {
   * style:, // container style, you can adjust the background color here
   * background: backgroundImage | linearGradientBackground, // panel image background or gradient background, the gradient format can refer to LinearGradient and RadialGradient components
   * topbarStyle:, // TopBar style, can adjust TopBar background color
   * topbarTextStyle:, // TopBar text style
   * renderTopBar: () => (), // custom render TopBar
   * hideTopbar: true | false, // control whether to hide TopBar
   * renderStatusBar: () => {}, // custom render StatusBar, IOS only
   * showOfflineView: true | false, // control whether to render OfflineView
   * OfflineView: ReactComponent, // custom OfflineView component
   * }
  // eslint-disable-next-line
  hookRoute(route) {
    // switch ( {
    //   case 'main':
    //     // eslint-disable-next-line
    //     route.background = background;
    //     break;

    //   default:
    //     break;
    // }

    return {};

   * @desc
   * Here you can use the id in the route to determine which page component to use.
   * In addition, if there are additional props that need to be passed to the page component, they can be passed here.
   * @param {Object} route-route object
   * @param {object} navigator-Navigator object, please refer to the specific usage method
  renderScene(route, navigator) {
    let component;
    let schema = {};
    let uiConfig = {};
     * Because we wrap `MainLayout` with` composeLayout`,
     * Therefore, you can get all the props passed from the redux store.
    const { dispatch, devInfo, dpState, logs } = this.props;

    if (!_.isEmpty(devInfo)) {
      schema = devInfo.schema || {};
      uiConfig = formatUiConfig(devInfo);

    switch ( {
      case "main":
        component = (
            dpData={{ state: dpState, schema, uiConfig }}


    return component;

export default composeLayout(store, MainLayout);

devInfo Detailed

Earlier in NavigatorLayout documentation, the unprocessed devInfo object has been explained, and here The devInfo object processed by composeLayout is also a common and important thing inside the panel. For the subsequent use of devInfo inside the panel, please refer to the following. The following will explain the role of some common fields.

  • name: Device name
  • productId: product id
  • uiId: panel id corresponding to the current product
  • bv: hardware baseline version
  • devId: device Id
  • gwId: Gateway Id, if it is a single product, devId is generally equal to gwId
  • ability: Only for Bluetooth devices, if it is a single-point Bluetooth device, the value is 5
  • appOnline: App is online
  • deviceOnline: Whether the device is online
  • isLocalOnline: Whether the LAN is online
  • isShare: Whether it is a shared device
  • isVDevice: whether it is a demo device
  • groupId: group device Id, can be used to determine whether the group device
  • networkType: The online type of the device
  • capability: the capability type of the device, indicating what capabilities the device supports, such as ZigBee, infrared, Bluetooth, etc.
  • schema: Definition of function point (dp, data point) of the product to which the device belongs. For the explanation of function points, please refer to dp explanation
  • state: state of the dp point