Awesome Zigbee Coordinator For Zigbee2Mqtt

[Serge]

How does one find the IP address of the SLZB-06?

As Bigstevep wrote above, the best if you can have a look in your router's web-interface.
Also you can use IP scanners, so you will find it as well.

We also added some changes to Z2M and the next Z2M's release (early June) will contain Adapter's mDNS autodiscovery. SLZB-06 is the first one that supports this feature so far in Z2M. This will simplify the config, e.g. you do not need to set-up Z2M at all, everything will be done automatically, just plug-and-play.
It is available in the dev branch already.
https://github.com/Koenkk/zigbee2mqt...conf-discovery

So since that release, you do not need to know the ip address, as you need to put in config only:

port: mdns://slzb-06

[Richel]

Hello Bigstevep, thank you for the such nice feedback, Hello Richel,ksum, ScottRennie, langenet, hello gentlemen.

my name is Serge, I am an engineer and developer of SLZB-06.
My colleague and I are running this SLZB-06 project (I am HW and my colleague is a SW engineer).
I registered here just to say thank you for your perfect feedback and also to help other users to set up their devices, as I see that set-up is not very common for everyone.

To be honest, it is the first time I hearing about HomeSeer systems, however, I had a brief look at them and I hope will help or to answer basic questions about the setup.

• So as far as I understood the system and documentation of mcsMQTT, mcsMQTT can serve as an MQTT broker. If this is the case, then we do not need to install the external MQTT broker (usually - Moscquitto) and use just an mcsMQTT.
• So, with the single set-up of HS and mcsMQTT, you can run as much as you want SLZB-06's, either connected over USB or Ethernet/WiFi or even remote ones, connected over the Internet.
• The only rule - each SLZB-06 should be accompanied by a separate instance of Zigbee2MQTT. You can run as much as you want instances of Zigbee2MQTT on the same server as HS.
• The easiest way to run separate instances of Z2M - is to run them via Docker containers.

To understand the architecture of the Software side and connection side - I made this simple block chart, see below.
In case of any questions, please let me know here by replying to this message, so I will get a notification to my email.

Greetings from Ukraine!

Can this somehow interface as a LAN device (not COM) with the new HomeSeer Zigbee Plus plugin?

[donstephens]

Can this somehow interface as a LAN device (not COM) with the new HomeSeer Zigbee Plus plugin?

+1

[ksum]

Can this somehow interface as a LAN device (not COM) with the new HomeSeer Zigbee Plus plugin?

Since the new plugin leverages zigbee2MQTT and the SLZB-06 works with zigbee2MQTT there is no reason it shouldn't work. As I understand the plugin, it is just interfacing directly to zigbee2MQTT as opposed to through MQTT. Installing it for you if needed as well. Your can also use an existing installation of zigbee2MQTT if you have one.

[Richel]

Since the new plugin leverages zigbee2MQTT and the SLZB-06 works with zigbee2MQTT there is no reason it shouldn't work. As I understand the plugin, it is just interfacing directly to zigbee2MQTT as opposed to through MQTT. Installing it for you if needed as well. Your can also use an existing installation of zigbee2MQTT if you have one.

Thanks. The setup for the new HomeSeer Zigbee Plus plugin "Back-End" asks for the COM port for the Zigbee adapter settings. That's where I am stymied, since I want to use the SLZB-06 over the LAN at a location remote from the computer running HS4. I think that I need to set up a virtual COM port (trying to figure how to do this).

[Bigstevep]

I’m not home to test but how about something like:

# Serial settings
serial:
# Location of SLZB-06
port: tcp://192.168.1.yourip:6638

[spud]

Thanks. The setup for the new HomeSeer Zigbee Plus plugin "Back-End" asks for the COM port for the Zigbee adapter settings. That's where I am stymied, since I want to use the SLZB-06 over the LAN at a location remote from the computer running HS4. I think that I need to set up a virtual COM port (trying to figure how to do this).

For now, the Zigbee2MQTT Back-end page only allow you to select a serial port, we may add more options in a future version. In the meantime you can edit manually the Zigbee2MQTT configuration file located in ./Data/ZigbeePlus/zigbee2mqtt/data/configuration.yaml.

• stop the plugin
• edit ./Data/ZigbeePlus/zigbee2mqtt/data/configuration.yaml, and set the options needed by your adapter
• restart the plugin

[spud]

As I understand the plugin, it is just interfacing directly to zigbee2MQTT as opposed to through MQTT.

No, the plugin talks to Zigbee2MQTT through MQTT. By default the plugin runs a MQTT broker, starts its own instance of Zigbee2MQTT, and runs a MQTT client that is used to talk to Zigbee2MQTT.
There are settings to use an external MQTT broker and/or an external Zigbee2MQTT instance if you want to manage that yourself.

[aarpi3]

No, the plugin talks to Zigbee2MQTT through MQTT. By default the plugin runs a MQTT broker, starts its own instance of Zigbee2MQTT, and runs a MQTT client that is used to talk to Zigbee2MQTT.
There are settings to use an external MQTT broker and/or an external Zigbee2MQTT instance if you want to manage that yourself.

Could the same approach/code be used towards other MQTT based systems?

Like wled, flic, Shelly ...

[Richel]

For now, the Zigbee2MQTT Back-end page only allow you to select a serial port, we may add more options in a future version. In the meantime you can edit manually the Zigbee2MQTT configuration file located in ./Data/ZigbeePlus/zigbee2mqtt/data/configuration.yaml.

• stop the plugin
• edit ./Data/ZigbeePlus/zigbee2mqtt/data/configuration.yaml, and set the options needed by your adapter
• restart the plugin

Worked!! Thanks.

[Khufu01]

No, the plugin talks to Zigbee2MQTT through MQTT. By default the plugin runs a MQTT broker, starts its own instance of Zigbee2MQTT, and runs a MQTT client that is used to talk to Zigbee2MQTT.
There are settings to use an external MQTT broker and/or an external Zigbee2MQTT instance if you want to manage that yourself.

If I read this correctly, to use multiple of these SLZB-06 network devices you cannot use the HS mcsMQTT broker. You have to go to an external configuration of the broker and as the dev mentions above, you have to use Docker containers. Is this correct?

[ksum]

If I read this correctly, to use multiple of these SLZB-06 network devices you cannot use the HS mcsMQTT broker. You have to go to an external configuration of the broker and as the dev mentions above, you have to use Docker containers. Is this correct?

mcsMQTT is not developed by HomeSeer and not the broker the ZigBee Plus plugin installs. The ZigBee Plus plugin installs is own broker but allows you to use an external broker if you have one. The mcsMQTT plugin is a separate plugin and is used to connect HomeSeer devices to MQTT clients. (It does much more as well, but that is not pertinent here.)

mcsMQTT can install an MQTT broker, or you can us a different broker, such as Mosquitto. HomeSeer is installing a broker if you use the plugin and do not have an external broker. You normally only have one broker and all your MQTT applications work through that. It can be in a docker container or not. I run Mosquitto on a Raspberry Pi 4B which also runs zigbee2MQTT, Node-Red, InfluxDB, and Grafana.

Serge 's diagram in post 28 would be better if it just had "MQTT Broker" in the purple area.

You would need multiple instances of zigbee2MQTT if running multiple SLZB-06 ZigBee Interfaces. You will only use one broker, though. These zigbee2MQTT instances could be on different devices, such as multiple Raspberry Pi units, or in docker instances. The question is, will you need multiple interfaces?

[Bigstevep]

mcsMQTT is not developed by HomeSeer and not the broker the ZigBee Plus plugin installs. The ZigBee Plus plugin installs is own broker but allows you to use an external broker if you have one. The mcsMQTT plugin is a separate plugin and is used to connect HomeSeer devices to MQTT clients. (It does much more as well, but that is not pertinent here.)

mcsMQTT can install an MQTT broker, or you can us a different broker, such as Mosquitto. HomeSeer is installing a broker if you use the plugin and do not have an external broker. You normally only have one broker and all your MQTT applications work through that. It can be in a docker container or not. I run Mosquitto on a Raspberry Pi 4B which also runs zigbee2MQTT, Node-Red, InfluxDB, and Grafana.

Serge 's diagram in post 28 would be better if it just had "MQTT Broker" in the purple area.

You would need multiple instances of zigbee2MQTT if running multiple SLZB-06 ZigBee Interfaces. You will only use one broker, though. These zigbee2MQTT instances could be on different devices, such as multiple Raspberry Pi units, or in docker instances. The question is, will you need multiple interfaces?

Good explanation. Also if you are running multiple instances into one broker with the base topic of zigbee2mqtt it will/could be confusing later where the heck that data came from. Now I’m running the ZigbeePlus plugin instance using that broker and the zigbee2mqtt base topic on a RPI using a mosquito broker with another base topic name on another instance. It’s true that I have two different front ends (one 8080 and the other 8090) and two base topics but when the devices are created in HS I can tell what instance it comes from!

[TC1]

Just got my SLZB-06 today, the documentation could be better.

For example, when I plug the SLZB-06 ethernet port into my network, only the network port orange activity light blinks, I never get a green link light indicator on the adapter (even though I can connect to the web interface on the device). Is this normal or did I get a bad adapter?

[Richel]

Just got my SLZB-06 today, the documentation could be better.

For example, when I plug the SLZB-06 ethernet port into my network, only the network port orange activity light blinks, I never get a green link light indicator on the adapter (even though I can connect to the web interface on the device). Is this normal or did I get a bad adapter?

Same here (no green light), but working as it should.