Zigbee + BLE Gateway
This product is designed to work with common ZigBee, BLE devices. The gateway is based on the controller ESP32 from Espressif. The tandem of chips from Texas Instruments ZIgbee CC2538 and amplifier CC2592, either ready chip NXP JN5168. To communicate with devices using the BLE protocol, the built-in capabilities of ESP32 are used.
Support for BLE and the NXP JN5168/JN5169 module is currently undergoing testing and is expected soon.
The gateway acts as the coordinator of Zigbee and allows you to:
1) Use most of the available Zigbee equipment. A list of supported and tested equipment is available at link. New equipment may be added after discussion with us.
2) Abandon the need to use cloud device manufacturers. As an alternative, it is proposed to use the cloud service Smart Logic System, or native applications for Android and Apple iPhone (under development).
3) Use common local automation systems, such as MajorDomo, ioBroker Smarthome, HomeAssistant, Node-Red, etc. For integration with these systems, the MQTT protocol is used. The structure of the MQTT protocol topics is identical to the zigbee2mqtt project, therefore, to use and integrate the gateway, there is no need to learn the scripting languages of the above systems, since the protocol is basically already available using extension modules.
Additional gateway features via the web interface
Management and viewing of device information through the Web interface of the gateway at http://ipadress (port 80). The ability to display the power source, battery level, available EndPoint devices in the web interface.
Creation of local automation within the gateway SimpleBind.
The ability to write scripts in Lua.
The ability to create groups to manage multiple devices at the same time (in development).
The ability to name the device. If you plan to use the gateway with local automation systems, it is recommended to check the box for sending addresses instead of devices.
Ability to remove the device.
The ability to display routes in the web-interface (in development).
The ability to establish direct connections Bind between ZigBee devices without the participation of a coordinator to manage end devices.
Ability to control hardware [LEDs (address or RGB)] (/faq_eng.md).
The ability to control sound (in the presence of a soldered amplifier) (in development)
Ability to change PanId and channel number.
The ability to specify the name of the gateway on the network.
The ability to switch the gateway to the AP mode when the hardware button is pressed for 2-5 seconds after power is supplied.
The list of supported devices is constantly updated (information is in the converters.txt file in the archive with firmware)
For firmware, run the appropriate batch file from the archive. At the first start, an access point is created with a name of the form zgwABCD, without a password. After connecting to it, the settings page automatically opens (if it didn’t open, you can go to the address 192.168.1.1) and register the connection to the access point and to the MQTT server (but you can also specify it later), press reboot and the gateway will connect to the access point and will start sending messages to MQTT. In case of problems with access to the captive portal, it is recommended to disable GPRS on Android smartphones. Firmware update can be done through the Web interface of the application.
Note: there are two firmware versions, for chips with 4mb and 16mb FLASH RAM. Versions are distinguished by the ability to update via OTA.
zigbee2mqtt message structure (most commands supported)
Thanks to the use of the MQTT protocol, the SLS ZG gateway can be integrated with any local or cloud automation system. The structure of topics almost completely repeats zigbee2mqtt. For ease of use, many drivers or integration modules have been developed for many systems.