🇩🇪 Deutsche Version der Beschreibung
And if you'd like to support my work, you can also
Controlling Jarolift(TM) TDEF 433MHz radio shutters via ESP32 and CC1101 Transceiver Module in asynchronous mode.
-
Web-based User Interface (WebUI):
A modern, mobile-friendly interface for easy configuration and control. -
MQTT Support:
Communication and control of devices are handled via MQTT, a lightweight and reliable messaging protocol. -
HomeAssistant Integration:
Automatic device discovery in HomeAssistant through MQTT Auto Discovery for seamless integration. -
Support for up to 16 Roller Shutters:
Control up to 16 roller shutters with ease, all managed through the WebUI and MQTT. -
Support for up to 6 Roller Shutter Groups:
define shutter groups to control several shutters at once
Experimental version. Use at your own risk. For private/educational use only. (Keeloq algorithm licensed only to TI Microcontrollers) This project is not affiliated in any way with the vendor of the Jarolift components. Jarolift is a Trademark of Schöneberger Rolladenfabrik GmbH & Co. KG
This version is for an ESP32 and is based on ideas and code from madmartin/Jarolift_MQTT.
The original control code was written from Steffen Hille in Nov, 2017
The project home is here: Project Home
(Desktop Version)
The WebUI is responsive and also offers a mobile layout.
(Mobile Version)
a standard SPI GPIO configuration is:
| CC1101-PIN | CC1101-Signal | ESP-GPIO |
|---|---|---|
| 2 | VCC | -- |
| 1 | GND | -- |
| 3 | GD0 | 21 |
| 8 | GD2 | 22 |
| 5 | SCK/CLK | 18 |
| 6 | MOSI | 23 |
| 7 | MISO | 19 |
| 4 | CS(N) | 5 |
example with ESP32-Mini and CC1101
example for direct replacement with ESP32-Mini and the custom board from M. Maywald
It is also possible to connect a W5500 Ethernet module to the Board or a generic ESP32.
Important
The connection cable should be as short as possible (approx 10cm)
Example for generic ESP32-Mini (Standard SPI port is used by CC1101)
| Signal | GPIO |
|---|---|
| CLK | 25 |
| MOSI | 26 |
| MISO | 27 |
| CS | 32 |
| INT | 33 |
| RST | 17 |
The software is created with Visual Studio Code and the PlatformIO-Plugin.
After installing the software you can clone the project from GitHub or you can download it as zip and open it in PlatformIO.
Then adapt the upload_port and corresponding settings in platformio.ini to your USB-to-serial Adapter and upload the code to the ESP.
Note
Python must also be installed in order to fully compile the project. The scripts folder contains, for instance, scripts for creating the web pages that are called when the project is compiled.
In the releases, you can find also the binary of the Software. If you don´t want to use PlatformIO, you can also use the esp32_jarolift_controller_flash_vx.x.x.bin file and flash it directly on the ESP. This bin-file is already a merge with bootloader.bin, partitions.bin and the application.bin. You can flash this image an the ESP at address 0x00.
Windows
There are several tools available to flash binaries to the ESP.
One of them is espressif-flash-download-tool
macOS/Linux
for Mac it is hard to find a tool with a graphical UI, but you can simple use the esptool.py:
- open Terminal
- install esptool:
pip install esptool - optional get the install path:
which esptool.py - set path:
export PATH="$PATH:/<path>/esptool.py"(<- change with result from 3.) - goto path where the bin file is located
- get Device String:
ls /dev/tty* | grep usb(use this in next Step for ) - upload:
esptool.py -p <UPLOAD-PORT> write_flash 0x00 esp32_jarolift_controller_flash_vx.x.x.bin
The first option is, to download the ota Update File from the latest release at GitHub. After you have downloaded this to your computer, you can perform a update with the embedded WebUI OTA-Update. You can find the update function in the "Tools" Tab of the WebUI.
here you can choose "Firmware" and select the esp32_jarolift_controller_ota_update_vx.x.x.bin file from the release section
since Version 1.4.0 it is also possible to update the controller directly in the WebUI without downloading the .bin file before. If you click on the Version info on the bottom left, a dialog will open. If there is a new version available, you can directly initiate the update here. It will then automatically download and install the latest release from github!
But it is also possible to download the software wireless with platformio.
You only have to change the upload_port settings in platformio.ini
There are two predefined Options:
- OPTION 1: direct cable upload
- OPTION 2: wireless OTA Update
There is a "Setup Mode" available. The "Setup Mode" is activated, when you press the "reset-button" of the ESP two times within 3 Seconds. The "Setup Mode" will also activated if there is no wifi connection configured.
If the ESP goes into "Setup Mode", it will automatically create a own network access point with ssid
📶 "ESP32_Jarolift"
After you are connected to this network, you can open the webUI on ip-address
"http://192.168.4.1"
Here you can setup all the configuration that fits to your heating system and your infrastructure.
-
WiFi
enter your WiFi credentials to connect the ESP to your network -
Ethernet W5500
use Ethernet connection based on W5500 to connect the ESP to your network -
Authentication
you can activate the authentication feature and configure user and password. -
NTP Server
the ESP can connect to a NTP server to get the right Time information. The default Time-Zone should fit if you are located in germany. Otherwise you can change it manually -
MQTT
here you can activate the MQTT communication and enter mandatory parameters All the parameters are mandatory! -
GPIO
Here you can configure the GPIO to connect the CC1101 to the ESP32 -
Jarolift
here you have to configure some Jarolift specific protocol settings -
Shutter
here you can configure each shutter with individual name -
Group
here you can define optional shutter-groups -
Language
There are two languages available. Choose what you prefer. The language take effect on the webUI and also on the mqtt messages!
Note
All settings are automatically saved when changes are made
Important
Changes to GPIO or Jarolift settings require a restart!
there is also a builtin file manager to open (show), download (export) and upload (import) the configuration file.
The configuration is stored in the config.json file. To backup and restore the configuration you can download and upload this file.
It is possible to migrate from a latest version of madmartin/Jarolift_MQTT to this project.
- get a working version of this project up and running
- set the right GPIO settings for CC1101
- set the Master Keys
- set the Log-Level in the Logger of the WebUI to "Debug"
- execute a shutter UP command of "old" Setup
(madmartin/Jarolift_MQTT)for channel 0!. - now you should see a debug message of this command in the Logger of the WebUI.
It contains a message withD (APP-JARO): (INF1) serial: 0xaabbcc00,
The first 6 digits are the serial number that you have to use for this project (in this example: aabbcc). this should be the same as configured in the WebUI of the "old" setup, but now we are sure to have the right one. - set this serial in the WebUI of this project
- read the actual device counter of the "old" setup from the System Page of the WebUI.
- set the same Device Counter value in the settings of this project.
- define the same shutter as in the "old" setup and activate them.
finished!
now restart the ESP and test it.
After restarting, first check whether the device counter has been read correctly from the EEPROM. Only continue testing if this is the case.
If everything done correct, all shutters should work like before. If not, some setting is wrong or you haven´t used the latest version of (madmartin/Jarolift_MQTT). In that case I would prefer to set a new Serial number, reset the Device Counter und learn the shutter again.
To control the shutters you can use the following mqtt commands. {UP, OPEN, 0} means, that you can use one of the listed payload commands.
command: restart ESP
topic: ../cmd/restart
payload: none
command: shutter up
topic: ../cmd/shutter/1 ... cmd/shutter/16
payload: {UP, OPEN, 0}
command: shutter down
topic: ../cmd/shutter/1 ... cmd/shutter/16
payload: {DOWN, CLOSE, 1}
command: shutter stop
topic: ../cmd/shutter/1 ... cmd/shutter/16
payload: {STOP, 2}
command: shutter shade
topic: ../cmd/shutter/1 ... cmd/shutter/16
payload: {SHADE, 3}
To control shutters a group you can use the following mqtt commands. {UP, OPEN, 0} means, that you can use one of the listed payload commands.
command: group up
topic: ../cmd/group/1 ... cmd/group/6
payload: {UP, OPEN, 0}
command: group down
topic: ../cmd/group/1 ... cmd/group/6
payload: {DOWN, CLOSE, 1}
command: group stop
topic: ../cmd/group/1 ... cmd/group/6
payload: {STOP, 2}
command: group shade
topic: ../cmd/group/1 ... cmd/group/6
payload: {SHADE, 3}
You can also use a generic group command and provide the bitmask to select the shutters directly.
The bitmask is a 16-bit number, with the least significant bit (on the right) representing channel 1.
A set bit means that the channel belongs to this group.
Example: 0000000000010101 means that channels 1, 3, and 5 belong to this group.
As payload, you can use three different formats to represent the same bitmask:
- Binary:
0b0000000000010101 - Hex:
0x15 - Decimal:
21
command: group up
topic: ../cmd/group/up
payload: {0b0000000000010101, 0x15, 21}
command: group down
topic: ../cmd/group/down
payload: {0b0000000000010101, 0x15, 21}
command: group stop
topic: ../cmd/group/stop
payload: {0b0000000000010101, 0x15, 21}
command: group shade
topic: ../cmd/group/shade
payload: {0b0000000000010101, 0x15, 21}
The controller will also send a status based on the commands.
Important
But it is important to know, that this status is only a "copy of the received command".
It does not correspond to the real status of the roller shutter, because unfortunately the roller shutter itself does not have a status that could be analyzed. So if the roller shutter is operated via the original remote control, for example, or via local operation, or is stopped during movement, then this status is no longer correct!
Status: Shutter OPEN
topic: ../status/shutter/1 ... status/shutter/16
payload: {0}
Status: Shutter CLOSED
topic: ../status/shutter/1 ... status/shutter/16
payload: {100}
Status: Shutter SHADE
topic: ../status/shutter/1 ... status/shutter/16
payload: {90}
Note
< ../ > is the placeholder for the MQTT topic which is specified in the settings.
status information about WiFi:
Topic: ESP32-Jarolift-Controller/wifi = {
"status":"online",
"rssi":"-50",
"signal":"90",
"ip":"192.168.1.1",
"date-time":"01.01.2022 - 10:20:30"
}
MQTT discovery for Home Assistant makes it easy to get all values in Home Assistant. The configured shutters will automatically visible as mqtt device in Home Assistant if HomeAssistant is enabled.
see also the official documentation: https://www.home-assistant.io/integrations/mqtt/#discovery-messages
In the mqtt settings you can activate the discovery function and also set the mqtt discovery topic and the device name for Home Assistant
in addition to mqtt there are more communication options.
There is also a log function with which you can record various messages depending on the filter and display them via the WebUI. This can be useful for your own debugging and also for the further development of the software.
In addition to the WebUI and MQTT, there is also a Telnet interface to communicate with the ESP. The interface offers several commands to read out information and send commands. An overview of the commands can be called up using the "help" command. To connect, a simple Telnet connection can be started via the corresponding IP address of the ESP.
Example:
> telnet 192.168.178.193
