#zigbee-archived
1 messages ยท Page 131 of 1
Think I'll maybe start with something cheaper to begin with if you've any other suggestions? ๐
The USB one then ๐
I would say 50 bucks are cheap in this hobby
They're all at least $40 if you want to avoid the CC2531 (which you do)
Seriously, don't cheap out - you're going to spend many many hundreds on the Zigbee devices anyway
You can take a big risk and get a Sonoff Zigbee bridge. Awesome ZB chip, but the wifi isn't ideal. I'm using it and it is ok-ish for me. Bit more than a tenner.
I've spent an easy ยฃ600 on just Zigbee kit over the last couple of years, and I've a long way to go yet ๐
That seems reasonablly price3d to me. 54$ is not gonna break my HA budget. I just want to understand all the components so that I can try to order things basically all at once, instead getting step one completed, then being stuck waiting/searching for something for step 2, wait for it to arrive, repeat for steps 3 and 4, only to realize that step 1's part is incompatible with step 5, which kicks off the entire process again
I'm just here for the couple of months it will take before openthread materializes, then I'm outta here ๐ฎ
That's my nightmare scenario
I just wish they put things in different frequencies and not 2,4
Pffft, Thread has been around for a while, Zigbee's going nowhere
So basically you're saying if I'm in this for the long run which I feel like I am, I've lots of plans. Then I'd be better just dropping the money on one from Tube and it'll be an investment?
@dawn wagon yeah, that's pretty much what you're paying for, e.g. tube's stuff will work with everything
Yes
Is that the thing with like no application-level spec so every device's behavior will be completely manufacturer-defined?
@austere patio so kinda like zigbee? ๐
Hey, Zigbee at least tries
I mean, there's so many quirks, I wonder why we still call 'em quirks, they're just properties at this point.
Zigbee 3.0 is a lot better
Ok. So, because I'm turbo-noob, if I write up a list of what I'm trying to accomplish, my intended shopping list, and wanted someone with experience to give me a general "yeah, that looks reasonable" thumbs up, A, what additional information would I need to share, and B, where would I ask that question without running afoul of ettiquette?
Zigbee is, manufacturers aren't (looking at you, Tuya...)
The forum IMO
You can find the community forum here
As long as I'm not about to invest in a protocol that's about to be replaced by something new and up coming
Roger, thank you Tinkerer!
Those people are smart
@bronze apex in theory, most stuff that can do zigbee 3 will also be able to to thread. Now, I wouldn't hold my breath, but in theory that's the situation.
And in reality, in 10 years Zigbee will still be going strong
Also, if you wanted to buy everything thread today, you wouldn't be able to, and HA and the likes don't support it at all right now
So eyes closed, buy zigbee
Eyes open, buy Zigbee ๐
Oh now you're throwing in thread, is this something I need to be aware of?
Thread is still largely vapour-ware
Ah fair, zigbee it is
(though I would still recommend everyone to get Tasmota or esphome-supported wifi hardware for anything mains-powered)
I've heard of choip or something?
I would say zwave is a tad better, but another price range
Yes, ZB is already unacceptably expensive in a lot of cases.
Z-Wave Plus is IMO largely where Zigbee 3.0 is - designed for proper interoperability
This stuff would have and should have cost pennies if some manufacturers weren't such a-holes. It's just a radio in a light-bulb, 50 cents surcharge sounds plenty.
Think it'll eventually replace zigbee?
Can you tell it pisses me off? ๐
I have hopes for chip and openthread, for those reasons, but I'm not an optimist.
ZB is transient to me as long as there's nearly no options to build firmware without paying for a compiler.
Given that CHIP is part of the Zigbee Alliance I have slightly more hope it'll work with existing Zigbee devices
Oh boy, another layer
But, given that all these new things take years to get market share, and rarely displace existing stuff... it's not like anybody has to worry
Do you think CHIP will start implementing quirks?
zb-quirks-quirks-quirks-handler
Hmmm by the sounds of it, it's not worth me worrying about yet anyway haha
In the end, all that matters is that your stuff works
Yes, and getting it to work is so so much harder if you're denied access to the stuff you need.
That stupid Ikea stuff... if it had esp32s inside I'd fix all of them in an afternoon.
Haha. I assume my coordinator can go anywhere?
https://www.codepile.net/pile/ql8v4jJw Device signature
(sorry that took so long, kiddo woke up)
Instead I can pay 100 bucks for a dev license and redevelop a stupid button with a radio, or a stupid pwm dimmer, probably need to spend 6 months to get proper power management
and i have no idea what it means
That's assuming that everyone has wifi that is capable of running over 50 devices, which most consumer setups are not capable of.
@forest cobalt rubbish, and even so, would probably have to spend less on fixing wifi than proper ZB gateways and routers.
That's a loaded question. Yes, it can go anywhere, but it also needs to be some place where it can get the best coverage and avoid WiFi signal interference.
And it has to be plugged into a computer (or ethernet if you're using Tube's)
I wouldn't say it's rubbish. I have over 100 WiFi devices and I can kill ANY consumer grade router with ease. ๐
That's 2x 50, and dunno what it is, but IoT stuff is very low-traffic.
I heard someone say that it needs to go into the device that's running home assistant?
If you're using ZHA, yes
@bronze apex if it's USB it needs to be connected to whatever is running your backend, yes
If you're using Z2M, not necessarily
If it's ethernet, it can go anywhere that has ethernet. If it has wifi, it can go anywhere but you're gonna have a bad time anyway
I run HA in a docker container on my pi if that makes a difference?
Not really ๐
You can run Z2M anywhere. You can only run ZHA as part of HA, wherever you run that
You can also plug the coordinator into another computer and tunnel the serial traffic with ser2net. Works best over ethernet.
But either you have to slap up something else to run Z2M on, or you're going to be running it on that same pi. So anything USB will connect to that.
I think you explained that before actually. I'm definitely edging towards z2m
@austere patio before I forget.. what firmware was it that you plan to run on that ZSLC5 or whatever MG21 you had?
No clue, whatever is the most recent EZSP coordinator firmware that can run on it
I tested esp-idf blackmagic with a 13P module and it seemed to work, but I have no firmware for it, nor for the ZSLC5
How picky are these modules as far as RAM and flash sizes are concerned? Will 256K firmware run on a 512K device at all?
The 13P one is especially weird (TYZS3). It's a 4-button battery-powered remote, but the chip has 512K storage and 64K RAM
Ridiculously overdimensioned
ZSLC5 is 512K 768K, but everything I see is for 256K
Hi, recently I have the problem that I from my IKEA E1744 SYMFONISK in conjunction with ZHA, that the same event is sent to me 4, 5 or 6 times in a row. Ideas what this can be?
@tawdry raft "sent" how?
Is it possible to see what zigbee version is reported on a device in zha?
for example if i peform a single click,i get the "single click" 5 times and my automation also triggerd 5 times
@tawdry raft yes but on what level do you get multiple events?
identical events in e.g. the event thingy in developer tools?
@tawdry raft posted a code wall, it is moved here --> https://paste.ubuntu.com/p/SNy8zmtDvd/
it is not the same event (see the different IDs) but the same event type that comes multiple times
Hmpf, I'm inclined to say.. that's what it's sending, so that's what ZHA is doing. Assuming that ID is actually coming from ZB and not from ZHA
But I don't know enough about it
https://imgur.com/a/tgzMoSE
is it normal for end devices to be connected to multiple routers?
Enabling https://www.home-assistant.io/integrations/zha/#debug-logging would show you exactly what's being received
If the TSN is different for each event, then the device is actually sending the event five times
Are you using a Conbee?
yes
Did you recently reboot your computer or unplug the stick (or restart HA)?
Might be related to this issue: https://github.com/zigpy/zigpy/issues/435#issuecomment-657069205
yes HA have restarted a few times in the last hours
Ah okay, thanks for the info!!!
Try what's suggested in that issue comment about "restarting" the remote by re-inserting its battery
Yes, look out, don't buy that ๐
There was some discussion about the topic earlier, so can scroll back. The ZB bridge is ok, but the wifi makes it potentially a bit flaky. USB or ethernet is preferred.
My experience with the ZB bridge isn't too bad, at least currently, but you've been warned ๐
Before buying any peripherals, it's best to check whether your preferred backend supports it. It's by no means generic, and especially when Tuya's involved, there may be differences between devices that look the same.
Iโm partial to the coordinators I make and sell. ๐ reports are they work well.
I'll also reiterate my opinion that's not universally shared here, but: for mains stuff like that, if there's a wifi version that supports tasmota or esphome, I would prefer that.
I'd take a Sonoff Dual R3 instead of that Tuya thing any day
I like doing both.. put a Shelly behind the nice looking switch decouple the switch from the relay and use zigbee bulbs to dial in desired color temp. Switch toggles the bulb. Relay on 100% of the time and can be used as a backup
Shelly good too
I have zigbee bulbs mainly because there's not a lot of nice wifi bulbs that support esphome or tasmota nowadays.
And also for battery-powered stuff, wifi sucks for that.
our preferred white temp for light is in between 3000k and 5000K so not really available in a dumb bulb...
Yeah, and built-in dimming is nice. Regular AC dimmers with LED bulbs is.. meh.
I keep seeing people mention "shelly" - what's that?
A company who make WiFi devices
Also, hi Tube! I just boutght a thing from you!
no no, thank you! I've got my other parts coming in tomorrow. You happen to know what general timeframe I should expect stuff? I just moved back down to lower 48, i'm not sure how long USPS takes to get stuff around
Itโs coming priority mail. Says 2-day but Iโd expect 3-4 days based on their current mess. Iโm on the mid east coast.
Right on. Thanks!
Is there anyone who can help me with HUSBZB-1 and setting up zigbee on homeassistant?
I'm on the way out, but it's a Emberznet / EZSP device, so you can use the instructions for that in zha or z2m.
Pretty sure that would be a horrible z2m experience
Good devices and active community for support on FB. All of the devices, except the motion sensor, can be reflashed with Tasmota, ESPHome etc. There are some guides on YouTube for OTA reflashing of Shelly - Seems you need to go to Tasmota first and then ESPHome.
Some of the devices - like the I3 and Uni are unusual and have functions not usually found elsewhere.
@mighty river not with the dual r3 specifically, it's relatively new, but I own several of its little brothers, the Mini
I have a bunch of ledvance bulbs sold under the Slyvania brand here in the US, I think they are older than what you can get in the EU, but they have been solid for me.
Isn't ledvance the same as Osram? If so, they have a firmware bug which makes them drop done messages from child devices IIRC
They are
Does the Shelly integrate to HA?
Ledvance is different than the original lightify bulbs from Osram
@molten linden not the same TI chip?
Osram sold off some of their business to Ledvance
Not sure whatโs in the Ledvance now. But I started with the Osram ones and ripped them all out as they were nothing but trouble
The Ledvance ones have been fine
cool to know
Hi. Does anyone here know how to get the IEEE of a device using templates? I'm trying to issue ZHA commands programatically and I need to get the IEEE. thanks
?
@mighty river the switch is decoupled and becomes just a simple input. But I believe the sonoffs are not "no neutral wire", which is a common thing for light switches, often they have a phase and a switching wire, so if the light is off, so is the power to the Sonoff. I.e. if it's wired like that and it switches the relay, it kills its own power.
It's not an issue if the switch is next to a socket, or if there's a smart bulb on the other end, as the bulb will technically be always on.
But if none of that applies, you'd need to pull a neutral wire or get a "no neutral" solution.
This applies to any of these in-wall switches, by the way, including any zigbee. If you don't have a neutral wire in your outlet box, you need something that explicitly mentions "no neutral" or make sure you have a neutral wire
never tried these but was interested to see that they are no-neutral-required switches
Sonoff has similar touch switches, yes. I don't think their in-wall ones have it, though.
did anyone try those sensors?
https://s.click.aliexpress.com/e/_AsCL7B
it wrks with z2m?
Technically it's 2 capacitors, but I can understand not everyone is comfortable adding capacitors to a light fixture themselves
They're still selling some products with the old TI chip and OSRAM Lightify firmware with LEDVANCE packaging and a LEDVANCE label on the controller.
("Einige Gerรคte im Handel haben keinen QR-Code" here https://www.bosch-smarthome.com/de/de/fwd/light/ means it most likely comes with an old OSRAM controller.)
(The old ones are horrible)
I haven't tried those sensors but hey look interesting. You might have to be the first.
You may just have gotten a free ticket for the Tuya lottery. Is it listed on zigbee.blakadder.com though?
Good to know. I typically look only for the smart+ series. If I get them and they register as Osram, I send them back ๐
Ah that's great (the neutral wire). I believe pretty much all of these disconnect the wall switch from mains and use it as a fancy GPIO pin toggle, just signalling
And you can use it as an extra switch in zb or esphome or mqtt. To toggle the light that it's connected to.. or to start party mode 3 rooms down.. it's yours to use as you please
And a couple of nights of fun!
Was going to buy the slaesh stick but seems to be out of stock ๐ข
Also looked at the tube at its out of stock also
Even the zzh is out of stock, damn
which are you looking for? I have all the ethernet and USB cc2652 coordinators on hand
(ethernet were out earlier today, but I built some more).
To be honest I'm not really sure what I am looking, just based on what I've heard from others i should avoid the cheap sticks
my USB one is comparable to the other sticks, but instead it's a small puck with a usb cable (takes care of the use an extension cable step for sticks). Ethernet one is great for centrally locating or to not have to deal with passthrough issues with VM solutions.
I run HA on docker so don't think it'll matter much to me. Just want to make sure I'm not cheaping out and end up replacing something in a matter of weeks, but I think it's a matter of having enough routers. Any real benefit for me to use the ethernet?
I wonโt try and up sell you, the main benefits I cite above.
Fair enough, respect that alot. I guess they are easy enough to setup etc? New to this if you didn't realise haha.
Just as easy as all the others. Ethernet one actually now has discovery support in zha if you go that route so may be the easiest. For the usb ones itโs just passing the serial port through to docker and specifying it in the config of zha or z2m.
Sounds simple enough
You get the big fat antenna and a premium zb chip on all of tube's stuff, the ethernet is just extra convenience, made sense to me because I like self-sustained devices, and the extra cost is quite reasonable if you consider the price of an esp32 ethernet board alone. I guess I'm paying mainly to keep docker away from my usb ports.
Agreed... I never knew I wanted the ethernet option until I got the ethernet option.
I've learned my lesson with openwrt and wifi usb adapters.. or I guess I'm scarred for life because of that ๐
I imagine myself in 30 years, and my gbit ethernet is like that old Mustang in grandpa's garage.
Iโm gonna screen shot these comments and and put them in the listings since I donโt pay square enough to allow product reviews.. ๐
Are things slightly more different by using docker?
with Ethernet you donโt need to touch your docker settings
With usb you just have to pass the usb device through to the ha container or z2m container
It's been worse than it is now, but it's always an extra layer that seems to rear its ugly head every so often, usually because of some poorly executed "security" enhancement.
Or some device node changes
Might be as well getting the ethernet one then by the sounds of it
IPv4 is 40 years old, it's got my trust ๐
Tube doesn't pay me enough to advertise, but for me it's a no-brainer ๐
And it's an esp32, can't wait to ruin my zigbee by running a wifi hotspot and BLE hub on it!
It's mine now, tube can't tell me what I can or can't do
I let my support and products do the talking..
Worked for me
Basically I know where to come for support when I buy one then ๐
Well the nature of the product should minimize the need for any... but it's a nice perk to have that to back it up.
Unless tube extends his support to rip those clusters out of your random tuya device, but I doubt he can keep that up for very long ๐
Tuya doing it the tuya way๐คฆโโ๏ธ
Ooh sm-011 efr32mg21 usb sticks popping up in my aliexpress for 16 eurobucks
I have a bag full of SM-011s
Not sure what to do with them ๐คฆโโ๏ธ
Bag =4 or 5
Small bag ๐ had I known, I would have grifted some to go with my order. Didn't you have a board for it already?
The Sonoff was going to end up redundant, but since Hedda mentioned that it should be possible to run it as a router with a few commands and the same firmware, it suddenly is useful again.
Iโd at least flash it so it was bootloader unlocked.
Well, the "tasmota" firmware, I mean.
Don't even know what was on it out of the box. "Don't turn it on, take it apart"
Got tons of Sonoff stuff. And I like them, they really try. But I've never used any of their stock software, I've violated every piece of hardware I got from them within minutes of opening the box.
= enp7s0 IPv4 sonoff_zb_bridge _ezsp._tcp local hostname = [sonoff_zb_bridge.local] address = [172.16.0.249] port = [6638] txt = [] ``` well that wasn't so hard, once I understood what this zeroconf thing was actually about.
A rather disappointing MDNS.addService("ezsp", "tcp", this->port_); ๐ฅฑ
I'll take this up with the zigpy guys, see if they need anything else than just "ezsp", but honestly can't think of anything
Maybe txt=['i_am_using_wifi'] so zha can scoff you for it
Zigpy doesn't itself do discovery beyond port probing but there was a similar change a few weeks ago in HA core to support network discovery of Tube's ethernet adapter for TI.
Yeah, I've got eyes on the relevant topics and a conversation with Hedda, will dump it there ๐
Hm I just realized, we need baud rate in there as well.
Does anyone know how to find the zigbee device path on #449717345808547842
Find it on the host, pass it through to the container
The approach is the same as finding any other newly connected USB device:
- Plug in the device
- Run
dmesg|tail -n 20to see the last 20 lines and help you identify the device - Now look in
/dev/serial/by-id/for something that matches - or just the device that appeared most recently
@sour shadow You can bind ZHA to the API in Phoscon?
I don't think that means what you think it means
If you're using ZHA you're not using anything from Phoscon
Ah - How do you connect to the RaspBee II then? Needs some sort of client on the RPi....
** If HA is running on the RPi **
Well, if it's not, you're not going to use ZHA
I was thinking of HA running on another host and RaspBee II on RPi
Then you need to go looking for various serial-over-network options
Or run Zigbee2MQTT there instead
I'm happy with the deCONZ/ Phoscon setup at the moment, but will try ZigBee2MQTT when I have some time
Those are the only options that easily allow you to decouple HA and your Zigbee stick
Yep - I misunderstood the original question.
Assumption that no one uses RPi for HA anymore 
considering rpi-gpio is on 125th place in the integration analytics I'd say that is a bold assumption
Hi, I was trying to install zigbee2mqtt using a conbee2 but I get these errors when starting the add on. Does someone know whats going on? https://paste.ubuntu.com/p/x2JJdZnyF4/
The number of people that should use a RPi for HA is at an all-time low. That's not a very useful statistic in the real world, though ๐
Why not use a Pi if you have one? Might I run into issues?
Is it though?
@prime saffron well if you plan to use it beyond testing, at minimum you should set something up to replace SD for storage.
Question to the group can I change coordinator in a ZHA network in HA without having to rebuild the zigbee network and re-add all devices again?
But if you end up having to hack external storage to a Pi, there's much cheaper and convenient options. I run on x86 thin clients, for instance.
Any second hand PC from the last 8 to 10 years will be lightyears ahead of the Pi
If you're switching between coordinators that use the same radio library (i.e. TI to TI or SiLabs to SiLabs), it's relatively easy. Otherwise you'll have to do a little bit of manual translation to make one backup format compatible with the other.
Eh, IO speed hasn't really been an issue for me. I don't see a reason to switch. I tried to setup a Ubuntu server on an older Dell but hardware incompatibility issues reared its head.
It's not just about speed, it's about reliability
Yes, though I go with the thin clients specifically because of the low power consumption. Can run on a $10 Pentium 4 server, but a blaring power-hungry monster is not ideal.
It's not about speed at all, indeed. HA pretty much kills SD cards with writes within months by default.
They're limiting writes a bit now, but it's still far from ideal
Alright, that's a bit concerning. I will try to move to an external drive soon then.
Best take care of backups/snapshots (not on the same SD) if you value your configuration.
My zigbee door sensor is "unavalable" after migrating to Docker. Should I just try to re-add it?
@blazing dagger that's often the easy way, yeah
Or "reconfigure" but I've had limited success with that
What's "reconfigure?"
Have you triggered the sensor at all?
I don't even know exactly, but it does fix some scenarios
Yes
There's little risk to a re-pair anyhow, zha at least will realize it's an existing device and connect the dots
I just flashed a sonoff zigbee bridge with tasmoto, set up ZHA, and then connected a sonoff motion sensor to it.
it detected motion for the first 5 min and now just shows no motion/clear constantly. I re-set/re-connected the sensor but still no luck.
any ideas on how to debug?
@trim tinsel you have 2 problems. One: the sonoff zb bridge and two: the sonoff motion sensor ๐
How's the battery in the motion sensor?
ha! in my defense the bridge is "supported" according to the ZHA docs
its brand new, but somehow already at 85%
Hmz
wait, its back to 100%
I have the same setup, and mine start to drop because of low batt even if they report plenty of juice, but shouldn't happen with fresh batts
Then my guess is range
its 1 foot from me :\
You being the zb bridge?
both the bridge and sensor are right next to me
Maybe it's too close ๐
It does have a retrigger limit of a minute or 1.5 even, but I suppose you've waited longer than that
Can look into signal quality then, may be wifi interference
i have no idea what changed :\ welcome to Zigbee! ๐
The zb bridge is also a blaring wifi interference source, so getting some distance between it and the sensor may help, but some investigation into your (and surrounding) wifi channels and your zb channel may be a good idea.
could you point me to some blogs/docs explaining how to do that investigation?
or where to start from
As well as checking if your zb bridge link isn't suffering from serial/wifi disconnects
Can see signal strengths in zha, the map, etc. Can scan wifi with a phone app
cool, thats a good starting point for me
Serial disconnects will be logged in HA logs
i have this: https://www.zigbee2mqtt.io/devices/TS0044.html#tuya-ts0044 and it sends z2m payloads weird, anyone know what is all about? i mean first click is instant but after the first click if i want to click it again there is a 1 second delay at least
if i click at 2 seconds distance clicks are instant
i think is related to 1_single, 1_double, 1_hold
the wird stuff is i dont have this problem with aqara ones
yah seem not
is like if i do single click to fast it has a lock
it takes the second single click but publishes with delay on z2mqtt
Waiting for hold, then?
Can poke around in the clusters a bit, see if there's anything about timings
Also I'm assuming here the delay is on the zigbee side of things, but is that actually the case?
i think so
why i don't like this is because all aqara ones that can do single double and hold
don't have this problem
so i see it as poor implementation from the manufacturer Tuya
Fully in line with what we've come to expect from them ๐
yah i did not know, is good that i bought from them only 2 things
that switch and this one
Though arguably, a lot of this is down to the individual manufacturers doing their own thing, but arguably that's on Tuya for allowing them to do that
not impressed with any of them
thinking about pulling the trigger on this set from ebay. https://www.ebay.com/itm/372646208459?epid=15035286341&hash=item56c371e3cb:g:YDkAAOSwv9pfhFfn I see a different set of Iris sensors on the blakadder site (https://zigbee.blakadder.com/sensors.html). Is there any reason why these i linked are a bad idea to buy? I don't have a zigbee hub yet, will be buying that as well
@hollow quest looks like you bought those a year back. ^ in retrospect would you recommend?
i need 20 sensors to get every door/window on my house so the ~$4/per price point is attractive, but not if they're going to be frustrating
hmm the only issue iโve had with these is the lack of included magnet
you mentioned lack of battery reporting too?
yeah i dont know what i'll do for magnet. maybe cabinet stop magnets
oh yeah let me check on that, i think battery reporting was added to zha a few releases back
iโm using a slightly smaller rectangular magnet that came with another door sensor, it doesnโt work very well
@cedar coyote battery reporting does work now
i might pull the trigger. need to decide on hub as well. im a little concerned about range
Hm my experience with sonoff door sensors, the included magnet part is mostly air and plastic, in retrospect I should have just stuck some tiny magnets on there instead. It does help if you know the position of the magnetic sensor, and also a strong magnet helps, of course. But can do with a fingernail-sized neodymium magnet if you put in a bit of effort. They're cheap as chips, or can salvage from e.g. a cd player ๐
Range is a matter of building your mesh
yeah i think i'll be okay, the front door and back door are fairly centrally located
hmm the iris 3320s are available for $1 more per, and they're on the blakadder site. maybe i'll go that route.
i wonder what the difference is
this is a shamefully dumb question. This is a zigbee hub, right? https://www.amazon.com/gp/product/B08BZQNK4L/
it doesn't mention "zigbee" on the description. I seem to recall a recommendation for Aqara
@cedar coyote says zigbee further down in the product description
Aqara sensors, not the hub. If you want to add random devices to your network, you generally want to avoid manufacturer hubs.
I have the sonoff hub and flashed tasmota, the only issue seems to be zha+ikea buttons

is there a comparably priced alternative hub that is more flexible?
standalone? I only know of the sonoff
See the topic @cedar coyote
or that
There are three Zigbee options with Home Assistant (regardless of how you install it). These are:
deCONZ is relatively stable and mature with its own UI (and Discord server). It can run in an add-on, in a Docker container, or natively. Only the ConBee range of sticks and RaspBee GPIO boards are supported. Known working devices are documented, and how to request support for a new device is documented too (you can't add unsupported devices yourself).
zha is actively developed as part of Home Assistant Core, using the zigpy stack, the UI also being part of Home Assistant. The EmberZNet based sticks are recommended, but there are other options. There is no list of supported devices, as any standards compliant device should work. Devices that require extra support are listed, and adding unsupported devices is documented (you can't add unsupported devices yourself).
Zigbee2MQTT is very actively developed and can run in an add-on, in a Docker container, and natively. As of 1.15 has a native UI, and it also uses MQTT for control and configuration. It supports mostly TI based sticks, with the recommended options being the Zig-Ah-Zig-Ah!, Slaesh's stick (though be aware of the well documented communication problems with the seller), Tube's CC2652P2 based coordinators and the TI Launch-XL boards. The known working devices are well documented (which usually includes how to pair them so you don't have to find the manual), and adding unsupported devices is also documented.
More in pinned messages
zha looks appealing. i'd feel better about the sonoff zbbridge if it was available on amazon. maybe thats a dumb bias.
Yeah, don't get that thing
alright. sonoff it is. may 5th delivery
Don't
ITead Sonoff ZBBridge (Note! WiFi-based bridges are not recommended for ZHA with EZSP radios. Also, this first have to be flashed with Tasmota firmware and Silabs EmberZNet NCP EZSP UART Host firmware to use as Serial-to-IP adapter)
yeah im reading this https://zigbee.blakadder.com/Sonoff_ZBBridge.html
The "not recommended" part is what I was hoping to emphasize. WiFi serial bridges don't work that well.
well. ideal situation for me is, go to amazon, add a bridge to my cart, plug it in, connect my contact sensors, see them in home assistant, live a happy life. but i think i have unrealistic expectations
so im trying to educate myself as to how to achieve this
That specific combination is the source of many complaints. If you start seeing NCP entered failed state errors and your Zigbee network becomes non-functional for 30 seconds at a time because serial communication was interrupted and needs to be reconnected, it won't be fun.
havent seen that on my sonoff
If it works for you then it works, but many people seem to have issues with serial over 2.4GHz WiFi.
does the conbee ii work w/ the home assistant operating system? the product description on amazon mentions rasbian
It'll work but you'll have better results with one of the Texas Instruments (CC2652) coordinators like Tube's (https://www.tubeszb.com/shop/coordinators/2) or a zzh (https://www.tindie.com/products/electrolama/zzh-cc2652r-multiprotocol-rf-stick/), or a SiLabs coordinator (https://www.tindie.com/products/elelabs/elelabs-zigbee-usb-adapter/)
ok cool. I hadnt heard of tubes before
They're like hollow sticks
isn't the sonoff SiLabs?
lol.
Stock is a bit of an issue atm, don't want to sound like an ad all the time, but tube has stock
well if i can plug this thing in and its gonna work and i dont have to flash a new firmware or anything it will be worth the $62
after shipping
The USB coordinator is cheaper if you don't need the ethernet
@prisma shell yes efr32mg21, nothing wrong with that
ZZH is also surprisingly in stock but ships from the UK
Hm how's the ch340 holding up on that?
Waiting for my zzh
Hasn't crashed my dev machine or my server this year so surprisingly well
It's just weird, for some people it's the "Just works" no.1 usb-to serial, for others it's "your regular Chinese rubbish", both are about equally represented.
it can be both
I think some people also had issues with USB passthrough or something
Well if it doesn't work, it can't be "Just Works", but I agree, plenty of Chinese "rubbish" that's "Good Enough"
Yeah, usb and docker/vm are just such a sh*t storm, even moreso in the past.
yeah one nice thing about ip/serial
Bonjour, je n'arrive pas a connecter mon raspbee .
so is this Tube zigbee company someone in this here discord?
i got a tracking number within like 15 minutes
HA and a lot of other OS stuff standardizing on docker and vms for consumer-grade software is quite daring. Might be starting to work out, but twas bumpy
@cedar coyote more like "a guy", I mean that in a positive way. Yes he's here ๐
is it you euro? ๐
Him and the other "indie" options like the ones above are such an awesome thing. Top-tier smartly engineered hardware and it's not even that expensive. Plus you get interaction that works
cool
Haha no, I am a customer though
that was said with a coy voice in my head
@pulsar crest posted a code wall, it is moved here --> https://paste.ubuntu.com/p/pCdbtfrx9h/
Good bot
I never understood the acm0 vs tty vs ttyUSB thing, are they all the same or does acm add modem features or something? Though this is AMA, different again
It's historic
Ama is arm serial ports if memory serves right
ACM is the same for x86
Then there is pure serial devices
And usb serial bridges
But it's just the names? Nothing functionally different?
@pulsar crest what's the story? Is this new out of the box? It seems to find the raspbee, but there's no response. So maybe bad serial settings, or the thing needs firmware or something
@jolly narwhal yeah of course, but generally.. I don't get extra features (relevant, that is) when using acm vs ttyUSB?
Like flow control or something
Like flow control or something
hi guys. pretty new to all this stuff, so hopefully somebody can point me in the right direction. my zigbee dongles came in the mail today and i just plugged them into the raspberry pi running home assistant. what is the preferred package to install to make this thing start doing the cool stuff it does?
@tender vine zigbee2mqtt or zha, depending on your zb hardware and religious views on integration
cool. i actually just found the writeup by the dongle manufacturer for getting it running in home assistant. its looks like ZHA is what they said to use. i got the thing setup. now i dont have any other zigbee thingies around to pair with it. ๐
but it says its working
is it possible to reflash the cc2531 via USB to the latest firmware ?
got an ancient firmware version on it
If by "latest" you mean 3.0.x, don't
You can flash the latest Z-Stack Home 1.2 (https://github.com/Koenkk/Z-Stack-firmware/blob/master/coordinator/Z-Stack_Home_1.2/bin/default/CC2531_DEFAULT_20201127.zip) with https://github.com/zigpy/zigpy-znp/blob/dev/TOOLS.md#flash-operations
Hi. Probably it's been asked a hundred times before but how can I implement the following scenario?
If it's night time than a motion detector should turn on all lighting in the house, but at a minimal brightness. If it's daytime then it should restore brightness and turn on just one light group?
anyone ever dealt with a sonoff snzb-03 motion sensor whos battery died? I appears to have lost it pairing also? Is there there a way to repair the device and not have it create a new device and make me have to redo all automations with new name? (using sonoff zigbee bridge flashed with tasmota)
?
oop-s
worng channel
Zigbee2MQTT:info 2021-04-27 21:23:01: Coordinator firmware version: '{"meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20180507,"transportrev":2},"type":"zStack12"}'
this is my current firmware
Yeah, see my above message
@austere patio thnks
Do an NVRAM or network backup (both are outlined in that linked document) just in case. Flashing the firmware over serial shouldn't touch NVRAM but with the CC2531 you can never be too sure
Though if you're using Z2M it'll just write its network settings so it's probably unnecessary
over serial .... but i dont have gpio pins
USB-serial
ah
have some wireless switches which z2m doesnt really detect nicely, heard that maybe updating cc2531 firmware might help ... ?
PoE lovers rejoice... err wait another few weeks then rejoice.. maybe.. ๐คฃ ๐ฌ
Yeah yeah this message sponsored by JLCPCB ๐
and digi-key
and I'm getting a puppy on Friday so time is going to be limited for a bit. ๐
Hah, happy for ya but glad my stuff is already shipped ๐
Generally been about 7-10 days for orders from JLCPCB.
digi-key I would expect to be a couple of days normally, but who knows how the shortages currently affect that
using the Olimex iso board, they said they had stock, so should be good.
Well, you know, I suppose
case is gonna be bigger and โช
It's gonna be a tube eventually and you know it
I either haven't been here long enough or I'm not smart enough ๐
first time I've ever dropped a hint
Well to be 'earnest' you may remind me of someone, but it's just a long shot
um.... if I have a device that likes to spam the network (and HA's database) with readings, how can I throttle it down a bit?
I'm using Z2M
What device?
I imagine that's a binary-only solution, and one-time at that ๐
for(Txt txt : txts){ } PRGRMR
If I make a zigbee channel change in the configuration.yaml should just a reboot of zigbee devices be sufficient or is there more to it than that?
zigpy_config:
network:
channel: 15 # What channel the radio should try to use.
channels: [15, 20, 25] # Channel mask```
Those settings only take effect when forming a new network. There's no simple way to change the channel at the moment but depending on the radio you're using, you can take a backup and change the channel in the resulting JSON
Thank you very much
unfortunately bellows fails to install
In what way?
An unfortunate way
Or If you can run docker this is an easy way to use bellows if your local python is โhaving issuesโ https://github.com/walthowd/husbzb-firmware
sorry bouncing between after hours work and home assistant
It fails in a way that fills 2 screens full of output that ends in command 'gcc' failed with exit status 1
I'm on hassOS
You can run the docker container within hassos if you log in as root and drop into a shell with login (since hassos is built around docker) but you'd have to stop Home Assistant from also using the USB stick
May be easier to just run this all on a second computer with Python 3.7+ installed (even windows will work, but in that case make sure to pip install pyserial-asyncio==0.4.0)
I assume if I run on a 2nd computer I need to plug the USB stick into that 2nd computer?
Yes
I guess hassos gives me no package manager to install gcc with
I'm completely docker ignorant
That I don't know. If you're doing it all within the managed OS you may as well run the commands in https://github.com/walthowd/husbzb-firmware/#coordinator-migration
Should just drop you into a shell where everything works, assuming you somehow shut down the home assistant docker container that's currently using your radio
well the bellows commands don't run, command not found. Unless I'm suppose to be in some other shell in this sea of shells
It's not installed in the main hassos OS
I don't even think that environment has Python
am I supposed to switch to some docker instance first?
I wouldn't recommend doing this with the Home Assistant OS. The Docker container running Home Assistant is using your radio, which would prevent any other application running on the same machine from interfacing with your radio
wouldn't the docker container running HA then presumably have bellows?
It does but if you stop Home Assistant, the container stops as well
I guess I'm not sure why I would need to stop home assistant
Home Assistant's ZHA component uses bellows to talk to your radio. You can't have two applications exclusively controlling your radio.
two applications, I'm sorry for being so lost. What would be the 2nd application?
You running bellows from the command line
I thought I'd get into HA's shell that has bellows, and proceed to backup the config
They would both try talking to your radio over the same serial port, which won't work
And I can't stop the service that's using hte radio from within the docker?
Two drivers, one car
Sot hat I can use bellows?
The Docker container runs Home Assistant directly. You'd either have to delete the ZHA component, or stop HA, which would cause the Docker container to exit
not trying to be argumentative in the least, just trying to get a grip on the scenario.
I think I'm okay with deleting ZHA, as long as bellows can backup the config after.
I'm not 100% sure what the consequences of doing that are, which is why I suggest installing Python and bellows on another computer, since you can just yank the stick out of your HA computer and plug it back in after you're done changing the channel
Unfortunately there's no way to do this through the UI so the CLI way is the only way at the moment
That's okay I don't mind command line, but I know nothing about docker so I'm floundering a bit lol
If you have a second computer then the Docker stuff is irrelevant, since you only need an environment with Python 3.7 or above installed
let's see if I can get those on mint
It's based on Ubuntu (I think?) so it should be python3
yeah it's ubuntu-ish
So something like apt install python3-pip and pip3 install bellows should work
thanks
looks like bellows won't install here either
different kind of errors.
but i'm not entirely sure it isn't network related so trying something..
That's better, hopefully this works
man that eui64 warning is ominous but i suppose it doesnt' really matter
The one indicating that you can't overwrite your adapter's EUI64 more than once?
yeah
I'm not clear on which option excludes it. I see sudo bellows -d /dev/ttyUSBX restore --i-understand-i-can-update-eui64-only-once-and-i-still-want-to-do-it -B backup.txt and sudo bellows d /dev/ttyUSBX -f -B backup.txt
sorry pulling from 2 different articles here
without the long switch, or without the -f
To me the long switch reads, do the thing anyway, and -f reads "force it"
so i'm not clear on which one is doing the eui64 write.
I believe the second command should just be bellows -d /dev/... backup > backup.json
Not sure where -f is coming from, it's not a recognized flag
So from here...
Under restore procedure
Do the really long one, then check info, if EUI64 doesn't match, do the short one with -f
So it almost seems like either way you're writing EUI64 doesn't it?
bellows -d /dev/... restore --force --backup-file backup.json works for me
Alright
I guess the only other part I'm not clear on. https://github.com/walthowd/husbzb-firmware/#coordinator-migration has backup, swap sticks, restore. I'd skip swap sticks, backup and restore. How would that enable the channel change?
Or do I edit the JSON in between
The latter
Swapping sticks is only for when you physically want to switch between two coordinator sticks
Since you'd need to migrate the network settings from the old one to the new one
So you can edit the channel in the backup and restore it to the same stick
got it
Should be "radioChannel": ...
I just tested the above two commands with my HUSBZB-1 and they worked fine
bellows -d /dev... info confirms that the channel was changed
You'll likely have to physically reboot every router on your network for them to maybe pick up the new channel
Sensors might not migrate
fortunately i only have lights at the moment
Plugging in the USB stick back into your HA computer should work fine, without having to restart HA or ZHA
If you're running all of these commands on a separate computer it shouldn't matter
Or do you mean that the backup and restore don't actually run because your serial port path is different on your second computer?
Try sudo ./bellows or sudo chmod 777 /dev/ttyUSB0 # :( and run it again as your user?
runs as local user, does not run as sudo..
You likely did pip install --user?
pip doesn't install to ~/.local/bin by default so ๐คทโโ๏ธ . The chmod thing (sorry permissions) should work though.
It runs fine, your user just doesn't have permission to open serial ports. Pretty sure that has something to do with the dialout group on Ubuntu but the "quick" fix is to just...let anyone communicate with the serial port (I assume it's actually /dev/ttyUSB0, easier to use /dev/serial/by-id/<some sensible name>)
Hence the chmod "fix"
i tried dropping into root and adding this dir to path but that didn't help
I 777'd it, still no love. it's executable but i think line 5 is making a reference to something else somewhere else
oh, you mean 777 the device?
Yeah
lol sorry i missed that
sure
alright, hurray brute force
okay, info now reads radioChannel=25,
Looks like it worked
now i'll plug it back in, and throw the main breaker to the house XD
See, this is much easier than doing it from a web UI. Make sure to keep the breaker off for like 5s. If you only momentarily flip it, some devices don't actually reboot.
good to know, thanks
they dont' seem to be figuring out hte new channel, I might need to reset them.
very possibly just how these bulbs are
Hey all. Got a weird one. Just introduced a SNZB-02 temp/humidity sensor. Using Google to get temp reading. I've got the entities set up as temp_sensor.bedroom_temperature and such. When I ask Google for my bedroom temperature it comes back with "the temperature is off and it's currently XX degrees"
Why is it reporting the temperature is "off" when it doesn't have an on/off state?
Same results for humidity too
i think that's more related to google then zigbee, I get that sensor is zigbee but from what I understand google is reporting that sensor temp / humidity? if so then go #integrations-archived as long as you can see that sensor temp and humidity in your ha correctly zigbee is ok
Yeah it's reporting the right values but it's weird hearing it say the temperature is off haha. Thanks though.
yah thats google all the way nothing to do with zigbee
Oh yeah definitely. I checked entities in the integration and HA is only sending the actual temp/humidity values. Checked in Google Home and found the name of the devices was set to what they did. Changing that name from "temperature" or "humidity" would cause Google to read out ""insert line here" is off and the temperature is 26 degrees"
So now I just have to find a funny name or something to put into the sensor name field in Google Home.
Ooooh, I might call them all "All bets"
please move this to #integrations-archived
Hi there, Im a little confused with these wifi and zigbee devices. I know we can tasmotize zigbee bridges like the Sonoff Zigbee bridge. But do we tasmotize the other devices like zigbee switches and sensors?
Nope. Sensors and such stay the same. Personally, I'd recommend against getting a bridge device and get a proper coordinator. The Sonoff bridge in particular is a recipe for disaster as it puts a WiFi radio and a Zigbee radio right next to each other. Interference hell.
Im going crazy flashing some of these tuya wifi switches and I am thinking of switching to zigbee ones but Im not sure how they work
Anyone knows a good channel for flashing tasmotize for Tuya devices?
Zigbee works like WiFi does, with some caveats. You can only have a single coordinator per network and the range is basically about 2/3rds of a WiFi signal due to power (Zigbee is a low-power protocol). But, you can add as many repeaters as you need. Repeaters are mains-powered devices (plugs, switches, bulbs, etc).
Is the latency of zigbee greater than wifi?
Not meaningfully
The data rate is lower, but then it's only sending small messages, and it's designed for this
The wake and connect time for wifi battery powered devices is appalling. In the order of 5-10 seconds.
yeah it might be 1s if my zigbee button is deep sleep
Devices wake up periodically (couple times per hour) to report battery status so they're never really in a deep sleep. Which button takes a second to register a click?
Hi there, I am having a very strange issue with an automation. HA is fully up to date. I have a ZZH stick all working fine with ZHA. I am using an Aqara motion sensor to turn on a Lidl light in the hall and a timer to turn it off again after 2 mins. This automation was working fine until I tried to change from using device.turn on to service.lights on. The automation fires as expected, HA thinks the light is on (Lovelace shows the toggle pill change from grey/left to blue/right), but the light is not actually on. If I toggle the light off and on via Lovelace, the light comes on as expected. There are no errors thrown in the logs. The timer fires correctly and I can see the countdown, and the automation to turn the light off works fine. I have deleted and recreated the automation. This morning it seemed to fix with a reboot of the host but it's not working again now. Does anyone have any suggestions? I did post in Automation but was advised to post here as ZHA/HA believes the zigbee light is on. Thank you
@minor pumice checked the signal quality, e.g. in the visualization? I had some similar issues and it turned out to be a range issue
would that be the case if I can toggle the light off/on and it comes on OK whilst the timer is running?
It shows as a 95 on the connection between the bulb and ZZH, also has routes via the mesh
If it's greenish then it's probably not a range issue, then.
It switches on fine manually, and it switches off per the automation
Hm, maybe set zha to a higher log level and catch the event, see if it tells you more
That it shows on in HA means that ZHA thinks the bulb is on
That's what is puzzling me, I know when a light isn't connected, my experience is that the toggle went back to the position it was in
Is it a single light? Not a ZB group or ha light group?
single light, not a group either HA or ZB
Alright, well that eliminates another issue that I could think of
Enable ZHA debug logging to see what the problem is: https://www.home-assistant.io/integrations/zha/#debug-logging
Oui
Tried putting this on pastebin but it's in Read Only mode at the moment.
2021-04-28 16:41:19 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x9D07:1:0x0006]: executed 'on' command with args: '()' kwargs: '{}' result: [1, <Status.SUCCESS: 0>]
2021-04-28 16:41:19 DEBUG (MainThread) [homeassistant.components.zha.entity] light.tz3000_dbou1ap4_ts0505a_4488d1fe_level_light_color_on_off: turned on: {'on_off': [1, <Status.SUCCESS: 0>]}
2021-04-28 16:42:24 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x4A4C:1:0x0008]: received attribute: 0 update with value: 255
2021-04-28 16:43:19 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x9D07:1:0x0008]: executed 'move_to_level_with_on_off' command with args: '(0, 30.0)' kwargs: '{}' result: [4, <Status.SUCCESS: 0>]
2021-04-28 16:43:19 DEBUG (MainThread) [homeassistant.components.zha.entity] light.tz3000_dbou1ap4_ts0505a_4488d1fe_level_light_color_on_off: turned off: [4, <Status.SUCCESS: 0>]
2021-04-28 16:43:25 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x9D07:1:0x0008]: executed 'move_to_level_with_on_off' command with args: '(1, 1)' kwargs: '{}' result: [4, <Status.SUCCESS: 0>]
2021-04-28 16:43:25 DEBUG (MainThread) [homeassistant.components.zha.entity] light.tz3000_dbou1ap4_ts0505a_4488d1fe_level_light_color_on_off: turned on: {'move_to_level_with_on_off': [4, <Status.SUCCESS: 0>]}
First time worked, after restarting the server to enable logging. Second time did not work.
The zigpy log lines have all the useful stuff. You can put them here: https://paste.ubuntu.com/
I am getting back into HA again. I bought a conbee II in 2019. Is it the same hardware?
https://www.amazon.com/gp/product/B07PZ7ZHG5/ref=ppx_yo_dt_b_asin_title_o06_s00?ie=UTF8&psc=1
All the conbees are the same
Thank you. Updated Logs: https://paste.ubuntu.com/p/xHf2tyktz5/ the device in question is the light.tz3000_dbou1ap4_ts0505a_4488d1fe_level_light_color_on_off. After a server restart, it seems to work once, then subsequent triggers don't actually turn the light on.
Can you post the unredacted log for all lines matching zigpy and zha? You should have lines with zigpy, zigpy_znp, and zha.
@austere patio thank you! where can i get info on how to update it?
Update it?
update the firmware on conbee
That'd be handled within the deCONZ UI AFAIK
Hmm. I'm not seeing anything unusual in the log. What part of it corresponds to the device "turning on" without turning on?
Towards the end, light.tz3000_dbou1ap4_ts0505a_4488d1fe_level_light_color_on_off: turned on: {'move_to_level_with_on_off': [4, <Status.SUCCESS: 0>]}. The only thing I can see in the logs, when it worked after a server restart it was a [1,<status rather than 4. It's bizzare.
should this not mean that lidl silvercrest doorbell is now supported?
https://github.com/jurriaan/deconz-rest-plugin/commit/e09d3365cf84fd13323ef772f242fa644efc3f7a
When you say "the first one", there are three commands in your log: on, move_to_level_with_on_off(level=0, transition=30s), and move_to_level_with_on_off(level=1, transition=1s)
Do you mean that the second move_to_level_with_on_off didn't turn your light on?
Some lights apparently don't respect the _with_on_off part of the command so they may need to be sent an explicit on afterwards (if I'm reading ZHA's source right?)
If so, open an issue with the content of the Zigbee device information dialog and state that that is the caseโฆ we have a list of devices that force the on command
No, that log didn't capture the 'working' automation. Too many people moving around so waited until the motion stopped detecting, the timer was idle and the light off. In the extract I posted earlier, you can see the line:
light.tz3000_dbou1ap4_ts0505a_4488d1fe_level_light_color_on_off: turned on: {'on_off': [1, <Status.SUCCESS: 0>]}
which worked, I then went to trigger it again and saw
light.tz3000_dbou1ap4_ts0505a_4488d1fe_level_light_color_on_off: turned on: {'move_to_level_with_on_off': [4, <Status.SUCCESS: 0>]}
which didn't. I can see the difference being the command on_off and move_to_level
So your light works with on_off but doesn't do move_to_level_with_on_off properly?
yeah looks to be
Thanks Tuya
I couldn't see the difference to start with, I am happy to add an issue under GH, which repo would be best to do so?
I think one in HA's repo for the ZHA component (https://github.com/home-assistant/core/issues/new/choose) but @tropic depot can clarify
Grab the "Zigbee Device Signature" as well if you're going to create the issue, it'll provide the required info about the device to fix it specifically
Yup
https://github.com/home-assistant/core/blob/296dc9303fc722658a60cb6ca84f550d63c1722f/homeassistant/components/zha/light.py#L536 we just need to add the right info hereโฆ
This isn't done with a quirk that overrides move_to_level_with_on_off to also call on_off?
Thank you both, will get it sorted
Thanks for the logs, I'm sure there are tons of other people with white-label Tuya bulbs experiencing this same issue
Anyone using Xiaomi Light Sensor (GZCGQ01LM) through deCONZ? Mine will not drain battery, shows 100% after a year almost. Have tried lifting the battery
Have you tried installing a mostly discharged battery?
The idea is great, but only have two devices, of same age. No other batteries to try unfortunately
If it's like the other Aqara sensors, they last for a few years for me but the battery percentage/voltage doesn't really drop much until the device is effectively dead
I don't use deCONZ and have no idea how to enable debug logging for it but from what I understand, this Aqara sensor specifically is Zigbee 3.0 compliant and should be reporting its own battery percentage
Aha.. Thanks, that is good to know. It is not a major thing really, but would be nice to know when it's time to order new batteries... ๐
Can you read the battery voltage and battery percentage from its power configuration (0x0001) cluster?
Oh... how would I do that?
deCONZ should have a GUI to do all this. I don't use it so ๐คทโโ๏ธ
I think that was the original plan but the commands are on different clusters and it wasn't easily possible (or something like that).
No
Yeah itโs a PITA
it can be doneโฆ but for now itโs like this
needs eventing between clusters and 2 cluster replacements per bulb
Iโll get the motivation to do it at some point (maybe)
You can't look at the cluster's endpoint attribute and then access its on_off cluster from within the level_control quirk?
Thanks, I will read up a bit on deCONZ. Haven't really yet so probably a lot to learn about it...
It's basically the first image in its manual: https://www.dresden-elektronik.de/funk/software/deconz.html?file=files/dresden-elektronik/content/downloads/dokumente/funktechnik/deCONZ-BHB-en.pdf
Ah! ๐ That one... When accessing it one gets two options, deCONZ and Phoscon. The latter a lot simpler interface. Will try the other one ๐
Yeah, the former seems to give you much lower-level access to the Zigbee network
You should see a "Power Configuration" cluster on some endpoint on your sensor, which will have various battery attributes you can try reading
Must be powerful batteries... Says "Mains" under power source... ๐ Lots of stuff in here, thanks for the hint!
I have restartet my Raspberry and now i have 2 Gateways in deconz with the same ID
I have found why it was happen but i am not shure how to fix it.
I have installed the HA with the Raspberry Image and there the HA runs in a docker.
The problem is that at installation time the stick was insertet when the system was running and it gets an IP from the Docker container.
Not at the reboot it gets the IP from the real system. So the HA thinks that this are 2 Devices.
https://github.com/home-assistant/core/issues/49825 Thank you Puddly & dmulchey. I will try and re-pair the device and get the signature when there is noone around to annoy
might have a "workaround" where I create a scene with the bulb and activate the scene .... edit ... never mind. didn't work
No need for the pairing log, the signature is displayed when you click the button: https://i.imgur.com/kFldS7b.png
(It's still mentioned that re-pairing is required in the ZHA quirks repo's issue template: https://github.com/zigpy/zha-device-handlers/blob/dev/.github/ISSUE_TEMPLATE/device-support-request.md#:~:text=device signature "Device signature")
Hmm, that may need to be changed
Or at least clarified
Though for quirks the pairing log contains more info than the signature so ๐คทโโ๏ธ
OK added the device signature to the GH issue
Thanks!
Does anyone know how to reach out to slaeh's iot stuff?
I paid 80 EUR for two sticks and received none and after several e-mails, telegram messages, etc no response whatsoever.
You may be able to find more info here: https://github.com/Koenkk/zigbee2mqtt/discussions/6702
Thanks, yeah he seems to be a scammer
Specifically the cancelmyorder@slae.sh e-mail
Dunno what the actual failure rate is for his shipments
I got an email with the tracking number, but the tracking says:
The item was scanned on 24.01.2021 and returned to sender.
January, 24 2021 09:48 Local time
And radio silence for more than 3 months. This is ridiculous
Yeah, it's a pretty unfortunate situation. He seems to have had major logistics issues and is dealing with them really poorly.
I am looking for a Zigbee in wall outlet for the US with energy monitoring. I am using DeConz to communicate with my Zigbee Network. I found this on Amazon (https://www.amazon.com/Jasco-Receptacle-Monitoring-Tamper-Resistant-43132/dp/B08G58HVL5/ref=sr_1_5?dchild=1&keywords=jasco+zigbee+outlet&qid=1619639631&sr=8-5) but have no idea whether or not it will work with DeConz. Any help that you could give would be greatly appreciated.
Yeah.. Btw, where did you get the cancelmyorder e-mail? On github I only see "And if you want to cancel your order, just mail to @.*** "
Dunno if it will "work" for an already-shipped order
But it's the only thing left before dealing with your payment processor directly
Hi. I have a conbee ii. Last days I noticed in logs that there is a hardwareaction.add and then a hardwareaction.remove of the device which repeats several times. Are there some issues or I have some fault hardware maybe? Had no issues until lately and havenโt done much of anything except applying HA and addon updates..
:))) I am sorry man i am not laughing at your misfortune, just laughing because most problems here are about conbee
๐คฃ
Thank you for the help last night, I have done a workaround this morning, calling the Issue Zigbee Cluster Command Service:
service: zha.issue_zigbee_cluster_command
data:
ieee: '00:0d:6f:00:05:7d:2d:34'
endpoint_id: 1
cluster_id: 6
cluster_type: in
command_type: server
command: 1
I have a couple of Xiaomi Light Sensor (GZCGQ01LM) through deCONZ. They are defiantely battery devices, but report 100% battery after a very long usage. When looking at them in deCONZ, they actually report as "Mains" devices... Can it be determined if that is a problem with my devices or deCONZ reading them?
Mine report (in Z2M) as battery, but if both of yours report as mains I'd say that's probably a deCONZ issue
deCONZ by dresden elektronik is a software that communicates with ConBee/RaspBee Zigbee gateways and exposes Zigbee devices that are connected to the gateway. Our #zigbee-archived channel is a good place to ask about using it with Home Assistant, but they also have their own Discord server.
I'd ask them directly โ๏ธ
Cool! I will, thanks! ๐
My ikea remotes are consuming batteries like crazy running ZHA. Latest one lasted only a few days before running out. Does anyone have tips for this?
Sounds like the signal isn't strong enough
The zigbee router is located less then a meter way, and I also have 3 zigbee lights in the ceiling as routers..
What Zigbee router are you on? there is an issue with them on Tasmota Sonoff devices
I have an slae.sh cc2652rb stick , running the latest firmware from Koenkk/Z-Stack-firmware
Since i've never had any issues i suck at debugging zigbee.. How can i see if the device is alive and sending data since it seems its not sending? Z2M in use, door sensor might be broken / stuck, dunno..
I usually open the Z2M UI and see what it reports
If you've enabled last_seen it'll tell you when it last reported in
You can also then operate the device and see what happens
which part in particular? it all looks ok to me, no logs, but.. hmm, need to check last_seen. Its a door sensor and its been saying door is open for many days (no idea when it actually started)
I find last_seen really handy for spotting when things fall off
Though, often something no longer reporting is a battery issue
ah, found it, looks to be disabled, thanks for the tipi, enabling
Yeah, I think it's disabled by default
last_seen: 2021-04-14T17:16:15.865Z
right on.. Need to try to give it a kick, maybe wrap some alerts around the last_seen also.
faulty device or something maybe, batter was reported last time to be 100% and 3200mV - this is the "scary" part when things report their last known values while not making it obvious they can be years old.. ๐
Reseating the battery got it online but seems to report incorrect state, also link quality didn't change from next to the stick to the door, might try with a new battery before declaring it as broken
Morning all! I'm new to HA and loving it! There's one bit I'm getting stuck with. I've got a dimmer switch in Zigbee2MQTT addon which is missing the brightness in HA (it exists in MQTT). I've performed an event listen in HA and can see that the brightness is being passed in:
Message 89 received on zigbee2mqtt/Office dimmer at 11:47: { "brightness": 85, "level": 340, "linkquality": 192, "state": "ON" }
I know I need to something with the configuration.yaml but I can't find a good guide - please can someone point me in the right direction?
As a side note, I found that the event listener under dev options shows nothing even if I put # in the listen field, whereas the one under the MQTT addon with a # shows everything - am I doing something wrong there?
Is there a way in zigbee2mqtt to set that if power comes back on with a device, in this case a light, a certain state can be set like it can be in the Philips Hue app?
If the device, and Z2M, support it you can set it in Z2M's UI
Only a handful of devices, mostly Hue ISTR, are supported right now
ISTR?
I Seem To Recall
I googled it and it came up with a post from you on the community page ๐
I'm guessing this is either such a basic question that you're rolling your eyes thinking RTFM! OR much more complicated and not enough detail provided...!
I'm OK either way but would really appreciate a little nudge in the right direction ๐
Are you using Discovery in both HA and Z2M?
Yep
Does it show a dimmer option in the Z2M frontend?
Yep
If you're the same Tinkerer as the Bearded Tinkerer from youtube, then I followed your guide to pull the latest-dev build for Z2M and the openssl version for Mosquitto
No, I'm not
And I'd never recommend folks run dev releases unless they know what they're doing
Step #1 is to run a stable release and confirm the issue there
OK - I'll do that now , thanks ๐ !
doesnt appear there is a 'stable' tag for Z2M on docker, I am running 1.18.2
I think they use latest
Thanks ๐
So here's two screenshots, one of Z2M with the brightness, and one in HA without:
ah image sharing is trned off in here for me
here ya go: https://imgur.com/a/gNmEjPa
What's the HA entity_id?
That's odd - I can see it in States and the brightness is there, it's just not present when i create an automation
'light.office_dimmer'
Ah, lights only have a brightness (or colour) when they're on
hmm - but I can't access brightness even when the light is on in the automations section, i just have set to on/off or toggle ๐
Sounds like a bug in HA
OK I can look into raising that.
Is there somewhere where I can manually edit the entity / devices so I can get it to show up? Brightness only shows in states, not under devices or entities.
I read about adding code to the configuration.yaml to support devices but couldnt find a beginners guide
Well, you can just edit the YAML for the automation
https://home-assistant.io/integrations/light covers the service calls
OK cool - I've read that so will give it a go ๐ Thanks a lot for your help ๐
You're not going to believe this but I just went to create an automation so I could add the yaml and it froze for a second then brightness popped into the list... how very odd!
Along with a bunch of options for flashing etc - wish I knew what happened!
how can I tell if I am running a dev / edge version of z2m?
Well, how did you install it?
docker container... hang on... ๐
just using the koenkk/zigbee2mqtt image
As far as I know that defaults then to :latest which for Z2M is the most recent stable release
That's not the case for everything though
yeah it did list as latest
pretty much trying to figure out how tf to do this
like, where am I meant to put the code to set the power_on_behaviour?
Think I have found an easier way in the UI, color_temp_startup - can set it to previous Color temperature after cold power on of this light
Any zigbee devices with an eye towards homebrewing?
Anything with cc2530
There is a more preferred device? I believed conbee was the go to dongle, maybe that was incorrect. But for all I know it may not be hardware, donโt know. I just noticed having rebooted the device last night nothing in logs now. I use rPi4, HAOS, with conbee and have not even physically touched the device for many many months, never an issue until now suddenly. I imagine such things are difficult to root cause. I did search the channel and google and found a few instances of the same behaviour, people suggesting updating firmware and hardware failure but with no explanation why or if anything they did resolved it.
what integration?
if is deCONZ then no you can't use anything else
you are bound to conbee, xbee etc
I use ZHA. Have from beginning. Tbh I only use it for a few battery powered temp / humidity sensors etc. but also in recent months started binding some hue dimmer switches and motion sensors directly rather than via hue integration.
for zha to be honest i would go with this: https://elelabs.com/products/elelabs-usb-adapter.html
but if you want to be able to switch zha with zigbee2mqtt
i would go with this: https://electrolama.com/projects/zig-a-zig-ah/
but for ZHA https://elelabs.com/products/elelabs-usb-adapter.html works very very well
and you can update firmware on it
you dont need crazy stuff do do it like usb to serial and all crazy things
just a linux machine and some knowledge
Well conbee stick gave no issues for 1 year, zero complaint or issue. Maybe I was lucky then.
sooner or later we will meet here again ๐
but yes maybe you are very lucky
there are more ppl that use conbee stick without issues it depends a lot of use case scenarios
I guess see how it goes if it starts again
Out of interest as I have your ear.. do you know if it is possible to connect a hue dimmer switch device to both HA via ZHA/Dongle and have it also attached to the hue hub?
i dont think so
if you pair it to ZHA will not be paired to the bulb and vice versa
but
and i did not test this
i believe you can do a bind in ZHA
tbh i have those dimmers and use them from years
i used them with ZHA, Zigbee2MQTT and they work flawlessly
never need to bind them
the only problem that I encounter on ZHA and on Zigbee2MQTT is the continuous push of dimmer is not linear
i think is way more linear and continuous when is bonded to the bulb directly
Try latest beta. Reset and rejoin the remote.
#zha cannot get a shenzhen homa RGB led driver to work with ZHA - is it possible? Only on/off + brightness working
Hi, I have tried updating my ZHAQuirks, but now my Zigbee devices are not working. Anyone here able to offer guidance on how to recover?
if you are running supervised/hassos you can just rebuild the ha container and it will wipe out any changes you made to the quirks folder
any reference to rebuilding the ha container?
it's via the ha-cli
command line
so you need to have an add-on installed that will give you a command line.
via ssh or via a shell in the browser
my install is using the Virtualbox method and I have Portainer installed, so it is that command line I need to get to?
no, do you have visual studio addon?
that has a terminal
command is ha core rebuild
no, I will add now
dumb question but is there any guidance on what kind of usb power supply rating to use w/ this tube zigbee gateway?
i dont see it in the readme on github so maybe 1A or even 0.5A is fine
OK, so I ran that command, which brought up a 'processing' and I lost connection for a few mins
sadly no change, should I uninstall ZHA and reinstall?
odd.. do you get an error in your logs that you could post to paste.ubuntu
looks like zigbee comms are working
seems as if the comms to the tasmota gateway is working (to me)
that looks fine. I think there is one error which doesn't look too big of a deal to me. are things working now?
I deleted the devices, uninstalled ZHA, restarted HA. Reinstalled ZHA and doing a discovery I got one of my devices found. But no entities. This is a good sign, as previous zhaquirks update got this working
however my blinds are not being discovered atm :/
Any should do, they don't draw much power
in the zhaquirk update process, which actual files should I be replacing?
in the guide it says - cp -a /config/temp/NEW_QUIRK ./
I assumed NEW_QUIRK referenced JUST the folder I needed the quirk for which in my case is the Tuya folder - that right?
What are you trying to do?
I have a light switch which doesnt show any entities
I found I needed to update the quirks, which previously got it working, but only 1 of the 2 gangs on the switch
Are you running the latest release of Home Assistant?
I then saw another update had occured, so went through same process, but this time it killed both of my zigbee devices
yes
What is the zigbee device signature for your broken device?
@mild lynx posted a code wall, it is moved here --> https://paste.ubuntu.com/p/47mGyZ3bWk/
There is no quirk for it so updating quirks won't help
TS0601 ?
it's the manufacturer code not matching _TZE200_g1ib5ldv
oh, I am guessing this may be an OEM manufacturer code, on the same model TS0601 then? If that is the case is there a way to get them to match to the Tuya folder for the quirk or have I missed something?
it's tuya where there are every one gets there own code or 2 or 3
looks like the cluster match, so you'd need it added in here: https://github.com/zigpy/zha-device-handlers/blob/833c1b913105c87fe93b8dfd20902d27ec4004f8/zhaquirks/tuya/ts0601.py#L176
it still might be inverted or need some other manipulations, I have a version of these an have sort of given up for a bit while the dust settled around the quirk
Ah, I see - in the Models_Info section?
yes just as the others are listed.
๐คฃ ๐คฆโโ๏ธ yet another model was just reported in the issue tracking these in the quriks repo
any update on getting both of the lights working on this switch - 1 switch with 2 light circuits?
opps I linked you to the blinds section of the TS0601, you'll want to to be up toward the top in the switch area I think.
What device is this?
yes, I found the correct section
tuya is a royal pita
yes, I am regretting getting this device
I also got one of these, but this worked first time - https://www.aliexpress.com/item/1005001698400295.html?spm=a2g0s.9042311.0.0.60ee4c4dAj6n2V
It's probably the one with the quirk already written
yes, it is - ("_TZE200_zah67ekd", "TS0601"),
I have a moes one too and its _TZE200_rddyvrci ๐คทโโ๏ธ like I said tuya ๐
it was working really nicely tbh and thanks to your help. I have that back working now
light switch however, still not
cool. my blinds aren't compatible as is, so need to do some surgery that I've been putting off.
Unfortunately, adding support for Tuya devices isn't as simple as fixing small glitches with most other devices. They have a proprietary protocol on top of Zigbee.
like you mean they just stuck a zigbee controller there existing products swapping out the esp?
I can discover the wall light, but there are no entities :/
Does clicking buttons generate any commands in your ZHA log?
You'll likely need to enable debug logging to see them
I'm struggling to start zigbee2mqtt with my CC2652R stick. The device is flashed and referred to in the config by serial-id.
https://paste.ubuntu.com/p/pC5ntRkTQM/
Any suggestions on what could be wrong?
I flashed it using this guide: https://electrolama.com/radio-docs/flash-cc-bsl/
Are there any other logs?
That is all the logs from zigbee2mqtt
Those are from the container, not Z2M itself. Check the logs/ folder for Z2M
checking
Ok, i'm actually able to access the frontend now. However I'm not able to pair my IKEA Trรฅdfri Adapter. As soon as i push/release the reset button, i get a red box telling me that it left(!) the network.
@austere patio you mentioned a SI Lockup Bug at one point
Do you have a link for this?
I had three of my IKEA Tradfris fall off the network inexplicably.
Another thing I just ran into (which is going to set me back another 6 hours to the client site) is restarting the Z2M instance with a dated database.db, coordinator_backup and the rest of the app/data/ file for Z2M
Although all the connections are there and present, devices and routers lose touch with the coordinator if the coordinator does not have the most up to data /app/dat
I wonder if itโs the mesh architecture that has changed via self-healing and the dated coordinator records donโt have this information since Iโve been running it on a stale database.db + coordinator_backup
If it's the same bug, you should be able to "fix" them by just power cycling them (turn them off for about 5 seconds)
Can I avoid this bug entirely via OTA update?
I don't believe Z2M applies the coordinator backup unless the network settings on the stick differ from what it expects, which will not be the case if you just go back in time a little
Sure, if IKEA releases firmwares based on the newer SiLabs SDK
They haven't so far
I was going 1 month back... fucked up by pushing stale backups from GitLab to avoid having a mounted volume on my gateway (I donโt want I/O on my gateway)
Okay. So now Iโm unsure if itโs that SI lockup bug or me just fucking up my backups.
The lockup bug would bring down every device joined through the bulbs
I also have many downed devices
So if you have a dense mesh and a few offline bulbs, it's probably not it
But if you have sensors offline that were previously joined through those bulbs, it's probably the bug
Since they won't find a new parent as long as their current parent is "online", though locked up and not routing messages
Was there a recent power outage or some other event that caused devices to re-join the network?
The bug is apparently triggered in part by a lot of devices joining the network
Ehhhh that wouldnโt be the case for me. I have all Aqara battery powered devices that report intermittently.
Iโm starting to think itโs my stale /app/data/ configs that Iโm loading.
The only data I think that would be cached are the short NWK addresses, which on occasion can change if a device re-joins the network with the coordinator offline
I need to learn more about what exactly coordinator_backup and database.do
I was treating them as โas long as they have the device paired with them at one time, theyโre goodโ. I only pushed new configs when I added new devices... and I havenโt added new devices so I thought the month old configs were fine.
But that would only "break" certain devices. Z2M should be logging if it receives a packet from an unknown (to it) device
The coordinator backup stores low-level network information specific to the coordinator hardware in a non-human-readable format
It lets you "copy" one coordinator to another
That data isn't used by Z2M until it sees that the coordinator does not have the same settings as what are in its configuration file
I went from this: https://ibb.co/M6hgvPg
To this: https://ibb.co/LZVBJn5
So many device fell off. I am unable to ping 5 of the routers for LQI now.
They still show as siblings, but all of those devices have fallen off -- https://ibb.co/d2JFyqZ
Okay. I finally made the decision to switch from Conbee/ZHA to CC2531/Z2M. I kept getting devices that don't respond anymore and delays that are beyond normal. So I'm going a different path, hoping it'll improve ๐
now go back and rethink that decision again
The CC2531 and CC2530 sticks are cheap for a reason. They're fine for testing, but do yourself a favour and buy something better.
You chose the shittiest stick on the planet
For Z2M use a CC2652 stick (see the pinned messages)
Well, shit.
On the bright side, they make ok routers
On the router side I should be fine, as half of my Zigbee devices are bulbs, dimmer switches or LED controllers. I've been so frustrated with all these devices not responding that I didn't really look past the overflow of CC2531 posts and just ordered one so I can just get away from this hellhole that the Raspbee/Conbee put me in.
The worst part is that the devices don't even fall of the network. They just stop responding. Randomly too. Not that it's a specific brand or bulb that stops responding.
I have bulbs from iCasa. GU10 bulbs from Owyean. LED controllers from Lonsonho and Gledopto. Dimmers switches from Lonsonho. Wall switches from Aqara.
And by random, shit just stops responding. Whether the lights tells me to go f*** myself or the switches be like, "well, press me 5 times and I might do what you want me to".
Maybe I'm completely off topic but i'm trying to make my irrigation system smart. Have a couple solutions and 1 of these solutions(cheap and simple) is buying the WOOX R7060. I have a Philips Hue bridge but can't find if they are compatible. Asked the same question in the forum but no reply yet. Does anybody know if its possible?
The good news is that when the CC2531 fails, Z2M should have auto-migration to the CC2652 stick without having you re-join devices
I also have this problem. Convinced something changed in the ZHA code that negatively affects ikea devices because thereโs reports they are still working fine on DeconZ and z2mqtt. There was a pull request fix in HA 2021.4 but it does not appear to fix the issue. My devices drain within 48 hours of inserting a fresh battery
Jep, same issue here.. Thinking about switching to z2mqtt this weekend, my wife is not happy with switches that stop working after a few days :)
Actually, same thing affects z2m with EZSP adapter, I believe ๐คฆโโ๏ธ
Believe part of the root cause is at the NCP firmware level
Does anyone remember some buttons/switches that were IP44 rated? Maybe IKEA?
I didnโt have problems for 6 months when I first got the ikea switches- so not sure how it could be the adapter. (I am running EZSP- Huzbz-1)
You can also update the firmware https://github.com/walthowd/husbzb-firmware I see EZSP is experimental in z2m - anyone have experience with that combo
I have ZHA with C2652 and the Ikea switches aren't misbehaving on my side. So it sounds like an adapter issue
I don't think there are IKEA switches that are IP44 rated. I know the motion sensor is
This guy is, just found it -- had to dig into the more details section to find the IP44 - https://www.ikea.com/us/en/p/tradfri-wireless-dimmer-white-10408598/
Oh, TIL! Interesting
I haven't been following the issue @last thicket as there has been a lot of noise, but I'd try upgrading to 6.7.8 and then you have to kick the devices out of 'short poll` mode
either rejoin, or reconfigure them via the ZHA device page (while pressing a button the remote to wake it)
there may be more to it, but it should be documented in the current open issues
Thanks, Iโll give it a try. Otherwise might just bit the bullet and upgrade my coordinator
You can seamlessly migrate to a CC2652 coordinator
I can recommend the zzh! Stick ๐๏ธ
I did the same from HUSBZB-1 to ELU013 to CC1352 to ZZH to Tube's Gateway -- just for funsies -- all on the same network, never rejoining
Nice, was thinking of getting Tubeโs. Just didnโt have a reason because everything else works great
Yeah I unpaired every battery change. Now Iโm paranoid I just got a bad batch of batteries ๐. Donโt think so because battery level still goes from 100 to 0
@gentle flint said this is fixed in latest beta if you leave and rejoin the device. #zigbee-archived message
you can try it
not much more i can say
Does anybody with one of the Tuya gateways know if they're cross-compatible across "brands"? Or are the hubs hard-coded to only work with Tuya devices by that one "brand"?
I don't have one (and I'm not 100 % sure) but I think they work across brands
For one, some gateways (like the LIDL gateway) have their own app but you can also use the Tuya SmartLife app
and pairing different devices should also work then (might even work in the normal LIDL SmartHome app, as it's essentially just a re-skin)
Tuya must have a database of their garbage manufacturer and model names that maps to some sort of Tuya capabilities
i'm also trying to find the ZHA-quirks folder under site-packages and its not there - unlike the documentation said.. really at a loss..
Hi all, i am new to zigbee, today i received my usb stick (CC2531), i want to user the ikea tradfri lamps and buttons, do i still need the ikea hub or is the CC2531 the replacement hub and do i connect devices to it instead?
It's there. Are you in the HA docker container?
Nope, the CC2531 is the new "hub"
yah i used portainer like the documentation said.. but no such folder path under the HA container.. i also look for the path elsewhere and the closest i found was under hassio_supervisor container.. but no ZHA-quirks... dont know what i am MISSING
It's definitely in there, since the HA container has all the Python packages. What's the name of the container's image?
There are like 10 containers to choose from so you could be in the wrong one
homeassistant/raspberrypi4-64-homeassistant:2021.4.6
That looks right
And /usr/local/lib/python3.8/site-packages/zhaquirks/ doesn't exist?
yah but there's no /usr/local/lib/python3.8/site-packages/zhaquirks/
Does /usr/local/lib/python3.8/site-packages/ exist?
i open the console and search ard.. the /usr/local/lib/python3.8/site-packages i found it at hassio_supervisor container..
but there's no ZHA-quirks folder
Does a /config/ folder exist in the container?
in the console i cant see it but on the samba share its there
I think you're still in the wrong container. The main Home Assistant container has a /config/ folder



