#zigbee-archived
1 messages ยท Page 145 of 1
https://github.com/Koenkk/zigbee2mqtt/releases is how you can tell what version "current" is
wow, missed that I guess... that is what happens when stuff "just works" I guess ๐ Thanks, I had a feeling I was looking at two different codebases or something. โค๏ธ now to figure out if I can just swap over or if I have to repair 47 devices!
The first link covers all you need
If you follow it step by step it'll migrate cleanly
Can also confirm the plug support was added in 1.19 so that checks out too, thanks!
1.19 brought some known issues if you use a TI coordinator, but if you have one of those the log file will tell you what the problem is and how to fix it
I have a usb-Silicon_Labs_slae.sh_cc2652rb_stick that is a TI chip iirc, but Ill have a go at it and see if and where I get stuck. I see its related to pan id, and Im running a custom one from last time I swapped the stick. ๐ค
It is, but not in the way you think ๐
well that was a 7 step butterly smooth fix, even the joined device that started it all just happely came along working with a smile.
Oh no! It's the same one I use. Seems fine so far...
Hi, if I'm discovering zigbee2mqtt devices via zigbee2mqtt topic, should I set
homeassistant: false?
As described in the docs (https://www.zigbee2mqtt.io/information/configuration.html), that's the default. You can omit it.
Actually, I think I have it backwards... you want to set homeassistant: true if you want the autodiscovery to kick in.
It's not bad, just not the best coordinator you can buy for $50 these days
hello , i have problem with my zigbee2mqtt network. A day ago my CC2531 lost connection with all my devices. I did restart my HASS, hole server, remove dongle form USB port and putting back and still not connect. Can you advise me , how to proceed
The pin from hellcry to scan for best zigbee channel - run it exactly like that with haos installation?
@honest salmon pull the power of one device and start it back up after 10sec. If that doesnโt work, you might have to re-pair everything, but start with 1 device . (I suppose thereโs nothing else connection to the usb ports?)
I have recently rebuilt my home assistant that was installed on Ubuntu on an Intel nuc. it is now running on the official intel nuc build. I restored my intance from my snapshot backup. Unfortunatley though my deconz instance will no longer discover my zigbee lights. I have a conbee 2 .
re-paring did solve the problem. But i'm not happy with that
@honest salmon don't got any other solution for that, if just a 'reboot' of the sensor/device didn't work out. Maybe someone that has the same hardware might know a trick though
but I doubt it
@burnt niche are other devices working ?
I discovered that with a conbee2 stick, I just have to restart the lightbulbs if I copy configs over
but I'm not running the intel nuc build (still docker)
I only have zigbee lights so far. I tried putting the bulbs into discovery mode again but they still havent been rediscovered. I have a philips hue bulb (free with first echo device) and 4 Ajax spotlight bulbs
for my hue bulb i just disconnected it, and put it back in
and they came back alive
I must say that I run my zigbee instance with join always on
but I heard people saying deconz is doing weird things sometimes (I only use it to upgrade my stick(s))
is there nothing to see in the logs what might be wrong ?
Nothing in the log is jumping out as an error
what you can do (what I would do) is remove one bulb and try to add it back again
i think there might be an issue with the db of the devices
or the stick now has another channel or network id
but your backup normally should've made that the same as before
but https://community.home-assistant.io/t/restored-hass-io-from-snapshot-all-devices-disappeared-from-phoscon/145318 seems like the same issue you have
I am using conbee with aqara sensors. I moved to new hardware and now my automations donโt work. How can I confirm that there is connection between the conbee stick and aqara door sensors?
see if the device is present
Have you updated the firmware? Original firmware kicks out end devices every 24 hours. Add xiaomi compatible routers or update firmware
I am hoping I am in the right place for my question. I wanted to know, are all zigbee devices compatible with home assistant zha? I am looking for a smart bulb that is compatible on Amazon.
There are lists of known-supported devices in the topic and pins.
If something's not on the list, there's a chance (but no guarantee) that it could be supported.
@dry fossil I on the pins but donโt see a list for zha
There is no official list for ZHA, because of the reason explained in one of the pins
There is an unofficial list in the pins
@sour shadow so if a I buy a zigbee bulb on Amazon itโs 50/50 hit or miss it will work with home assistant zha?
Well, no
If you check the unofficial hardware list and it's listed as supported, you should be fine
If you don't check, or it's not listed, then it really depends on how standards compliant that random bulb is
If it's fully standards compliant, it should work
If it's not... who knows
You have to disable the ZHA integration first. Also, the leave/form will delete your network and form a new one, so if you have many a lot of devices, I'd do a network backup instead and edit the channel in there before restoring.
If something pairs, can you always โmake it workโ?
I just got my first unsupported device ๐
Yes
Sounds like a dumb question, likely isโฆ I get non-standard quirky stuff, just wandering is an initial pair is enough for quirks
Great! Thanks
If you're using Z2M, then it considers any device that isn't explicitly supported as "unsupported". In that case, "supporting" the device usually involves just adding its manufacturer and model name to the appropriate handler.
Yeah, mine pairs but itโs the first time Iโve had an unsupported device. Itโs from a manufacturer thatโs already on the supported list just a totally different type (struggling to see similar too) - wish me luck!
Probably Tuya...
Na
Well donโt think so hehe, none of the other devices are - itโs a salus โclamp meterโ - ecm600
Ah. That might be simpler then.
Iโm a bit of a noob but can hopefully figure it out and stick in a pr
Was nice and cheap (from eBay, an ecosystem thatโs reasonably expensive that I bet no one uses) and seems like a nice way of monitoring whole house energy use
hey, has anyone seen any door sensors that update periodically?
so far I've tried Aqara, Tuya and some no-name 433MHz ones, but all seem to only send a message on contact -- if you miss that, you're stuck with the old status
You shouldn't be missing messages
Can't say I've experienced missing messages with Zigbee
I see it very occasionally on my Z-Wave mesh, but it's damned rare there
are devices buffering/retrying them if the gw is down?
I don't believe for more than a few seconds. Yeah, why would your coordinator be going down?
eh I keep messing with zigbee2mqtt on a pi zero, I just did an upgrade and it took like 30 minutes
it would be nice to know the status of my doors after it comes back up
You may have better luck running ser2net on the pi zero and Z2M on a more capable computer, though if you're doing that over WiFi you may run into more problems.
a PIR will make lots of noise and still last a long time on battery, so DS updates every ~10 minutes would be awesome
interesting, I could try that
Docker makes life so much easier at upgrade time
I was considering moving the dongle to my main HA machine, but it's down in the basement so I'd have to get a couple of plugs to reliably mesh it there
yeah, tell me about it, I can't get z2m to start on docker on the zero
not sure why
Probably Zero related
https://www.tubeszb.com/shop/coordinators/2 should be back in stock this week
I've been running it directly in tmux for a long time now, it just works
but like I said, the npm install is painful
will a coordinator like that bridge directly to mqtt?
or do I still need z2m on another machine?
No, you still need Z2M
If you wanted to you could use a Tasmota Zigbee gateway, but those things are damn limited
Tube's ethernet coordinator is like ser2net + a dongle in a box. Z2M can connect to it just the same as it does to a dongle over USB serial.
yeah I have a module that should work with an esp8266, might be able to run tasmota on it
iirc the range isn't that great though
I'm totally trying to move the zero to ser2net
but back to my original question, any DS that will update periodically?
any idea whether you can get any of them to send updates?
They update when there's something to report, so no.
๐
You might be able to set up attribute reporting for the on/off attribute, but I'm not sure if that's something anybody ever implements
that's not great
Making sure your coordinator doesn't go offline is a better solution. I know Aqara sensors will send their state every hour or so.
I have some cheap 433MHz door sensors that only update on closing the contact, as far as I can tell
damn useless
Sensors that periodically report their state is likely to be viewed as a waste of time and battery life
If you really want that, it's doing to be #diy-archived time
well the PIR can make tons of noise and still last a long time, so the DS should be able to ping every now and then
Simply moving off a Zero is likely to be an easier solution
Tuya and Aqara are the two brands that don't really follow the spec at all so the Aqara definitely don't support attribute reporting config, Tuya probably doesn't as well. I'll have to double check with spec-compliant sensor.
Hue, maybe, then ๐
yeah, I started off with Aqara, just installed a few Tuyas today
they're huge and the included magnets are useless
Tuya seem to be worse than Xiaomi for following standards
I really love Aqara sensors, small and great looking
apparently the door sensors also give you temperature? just saw that today
A useless one ๐
The Terncy door/window sensors are even smaller and better looking FYI - though mine refuse to pair 
It's the temperature of the microcontroller. Only useful if you want to know if it's hot or not. I think they're accurate to within 10-20 degrees of the ambient temperature.
Yeah, that seems about right, based on what I see
ah good for fire detection then
They read "high" by a pointless amount
btw, any good zigbee smoke alarms?
I only found a few 433MHz ones, not that many options
zigbee would be particularly well suited for that, could bind them to a siren or something
I wouldn't trust a Zigbee smoke alarm very much, especially when it's interacting with a Pi Zero ๐
the zigbee part is a bonus, I still want it to make noise
I'd think 433 actually makes more sense for an alarm.
Personally I'd buy a quality smoke alarm with an interconnect wire, and tap that
Or that
So many of the smart smoke alarms are only good for decoration
Actual tests of a lot of them have found that they don't work
hmm btw, I don't know that much about zigbee, can you have a backup coordinator receiving messages if the main one goes down?
obviously with 433MHz that's not a problem
Nah, single coordinator.
Wired > 433 > Zigbee
At least with 433, you're just listening for a broadcast.
hmm
Wired > anything wireless
yeah but with zigbee you get mesh
At least with Zigbee you get bi-directional comms, so you know if something is alive ๐
Mesh doesn't matter if the coordinator is down.
I don't know how you deal with 433MHz range
yeah, I mean it's not clearly 433MHz > zigbee
Only a problem if you run on a Pi Zero apparently ๐
433 range is better than Zigbee range, no? I can tell when my neighbours' doorbells halfway down the street ring.
Now if only you could send a fake doorbell signal...
also batteries for 433MHz are weird and expensive
I'm recording all the codes for that very reason ๐ Just need to map them to houses so I know who I'm annoying.
hmm I tried a few 433MHz devices and now I've been getting more zigbees
I wonder whether I should go back on that for things like intrusion
Looks like their codes don't rotate ๐
Redundant listeners, or just not a broken Zigbee coordinator...
how do you dedupe them in mqtt?
I was indeed thinking that a zigbee intruder alarm based on this zero wouldn't be that secure ๐
are there any go to alarm systems to run independently and just interface to HA?
or would you have to listen in to the sensors separately?
Hey guys, anyone have experienced this with sonoff R3 zigbee?
um i cant post images, alright, just a sec
I have the device up, i can see when state changes but i cannot toggle using home assistant
Mine also fails to configure attribute reporting but I can control it fine
What does ZHA debug logging (https://www.home-assistant.io/integrations/zha/#debug-logging) say when you try sending a request?
Has anyone was able to change auto-off timer of watering computer Lidl PSBZS A1 using ZHA?
let me check and paste here
Isnt zwave better than zigbee again since the interconnection group keeps if the power goes out
If you want to pay three times as much per device, sure.
For sure! Hard at work today.
sotty it toke me too much
Now its working SOMETIMES (i didnt do anything)
not to get totaly off topic with 433mhz talk, but I found it hillarious that I pick up my neighbours tire pressure reports so I can tell if his car is home or not... ๐ (rtl_433 is fun)
Neighbours are away, time to pillage
I have a few spare SDRs, I should explore that at some point
TXStatus.MAC_CHANNEL_ACCESS_FAILURE means that you are experiencing so much interference that the Conbee is refusing to transmit
Plug your Conbee into a USB 2.0 port through a USB extension cable and make sure it's away from all potential sources of interference, like active USB 3.0 ports
get them while they are hot ๐ฅ ๐
Um nice? jajaja just worked! Thank you very much!!
I'm having trouble setting up an automation between a TRADFRI on/off remote and a Tradfri power outlet. I'm concerned the switch has stopped sending any single. I'm using ZHA. How can I troubleshoot whether the remotes sending anything?
I'm also wondering if my issue is because the outlet i'm trying to control is directly above my garage door opener, so maybe there is interference. Because when I try to manipulate the power outlet switch in HA it's really hit and miss for response
Sounds like it's not well connected to the mesh
I'm gonna restart the server
So in the network visulzzation there's no line at all showing a connection to the on/off switch
I am looking to migrate to ZHA for my new house. Does HA also recommend a certain chip for Zigbee? (e.g. z2mqtt recommends CC2652R here -> https://www.zigbee2mqtt.io/information/supported_adapters.html).
Or would the same list apply to ZHA as well ๐
ZHA supports all of those. The EZSP ones are also completely stable in ZHA.
Thanks! I saw them listed in the documentation indeed, but was just wondering what ZHA users see as the best of the best right now ;-).
The CC2652/CC1352 are fine, as are the newer EZSP coordinators
But maybe I should just have a look at ones that are recommended by Z2MTT, since that should be more than enough for my usecase ๐
And since I am here right now, I saw on blakadder quite a difference between ZHA and Z2MQTT in terms of device support.
Could I buy unsupported ones in ZHA and write the quirks myself?
Tube also just made a few more ethernet CC2652P2 coordinators: https://www.tubeszb.com/product/cc2652_coordinator/1
Or is this something where the core is just too different, thus ZHA will only work with more compliant devices
All of the existing quirks are here: https://github.com/zigpy/zha-device-handlers/
You can write your own by just adding a new one to the module. Or having extra quirks out-of-tree by dropping the modules into a path you specify: https://www.home-assistant.io/integrations/zha/#custom_quirks_path
But is it possible to port quirks from zigbee2mqtt (with some efforts + coding knowledge), or are the coordinators/stack too different?
Otherwise I am happy to order some newer device (like https://nl.aliexpress.com/item/1005002975309479.html), that are currently unsupported.
And add them to the device handlers.
Z2M just exposes functionality. ZHA tries to make non-compliant devices appear compliant with quirks so they take a little more effort to write.
Thanks @austere patio, good to get some background. And happy to contribute back eventually ๐
Tuya stuff is a bit tricker because Tuya decided to implement a lot of functionality with a proprietary protocol on top of Zigbee. They take a little more work to support (assuming your device isn't just a renamed version of an existing one, in which case it should be quite easy).
The Z2M docs have a section outlining how their super special protocol works but you can see the existing devices in that same repo (the low-level Tuya protocol stuff is in tuya/__init__.py)
Maybe I will just order one to tinker with, they look smaller than others ๐
You can also buy the cheaper sensortag from ti - LPSTK CC1352R However, flashing this would require a dev cc1352 or cc2652 board (which has xds110 chip) or a debugger
The irony is that the official xds110 debug probe costs double the cc1352p-2 dev kit. ๐ค
Anyone using the recently added alarm functionality in ZHA ?
Have somebody the "ROBB Smarrt Draadloze Schakelaar Wit 8knops Zigbee" working with ZHA? Or with a custom quirk
is it possible to backup ZHA integration connected to a sonoff bridge running Tasmota, using socket://xxx.xxx.xxx.xxx:8888?
or is it stick to stick only using zigpy_znp
i've been trying to backup a sonoff bridge using zigpy_znp but it trows an error
Please don't say I have an error or describe an error. Share the whole actual error message so we can help you.
You need to use bellows
And can I then migrate those entities to a cc2652p2 stick?
Any website with a tutorial/example somewhere?๐
Hi everyone! I'm interested in zigbee integration with HA. I have some zigbee devices and would like to get them into the HA. I already have ordered RaspBee 2 (as my HA is installed on raspberry pi 4), but unfortunately it just doesn't fit into my case. I'm kinda looking now for the new gateway/stick to get everything working. What can you advice? Lately I have seen lot's about ConBee II & Sonoff ZigBee bridge. What is your experience? Can you advice something with good range and easy to setup? ๐
Neither of those
CC2652 based stick, and either Zigbee2MQTT or ZHA
Range is all about the mesh - see the pinned messages
okay thank you for the advice - I have heard about the mesh. So I will try to research about cc2652, I already have seen lots of guides with them ๐
https://www.zigbee2mqtt.io/information/supported_adapters.html is a good shopping list, and if you're in North America then Tube has stock today (and likely not tomorrow)
Hi, anyone els here that have a problem with Deconz not connecting to your network anymore when using Raspbee II?
Or maybe thats a question for Dresden?
I'd ask on their Discord
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.
Thanks!
I'm not from NA and it looks like here in EU it's pretty hard to order cc2652 stick ๐ฆ
DHL shipping is still slow for some customers. Please do not expect your order to arrive before Christmas. Most are taking a few weeks, but some have taken 3-4 months.
Christmas is like overkill ))) Will try to search somewhere else
Oh, that's Slaesh
Yeah, don't buy from them ๐
There's various EU sources, but shipping from Tube to the EU is pretty quick
okay I'll take a look at what they are offering
everything out of stock already ๐
I think he's making more very soon.
reversed not today, but likely tomorrow. ๐คฃ
just going to ask a stupid question, is there a way to let a lightbulb send a last_seen for atleast once every 24h (without having to trigger them)
I guess not, but you never know, there's some magic trick to it
@vital ermine
I'm using Zigbee2MQTT and it works quite well, but I have an "Aqara vibration sensor" I originally got to try to determine dryer status, it seems to only fire when I drop it 1+in to my desk, then only 10s too. I set the sensitivity to high as per https://www.zigbee2mqtt.io/devices/DJT11LM.html but still nothing. Am I missing something, or is this sensor just not that sensitive?
anyone know of a zigbee soil moisture sensor? i tried googling it by could not find anything. cannot believe those do not exist ๐ฎ
I've asked (and searched for) this before. Found none. Big opportunity for a manufacturer right there.
i would buy a bunch if they were at the aqara price
Hi all, I'm having trouble with Enbrighten Zigbee Smart Light Switch (model 43076). I can pair it to Home Assistant ZHA, but the device is not responding to any commands? How can I debug the issue. I'm pretty new to HA
Plaid soil sensor
Which are more reliable? IKEA tradfri or sonoff zigbee? For use with a coordinator
As entire brands, I'd go with Ikea over Sonoff, but it really depends on what question you're actually asking
Iโm specifically interested in presence and window sensors
Then I'd recommend Xiaomi Aqara
Are they less prone to disconnections and pairing issues? What makes you recommend them?
- Size/looks
- Zero issues with them
Nice, Iโll see if I can find a reliable place to buy them. Thanks for the help
AliExpress
Sadly their shipping method takes several months with the current condition of our postal service here
Maybe I can get ship it with fedex
They're likely available through other places, but the great thing about Ali is that you pay a lot less ๐
@hoary crest I use a miflora and a pi 0 ๐
Seen the miflora too. Would be perfect if they were zigbee ootb without the pi 0 overhead.
That looks perfect. Will check them out closer when at home. Thank you!
that's true @hoary crest but imagine having multiple of them and connecting them through the same pi 0
now I only need more plants ๐
I'm having issues with my ConBee II after updating to core-2021.7.3. I had the same problem with core-2021.7.2 and just rolled back (hoping 7.3 would correct). After the update, when I go to Integrations, I see this error under the ConBee II:
Retrying setup: [Errno 2] could not open port /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2437121-if00: [Errno 2] No such file or directory:
When this happened on 7.2, I restarted the VM, rebooted the physical box, unplugged and replugged the USB sticl. Nothing seemed to fix it. Any thoughts? I'm running a Hassio VM on an UNRaid box.
Is the serial device actually still available in the vm?
maybe under a changed name/id?
It does appear to be when I look at the VM settings in Unraid. Do you know off the top of your head where to look for the available devices (with paths) in HA?
Under Supervisor ---> System ---> Host ---> three dots at the bottom right of the Host part
Click on hardware there
Thanks feyo! I have two different sticks for ZWave and Zigbee. I can see the ZWave stick path listed under ttyACM0. I don't see the Zigbee. I think your theory is correct but I'm not sure why it wouldn't be available after this update. Bug in the new version of Core?
Won't be Core - that's entirely Supervisor land at that point
I dont really have enough insight into the underpinnings to consider how likely that is. Personally Id first look into my own configs and recheck everything there. Have you completely removed the usb passthrough in unraid, shutdown the vm, rebooted, then shutdown again and attached the device again? Sometimes passthrough is a bit finicky.
If the Supervisor menu doesn't show the device, then the underlying HAOS doesn't know about it either
I think he meant if there might be a bug in how core <->hypervisor usb passthrough works.
Nah
But, Id doubt it, personally.
The Supervisor menu doesn't involve Core at all
Sorry, I used the wrong word anyway. I meant the hypervisor ๐
Yeah, a problem between the VM and HAOS ... that seems more likely
Appreciate you both. I had tried reboots, etc. last time but I did not remove the passthrough on the VM. I will try that and see what happens.
Id shut the vm down completely. I know from experience with KVM that reboots sometimes dont fix passthrough issues as the passthrough settings sometimes dont get updated.
The VM sometimes needs to be shutdown completely for a second or two. At least in Proxmox.
Which is KVM.
also check if the vm still has privilege access to the host
That did it! Removing the pass-through, shutting down the VM, adding pass-through back and restarting the VM did it. Thanks again!!!
I am finally in the process of closing on my first home and have home assistant set up in my apartment, however now that I will own my own place I want to expand on it. I am looking for a smart lock that connects well to HA.
Does anyone have any recommendations? My googling hasn't come up with much
Did you look at the ones on the blakadder list? https://zigbee.blakadder.com/locks.html
I have not seen this site before, I have no idea how this never came up in any of my searches...
I will take a look through. Thanks!

Hi all, anyone know how to remove ZHA from my sonoff zbbridge so I can try z2mqtt?
You don't have to remove it from the bridge, just remove ZHA from HA
oh awesome, thanks
I've been planning doing it for a little while but all of a sudden all my lights have stopped responding to on/off, so my hand has been forced!
Yeah. Need to try to fix it before darkness comes and we're peeing without light
So I've enabled join on Zigbee2MQTT and put all my lights into pairing mode, nothing is being logged in the Z2M logs apart from the log to say it's allowing to join
Do I have to change any settings in tasmota or anything?
Hey there,
does anyone know if it is possible to set the consumption state of a simple metering device with deconz? The ui shows the consumption state as read only. I want to synchronize the zigbee sensor with my electricity meter (initial value)
My issue was solved by unplugging and replugging my Sonoff bridge
Is there a cheap development board for zigbee like esp8266 is for WiFi?
might be a bit late to this already, but the changelog for the latest (development) Z-Stack firmware mentions Fix joining not working when joining is only permitted on specific router
https://github.com/Koenkk/Z-Stack-firmware/blob/develop/coordinator/Z-Stack_3.x.0/CHANGELOG.md#20210708
wasn't this issue worked around with in zigpy_znp by also allowing joins on the coordinator?
Yeah, but the Z-Stack fix allows the join to happen without the coordinator broadcasting that it will allow the new device to join through it
Otherwise even if you permit joins through a specific router, the device can still join through the coordinator
oh, I see
Depends on what you call cheap ;-) CC1235P / CC2562 dev kits are the best and cost used 49. You can directly purchase from TI site. There are cheap cc2530 boards, but these chips are based on 8051 and the only feasible IDE is by IAR (Afaik) and they are pretty expensive (talking in '000 here)
However if you want to build the client components mostly, nordic nrf52840 or nrf5340 dev kits are also good. Those chips don't have coordinator support yet in z2m
Wow itโs crazy how you can buy a zigbee ready device for a fraction of the price of a development board. I hope this changes in the future so I can have the freedom I have with the ESP family. Would be so cool to have something like tasmota or esphome with the capabilities of zigbee
Unlikely to change this approach, the dev kits were relatively very expensive and remain so. The only good part is the software has now become cheap /free. The cheapest dev usb dongle you can buy is nrf52840 dongle, it just usd 10 I think. But you need to be careful with that dongle, if you accidentally erase the entire flash (including the bootloader) you would need a devkit or debugger to reinstall it before you flash any images on them
Hi all, anyone else had issues with zigbee2mqtt where it consistently fails to interview devices?
Could be interference
Is the stick directly connected or with a usb cable? Are there other usb devices connected? And last but not least, is joining allowed on the stick ?
Anyone know of a Zigbee smart plug or switch that can handle anything above 2300W? Both my Aqara Smart plug and Aqara Single Switch Module T1 stops at 2300w which is not enough for the AC to startup (It uses 1000w after starting only) But uses a bit more on start.
there's plenty of 16A plugs
Great thanks found one called "Apex Smart Plug" 16A up to 3860W so shuold be good, thanks!
The Sengled bulbs required a specific Zigbee channel right?
Please help. Where to start searching?
Sonoff ZB bridge tasmotized worked fine until this morning. On console I can see: https://paste.ubuntu.com/p/jddV4jbWSw/
I cannot add any zigbee device. The whole system is down.
On Tasmota forum I got advice to look for help on ZHA channel. #integrations-archived?
this is the "zha channel"
you need to check HA logs to see if there are any zha errors
I am using some aqara sensors and ZHA. I also have two home depot ecosmart lights. When I look at the ZHA visualization I can see that two of the aqara sensors are connecting through one of the lights. As a result they have the lowest strength of all my sensors. Is there a way to make them connect directly to the conbee 2? I have other sensors in the same general vicinity that are not using the lightbulb as a parent.
unpair them and re-pair them close to the conbee stick, but normally they should take the best path (somehow)
I used to bother me at it, but I gave up ๐
if it works stable, it's good
according to the zigbee map i have, there's a sensor which is just floating and not connected, but is reporting just fine ๐
Re-join them to your network but instead of clicking the "add devices" button, go to the Conbee device page and click "add devices through this device" (or whatever it's called)
Thanks!
Mostly though, if they work, don't worry about it
Would it also work to unscrew the light bulb (to physically remove power) then try re-pairing the sensor? I repaired through "add devices through this device" on the conbee II and the topology map is still showing the direct connection to the light? Would I need to restart HA?
I'd expect any mains powered device, like a bulb, to automatically re-route as it sees fit
seems reasonable
I don't believe the topology map is updated with new info at runtime, it has to re-scan every few hours
Hopefully it worked. The light bulb is an awful router. The two sensors that connect to it are the 2 that I have the most issues with not capturing motion.
It works 98% of the time and the others work 100%. It's probably just me being anal about it
But unscrewing that bulb and re-joining the sensor will definitely make sure it doesn't pick that bulb as a parent ๐
Until the bulb is back in the mesh ๐
I don't think any unmodded Aqara sensors switch parents, do they? I specifically tested my temp and door sensors, they just sat there and waited for the parent to come back online.
It's rare, but I've had some of mine do it - but only on my Zigbee 3.0 mesh and they've only switched between Zigbee 3.0 parents
Ikea bulbs + Ikea on off switch - I have a problem to unbind one of two controlers directly binded with the bulb. Either both are paired or no one. After few secs of unpairing one and pairing only back to Zigbee2mqtt not to bulb the same will return to the paired state. Any solutions or do you have the same situation?
Did the bulbs update
Nothing changed
Anyone know if it's possible to change the color_mode of a light in z2m? Some of my Tradfri bulbs are reporting xy but that's a lie, they're color_temp
Not as such, no. You'd have to modify the Herdsman converter for it
Oh! I've just realised that they're defaulting to xy. Just turned one of them on, changed the color_temp and now they're reporting correctly
I am fairly frequently getting timeouts though
Timeouts would suggest either:
- The connection to the mesh is poor
- You're overloading the mesh with too many commands (eg trying to turn on multiple lights at the same time)
I definitely was overloading the mesh with a badly set up blueprint, but that's fixed. I can't imagine why the connection to the mesh is poor, it's all lights having issues and there's loads of lights with a good connection
I had three lights I was turning on/off together, and at random one wouldn't. I moved to using a Zigbee group and the problem vanished
Yeah, I've created groups for all the associated ones
Interestingly it did seem to be the ones with the wrong color_mode. Maybe they just weren't fully fully paired properly
Huh. It seems to go awry when I try to set the power_on_behaviour on some lights
hmm anyone had this before?
SP-EUC01 aqara plug, responds fine through Z2M frontend, fine through homeassistant, but not fine when triggering through node-red
Ordered a zigbee coordinator from tubes ZB. I wonder how well zigbee2mqtt works for me
I've got a few Aqara Opple 6 button (3 switch) light switches, anyone know if it's possible to bind each switch to a different light group?
Iโm using a zigbee usb radio to connect to zha in home assistant. Setup with a couple of aqara buttons went well, but they have now dropped off connection after a couple of days. Straight line distance away is only maybe 3 metres, but it is through a wall? Iโm considering getting an aqara hub to help with connection as I intend to get more aqara stuff once I can get them connected. However, Iโm a bit confused which aqara hub works with home assistant. Could someone who has one working recommended?
The hub won't help
You want Zigbee routers - see the pinned messages for how Zigbee works
Ok thanks for the reply. As I understand it then a router works to increase the range of the network like a signal repeater?
I'm pretty sure that's not possible. You can only bind the switch to one Zigbee group afaik
In an attempt to achieve 34 dbm output from Tube's CC2562P coordinator, I have attached Sunhans' 2.4GhZ Signal Booster. The signal booster calls for ideally 10 - 14 dbm input power. I have experimented all the way through 0 - 20 dbm on Zigbee2MQTT's experimental: "transmit_power" settings but have not been able to see traffic through signal booster's "activity LED" yet. I'm on Channel 11.
Anyone have any ideas as to why this wouldn't work?
Do you have the right connectors?
Not screwing a RP-SMA male onto a SMA female connector?
You can check, one has to have a pin and the other a socket
I am connecting 2.4ghz booster to tube coordinator via SMA-FEMALE
Not sure which is which. If you unscrew the two pairs of connections, you should not be seeing two holes or two pins.
2.4ghz booster (SMA-FEMALE) <--> RG316 cable with SMA connectors <--> Tube Coordinator
ahhh!
omg you're fucking right
Female into Female. I am an idiot.
Will report back when I have this fixed ๐
I guess the real question would be whether or not this will have a positive impact on your network, especially if packets will be able to travel only in one direction due to range or something
What do you mean one direction due to range?
Like if your coordinator is able to reach a device because of the increased TX power, but that device can't reply
Transmit Gain == 14 - 17 DB
Receive Gain == =< 12 DB
It looks like very substantial increases
You should add more routers, not a signal booster.
Anyone else have issues with Z2M saying lights are off when they're on?
And it sometimes seems very slow to respond in comparison with ZHA
I've got it on channel 11. The majority of the wifi networks around me are on channel 1. I'll try changing to channel 25
Good thing I didn't just spend an entire evening getting everything paired correctly ๐คฆโโ๏ธ
You can change channel after the fact but this might depend on your integration doing the right thing for the network to do so
While waiting for the CC2652P2 from tube i am reading stuff to be prepared to set everything up. While searching i came across a page that explains how to do a firmware update. I see you loose all data if you dont make a backup. Whats in those firmware updates? are these necessary? i mean are new features and devices added or is this mainly tweaks? I am trying to avoid these kind of things in which you break every device in your house by doing an update
@gentle fern I have your problem with zha atm so i dont think its any different.
Updates can be anything, including security patches. Don't avoid updates, just make the plan on how you're going to do it. I.e. back up your stuff
I didn't have the same problem with ZHA, or at least not for a long time. I vaguely remember having some issues when I first set it up but I think that might have been channel related too
Had lots of trouble pairing with Z2M too, had to get devices within a metre of the coordinator. That really should have been a hint
That points to major mesh issues...
I had issues pairing devices initially, but once I sorted out my mesh the problems went away.
The last set of firmware updates included stability updates that stopped CC2652 based coordinators from locking up, for example. Certainly with Z2M it'll handle coordinator backups and restores for you. See https://www.zigbee2mqtt.io/information/FAQ.html#what-does-and-does-not-require-repairing-of-all-devices
When you say major mesh issues, what do you mean? What did you do to sort them? Anything other than changing channel?
Well, if you're having to bring devices within one meter of the coordinator.... that suggests either:
- You have no routers
- The connection to those routers is unreliable
- There's lots of interference
Well, (4) you're trying to pair an Ikea device and not been patient enough
I've got 20 bulbs (yes, Ikea) that are all paired. Eventually successfully. Why might the connection to the bulbs be unreliable? Anything other than interference?
Interference or range
Do see the pinned messages for things like ensuring you've got the coordinator on an extension cable, away from WiFi devices, not using USB 3.0 ports, scanning for quiet channels, etc
Definitely not range, gotta be interference. My wifi is on 1 and zigbee on 11, that's gotta be it
๐
Yeah, I had it all set up fine with ZHA but forgot to check the channel when I moved to Z2M. Just didn't set a channel and it picked 11
Yeah, that's the default for Z2M
It's dumb, other than it being one of the ZLL channels, so widely supported
I'll try 25, closest on wifi 11 is at 37dBm
Failing that, 20 is it. There's a wifi 6 at 54dBm
Yeah, not convinced that all of them will and not too sure where that info is
The Z2M hardware list sometimes covers it, but it's often a case of just trying
I know all my Xiaomi, Ikea, and Gledopto kit supports it
Sadly my Konke kit doesn't
There's actually some maniac with a wifi network on channel 13
Looking forward to living in a detached house where this isn't an issue
We didn't have major issues in the last house, which was a semi, but then the neighbour didn't have any internet ๐
As far as the other bits, non-USB 3.0 et al, I'm using a sonoff zbbridge mounted to the wall just above my server which has no wifi interface
Well, that's got built in interference, so not a great choice 
Hmm. Let's see how the channel change goes
https://github.com/Koenkk/zigbee-herdsman/issues/319#issuecomment-789757269
not recommended since the WiFi connection does not make for a stable solution
It's been solid so far
The same overall issue of using a WiFi connected devices as a Bluetooth scanner for monitor - the overlapping frequencies causes it to jam itself
Yeah, I've just made the connection. A wifi coordinator on channel 1, coordinating on zigbee channel 11 does not a stable mesh make!
Even if they're well separated there will still be some issues - but they should hopefully not be terrible
I'd highly recommend moving to a different coordinator
Tube (https://www.tubeszb.com/shop/coordinators/2) does wired network coordinators, and he'll likely get stock back in at some point (he just had stock, but sold out)
Oh well now I need to get a PoE switch, don't I

I promised my wife I would stop hitting Amazon so hard. This is not going well
Have you found AliExpress yet?
Cheaper, takes a while to ship, and you get surprises in the post ๐คฃ
Yeah, got all my switches from there
And ESP32s
I'll stick with my Sonoff for now, see how it goes. Gotta stop spending money at some point

Just got a google coral to play with frigate. Very cool. Even better in a couple of releases time when he adds static object detection
Yeah, I'm still using MotionEye for now, waiting for timelapse recording so I can give it a proper try out
Whats the default channel of ZHA? 15?
Has anyone been able to get Zigbee working on vitual box setup with a Nortek combo adapter?
Generally yes. It might differ depending on what stick you're using and if you already setup the stick with another library
When I add the integration it fails to connect on the radio selection.
Is there a setting in virtual box I need to set for the USB device?
The zwave function of the stick is working.
I have had allot of trouble with Zigbee stick and virtual box
VB will lose the stick after a full home assistant reboot
then its a big pain to get it back... so everytime you update the OS / Core you will lose the stick again
I would NOT recommend using a usb zigbee stick with VB
Yes, I had that issue already and noticed it was missing.
IF you find it and leave HA be it will continue to work. But as soon as you do a full reboot you can start from scratch. i have no idea why VB is losing the connection everytime the software reboots. I havent found any solution whatsoever
What setup would you recommend with the Nortek combo stick. I used to have a raspberry pi but it kept crashing.
Only people telling me to stop using VB with a zigbee stick
im running it with great success on a raspi 4b with 8GB of ram for a few months now not been crashing.
I use the official power suply. I have been reading reports of other power suplies not working very well and letting the pi's crash due to the lack of enough power
Tube's ZB website is selling zigbee coordinators which can be connected to the network seperately
then you connect to it via the network. that should work with VB
@azure tinsel using the pi with a sd card or usb ssd ?
I experienced issues with an usb ssd and conbee 2 stick at the same time, didn't investigate it any further
I was running on a raspberry pi 4 with 2GB and the power supply that came with it and moved to SSD
SD card WD purple. and recorder stored on a seperate synology nas
I believe the usb ssd uses too much resources for the zigbee stick to work 100%
Wouldn't surprise me. All 4 ports have a combined power output of 1200mA
im using zha with the nortek stick atm on the pi 4b havent had trouble so far
i could really recommend the micro sd from WD type purple
they are specially designed for heavy load for long periods of time
just be sure to make a backup so you can set it back up when the card crashes.
Is it normal with Z2M that while I'm attempting to join all of my lights become unresponsive?
It still received updates from end devices but doesn't seem to be able to issue any commands
Sounds like you're using an underpowered stick or you have issues.
I'm using a Sonoff ZBBridge which has been solid on ZHA for nearly a year now
Well at least I've figured out the sequence of events. If I try to issue commands while something is pairing the device will fail to pair and the command will not work
It does sound underpowered, doesn't it
But does Z2M have a greater performance impact that ZHA?
than*
If you just put your whole network on another configuration then it can take a while before the network is "settled" I have put back a snapshot of my system a few times now and everytime I did that lights arent responsive until a few hours later when the network is build. Not sure if that is the issue here though
I'm planning on running 2 zigbee networks and put everything on z2mqtt one by one instead of everything at the same time
Anybody here using binding of switch and bulb?
I've got some runlesswire clicks and ikea tradfri switches in the mail that I plan to do that with... ask me in a week ๐
I am really strugling ๐ฆ
I too want to know about binding. I have made a network using CC2531 with ZHA (running on pi4 with SSD) network and all switches are main switches creating a mesh network. But still the switches at first click are working but second click gives a delay...I feel it might be a binding issue.
But again i ain't sure why am I getting a delay on the second click when every switch is a router..
Delays... CC2531... I sense a pattern.
CC2531 can only handle two concurrent requests without occasionally throwing "out of memory" errors
You can bump up the software limit a little at the expense of some request patterns taking longer due to retrying:
zha:
zigpy_config:
znp_config:
max_concurrent_requests: 4
Or try 99999 and see what happens
In max_concurrent_requests??
Yeah, it effectively disables the software limiting.
But all my 40 devices are routing and if I see in the visualisation the cc2351 is just connected to 3 devices..
Maybe your right that might improve the latency issue ..I will try and get back..
You should upgrade your stick 
inb4, that's not what she said
Availability of stick is difficult and I tried using conbee 2 to integrate with ZHA. It didn't recognise my tuya devices...but CC2351 did...
Thankfully you can migrate from a CC253x stick to a CC2652 stick fairly trivially
Again availability... ๐ญ
Good news, everywhere will get stock in at some point
Tube had stock this week, and sold out fast
Electrolama has a signup list so you can get notified
I think Tube has a similar option
Slae.sh has stock right now - I managed to order it. Dunno yet if I will need to wait for 3-4 months, as he already had such cases previously...
@proven vector someone I know had his stick already delivered
so I think stock and shipping are pretty accurate now
hoping for the best ๐ but yeah - he has stock right now
Yeah, his shipping is better, but his communication still sucks apparently. If you have any issues, expect a struggle to get any response
๐ Well, I'm hoping for the best... I have a Sonoff ZBBridge in a shop near my house - 15 min walking. But I want to try CC2652 stick 1st
Right now I'm using Alexa Echo as ZigBee hub. It kinda works, but very crappy. I can't understand if it's because of the crappy Chinese controllers from Sunricher, or because of the Amazon Alexa "greatness" ๐ Too bad Echo can't be used as a ZigBee gateway for HA...
You can thank Amazon for that. Closed ecosystems are lame.
There are always pros/cons. But for me as an IT guy itโs definately a con
Yes, a waiting list is linked on the front page of the store. expect the store to be out of stock of things for a while as I work through what has built up over the last couple days.
Anybody would think:
- You're popular
- There's a world wide chip shortage
๐
I tried this till 50 current and when I over powered it all devices went offline .... I don't know what to do now...I removed the code but it's the same
You could get a better stick.
I can sell any of the sticks for 1 million dollars. Regards mr. Zigbee scalper
@dry fossil I got your point from yesterday and I have ordered already for it way before that...but that ain't a solution for the on going issue. It would be better if someone could help rather than just marketing a stick..
The only solution to CC253x sticks is to replace them
They're known to misbehave, lock up, run slow, and otherwise be a PITA
I'm not 'marketing' anything. I have nothing to gain if you buy a better stick, other than the satisfaction of knowing that yet another person has a stable Zigbee mesh now.
You're running pretty much the least capable coordinator available and wondering why you're having performance issues. There's one solution - don't use it.
I think the only way your situation could be any worse is if you were using deCONZ ๐
Not using deConz or conbee...and iam sorry I freaked out .. but I restarted the entire pi system and it all worked back again...
Yeah, you have to power cycle those sticks periodically
Iam using zha...I tried with conbee but it didn't work wasn't detecting my devices ..
That's probably more likely to be a ZHA/mesh thing than a ConBee thing, but I know a lot of people have issues with the ConBee
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 (though the HUSBZB-1 uses an older chipset), 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 option being the [CC2652 based sticks](#zigbee-archived message). If you want to use an EmberZNet stick see this issue. 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.
IMO ZHA or Zigbee2MQTT are the sane choices
My mesh is well connected with only few red lines for the sensors....and all are white lines and greens...I figure that's a good sign for a mesh..
@worthy patio When using Discord's new Reply feature it defaults to pinging the person you reply to, which can get frustrating for the target. Click @ ON to @ OFF to stop this - on the right side of the compose bar.
I've no idea what the line colours mean, I don't use ZHA
Try getting notification pings multiple times an hour - it gets old fast ๐
I have this bad habit of trying to help people
Which sometimes makes people think I'm their personal helpdesk.... that never ends well ||for them||
Last time somebody tried that the computer crashed itself, hard ๐
wouldn't it be easier to adjust settings on your side rather than trying to get the entire internet to adjust their settings?
@sour shadow thanks for all the help trust me when I say this I hold you on high regards..
Right, and that works really well if I'm not a moderator 
Thankfully I can just block idiots who don't listen, or who seem to view it as a me problem
what i can get as a recommendation for a thermostat that will be put on radiators to set up temp in room (zigbee2mqtt)
i am curious what ppl use
What you use depends on the plumbing in your country...
Check out the supported devices in the pins/topic. See what works for your radiator.
yah i know about pins i made one myself but i am more curious about what ppl use and experiences
they are normal radiators with central heating system
What other people use is irrelevant if they don't physically fit your hardware.
That setting shouldn't cause any issues like that, it's not something written to the stick. What does ZHA debug logging tell you? https://www.home-assistant.io/integrations/zha/#debug-logging
So I'm having a issue with zigbee2mqtt and the xfinity keypads. I think the posted topics are dismissed too fast and HA cant catch it because I can see it for a split second in the state tab and if I put the code in again or a few times HA finally catches it and triggers the automation. So is there a way to slow down the dismissing of the "action": "action_code": to give HA a chance to see it?
Would setting a retain for like 3 seconds do anything? Guess I can try and see
edit: nope still only flashed a split second
There's a debounce option that may do what you need
Well now I cant turn off retain.... ๐ฉ
You can, but you have to delete all the retained messages
Or you publish a null retained message to that topic
Yea just did that with mqttexplorer but in z2m I cant uncheck the retain box it stays checked
Stop it, modify the YAML, start it again 
should I remote the retain and retention line or just change to false? edit, just deleted the lines lets see
remove*
Alright set to debounce but I still have to put the code in more than once before HA triggers because the state of the "action_code": goes away so fast. I can see it pop up but I think HA misses it. ๐ I think the debounce helps with arming though since that is two topics action and action_code so its a step in the right direction.
So I'm not watching for payload for disarming I am watching the 'sensor.side_door_keypad_action_code' for a entered code since when I tried to watch for the code as a mqtt payload it never saw it and in mqttexplorer I see the code in the topic but it is in red. I'm really confused about the proper way to trigger with this device. It goes to null really fast.
I am using zigbee to mqtt to allow me use a Philips hue motion sensor but randomly it will keep on going off the network
That would suggest the signal from the nearest router isn't strong enough - or the nearest router is a light bulb you're cutting the power to
All my other devices are working fine and it is only the motion sensor
The Stick is in the next room to it and i only have sensor and buttons no lights
@drifting raven When using Discord's new Reply feature it defaults to pinging the person you reply to, which can get frustrating for the target. Click @ ON to @ OFF to stop this - on the right side of the compose bar.
zzh (CC2652R Stick)
Should be mostly fine then, as long as the wall is standard drywall/plasterboard and not brick/stone/concrete/wood
So why is it doing it then
What's the LQI reported by it?
Gentleman
I've done it
50% increase on my zigbee coordinator (measured by LQI) by leveraging 2.4ghz signal booster
From 14 feet away @ transmit_power: 13:
Tube's stock ANT = 97.7 AVG LQI
2.4ghz signal booster + 6dBi ANT = 145.2 AVG LQI
I am going to run a few more tests but the advantage is very obvious at this point. The issue that I am having is keeping the coordinator connection strong in a mesh of ~120 sensors in a facility. I think by improving the TX/RX of the Zigbee coordinator's signal strength, I will maintain better connections with my mains-powered routers and will have less dropped connections / having to restart my routers.
The TI MAC computes an 8-bit โlink quality indexโ (LQI) for each received packet from the 2.4 GHz radio. The LQI is computed from the raw โreceived signal strength indexโ (RSSI) by linearly scaling it between the minimum and maximum defined RF power levels for the radio. This provides an LQI value that is based entirely on the strength of the received signal. This can be misleading in the case of a narrowband interferer that is within the channel bandwidth โ the RSSI may be increased even though the true link quality decreases.
Greetings all, So while I am waiting to get my Electrolama zig-a-zig-ah! (zzh!) so I can start doing some zigbee to mqtt, I am using my sonoff zigbee bridge as my coordinator. Do you have any recommendations on some plugs that I can plug in around the house to act as routers as my coordinator is in my garage and I want to make sure I get decent coverage
What is that supposed to mean @austere patio ?
Last-hop LQI for TI coordinators isn't a great measure of the actual link quality
Then why use LQI at all / ever?
That is a good question
There is the ZCL Diagnostic cluster that has some low-level success/failure counters that I think you can read
I don't have the time to go that deep at this point
I've posted a 50% increase in LQI. I haven't even tuned it yet with tests on transmit powers 0 - 20
Yeah. I'm not trying to discourage or dismiss any potential performance gains. I'm just saying that making the LQI get bigger may not necessarily result in a better link quality.
I haven't tested it (yet) but you can also re-compile Z-Stack and enable LQI adjustment, which the dev guide says will scale the LQI to "'de-rate' noisy packets"
Yeah I don't have time
Did you ever move that WiFi AP off of channel 1 so it doesn't conflict with your Zigbee network?
Sounds like something I would do if I was out to build an enterprise-grade zigbee cooridnator, but that is not my focus at this time.
This test was on my home network.
Moving my client's network to channel 25 was good help
The problem of routers dropping still persists
Hard to tell why that happens when the only feedback you can really get from the network is the router not responding to packets or otherwise leaving
My theory on this, much like the failings of being able to query LQI from routers, is due to lack of signal strength from my zigbee coordinator
I understand that from a technical perspective, but the easier lift for me at this point is brute force: a mains-powered 2.4ghz signal amplifier to realize 12db+ increases on TX/RX
Yeah. In the end, things working is really the only thing that matters.
Does anyone know how well CMARS Smart Plug, ZigBee Switch Mini Smart Outlet work? I see I can get 2 of them on Amazon for $20.00 and would like to put some throughout the house as mesh extenders
The points you bring up are what I would do to create an enterprise-grade zigbee coordinator
+20dbi is not enough juice to blanket a facility in adequate coverage
You need to juice the output from the zigbee radio.
Once you juice the radio, then I think to ensure you're not losing packets and the noise is low, I would run tests to check the diagnostic cluster.
It is a mesh after all so having a strong coordinator signal may not help the case when a device's weak radio can't reply back due to transient interference or other adverse network conditions
My end-devices perform perfectly. I only lose routers. When I lose routers, the end-devices jump to another router.
The signal strength average between my end-devices and their routers looks healthy (125)
I don't foresee there being enough interference on channel 25 from a coordinator (located in a supply closet) will have.
The LQI values reported by SiLabs routers may be more useful, as they seem to incorporate retries and stuff like that into the calculation. If you're running Aqara routers then I'm not sure, they're NXP.
I have 10 ikea tradfris at my house
I can run the same tests with those devices
The result I realized were based on a push-button AQARA end-device
My guess is that with a stronger radio on the IKEA Tradfri's (vs the push-button AQARA), I'd see an equal increase in LQI.
Maybe for the coordinator's reported LQI. I'd be curious to see what the LQI in the other direction (as reported by the Tradfri device) looks like before/after the change
Sunhans sh-2500
$35.99 on Amazon Prime
I'm moving forward now. Will look to provision at facility on Monday after more testing around my apartment.
Good luck
has anyone used: Smart Plug,DOGAIN Zigbee Smart Plugs Outlet and will they act as Zigbee Repeater/Router to extend zigbee mesh?
These instructions don't seem to work: https://github.com/zigpy/zigpy-znp#testing-dev-with-home-assistant-os
Probably because of https://github.com/home-assistant/addons/issues/434#issuecomment-440627729
@uneven ruin do you have any that you can recommend?
I have come to the decision that, while ZHA works absolutely fine with the Sonoff ZBBridge, Z2M does not. Fairly frequently getting incorrect state reported for some lights, troubles pairing, inability to issue commands to devices while pairing new devices. Order placed with Slaesh, looking forward to having a stable mesh.
When you add repeating devices to an existing network, do you see children reconnect via the closer repeater in the visualisation? Do everything self configure?
ZHA
Or do I re-add end devices via that repeater in the gui?
Anyone have experience with the Ikea smart outlets? I'd like to get them in the mesh as a repeater and an outlet. I read that they do not have an on/off switch though. Does that mean if I toggle it off in HA the only way to restore power to it is to toggle it on again?
Got a question about HA/Zigbee groups: Iโve added XX Philips lights to a Zigbee group, all of them support color. However, from the control menu when I click on the HA entity (of the group) - Iโm only able to adjust the brightness. How can I also control the color? (My integration is Z2M)
Anyone had issue with Fyrtur not updating state and position in HA with ZHA?
Seems like there's a solution for Deconz but not ZHA?
https://community.home-assistant.io/t/fyrtur-state-not-updating-in-ha/148858
Enbrighten Zigbee Smart Light Outlet - not exactly the same since you replace the outlet but the signal strength is amazing
it will slowly reconfigure its self
I added an outlet last night which showed up with no connections for a while but this morning its a central node to the mesh
I also have a peanut brand one that works well. had to figure out the firmware upgrade through ZHA to get the power monitoring but the router feature is way better
Thanks
For LQI and RSSI am I looking for a high LQI? What is a good RSSI value?
LQI of not zero
Legend has it that someone once saw 256.
Stable matters more than any number, though LQI is device/platform specific, and sometimes 255 means don't know
I have a sensor saying 255 and I'm sure it's not ๐
Can anyone lead me in the right direction to change zigbee channel on ZHA running a HUSBZB-1 running HASS OS
Do you have the SSH addon installed or have access to a second computer with Python?
Yes I Have the SSH add on
You can follow these instructions to get into the appropriate shell: https://github.com/zigpy/zigpy-znp/blob/dev/TOOLS.md#in-home-assistant-os
Hi everybody, I re-connected an Aqara Vibration sensor to the zigbee2mqtt.
It has no state.
It reports the battery, the angles and all, but doesn't report the tilt/free-fall/vibrate.
This same issue this guy posted time ago. The solution is 'uncommon'. Can anyone here suggest something more?
Thanks! https://community.home-assistant.io/t/issues-with-xiaomi-vibration-sensor/90077
Thanks @mystic copper
Once you've disabled ZHA and are in there, bellows -d /dev/... backup > /config/backup.json will make a backup
Ok cool
Edit the logical channel in there and restore it with bellows -d /dev/... restore -f -B /config/backup.json
great
If you have mains-powered devices like bulbs, power cycle them at the switch after re-enabling ZHA
Some should re-join the new network
Ok cool I was thinking I would have to repair everything
You probably will
Ok well at least I entered into it with that mindset
Zigbee doesn't handle channel changes as gracefully as WiFi. There are some other ways to change the channel but I've not tested any with EZSP coordinators.
Maybe try also incrementing nwkUpdateId by 1?
in the frontend, try clicking the orange button for the device
if not, remove and re-pair it seems the fastest solution
done 3 times. and the orange button says
Device 'area03_vibration' cannot be configured
force removed it as well ?
yep. last time i used it was on another HA installation. This new HA has never seen this sensor. And it's my only one vibration
it sometimes still remains in database.db
what i'd do, turn off Z2M, copy the database.db file
and remove the sensor entity there
also in devices.yaml
and state.json you might check as well
done already :/ i've been struggling on this for 3 days. I'm not new to HA. I also use to delete the DB every 3 weeks just cause i don't need it.
mmm that's a bummer
I know one more last thing to try
and remove the battery from the sensor for a couple minutes
then try to re-pair
indeed :/ i never ask anything here, when i do is when it's my last choice. of course you gave me great suggestions! thanks for that
no problem, I once had some similar issue fixed with all those steps
I will insist (:
Hi, I'm pretty new to Zigbee, got a few devices to try out and I'm struggling a bit with one of the devices. It's a Tuya based 4 button scene switch (TS004F).
It was detected by ZHA as a device but it only registered the battery level and an 'on-off' switch that didn't seem to equate to any of the buttons.
I deleted the device with the intention of adding it again to see if I got a better result, but it every time I try to 'add device' in ZHA, the device doesn't show up even though it's right next to the hub.
I've tried rebooting Home Assistant in case it was caching something but it still doesn't show up. Is there a cache hiding somewhere that remembers previously deleted devices to exclude them from showing up again?
If it's a Tuya device, it needs to be explicitly supported. Try searching for the exact model and manufacturer names in here: https://github.com/zigpy/zha-device-handlers/issues
there is some work on that switch in quirks now, but looks to be just in testing and incomplete currently. https://github.com/zigpy/zha-device-handlers/pull/969#issuecomment-883917419
I see, I can see the device in that list as a 'Device Support Request' so I guess that means it's not there yet.
Forgive my ignorance...do you think it's the not-yet-supported nature of the device why it's not showing up when I've tried to rediscover it after deleting it?
If it makes any difference, I originally set it up on 2021.7 and now I'm on 2021.7.4.
Did you remove the device before trying to re-add it?
I did - I removed it using the remove button on the device screen
is this normal for zigbee networks ? (34 devies, small apartment) https://imgur.com/a/9JN3d6V
I really think that Z2M is fundamentally broken for Sonoff ZBBridge. I've just set up ZHA again and it works flawlessly when Z2M has delays up the wazoo
Do hue bulbs repeat ok? I think I remember seeing they didnt?
They mostly do (better than OSRAM lol)
The Bluetooth enabled bulbs use a newer Silabs chip and Zigbee 3.0.
The older ones (without Bluetooth) are still fine too
Morning all, a load of my lights have been given the wrong color_mode. It's saying they support hs when actually they only support color_temp. Anything I can do to correct it?
Also, what sort of problem does this indicate? WARNING (MainThread) [zigpy.appdb] Skipping invalid neighbors_v4 row: (5c:02:72:ff:fe:43:e4:60, cc:cc:cc:cc:dc:12:cf:a4, 60:a4:23:ff:fe:1d:49:5e, 0, 0, 1, 0, 0, 2, 0, 0, 206)
Solved this. Set the correct thing in customize, restarted, removed it, restarted. Fixed
I do now have a couple of switches reporting they have a main power source when they should be battery :/
About to change Zigbee coordinator. Apart from noting all sensor/devices names, is there anything else that I should think of before starting?
Depending on the number of devices and how comfortable you are with running a few commands, you may be able to migrate without having to re-join anything. What coordinator are you switching from and to?
It's a bug but nothing to worry about, it'll be fixed in an upcoming HA release.
Great, thanks puddly
Any idea on the switches not getting their battery? Also they are not populating the zha_event data the same as the ones that are working correctly
Did you recently upgrade from 2021.6 to 2021.7?
Fairly, yeah
Your device likely was incorrectly initialized when it joined and was missing a node descriptor. ZHA displays Battery or Unknown when the power source is unknown (in your case missing). 2021.7 fixed that bug and your device apparently says it's mains-powered.
That sounds great. I am switching from a ConbeeII to a cc2652R based zzh stick
Ah, that's the migration that doesn't exist yet, sorry
Everything but the Conbee works though
No worries. I don't have so many devices
If you have a ton of devices you could manually fill out the info by reading it out with deCONZ, but otherwise it's probably faster to just make a new network
Yeah, I think I will do the latter. Thanks tho
I've just removed the battery, put it back in and re-paired. Now it says unknown... And what about the wrong event data?
Not too sure about that one, sorry
Cool cool, ta
Best motion sensors that have light meter built in?
Ikeas don't, hues outdoor does, but don't really want 40 euro in every room.
Might be able to use a "global" sensor for light, and use cheap simple sensors otherwise.
Thanks!
Separate sensors
The Xiaomi Mijia light sensors are awesome, couple those with any motion sensor of your choice
I love the hue motion sensors despite the high price. The main reason i like them is the form factor, it has light and temp sensor, 15 sec update. And you can use normal rechargable batteries in them. the 20 euro they cost more is more then well spend in my opinion
I also have a few tuya ones in different size and shapes. I must say they work perfect too. but in the long run i will replace them all for hue
And besides that one more thing. My motion sensor outside from hue is on placed on the wrong spot and detects motion every 15 seconds a.t.m. for roughly 12 hours a day. (its next to a greenhouse which heat comes out of the doorway triggering the motion) This sensor is placed there several months ago and since then triggering motion every 15 seconds. And still after half a year the battery is still 100% So these things are insanely power efficient. Some tuya ones that i have for the same period allready are on their second battery (3v liion cell battery) So also for batterylife i would always recommend hue
I am installing a zzh coordinator with zigbee2mqtt as an addon, has installed mosquitto broker and got it all started, seems ok so far. But a few Q's... I find an integration MQTT that has a configure link. Shall I configure that too? And how do I initiate pairing mode? And what is the sun-button in the webgui?
Push the sun button, see what happens ๐
For pairing, push the button marked Permit join
Aha, so it stays in pairing mode as long as it is permitted? I willl give it a testrun, thanks ๐
Well, pairing succeeded, but it won't show up in HA... Where should I start to dig please?
Make sure that the add-on is using the same broker, that HA is using MQTT Discovery (that's the default these days) and that Z2M has Home Assistant enabled (can be done in the UI)
Check too that you're on Z2M 1.20.x, not 1.18.x
Perfect, many thanks. Will start with this ๐
All the config can be done in the UI these days - don't mix up UI and YAML. If you do both the results are unpredictable, and likely to be broken
Oh. Thanks for the warning!
Issue seems to be the broker... There is an built-in one in HA? Can that be used for configuring MQTT? Or will I have to use for example Mosquitto (as I did initially, now uninstalled)?
I get this in Mosquitto log after startup
1627208681: New connection from 172.30.33.5 on port 1883.```
You did configure Z2M with auth for MQTT?
I will not say I did as something obviously is not right, but think I did. Will try to check again
Check the logs for Z2M and HA
Does anyone have any tips for getting a couple of Opple switches to pair correctly? They keep not reporting power
And... which Zigbee integration?
Sorry, ZHA. I've given up on Z2M and sonoff bridge
Then I'd bet they send events
HA Integration log throws this
12:04:20 PM โ (ERROR) components/mqtt/__init__.py``` and my HA configuration.yaml has these lines
```mqtt:
discovery: true
broker: mqtt://core-mosquitto:1883 ```
How devices look in ZHA and Z2M is going to be quite different
Don't set it up in YAML, do it all in the UI
Which I may have mentioned before
You added a broken subset of the required config, with no auth, no LWT, and basically broke it ๐
I'm good at something... ๐ No, really. Perhaps I should start over, or can I rescue any bits from this?
Remove the YAML
Restart HA
Set it up correctly in the UI
As you're using the add-on it may already have done that for you
Much was filled in, true, but still didn't show in HA
Well, no, because you added the YAML
I warned you not to do that, and you even acknowledged it 
Not much I can do if you're going to deliberately ignore advice
this one is the best in terms of sensoring. size, not so much https://zigbee.blakadder.com/Develco_MOSZB-140.html
Ooooh, I can get those easily here.... another one to try ๐
Well, I do appriciate the help, and yes, I mistakenly added to yaml. Will not do that any more...
So most of the switches are pairing fine and configuring correctly, just 2 aren't.
No idea then, hopefully somebody else may know
Thanks @sour shadow ! I finally got it working using your guidance. I did start with reading way too many different guides, then it all got mixed up, sorry for the confusion
Anyone else found that ZHA is keeping their coordinator in pairing mode even after is stops 'Searching'?
Cheers!!!
My flow: Add device -> pair switch -> fails to configure correctly -> wait for searching to finish -> put switch into pairing mode again to remove it from the network
Now what I would expect in the logs is to just see the device leaving the network. What I actually see is it re-joining when the coordinator is no longer searching
@gentle fern keep removing and adding it until the power shows. Sometimes it took allot of tries for me to
It's like the interview most of the time does not get completely through
You could also try to just put the switch in pairing mode after it allready has been found and let zha find it again. Sometimes the battery pops up
If it does then it's correctly configured. It seems like these battery powered devices cut off the interview
I've done it so many times
What switches do you have
Aqara Opple
They can successfully have battery stats with zha
Sometimes it helps toput them in pairing mode during the interview
I know, 7 out of 8 do. 1 is just being a dick
Ah ok... Then maybe it's the switch itself. Not sure what's wrong then
Is was 2 being awkward, but I managed to get one of them to pair
Have you tried removing the battery
Yeah. Tried putting it into pairing mode and then quickly removing the battery to get it properly unpaired, tried holding the pairing button while putting the battery in
Strange.. if you paired a bunch allready I'm not sure what's wrong.
Meither. It's very frustrating. It's also frustrating, and slightly worrying, that ZHA seems to keep my coordinator in pairing mode even after it's stopped searching
Joins are permitted for only 60 seconds. Why do you think your coordinator is still allowing joins after that?
hello from germany ๐ i have a big problem with my rasbee2 .... i just can't get it involved anymore.
yesterday i switched from the sd card to an ssd and nothing has been running since ...
does any of you also use the rasbee2 or all only the conbee usb stick?
My flow: Add device -> pair switch -> fails to configure correctly -> wait for searching to finish -> put switch into pairing mode again to remove it from the network
Now what I would expect in the logs is to just see the device leaving the network. What I actually see is it re-joining when the coordinator is no longer searching
Once it has the network key there's not much you can do to prevent it from joining the network
If it re-joins after you factory reset it, then the reset didn't seem to work
I have no idea how to factory reset it. I'll look that up
Yeah, so it's supposed to reset when you put it into pairing mode
In that case, can you record the whole thing with debug logging enabled (https://www.home-assistant.io/integrations/zha/#debug-logging )?
The only coordinator that I'm aware of that had issues with keeping joins enabled was the CC2531, but that was fixed months ago.
Since one of the last HA updates I cannot pair new zigbee devices. Anyone else here with similar problems? (ZHA with conbee2 and latest firmware)
I can see some Errors like: 0xbe93] Delivery error for seq # 0xd1, on endpoint id 0 cluster 0x8000: message send failure
And Log says raspbee2 instead of conbee2
The code that talks to the Conbee hasn't been updated since March so I don't think anything in the latest update would cause your problems
Can you enable debug logging (https://www.home-assistant.io/integrations/zha/#debug-logging) and post a log?
the log is huge. anything I can grep for?
zigpy|zha|deconz should work
I get many errors like these with different devices:
@loud belfry posted a code wall, it is moved here --> https://paste.ubuntu.com/p/8HfPqNH7q8/
@loud belfry Rule #6: Spam will not be tolerated, including but not limited to: self-promotion, flooding, text walls (longer than 15 lines) and unapproved bots.
Please take the time now to review all of the rules and references in #rules.
For sharing code or logs use https://paste.ubuntu.com/.
TXStatus.MAC_CHANNEL_ACCESS_FAILURE means that the Conbee refuses to transmit due to interference
Plug it into a USB 2.0 extension cable, away from any potential sources of interference (including active USB 3.0 ports)
Thanks for the response. I already have a Setup with extension and USB 2 Port. This is now working for over a year. But I ordered a new Extension and will reposition the stick and try again.
Any new additions, like new SSD enclosure, a wireless keyboard, Bluetooth etc also could be source of interference. Think what changed recently
It does not, unless you leave your browser opened on the device add page and there reconnect
good morning everyone ๐ does anyone of you use a rasbee2?
@tiny gate Don't ask to ask, just ask your question. Then people can answer when they're around.
When you do ask a question, try to provide as much background detail as possible. Ask yourself these questions first so that others don't have to:
- What version of the Home Assistant are you running? (remember, last isn't a version)
- What exactly are you trying to do that won't work?
- Is the problem uniform or erratic?
- What's the exact error message?
- When did it arise?
- What exactly don't you "get"?
- Can you share sample code, ideally with line errors where the error occurs?
I found another problem in log, maybe this prevents correct initalization. Any toughts @gentle flint @austere patio https://paste.ubuntu.com/p/wp65zsdKrS/
okay ๐ so: i switched from an sd card to an ssd card. since then I have had problems with my rasbee 2. I absolutely can no longer get it involved. I tried everything possible for over 15 hours yesterday. now I hope for more help. maybe someone like to go through his config with me?
the problems are probably also known with a conbee 2. This should be remedied with a USB cable. brings me nothing with the gpio
If you moved from SD to SSD then it's possibly a power issue
too weak power supply?
I have the original from the Raspberry
I then set everything up again and installed the phoscon image (Raspbian Buster Desktop
Beta image with desktop based on Debian Buster) then I installed HomeAssistant and supervisor manually. In principle, however, it starts with what I have to enter in /Boot/config.TXT ... I always find different options
it should work, because I get it integrated via the deconz integration. I would like to use either Zigbeemqtt or โzhaโ.
The RaspBee and ConBee are best used with deCONZ
If you're using ZHA or Z2M then use a CC2652 based stick, or a current generation EZSP stick
When I was on the SD card, I had "zha" and it worked perfectly
so better an ssd with its own power supply?
if I had been told yesterday ๐ I would have saved myself a lot of work
Well, if it used to work, and you change one thing, then it no longer works.... odds are the problem relates to what you changed
Sure
okay, that helped me a lot! Thank you very much! Butโฆ
why does the dconz app find it, but not zha ?!
for zha I mean that i have to change the config.txt ...
What OS and environment?
Host is current Debian stable. HA running on Docker 2021.7.4
I got myself an Ikea Tradfri 5 button remote to try out and was able to successfully bind the remote directly in ZHA to a light group for Groups (though tbh I don't know what this binding does yet), OnOff, and LevelControl, and it was pretty easy! Nice! Did a little digging into device quirks and I have a rough understanding of how the quirk is translating zha_events from the button presses. There are also left and right buttons on the switch, and I see a "ScenesCluster" binding for the remote, is there some documentation on how that is supposed to work?
(I ended up creating an automation to select through scenes and bound that to triggers on the button presses, but I was wondering if there was a more ZHA+bind-y way to do that)
This problem should be fixed in HA dev
ok, so maybe with the next patch?
I think so, I'm not 100% sure what the release schedule is
As https://github.com/home-assistant/core/pull/53472 doesn't have a milestone, I don't think it'll be cherry-picked into a "patched version" (next one would be 2021.7.5).
You can manually update to the latest dev build: 2021.8.0.dev20210726 (note: since it's not even in beta, it may break stuff -- works fine for me lol. Just remember to take a backup before if you attempt to do this. HassOS: core update --version 2021.8.0.dev20210726)
Otherwise, wait ~2 days (28.07.21), as we'll get the 2021.8.0 beta then which will include the fix. It should be pushed to stable on 04.08.21)
Over 20 of my about 35 Ikea sensors and remotes are showing battery level null (zigbee2mqtt), some might have almost empty batteries, but they are working and even though changing new batteries, they are still sending null battery level. Is there something I should know?
Hey. I'm trying to connect my ID lock 150 to HA with Conbee 2, but I don't understand much of it. Is anyone able to help me?
I have installed deCONZ in HA, if that's what you're asking? Sorry, I'm new to much of this ๐
I have a few lamps already. And a new device is listet that I haven't added myself, so maybe that's the lock?
It's just called 0x3F2E, so not very descripive.
Did you try to pair the lock?
That's what I need help with, not sure how to do that.
In general, same way as anything else
With the lights, it was just to press "search" in the Phoscon app.
Put deCONZ into pairing mode, put the device into pairing mode, swear a lot
Sounds like much the same then
The lights clearly defaulted to pairing mode, you just need to put the lock into it
2 sec
Am I not allowed to post pictures here?
The instructions says to put in batteries, and it should go in pairing mode, and a blue light should blink when it's paired. It did blink earlier, and I have a new device in my cluster, so maybe it has auto-added itself?
Please use imgur or other image sharing web sites, and share the link here.
Image posting is blocked in most channels to discourage people from sharing text as images.
Sounds it, if deCONZ was in pairing mode 
Is there a way to figure out what that new thing in deCONZ is, or check to see if it's my door? To me it's just a bunch of numbers.
You should have associated entities or devices in HA, hopefully
Look for one called lock.?
You can remove nodes, yes
trying to move a sensor from my smartthings deployment to HA
How would one go about getting attributes added to a device in ZHA? The main reason I wanted to try Z2M was because it reports the smoke density from my xiaomi smoke alarm. Seeing as Z2M was an abject failure for me how would I get that smoke density from ZHA?
using HAZ
With most Zigbee stuff you can just pair it directly to the new controller
ZHA*
Putting it into pairing mode causes it to "leave" the previous mesh
Okay I guess I'll just have to figure out what I'm doing wrong on the pairing.
That's the badger
With Z2M I get constant timeouts ๐ฆ
It just hates you, don't worry about it ๐
But it is a lovely interface!
You probably have to look at the endpoints and the clusters
The node descriptor doesn't tell you much
It really does. It hates me so much
Yeah, any hints?
just my 0.02 as a new user, I used deconz for all of a day before switching to ZHA and ZHA is far superior
Figure out what attributes they are (if they're even attributes...) and add them to the appropriate cluster
If Z2M implements it then just look at the appropriate handler
I'm fairly sure I know what cluster attribute it is. There's an AnalogInput cluster with a present_value attribute. I just have no idea where to go from there
I would obviously like to confirm that I'm correct, but don't really fancy starting a fire :/
Are you able to read the attribute within ZHA?
Yeah, it says 0.0. As I said, would love to see it change but not willing to start a fire
This appears to be the relevant line from Z2M https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/converters/fromZigbee.js#L5335
Looks like the non-standard Xiaomi heartbeat
Depending on the type of sensor you may be able to trigger it with dust
But idk if that will permanently degrade its operation
I am unsure what to do with this info
Enable ZHA debug logging (https://www.home-assistant.io/integrations/zha/#debug-logging) and record the Xiaomi heartbeat attribute report that occurs. It'll be for attribute 65281 (0xFF01)
If I'm reading the Z2M converter correctly, it's using the non-standard Xiaomi packed attribute report
@spare talon I installed ZHA, and it recognized the lock with name and everything straight away ๐ Thanks!
attribute_id: [65281] value: [{'battery_voltage_mV': 3135, 'temperature': 34, 'X-attrib-4': 5032, 'X-attrib-5': 24, 'X-attrib-6': 1310740, 'path': 26456, '0xff01-8': 4100, '0xff01-100': 0, '0xff01-150': 0}] ๐ฅ
It should be the -100 one
Because ZHA quirks turn non-standard devices into standard ones, you'll have to map that attribute report to the correct Zigbee ZCL cluster and attribute
And where might I find the info to ascertain that?
Hmm. Maybe the PM2.5 measurement cluster??
Don't suppose you could point me to any examples of where similar things have been done? Monkey see, and all...
I'm not all that involved with quirks but here's the PR that added support for it https://github.com/zigpy/zha-device-handlers/pull/46, maybe leave a comment if you get stuck. You can see how other clusters for devices with Xiaomi attribute reports are implemented (https://github.com/zigpy/zha-device-handlers/blob/9c278b8f9c42a8d8f0c1d1b8dc3b137992f19981/zhaquirks/xiaomi/__init__.py#L185-L217) so maybe add a PM25 cluster and do the same thing there? That's just my guess.
I'm not entirely sure what you mean by a PM25 cluster
ah!
I'm not sure what in the zigbee spec matches up with "smoke density" or whatever the alarm outputs, but that (to me) seemed reasonable
Yeah, that seems sensible to me too
Today I replaced my USB extension cable with a new one and my conbee2/zha startesd working again. Thanks for your help!
My automations based on Hue dimmer switches connected to a Hue bridge recently stopped working.. The dimmer switches control lights correctly through Hue bridge and I can still set and read light status correctly throuh HA. Idea appreciated
(Attempted to listen for events in case an ID had changed or something, but couldn't see anything directly related to the switches throuhg listening to "state changes", only the state changes of the lighs themselves based on input through the switches. It's also a "hue events" option, but that doesn't actually give any data)
Seems to be like the Hue bridge no longer send input data from my dimmer switches to HA (after changing to push API).. But I might very well be missing something..
If you're still using one of those dumb bridges, you should probably be in #integrations-archived. This channel is for people wise enough to use one of the 3 integrations that talk directly to HA.
ok, integrations might be better, but I disagree regarding "dumb" and "smart" as I consider it s design decition not to depend on HA for basic functionality like lights which will work dependent of HA
and, yes, I also have ZHA and Zigbee devices directly connected, but that's beside the point as it's not "critical functionality"
You don't need a bridge to bind switches to bulbs
They can communicate directly and just report the state change (assuming the devices are all standards-compliant, otherwise you run into issues)
running the latest Home Assistant dev build
not sure if it's actually impacting something
The affected IEEE addresses are Xiaomi Zigbee 3.0 smart plugs and Xiaomi/Aqara Opple (Zigbee 3.0) remotes
Hmmm. That would only be generated if either the ieee doesn't exist (i.e. the device has been removed), or the database doesn't have that specific endpoint for the device but there seem to be attribute records for them
The only schema change is the endpoint_id constraint
Does a quirk add endpoints or something?
The devices definitely still work. It's possible that the quirk might change the endpoints for the Aqara Opple remotes. I think I had one of the remotes paired without a quirk existing at that point
I think the quirk puts the remote into some other mode where it exposes more endpoints (or it just replaces them).
For the smart plugs, someone mentioned they have a tendency to just present different endpoint sometimes. (Not exactly what I recall but maybe related: https://github.com/zigpy/zha-device-handlers/issues/516#issuecomment-727282163)
Hmm, this isn't good
It's not going to critically break anything but the attribute cache won't be persisted to the database for these endpoints that don't really exist
What does sqlite3 /path/to/zigbee.db .dump | grep '04:cf:8c:df:3c:7e:4c:3f' show for the device?
Yeah, looks like the device is only supposed to have endpoints 1 and 242, but also seems to have attribute records for endpoints 21 and 22
ah, it might be that I had a custom quirk installed for that one too at some point (Aqara Smart Plug)
and the Aqara Opple remotes didn't have a quirk yet
Do the remotes (without quirks) also follow a similar pattern?
I don't think zigpy would process the attribute report unless the device object itself has the appropriate endpoint
Which seems like it could only be added with a quirk of some kind
here's the grep for a remote: https://paste.ubuntu.com/p/6nCXVmStQ9/
Either the quirk didn't exist when I initially paired these (which is probably not the case for all three remotes I have paired that still show up as a warning in the log file) or the quirk changes an attribute which makes the remote present different endpoints (https://github.com/zigpy/zha-device-handlers/blob/21af0860992021c39b26260b6e2ae4f9c1af75d1/zhaquirks/xiaomi/aqara/opple_remote.py#L154)
Hmm, same thing. Has only endpoint 1 but has cached attributes for endpoints 1, 2, 3, and 4
Since I'm pretty sure I never installed a custom quirk (while developing or whatever) for these remotes, it must be related to the remotes actually presenting different endpoints at initial pairing (or the quirk doing something special)
The quirk seems to add extra endpoints: https://github.com/zigpy/zha-device-handlers/blob/795cc68a82ad4d2b4048bcdc063e36d4d2468af6/zhaquirks/xiaomi/aqara/opple_remote.py#L792
yeah, that's the one that's used by the remote
Looks like the schema just needs to be relaxed. Time for a v6 migration...
Thanks for testing it out before the beta
Ah, yeah, xiaomi does that where it sends updates from non existing endpoints 21 and 22. Iirc for power measurements.
And some quirks also send attribute updates on the virtual endpoints, that's why attributes table had foreign key only on device IEEE and not on the endpoint
anyone see this?: https://sync-sign.com looks like a great low cost e-ink control interface. the hub also supports zigbee and there are some mqtt example plugins. ordering a dev kit to play with myself.
A ~$200 "dev kit" and old Xiaomi Mijia sensors being resold for $40 each. Seems suspicious...
@onyx talon Very, very cool concept. If you're interested in developing an end-to-end IoT solution, this looks like an easier way to get your feet wet than DEVELCO's developer kit. I'm pretty sure they wanted $2,500 for theirs. Although above all, I'd recommend architecting your own technology stack for autonomy and costs. We use Zigbee >> Mosquitto >> Balena >> AWS IoT Core >> AWS DynamoDB.
There is A LOT of room for vertical IoT solutions and enterprise products in the Zigbee space. You can slowly see it starting to see these solutions start to bubble-up out of the tinkerer / maker ecosystem, but we are still very much in the early innings.
if a device (Iris 3210-L) shows energy in Smartthings but not in zigbee2mqtt, is it safe to assume that the Smartthings DHT is calculating it?
ya in W
it can be calculated of course, but if the plug itself has it i'd rather use it from there
what does the debug log report ?
reading over the DHT it looks like it's being calculated
https://www.zigbee2mqtt.io/devices/3210-L.html (it should report apparently)
it's reporting what it says there, but not energy (cumulative) like ST does
perfect, was just trying to make sure i wasn't missing anything
Probably living in a dreamland here, but is there a smart switch that will control a smart bulb rather than turning off the power with the following features:
- Zigbee
- No batteries (i.e. wired)
- Supports binding (so it will work if the coordinator fails)
- Isn't Xiaomi
The Zigbee Binding requirements unfortunately means no kinetic/ green power devices ๐ฆ I will likely use Zigbee2mqtt.
if you hack a hue dimmer, it might work ? ๐
replace the battery with a wired adapter that provides the same voltage/power
Is anyone using the Philips Hue Tap switch with non-Hue routers? I'm seeing documentation everywhere mention that only Hue devices can act as ZGP proxies for them but all of my IKEA routers have a ZGP endpoint. It seems like they should also work?
Yes enbrighten switches are like that. What is the problem with the batteries? Changing one in two years isn't big deal for me.
I loved the centralite switches, that go over existing ones, too bad they are not making those anymore
can you uncouple them from relay to keep power flowing?
Just don't connect anything on the load side, then it would satisfy all the requirements
I mean you connect both switch and bulb to the line side of the switch and leave the load side unconnected if you really want to do it that way
Any insights on this folks? #zigbee-archived message
For most domestic setups, tens of thousands is probably too many
Oh wow. I was foolishly thinking the limit was a few dozen
On a CC2531 you can still scale to many hundreds, performance just sucks
The theoretical limit is about 65K
Any insight to when the noticeable performance threshold is?
With the CC2652.... more than hundreds
That is very comforting thank you!
I've got about 60 devices and there's no performance difference than when I had 5
I was noticing 20 was a big problem with a CC2531 so I upgraded and was worried I was getting carried away with doing nearly every bulb and lamp in my house.
I think the "hard" limit for the CC2652R with the default firmware is somewhere around 300
There's a limit of 200 Zigbee 3.0 devices anyway