Linux controller JetHome JetHub H1



The controller can be purchased from the manufacturer’s website:

General Description

Controller JetHome JetHub H1 is designed to build home automation and monitoring systems: interrogating sensors, using as a data collection and transmission device, acting as a PLC in the “smart home” systems.

The powerful quad-core processor JetHome JetHub H1 will allow it to be used as a central controller in smart home systems together with various wireless sensors Wi-Fi and ZigBee from other manufacturers.

The controller case is made in a modern laconic design, which will fit into any interior.


  • Quad-core processor Amlogic S905W (ARM Cortex-A53) with operating frequency up to 1.2 GHz.

  • 1GBytes or 2GBytes DDR3 RAM.

  • Non-volatile eMMC flash memory 8 GB, 16 GB or 32 GB.



The figure indicates:

  • ETHERNET- Ethernet connector.

  • DC 5V / CONSOLE - MicroUSB connector for controller power and Linux console output.

  • USB 1 - USB connector for connecting external devices and controller firmware.

  • USB 2 - USB connector for connecting external devices.

  • SD-CARD - slot for connecting MicroSD memory cards.

  • WIFI - Wi-Fi/Bluetooth module.

  • WM 1 - The main module for communication with wireless devices (Zigbee).

  • WM 2 - Additional module for communication with wireless devices (optional).

  • DBG 1 - connector for the firmware of the main wireless module.

  • DBG 2 - connector for the optional wireless module firmware.

  • BOOT - button to switch the loading mode. The button is accessible through a hole in the controller housing. Do not use sharp objects or force when pressing the button.

  • RESET - controller hardware reset button.

  • UPDATE - pins to disable the built-in eMMC flash memory (used when restoring the controller firmware).

  • PWR - green LED indicating the presence of power.

  • STAT - blue custom LED.

Dimensions and weight

  • Overall dimensions: 100 x 97 x 20 mm;

  • Weight without power supply: 120 г


  • Integrated dual-band (2.4 GHz and 5 GHz) wireless module Wi-Fi/Bluetooth Realtek RTL8822CS. Supports Wi-Fi IEEE 802.11a/b/g/n/ac, 2×2 MIMO, and Bluetooth 5.0 standards.

  • Ethernet IEEE 802.3 10/100 Mbps.

  • Wireless Zigbee module TI CC2538 + CC2592 or TI CC2652P1 with up to 20 dBm output power and support for Zigbee 3 standard.


  • Supports MicroSD 2.x/3.x/4.x DS/HS cards;

  • 2 x USB 2.0 high-speed;

  • The Serial Console is connected to the MicroUSB power connector.


There are two LEDs on the controller board:

  • Green LED - to indicate the presence of power supply voltage.

  • Blue LED - the user LED is connected to the GPIODV_24 pin of the Amlogic S905W processor.

Wireless module (Zigbee)

The controller motherboard has a mounting location for the wireless module. Depending on the controller configuration, a wireless module can be installed on the board (see Zigbee modules PCBA).

There is a WM DBG connector on the controller motherboard next to the wireless module seat for debugging or flashing the wireless module:



The module is connected to the UARTAO_B port of the processor, hardware control of reception/transmission (RTS and CTS lines) is not used. The device is displayed in the system as /dev/ttyAML2.

The GPIO processor is used to control the wireless module, which are connected to the lines RESET and BOOT of the wireless module (see Working with discrete outputs in Linux)

Module output

CPU output

Linux sysfs

Linux gpiolib

Active low




gpiochip 0, line 6





gpiochip 0, line 9


Hardware reset of the wireless module is done by writing a logic level 1 to GPIO RESET of the processor (see table above). Return to operation mode is performed by writing logical level 0 to GPIO RESET of the processor.

The boot mode is controlled by writing 0 or 1 to GPIO of BOOT processor (see table above). For the Zigbee wireless module, entering boot mode is done by logical level 0 on pin BOOT during Zigbee module reset.

Switching of modes takes place when the module is switched on or when it is reset by hardware reset. Therefore, after changing the logic level on the pin BOOT of the module, it is necessary to perform a hardware reset of the module.


The console is connected to the Micro-USB connector (also used to power the controller) via a Silicon Labs CP2102 USB-UART interface converter installed on the board.

The console is connected to the UART_AO_A port of the Amlogic S905W processor.


  • The driver for the USB-UART interface converter CP2102 for Windows OS can be downloaded at the manufacturer’s website.

  • In Linux it is usually not necessary to install an additional driver.

Port configuration:

  • Speed 115200 bps

  • Data length 8 bits

  • Stop bit 1

  • Parity is not used

  • Hardware flow control is not used


The controller is powered from a stabilized DC source +5V, via a MicroUSB connector. Power consumption - not more than 5W (excluding external consumers connected to USB ports).

It is recommended to use the power supply unit supplied with the controller to power the controller.


When powering the controller from a computer or other USB device, or when using a third-party power supply, make sure that the device or power supply is capable of providing the necessary output power:

  • Up to 5W if no additional devices will be connected to the controller.

  • Up to 10W if additional devices powered from the USB port will be connected to the controller’s USB ports.


When powering the controller from the USB port of a computer, be aware that the standard USB 2.0 interface may limit the output current to 0.5A, which may not be enough for normal operation of the controller under load.


Officially supported software:


It is also possible to install such popular automation systems: OpenHAB, NodeRed and other Linux-based systems.

Controller firmware


You can find the current firmware image for your device here: JetHome firmware portal.

Switching to firmware mode

  • Disconnect power to the controller (the * MicroUSB* connector on the back of the case). Further in the process of flashing there is no need to connect it.

  • Open the case of the controller to get access to the board.

  • Connect the pins Update located on the controller board near the battery.

  • Connect the controller with the cable USB A - USB A to the computer.

  • Make sure that the Burning Tool program has detected a connection to the controller.

  • Open the pins at Update (Important!).

  • Then start the process of flashing the controller.



Flashing by a method not recommended may lead to malfunction of the controller!

When flashing via microSD or USB Flash boot using the armbian-install utility or direct writing to eMMC, the service area which contains usid (including hardware version), based on which the firmware identifies the installed Wi-Fi / Bluetooth chip, will be erased.

Button BOOT

On the back of the controller, between the Ethernet and microUSB interfaces, there is a button BOOT recessed into the housing. The button allows you to put the controller in the firmware mode. Some users are not attentive to the sequence of actions when flashing the controller described in our documentation and with excessive effort they tear off the button from the board or cause mechanical damage to it. Thus, they make it unusable.


How to press the button correctly BOOT

  • Take a pointed object - a paper clip or toothpick will do just fine.

  • Disconnect the controller from the power supply.

  • You can practice and feel the stroke of the button. When pressed correctly, you will feel the characteristic click of the microswitch.

  • Press the button and supply power to the controller. You can start the flashing process.


To prevent mechanical damage to the button BOOT, when accessing the button through the hole in the controller housing, do not use sharp objects and do not apply great force when pressing the button.

What to do if the BOOT button is broken


If the button does break, do not panic. You can flash the controller using Amlogic Burning Tool. To do this:

Safety precautions

  • Do not allow moisture to get on the contacts of output connectors and internal elements of the controller.

  • The controller must not be used in the presence of acids, alkalis, oils and other aggressive substances in the atmosphere.

  • The controller is not intended for use on objects that are potentially dangerous to life and health of others.

  • It is not allowed to connect the instrument to the local Ethernet network with access to the Internet network without providing reliable means of interconnection protection.

Operating conditions

  • Ambient temperature: 0..+40 С.

  • Relative humidity up to 80% without condensation.

  • Closed explosion-proof rooms without aggressive vapors and gases.

Wiring recommendations

It is recommended that stranded copper cables be used to ensure reliable electrical connections. The cable ends should be stripped and then tinned or cable lugs should be used. The cable strands should be stripped so that their bare ends do not protrude beyond the terminal block after connection to the controller.

General requirements for connection lines:

  • When laying the cables, the communication lines that connect the device to the sensors or other devices should be separated into separate routes, and located separately from power cables and cables that cause high-frequency and pulse interference.

  • To protect the inputs of the device from the influence of electromagnetic interference, the communication lines of the controller should be shielded. Special cables with braided shielding can be used as shields.

  • It is recommended to install line noise filters in the power line of the controller.

  • In the case of controlling power equipment, it is recommended that spark-quenching filters be installed on the switching line of this equipment.



The controller is not designed for heavy 24/7 tasks such as video processing.