Been using mine for just over a week and it's been great. Easy migration from Sonoff stick and ability to have it nowhere near the server is priceless. The ability to put out multiple of these also puts it on another level. Works easily with Z2MQTT and ZHA
Nice choice of co-ordinator. I finally dove into home assistant about a month ago but went the VM route for HA installation. I just thought it would be easier. I picked up the same co-ordinator (SLZB-06M), but went with what I thought was the easier way to learn, and that was ZHA. I only have a few lights, motion sensors and smart plugs at the moment. I did dabble with zigbee to mqtt and felt a little overwhelmed, so went back to ZHA. Might try it out again at some point before I get more devices, but loving home assistant, it's so cool.
This ?new? channel really speaks to me. Tinker life, best life. My wife has a saying when I make a minor upgrade and end up taking down the houses network or automations. "You tinkered that to death"
Been putting off my smart home hobby for a long time, but once I move in with my partner I'm very excited to get back into all this. Really wanted to try Zigbee.
Thanks. The SMLIGHT device is a great unit. I use to use the SONOFF unit. It was a very easy and quick to migration from the SONOFF to the SMLIGHT and no downtime and no re-pairing.
OTA firmware update can be dangerous when you want to update your smart power plug which measures energy consumption of your whole homelab (homassistant included). Because the plug turnes off and back on upon update :) Almost learned it the hard way. Thank God I first tried to update its twin measuring the consumption of less critical devices😀
There's three different coloured boxes. There's a brown one SLZB-06m, a blue one SLZB-06, and a black one SLZB-06p7. Which one did you get? Anyone knows the difference
Better range. Put it anywhere you want in the house - so you can have your HA machine in a closet in a basement and have the Z coordinator on the main level. This model is using a Texas Instruments Zigbee chip and not one from Silicon Labs, which is a plus if you ever have to connect it via USB and also have a Silicon Labs Z-Wave controller - no conflict. WebUI is fantastic for managing the device's own settings/updates.
You literally got to see an overview of the whole web UI that this device has, in this video. it's objectively better than sonoff products with a boat load of features.
Hi, home assistant in macvlan you need to run promiscuous mode on the vm if you want to get auto discovery… plus a script for the host. And keep in mind that you can’t get govee to work in this mode. If anyone intrested in my findings i’l put them here later…
9 minutes was really fast, some of my battery operated devices or powered devices can take up towards 1,5 hours to update. Zigbee in itself isn't that slow with 250 kbit/s
Actually, you should avoid letting your EndDevices connect to the coordinator. An EndDevice is nearly always a device running on battery and wants to wake up, do a reading, send that back and go to sleep again. This means an EndDevice must be dealt with directly. A router has main power and can wait. A coordinator has a rather large workload so dealing with the priorty that EndDevices wants will slow it down and that will effect the performance of the entire network. In ZHA there is a setting to deny EndDevices to connect to the coordinator. Made a huge difference. If you find that your enddevices run down their batteries faster than they should, it could also be a sign of this. The coordinator can't keep up and your enddevices are forced to stay awake longer than normal.
Thats really interesting - I would love to see a performance test for end devices connected to the coordinater vs a router. I've got quite a large zigbee network, so any efficiency gain is beneficial to me.
@@ThisIsAitch I used to loose some EndDevices of and on (typically sonoff temp sensor and Aquara wall switch without neutral. The one with neutral is a router) plus sometimes my Zigbee coordinator needed a reload. Sometimes I had several seconds of response time on some devices. After isolating the coordinator from the EndDevices, my Zigbee network has been rock solid and much faster. In the configure.yaml, I've added under the zha: section zigpy_config: source_routing: false CONFIG_MAX_END_DEVICE_CHILDREN: 0
@@My-noname This setting prevents my ZHA from starting. I see no mention of this working in ZHA anywhere but your comment (not in the docs either). I see it's an option for Z2M though. Can you guide me somewhere to troubeshoot? Thank you!
@@MiniPlex2 Wait a minute. There was one line missing! Sorry. Before the source_routing line, there should be a line with zigpy_config: Then it will work For clarity. here is the whole thing zha: zigpy_config: source_routing: false ezsp_config: CONFIG MAX_END_DEVICE_CHILDREN: 0
This is awesome but also Fu#$%^d, as a programmer ok I can go through and really appreciate your work, but explain it to masses, why is it soooo complicated, why all this things cannot just work? Even if you setup everything for your parents, there is a time when you need to or want to have a break and go on vacation, things start to happen, this is the same when you have your own setup and you leave your home for a few days and your wife stays at home.
I wish you would have shown the settings for POE switch.... Some of us a trying to follow along. Not trying to be a jerk, but some of us have some of the same gear and it's a wasted opportunity to not cover settings on equipment we share... I mean, you're already doing a video, and many of us follow you so we can better learn to use what we have or expand on it. Why skip any of it?
How can you be so shameless advertising this crap! When connected via the ethernet, turn of the power in the house and turn it back on after some time - it will never reconnect! Never! After whole of your tcp ip network reboots, you will have manually power it of and then on again, to make the esp module reboot to enable reconnect... This means you never know if your zigbee network still works or not! Every power outage will crush zigbee untill you notice and manually reboot the coordinator. I have 3 pcs of this shit at my shelf which I had to drop after I descovered this issue...
One thing to note that this particular coordinator is Ukrainian made. While I support them in general they are also very good hackers. So I may not necessarily would support them with giving access to my network...
That's a pretty big generalization. As with all IoT devices, if you don't trust them and they can work local, just block internet access, isolate the VLAN, and all the other normal things you do for devices you don't trust. The same could be said about any other device made anywhere else, even your home country... especially cameras, etc...
@@TechnoTimTinkers I wouldn't call it generalization, maybe overcautiousness. But yeah, locking down the rabbit internet from the stick would be a good assurance.
@@TechnoTimTinkers If I was going to generalize about any country and backdoor devices only one comes to mind. The USA. It's the only country in the world that has a well documented history of this sort of clandestine thing. Other countries like the UK and China are pretty transparent about their mass surveillance.
Moving from zigbee2mqtt to ZHA is easy. Not as easy the other way around though. Some zigbee.chips work better with one or the other. I learned this when I got the sky connect, which is meant for ZHA. I was using Z2M at the time. To move to ZHA 1 - open zigbee2mqtt, click settings, backup the radio 2 - unzip file, fine coordinator.backuo.json 3 - plug in new Zigbee adapter for ZHA and stop Z2M add on 4 - I still ZHA, choose coordinator, then option to migrate from file, choose json file and your done. 5 - If ZHA is already installed migrate radio and choose the same json file. Note, any existing devices in ZHA will be lost You can create a backup of the ZBA radio but there is no easy way to migrate from ZHA to zigbee2mqtt.
Been using mine for just over a week and it's been great. Easy migration from Sonoff stick and ability to have it nowhere near the server is priceless. The ability to put out multiple of these also puts it on another level. Works easily with Z2MQTT and ZHA
Nice choice of co-ordinator.
I finally dove into home assistant about a month ago but went the VM route for HA installation. I just thought it would be easier. I picked up the same co-ordinator (SLZB-06M), but went with what I thought was the easier way to learn, and that was ZHA. I only have a few lights, motion sensors and smart plugs at the moment. I did dabble with zigbee to mqtt and felt a little overwhelmed, so went back to ZHA. Might try it out again at some point before I get more devices, but loving home assistant, it's so cool.
It's always strange when you work with some topic and one of your favorite content creator drops a video on the same topic. 😂
This ?new? channel really speaks to me. Tinker life, best life. My wife has a saying when I make a minor upgrade and end up taking down the houses network or automations. "You tinkered that to death"
lol, I love it!
Been putting off my smart home hobby for a long time, but once I move in with my partner I'm very excited to get back into all this. Really wanted to try Zigbee.
Thanks. The SMLIGHT device is a great unit. I use to use the SONOFF unit. It was a very easy and quick to migration from the SONOFF to the SMLIGHT and no downtime and no re-pairing.
Dangit! Ive been looking at that device for a couple months. Now i have to buy it before they go out of stock or the price goes up.😢
Thanks Tim.
I’m thankful for this channel! Thanks, Tim!
Just bought this a few days ago, timing!
That's totally awesome!🤓😎
I enjoy watching your main channel. I had no idea you had second ones.
Thank you! Yeah, created another channel just for things that don’t really fit into my main channel.
OTA firmware update can be dangerous when you want to update your smart power plug which measures energy consumption of your whole homelab (homassistant included). Because the plug turnes off and back on upon update :) Almost learned it the hard way. Thank God I first tried to update its twin measuring the consumption of less critical devices😀
In the last version 2.5 u have the tab for cooordinator o router
Could you fi a video if you already have a z2mqtt network and how to transfer
You need to copy the IEEE ID from the old Controller to the new one.
Can you run ZHA and Z2M simultaneously with the SLZB-06?
Why?
If you want to run both in parallel you should use two coordinators under two Zigbee frequencies
@TechoTim do you have a video on how to setup Cloudflare with Traefik? Great videos.
Thanks! I do not yet, only traefik. I have considered it but it's still in the backlog!
I look forward to it. I have Cloudflare setup but I’m new to Traefik. I’ll definitely watch your Traefik video again and see what happens.
There's three different coloured boxes. There's a brown one SLZB-06m, a blue one SLZB-06, and a black one SLZB-06p7. Which one did you get?
Anyone knows the difference
Anyone know the differences between the various versions?
so I'm using a sonoff usb adapter for my ZigBee devices. What is pros and cons for this vs that other than POE?
Better range. Put it anywhere you want in the house - so you can have your HA machine in a closet in a basement and have the Z coordinator on the main level. This model is using a Texas Instruments Zigbee chip and not one from Silicon Labs, which is a plus if you ever have to connect it via USB and also have a Silicon Labs Z-Wave controller - no conflict. WebUI is fantastic for managing the device's own settings/updates.
You literally got to see an overview of the whole web UI that this device has, in this video. it's objectively better than sonoff products with a boat load of features.
Does this work with Aqara?
Some devices but not everything, I have there m2 hub just for the u100 locks for example.
Hi, home assistant in macvlan you need to run promiscuous mode on the vm if you want to get auto discovery… plus a script for the host. And keep in mind that you can’t get govee to work in this mode. If anyone intrested in my findings i’l put them here later…
4:05 No IPv6 ?
"Next insecurity"
You said that right!
9 minutes was really fast, some of my battery operated devices or powered devices can take up towards 1,5 hours to update.
Zigbee in itself isn't that slow with 250 kbit/s
Wow! Yeah, that's a long time!
POE! That's pretty sweet.
Actually, you should avoid letting your EndDevices connect to the coordinator.
An EndDevice is nearly always a device running on battery and wants to wake up, do a reading, send that back and go to sleep again. This means an EndDevice must be dealt with directly. A router has main power and can wait. A coordinator has a rather large workload so dealing with the priorty that EndDevices wants will slow it down and that will effect the performance of the entire network.
In ZHA there is a setting to deny EndDevices to connect to the coordinator. Made a huge difference.
If you find that your enddevices run down their batteries faster than they should, it could also be a sign of this. The coordinator can't keep up and your enddevices are forced to stay awake longer than normal.
Thats really interesting - I would love to see a performance test for end devices connected to the coordinater vs a router. I've got quite a large zigbee network, so any efficiency gain is beneficial to me.
@@ThisIsAitch I used to loose some EndDevices of and on (typically sonoff temp sensor and Aquara wall switch without neutral. The one with neutral is a router) plus sometimes my Zigbee coordinator needed a reload.
Sometimes I had several seconds of response time on some devices.
After isolating the coordinator from the EndDevices, my Zigbee network has been rock solid and much faster.
In the configure.yaml, I've added under the zha: section
zigpy_config:
source_routing: false
CONFIG_MAX_END_DEVICE_CHILDREN: 0
@@My-noname This setting prevents my ZHA from starting. I see no mention of this working in ZHA anywhere but your comment (not in the docs either). I see it's an option for Z2M though. Can you guide me somewhere to troubeshoot? Thank you!
@@MiniPlex2Been running it like that for a long time now. It's the HA zha forum, somewhere. I didn't invent it myself.
@@MiniPlex2 Wait a minute. There was one line missing! Sorry. Before the source_routing line, there should be a line with
zigpy_config:
Then it will work
For clarity. here is the whole thing
zha:
zigpy_config:
source_routing: false
ezsp_config:
CONFIG MAX_END_DEVICE_CHILDREN: 0
This is awesome but also Fu#$%^d, as a programmer ok I can go through and really appreciate your work, but explain it to masses, why is it soooo complicated, why all this things cannot just work? Even if you setup everything for your parents, there is a time when you need to or want to have a break and go on vacation, things start to happen, this is the same when you have your own setup and you leave your home for a few days and your wife stays at home.
I wish you would have shown the settings for POE switch.... Some of us a trying to follow along. Not trying to be a jerk, but some of us have some of the same gear and it's a wasted opportunity to not cover settings on equipment we share... I mean, you're already doing a video, and many of us follow you so we can better learn to use what we have or expand on it. Why skip any of it?
Sorry but there weren't any settings to configure. Just plug it in and it turns on. I will consider this next time!
@@TechnoTimTinkers Thank you
You made this way more complicated than it needed to be.
How so?
How can you be so shameless advertising this crap!
When connected via the ethernet, turn of the power in the house and turn it back on after some time - it will never reconnect! Never! After whole of your tcp ip network reboots, you will have manually power it of and then on again, to make the esp module reboot to enable reconnect... This means you never know if your zigbee network still works or not! Every power outage will crush zigbee untill you notice and manually reboot the coordinator. I have 3 pcs of this shit at my shelf which I had to drop after I descovered this issue...
Odd, I’ve never had this happen once.
Use a fixed ip address?
One thing to note that this particular coordinator is Ukrainian made. While I support them in general they are also very good hackers. So I may not necessarily would support them with giving access to my network...
That's a pretty big generalization. As with all IoT devices, if you don't trust them and they can work local, just block internet access, isolate the VLAN, and all the other normal things you do for devices you don't trust. The same could be said about any other device made anywhere else, even your home country... especially cameras, etc...
@@TechnoTimTinkers I wouldn't call it generalization, maybe overcautiousness. But yeah, locking down the rabbit internet from the stick would be a good assurance.
@@TechnoTimTinkers If I was going to generalize about any country and backdoor devices only one comes to mind. The USA. It's the only country in the world that has a well documented history of this sort of clandestine thing. Other countries like the UK and China are pretty transparent about their mass surveillance.
Also support not generalizing but to accept the premise... I'd argue that they should then make a pretty-secure product.
I'm actually more inclined to but it for a number of reasons... Maybe be the only iot company securing their iot product... They have to...
Moving from zigbee2mqtt to ZHA is easy. Not as easy the other way around though. Some zigbee.chips work better with one or the other. I learned this when I got the sky connect, which is meant for ZHA. I was using Z2M at the time. To move to ZHA
1 - open zigbee2mqtt, click settings, backup the radio
2 - unzip file, fine coordinator.backuo.json
3 - plug in new Zigbee adapter for ZHA and stop Z2M add on
4 - I still ZHA, choose coordinator, then option to migrate from file, choose json file and your done.
5 - If ZHA is already installed migrate radio and choose the same json file. Note, any existing devices in ZHA will be lost
You can create a backup of the ZBA radio but there is no easy way to migrate from ZHA to zigbee2mqtt.