FAQ ans Lifehacks

• Good to know
  • Submitting feedbacks OTA from SLZB-06/06M web interface
  • Best channel for a Zigbee network
  • mDNS Audotdiscovery (SLZB-06)
  • Type-A to Type-C cables support
• Common errors
  • Zigbee2MQTT: Error Network Commissioning Timeout (panID or extendedPanID already exists nearby)
• Add some functionality
  • SLZB-06/06M & ESPHome firmware
• Privacy and analytics

Good to know

Submitting feedbacks OTA from SLZB-06/06M web interface

In the case you:

• identified any bugs in firmware;
• found translation error in firmware;
• want to say "Thank you" to the engineering team;
• would like to suggest improvement idea,
  please submit them via web interface here:
  

Best channel for a Zigbee network

According to this article by Metageek the best is to use channel 15 for ZIgbee and channels 1,6 and 11 for your home WiFi networks. The rule - make the networks as less overlaps as possible.
Have a look on other interesting topics at those web-resource, some of them are listed below:

• ZigBee and Wi-Fi Coexistence;
• Choosing a WiFi Channel;
• Why Channels 1, 6, and 11? (video);

mDNS Audotdiscovery (SLZB-06)

• if you do not know your SLZB-06 adapter's IP address, you can reach web-interface by following to slzb-06.local or slzb-06m.localin your browser.
• if you do not know your SLZB-06 adapter's IP address, you can set-up you Zigbee2MQTT autodiscovery by setting these parameters:

...
serial:
  port: mdns://slzb-06 //for SLZB-06 series
...

Type-A to Type-C cables support

• In case of USB connection or flashing over USB - please use Type-A (your PC) to Type-C (SLZB-06/06M) cables. Flashing and Zigbee bridge does not work with Type-C to Type-C cables.

Common errors

Zigbee2MQTT: Error Network Commissioning Timeout (panID or extendedPanID already exists nearby)

This error is discussed in these two threads: first and second.
According to the first thread, the most possible issue cause this error is: zigbee2mqtt will always use the same, default extendedPanId unless you set it to something else in the config file

advanced:
  pan_id: GENERATE
  ext_pan_id: [0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08]
  network_key: GENERATE

According to the second thread, the users propose to start without antennas or routers nearby: Try unscrewing the antenna during startup. Or unplug any near by routers temporarily. Try to do abovementioned as well as start ZHA just to test your device:

1. Go to Home Assistant
2. Click Settings
3. Go to Devices & Services
4. Click Add integration (right bottom corner)
5. Find «Zigbee Home Automation», click on it;
6. Between two options «Add Zigbee device» and «Zigbee Home Automation» choose Zigbee Home Automation;
7. Select serial port window - Enter manually
8. Radio type window - ZNP = Texas Instruments Z-Stack ZNP …
9. Serial port settings window:

• Serial device path: « socket://192.168.1.105:6638 », where 192.168.1.105 is IP address of your SLZB-06;
• port speed left by default 115200;
• data flow control undefined (it does not matter for LAN adapters)

10. Press Submit.
11. Network formation window - Erase network settings and form a new network
12. Wait for Zigbee network and try to add some Zigbee end-device (e.g. sensor etc)

If ZHA starts - means that the problem in communication between Zigbee2MQTT and Z-Stack firmware, flashed to the adapter. To solve it - try steps above ZHA part.

Add some functionality

SLZB-06/06M & ESPHome firmware

You can run ESPHome firmware on your SLZB-06/06M device. Follow these official sources:

• ESPHome Bluetooth Proxy, follow this manual.
• ESPHome Bluetooth Low Energy Tracker Hub.
• ESPHome BLE CLient.

WARNING

chapter to be added

Privacy and analytics

TIP

Non-personalized analytical data is shared ONLY when the option is enabled, via Secured HTTP (HTTPS) protocol. The Analytics system was first introduced in new SLZB-06's firmware 2.0.0.

Users of SLZB-06 series coordinators have the option to share their non-personal secure data via the analytics integration though Secured HTTP (HTTPS) protocol.
The data serves to influence the development priorities of SLZB-06 firmwares. Additionally, it aids in persuading manufacturer to include features that emphasize local control and privacy.

SLZB-06 can share the following data

• ONLY when the option is enabled ,
• ONLY over Secured HTTP (HTTPS) protocol
• ONLY non-persoanalized data, which is:

1. Unique device ID (example 540129d71019bb0c3eedfb5cca20824e768215e275462380c2627f4c4212f842);
2. Core processor model (example ESP32);
3. Zigbee processor model (example CC2652P2);
4. Core firmware version (example 2.0.12-dev);
5. Zigbee firmware version (example 20230507);
   Additionally since FW v3.0.0:
6. Device operational mode (Coord/Router/Thread/ZigbeeHub) (example 1);
7. Connected mode (USB/WiFi/Ethernet) (example 3);
8. How many Zigbee devices are paired (number) (example 7);
9. How many scripts were created? (example 2);
10. How many scripts are with "autostart mode"? (example 1);
11. Free RAM at the report time (example 125);
12. Uptime in milliseconds (example 13332);
13. [Reserved] How many devices are paired via Thread (example 5);
14. [Reserved] Is MQTT enabled? Yes/No (example 0);
15. [Reserved] Is Telegram enabled? Yes/No (example 0);
16. Language ID (example 1);
17. Enable Zigbee Socket packet processing. Yes/No (example 0);
18. Allow multi-threaded socket connection. Yes/No (example 1);
19. Flashed custom IEEE? Yes/No (example 1);

Turn ON and OFF could be set via special checkbox in General settings:

Once activated, data can be sent during the device boot (5 attempts) or after Zigbee processor OTA update.

TIP

We would be immensely grateful if you choose to keep this functionality enabled.