Hello, I saw in some older reddit posts that sonoff zigbee USB E was unstable (posts from 2-3 yo), but on a more recent post someone said that now it's stable. Does anyone know where I could find some info about this?
I'm trying to decide between E and P versions, because E version looks like more "futureproof" supporting multiple protocols
#sonoff zigbee E or P
1 messages Β· Page 1 of 1 (latest)
Don't buy the P
Probably don't buy the E either, devices from SMLight and Tube are better
But if all you can find/afford is the E then it's ok
Oh, and both support multiple protocols - neither support multiple protocols at the same time
E and P have very similar price
See the pins in #zigbee-archived for Tube and SMLight
i just chechek for P because most people recommand it (on reddit)
Most people don't understand the hardware faults with it π
also i see that E has the same soc as skyconnect
Yes
Most Zigbee sticks are based around two main chipsets, and the handful of variants of both
thank you, i took a look at the pinned post and...nobody is selling them in my country, so sonoffs would be more accesible
You can amost always just import them
the price is also 3X π
You're gonna spend way more on Zigbee devices. Do you really want to cheap out on the most critical device in that mesh?
I spent about $60 equivalent on my coordinator, and I've spent easily $300+ on Zigbee devices
atm i have only a few diy sensors battery powered based on esp8266 and linked to HA, i wanted to try one (at least at start π ) zigbee pir sensor to see the differences
Actually, make that easily $900 now
(over the course of about 5 years)
The main difference with Zigbee is battery life - you'll easily get 18+ months per coin battery
i saw the battery life, i got like ~1 year but with 18650 from old powerbanks, the purpose of the project is to create cheap "iot" sensors made from scratch, it's just a degree project
Creating Zigbee sensors is harder than ESP based ones, there's not anything like as much information out there
i know, mines are wifi based, using a pi zero as a "coordinator server" and also using the pi to use "pre defined" classes that get the ip and name of sensor as parameters, compile the files and upload them to the esp.
i don't even wanna try to create zigbee, i just want to compare with them π
Smaller, better looking, longer battery life, sometimes cheaper.
Also sometimes utterly crap sensors that you'll curse a lot (Sonoff or Tuya)
a few days ago i saw that some people recommand the sonoff pir snzb-03, and today when i read again a lot of people were complaining about false positives...is sonoff really a bad "brand" for those type of things?
i have some sonoff basic sockets for a few years and never had problems with them (they are using ewelink, their software)
Yes, their entire Zigbee range varies from ok to downright crap
A bit like Tuya and Tuya rebrands
i found a site that sells SMLIGHT SLZB-06 directly from my country, guess i'll go for it
what brands would you recommand?i'm looking for pir senros, door/window senros, and temeprature and humidity (here i saw that aqara also have a pressur sensor together with humidity and temperature)
3Reality, Hue, Innr, Xiaomi (Aqara and Mijia), Gledopto, Ikea
oh...there are multiple versions of smlight slzb-06...
SLZB06
SLZB06M
SLZB06P7
SLZB-06p10
Their site explains them
I'd personally suggest the EFR based ones, rather than the CC265x based ones
then SLZB06M it is π
do you own a erf based smlight coordinator?
they really can use 2 protocls in the same time?like matter-thread and zigbee?
Well, in theory they can
Just like in theory you can use a Tesla as a boat
The experience is going to be ... not great, if you're lucky
then i'll just look at zigbee devices then π
There's nothing wrong with Thread and Matter, just don't expect to use one stick for everything
hello @boreal smelt , i finally received my smlight slzb-06, and integrated it with home assistant, but i'm trying to find out if it's using zha/zigbee2mqtt (i've read that zibgee2mqtt is more customizable)
in the smlight web GUI this is checked but i have no ideea if it's comunicating with z2m or zha with by sonoff pir
Which did you install? If you installed nothing itβs probably ZHA
Nothing... It was plug and play
then..how can i change it?
i've found this in smlight web GUI
but i'm using docker and when i try to create zigbeemqtt container it asks for an USB prot...
but i'm using it on wifi
Back up, so Home Assistant is installed in docker too
yep
I am not sure if that has ZHA support built in or not
But it says itβs connected in the SMLIGHT UI
yep, in HA - settings -integration it discovered this one
and i've just pressed "add" button
Yeah just roll with that then
There are only a few outlier devices which work better with z2m I think
99.5% sure ZHA will get you what you need without extra fuss
i've just read that z2m might be faster, supports more devices and it can show more attributes
100% i don't need any of that
but just wanted to experiment
Give this a try you can always migrate to z2m
yes but how i can migrate? π
1 now π
Lol
but how i can switch from zha to z2m?
The key thing is if/when you configure z2m you would be pointing it to a tcp socket and not a USB port
So for example my configuration.yaml looks like this serial: port: tcp://10.10.1.154:6638 adapter: zstack baudrate: 115200
this is the point when i've stoppe dunderstaning
this configuration is from HA
but don't i need to already have the z2m addons
to have this configuration?
another container with z2m *
Zigbee to MQTT bridge, get rid of your proprietary Zigbee bridges
You would need to follow that
Basically the only thing HA would know about it is there are devices it would discover via MQTT
so somehow i should have somethings like
--device=tcp://192.168.x.x:6638 ?
Following this example https://www.zigbee2mqtt.io/guide/installation/01_linux.html#configuring ```# MQTT settings
mqtt:
# MQTT base topic for Zigbee2MQTT MQTT messages
base_topic: zigbee2mqtt
# MQTT server URL
server: 'mqtt://<your mqtt broker IP>'
# MQTT server authentication, uncomment if required:
# user: my_user
# password: my_password
Serial settings
serial:
# Location of the adapter (see first step of this guide)
port: tcp://<your smlight ip>:6638```
ok, i started to create a container with that --device worngly typec, and now it created the configuration.yml file
i'll give it a try
As you can see zha just works out of the box
But if you're in the mood to tinker lol
what can i say, i like to make my life complicated for simple things
i have nothing
i thought that smlight slzb-06m will work as a borker
now i think i get it, so basically the cigbee coordinator will "convert" the data to mqtt?
Z2M will do that
And then it needs an MQTT broker to publish to, then HA connects to that broker, auto discovers the devices
good way to scracth my left ear with my right hand
I only use Z2M because I actually had all of that before I dove into HA
So it was easier to migrate my setup to the Z2M addon than start over
then i'll guess i will try to move to z2m when i'll have more time π
Well, honestly, if you're going to mess with it I'd do it before your Zigbee network grows and you have to re-pair everything
With one device playing around is trivial, with two dozen it's a pain
I am sure there are all-in-one tutorials for standing all this up
i'll take a better* look
This one seems decent, what's missing is connecting HA to MQTT at the end https://pimylifeup.com/docker-zigbee2mqtt/