#zigbee-archived
1 messages · Page 22 of 1
ive been trying to research on this
most vendor i spoke to kept discouraging me on this but not able to tell me exactly why its discourage
17th try was the charm, finally got the fp1 to pair
Interesting:
pi@homeassistan:~/Firmware/cc2538-bsl $ sudo ./cc2538-bsl.py -v -p /dev/ttyAMA0 ../Z-Stack-firmware/coordinator/Z-Stack_3.x.0/bin/CC1352P2_CC2652P_launchpad_coordinator_20220219.hex Opening port /dev/ttyAMA0, baud 500000 Reading data from ../Z-Stack-firmware/coordinator/Z-Stack_3.x.0/bin/CC1352P2_CC2652P_launchpad_coordinator_20220219.hex Firmware file: Intel Hex Connecting to target... CC1350 PG2.0 (7x7mm): 352KB Flash, 20KB SRAM, CCFG.BL_CONFIG at 0x00057FD8 Primary IEEE Address: 00:12:4B:00:22:98:07:07 Verifying by comparing CRC32 calculations. ERROR: NO CRC32 match: Local = 0xddfc152d, Target = 0xbff209d6 pi@homeassistan:~/Firmware/cc2538-bsl $
'pi@homeassistan:~/Firmware/cc2538-bsl $ sudo ./cc2538-bsl.py -evw -p /dev/ttyAMA0 ../Z-Stack-firmware/coordinator/Z-Stack_3.x.0/bin/CC1352P2_CC2652P_launchpad_coordinator_20220219.hex
Opening port /dev/ttyAMA0, baud 500000
Reading data from ../Z-Stack-firmware/coordinator/Z-Stack_3.x.0/bin/CC1352P2_CC2652P_launchpad_coordinator_20220219.hex
Firmware file: Intel Hex
Connecting to target...
CC1350 PG2.0 (7x7mm): 352KB Flash, 20KB SRAM, CCFG.BL_CONFIG at 0x00057FD8
Primary IEEE Address: 00:12:4B:00:22:98:07:07
Performing mass erase
Erasing all main bank flash sectors
Erase done
Writing 360448 bytes starting at address 0x00000000
Write 104 bytes at 0x00057F988
Write done
Verifying by comparing CRC32 calculations.
Verified (match: 0xddfc152d)
'
@fair mountain Did you update HA for that or did the problem resolve by itself?
My update notifications are gone, too. But when I trigger a manual firmware check, I get "Device didn't respond to OTA request" for all devices.
As far as I can see, the firmware versions are the same as last week.
Hi people ! Merry Xmax !
Quick question : Is it possible to use a Zigbee HAT installed on a Pi4 as a ZigbeeOverEthernet device ? (Zigbee module = CC2538 from Cod.m)
I am currently using Z2M directly on the Pi4, but I would like to switch everything to ZHA directly on my NUC where HA is running.
Thanks !
zigbee devices (usually powered ones) will act as a router
I've been having general weirdness, with some lights not responding the last week or two. Haven't changed any hardware, just HA updates. Before I go chasing the issue, I wanted to check in if there are any known issues with ZigBee lately.
Am I being special? Sonoff zigbee 3.0 usb dongle is giving me agg. When I go to configure it, it asks me if I want to manually upload a backup, or delete network settings and create new network. I don't have a manual backup as it's new, and erasing the network throws up an error
Any ideas on what I can do to fix my network? I just added 30 or so inovelli blue switches. I'm at 150 devices on network, running 122022 zstack firmware. 139 routers. Everything was running great until adding the Inovelli Blues. Now everything is very sluggish and I'm getting a bunch of warnings regarding "No network route (205)". Am I at the point where my network table is too full and that I need to split into two networks?
Also having devices drop off the network
Hi, I reflashed my CC2652P with a different OS (Raspbian) and, after several attempts, it worked.
Now I have to repair all my devices - interesting enough that zigbee2mqtt now shows OTAs for alle the Tradfri bulbs. My E1812 button got updated as well.
How do I have to bind the E1812 to receive actions in Homeassistant?
(or button events like click and release
hey, i have a couple of rogue philips hue lights that i cant get to pair again
they stopped working and now i cant find them or pair them
I just plugged mine into the pi, asked it to find an pir but found to set to search the use the pin to reset the pir and it found it in seconds. Issue I have is I have the wifi/zigbee pro bridge as well and was hoping to link them both. Id still get alerts from the mobile.
What problem?
Hi @mellow geode it's me again. One question:
I've got an Zigbee Tuya RGB Controller, but my Stripe is RBG instead. So Colors are wrong when using the Color Picker. Is it possible to somehow remap color order?
Pretty sure that’s not possible. Couldn’t you just physically swap the G and B wires?
Hi, I got a device that lost contact (an Aqara/LUMI weather), and I removed it from the list. Now I am trying to add it again, but it never gets discovered. Any tips?
Others of the same gets discovered right away
what would be the best way to increase the range of zigbee network?
Get devices that act as zigbee routers (most mains-powered zigbee devices)
Exceptions include Sengled lights and most no-neutral switches
Just had an idea pop in my head, thought to share it …
And see if it could be possible
The Philips Hue Bridge is basically is Zigbee hub that connects to a wifi network and basically has a zigbee controller firmware built in
Is it possible to create a firmware for the Philips Hue Bridge to make it function as a Zigbee repeater ? Instead of a controller?
while it has a radio for it, the hue bridge does not connect via wifi.
there are also no custom firmwares out there
And as cheap as Zigbee devices are, I doubt it's worth people making one to be honest!
I'm sitting with a fresh install of HA, and are trying to integrate my Conbee II stick (latest firmware from September) - I've had it "connected" using deConz, but it couldn't find any of my Sonoff units
Now I've tried using the normal ZHA route, but when I've it from the menu (/dev/ttyACM0 - ConBee II, s/n: DE2292596 - dresden elektronik ingenieurtechnik Gmbh), it works for a bit, then I select Radio Type "deCONZ = dresden elektronik deCONZ protocol: ConBee I/II, RaspBee I/II" and then have to enter the "serial port setting", where "/dev/ttyACM0" is prefilled but it won't accept it.
Any ideas what I'm doing wrong?
It's likely asking you to use the serial ID instead of the port ID. Check the section below radio type here: https://www.home-assistant.io/integrations/zha/#configuration---gui
@raven jewel Got the same "Failed to connect" when using "/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2292596-if00"
What kind of machine are you running? Raspberry Pi?
Unplug it and re plug it it. Conbees get in a weird state sometimes
Sorry for the late responses - my discord isn't making any sounds :S
Its a Pi 4 - I've just restarted it and are gonna retry it
Make sure your power supply is sufficient
And that the Conbee is on an extension cable to avoid interference
PSU should be sufficient, trying an extension
Extension cable for the dongle did nothing, switching up the PSU
It's the same - Failed to Connect - dmesg gives me nothing useful, is there any other logs I can check?
Ehh, it "passed" after dis-/reconnecting a lot of time, then after choosing to "erase and start a new network" the logs now gives me this:
Error setting up entry /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2292596-if00 for zha
03:39:04 – (ERROR) components/zha/core/gateway.py
Couldn't start deCONZ = dresden elektronik deCONZ protocol: ConBee I/II, RaspBee I/II coordinator (attempt 1 of 3)
03:39:04 – (WARNING) Zigbee Home Automation - message first occurred at 03:38:54 and shows up 3 times
No response to 'Command.read_parameter' command with seq id '0x02'
03:39:04 – (WARNING) components/zha/core/gateway.py - message first occurred at 03:38:54 and shows up 3 times
No response to 'Command.version' command with seq id '0x03'
03:38:01 – (WARNING) components/zha/config_flow.py - message first occurred at 03:35:48 and shows up 2 times
No response to 'Command.read_parameter' command with seq id '0x02'
03:37:47 – (WARNING) components/zha/radio_manager.py - message first occurred at 03:35:39 and shows up 2 times
Should I still install deConz?
Wild guess, but it might be that your Conbee is dying, they're not great Zigbee dongles anyway
Feck! It's practically new, been sitting in my drawer for like ½ a year though 😛 What Dongle should one go with then?
I've got a Sonoff ZB Bridge with an old Tasmota version on it and a CC2531 stick lying around, could they perhaps be used?
The pins have recommendations. I have the Sonoff plus stick.
@raven jewel Thank you for your help and suggestions, sounds like I'm going to have to continue with it tomorrow 🙂 Gotta go to bed, the kids are bound to wake up early tomorrow and It's my turn to get up with them, so the GF can sleep in 🙂
Hello, I bought this https://moeshouse.com/products/1-4-gang-tuya-zigbee-wireless-12-scene-switch-mechanical-push-button-controller-battery-powered-smart-home-automation-scenario-switch-for-tuya-smart-devices and I successfully integrated in Z2M, but in my HA I can see only a binary_sensor Action and when I click onmy taster i can see that value of that sensor is changing to single_1, single_2, etc.
My question is: can I add something in the config file of moes switch on the side in Z2M to have presented switches in HA?
or I need to write automation for listening mqtt event?
It must be a sensor, not a binary sensor to be displaying those values.
And you could use #templates-archived to make a binary sensor for each action but that seems rather unnecessary.
do i need to link the zigbee device before i install them or i should install them in the final location then link up from home assistant
Pair (link) them in their final location
If you do anything else you risk them not working
means i need to bring my HA around the house?
It's a mesh network
They're an idiot
just wanna confirm
I can confirm, they're an idiot
Well, that's how you set up the router devices
You leave your host with the Zigbee stick where it is, don't move it
Then you pair the nearest router device, then the next nearest, and so on
Moving slowly "out" from the server
Once done you pair all the end devices (sensors)
First there were these update notifications, which are now gone (without performing any updates). Then I couldn't check for new updates anymore getting the "Device didn't respond to OTA request" message.
What are the best zigbee bulbs? Looking for floods and normal, rgb and white, routers, and can be updated using zha? I have a theory my fleet of sengled crash and turn on randomly but I can’t update them and they aren’t routers.
Hi. I have ikea shortcut button and ikea wireless plug. Is it possible to make them work together without having any zigbee network/coordinator in the house? I want to setup remote light using this in my parents house but they don't have any home automation system
You can bind them directly to one another, press and hold the reset button inside the shortcut button near the plug until the light on the plug flashes a few times
no need to reset the plug as well?
Not usually. If you do, then you'll need a paperclip to stick into the end. But I've not previously needed to do that
alright lets try it
it kinna works except I need to press the button 20 times and sometimes it reacts and sometimes not
ok I think I get it
Double click = off
single click= on
thanks
Anyone use the slaesh stick? I've tried updating and I keep getting a timeout error
I do with zigbee2mqtt.
I remember my friend once tried to flash it and did something wrong and bricked it
he had to buy a new one
I upgraded the firmware on it once and I'm not touching it now unnecessarily
It's still serial flashable if you flash a version with the wrong bootloader
I get the feeling this won't be easy?
So how do I go about fixing this?
You would need a JTAG adapter to flash the right firmware
What does one of them look like?
Or a Pi and some duponts: https://gist.github.com/tobiasfrejo/d98e9f4cbbc6893662ab032b06388685
i'm trying to pass through in docker-compose my usb dongle stick. '/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_94374ea03fc8eb11977ec1c3de5b81b4-if00-port0:/dev/ttyUSB0' should work, no?
when i run z2m it can't find /dev/ttyUSB0
I have a USB to TTL FT232RL that I used once to flash my sonoff plug with tasmota, will that help me at all?
That's what I've got
nevermind figured it out. was an issue with recreating image w/ new docker-compose.yaml
i've now tried two different coordinators (sonoff and tubezb 2652P) and i can not get network to work. i keep getting the following errors: 2022-12-26 10:42:18Error: CommandResponse 0x00158d0004ff2e08/1 genOta.queryNextImageResponse({"status":152}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms)
According to the doc on slaesh website (https://slae.sh/images/pinout.svg) this looks like the same pinouts as what is in that link you sent? Besides VDC? The slaesh board has VCC_IN? Surely I'd be able to use header pins and connect them up?
I think I'll be able to do it using the pins according to the slae.sh docs and using a raspberry pi then
Hi everyone. I got a Aquara pet feeder yesterday and had no problem pairing it and interviewing it in ZHA, but I'm not able to dispense food with it from homeassistant, and after a few hours is shows up as offline on ZHA. Any reason it could be doing that? Its plugged into mains power so it shouldn't be a battery issue
When I visualize topology, I see the feeder there, but not connected to anything
Looks like it is due to the new inovelli blue switches causing issues with my network
0x885F: Update device availability - device available: False - new availability: False - changed: False
Device 0x885f (54:ef:44:10:00:45:8b:65) left the network
Well this is what the logs say
Is this thing leaving the network as soon as it joins it?
Welp. Unjoining it and rejoining doesn't help
How so?
There was a bad batch of switches with defective radios, you should be able to tell based on their IEEE address.
this is new batch that came in. Air gapped all of them and network returned to normal
What issues are you referring to?
network essentially doesn't work
everything times out
SRSP, No network route, time out > 10000
i've replaced coordinators with same issue
tried a few zstack firmwares as well, same outcome
i think the switches are just flooding the network with data
I'm trying to add switches back slowly and will likely try two networks to see if that improves things
also making sure energy reports are turned off
What other routers are on your network?
Hi. I've been using Sonoff ZB Bridge with tasmota firmware as my coordinator with zigbee2mqtt for almost a year. All well until the 1.28.0 update. Starting from 1.28 I had mixed results. Since I had a zzh! cc2652r sitting somewhere in my drawer, today I decided to give it a go this time with ZHA integration. Now, since I run HA on proxmox I had to do all the magic with USB IDs and such. Done. When installing the ZHA integration in HA, I choose manual (if set to auto it sets the coordinator at /dev/ttyUSB0 which is not always true after vm restart, so I wanted to use the longer: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0) but then I get the next screen with port speed setting and data flow control (https://itpasja.pl/ext/zzh.png) and the question is: what is the speed for zzh! and what is that mysterious third data flow control option that has no name?
I've got 137 mostly hue bulbs
And how many of these Inovelli switches?
It was 20, now down to 2 and slowly increasing
Was hoping to get up to 50
Hmm. It could be that Z2M's default reporting interval for these devices is flooding the network with continuous traffic. What is the reporting config for these bulbs and the Inovelli switches?
How would I find that out?
Z2M should let you set up reporting for each device.
Power was the only thing I saw and I bumped that out as much as possible
Hey guys, is it possible to migrate from zha to z2mqtt without having to repair all devices? After six months of no issues half my ikea remotes stopped working and also refuse to appear in pairing
I have almost 100 devices, I’d rather throw everything out that set them all up again
I mean a couple paired after 20 retries right next to the coordinator
Are you using a Conbee by any chance?
Yes
Conbee II
@raven jewel please don’t leave me hanging, I have a very angry wife over my head
lol
Well first of all it's boxing day, so I am watching a film with my family.
Secondly, did you check the pins? Conbee are incredibly susceptible to interference so you really must use a USB extension cable with it
I have it on a 3 meter extension. The whole set up was working flawlessly for almost 8 months. Now that you mention interference I have a coral usb but it is running 2 floors away from the conbee
Would replacing the conbee solve the interference issues?
Hi which dongle to buy -e or -p? What’s the main difference ?
It seems -e is the newer version
E is experimental
If I replace conbee with a sonoff will I need to set up everything again?
More or less, it's a different chipset, so not fully supported except with ZHA
Either is a good choice for ZHA. P is the only good choice between the two for zigbee2mqtt since the E only had experimental support
Haven't had an issue with the experimental driver with the Skyconnect, FWIW
I have it working with ZHA. Seems to be ok for the most part...one day a number of devices went offline, but could not find out why....have moved the gateway to a different part of the house...so far so good
100 devices isn't that much
What?
Yes I agree it’s not that much but resetting, naming, assign to groups and the fox all the automations
Oh I just read back. Now I see the context
You can replace it with a stick that isn't as sensitive, but if you have environmental problems I would solve those first. If you do end up buying a new stick, just plug the new stick in, click the "Migrate" button in ZHA's config, and it'll move the network settings over to the new stick.
Is there a way to wake up or refresh a specific zigbee device? My aqara pet feeder has shown up as offline for 6hours. Its about 8 from two zigbee devices and about 15 and 20 feet from three others. Its plugged into mains power so I don't know why its not coming online
If it's been offline for six hours, that means that no data has been received from the device in that time. It's unreachable. Have you tried unplugging it and plugging it back in?
@austere patio Yep, done that and also tried swapping it momentarily to battery power to see if that helped and it didn't. It only every really seems to successfully interview and then that's it
What routing devices do you have?
If it can switch to battery power, it probably isn't itself a router
Possibly, but it does show up in the ZHA visualization as a router, and I assumed that info came from the device itself since it was plugged into mains power
That said in the same room with it about 5' away is a Sonoff S31 plug with another one about 10' away
In the adjacent room about 8' away are a pair of Zemismart zigbee blind motors that are also plugged into mains power.
They're all showing on ZHA's visualization as routers
One notable thing and I wonder if it matters is when it is interviewed, it does seem like the LQI and the RSSI are both unknown
Can you upload the diagnostic info?
Hmm, it is a router
Yea, looking at what everyone else has been writing about this feeder and the new integration from the latest release, it seems like everyone has had very little issue with it. Other than seeing no RSSI, and LQI everything appears like it should work. I guess its entirely possible this particular unit is defective, but that would be a little odd of an occurrence but totally possible.
If you see no LQI and no RSSI, no packets have been received from the device
So I guess the question then becomes, how do I force packets to be sent and received then? Like waking up the feeder?
Hmm
I know I tried manually triggering the feeder in the front, but that didn't wake it up
It should just happen, there's no way to force packets to be sent other than triggering the device (which is only ever necessary for end-devices that run on batteries). I suspect the Sonoff router may be the problem. Try removing or power cycling it and see what happens.
Good idea.
Give me a few mins
Well I power cycled the four closest zigbee routers and it doesn't seem to have changed anything.
I take that back. All the other end devices have better connections
haha
Did you move it after pairing to the network? From my understanding Aqara devices associate with 1 router and will never heal if they lose connectivity, so you'd have to re-pair with a closer router to wherever you placed it
Nope. Its been in the kitchen every time I've paired it
Only one time did I try it somewhere else in the house and it did the same thing. So I did it again in the kitchen
The kitchen arguably should be the best spot for it anyway with 4 other routers in within 10 feet of it.
I haven't used ZHA, but at least in Z2M it's possible to allow joining to a specific router, i.e. force it to join via one close by rather than letting it pick one on its own
Yea when I started doing zigbee I really struggled wrapping my head around Z2M. I was hoping the Zigbee toolbox in HACS would let me do just that
Click on the device's info page and you can choose "Add devices via this device" in a dropdown
Oh whoa!
Let me try that
OK so now I'm showing an LQI and an RSSI, but I'm still getting no response when I send it commands, and its still not showing up linked with anything in the visualization
Ended up readding and adjusting the power reporting for each switch. So far, seems to be behaving. If continues to work tomorrow I'll start adding more switches to the network
Have you installed any of the inovelli blues?
Just one for testing
Interesting. Restarted my instance and once again unknown. Lost connection.
Hello, just received 2 Tuya ZY-M100 presence sensors, and all the data I’ve seen online shows at least partially working with ZHA (just a binary sensor for presence), but when I add it, I don’t even get that. I have no entities for some reason
I might try power cycling again and if that doesn't work I'll try add devices through another device
Ok I'm once again getting the same issue. Losing connection after the initial interview. Even if I chose another device to add the feeder through. I'm inclined to believe this particular feeder might have something wrong with it.
Hello everyone. Since yesterday I lost signal of a device (lixee_tic). It’s a device I plugged into my electric provider to measure the consumptions of my house. Yes it’s a bit far away from my zigbee coordinator but I added some device between them so the signal can be routed. But it seems it’s not routed. Any advice please ? Here is my zigbee schema : https://photos.app.goo.gl/BAmZkZU5ZjKUzBFm9
I have a sonoff switch outside the house which is 3-4 meters direct from the lixee and à Adeo plug 5-6 meters with a wall from the lixee
How can I check for environmental problems? The whole system had been working without issues for months
head's up, if anyone needs to use a hygrometer, stay away from sonoff
i've had 2 now have the humidity sensor go fubar now after prolonged exposure to high humidity
It’s only the remotes that have problems, I can operate all the bulbs and look at the sensors from HA just fine
Are these IKEA remotes?
IKEA remotes have been known to have an issue where the battery drains very fast when they're not paired to their hubs.
@raven jewel i am trying with new batteries. Now i have the same issue with one of my blinds, its 1 meter away from a bulb, im trying to pair it via this bulb, and its just not appearing
One thing i notice is that the device discovery in zha is not timing out, is this something new?
I don't know. I use Zigbee2MQTT
so back to my question from yesterday, if i move to zigbee2MQTT do i have to re-pair all the devices?
Not sure...I don't have the sonoff stick.
hi
I just bought Conbee II zigbee stick
and tried deconz
and ZHA
I added a Philips hue ceiling light and a Hue Motion Sensor
I had issues with Deconz on my ceiling light
so I switched to ZHA
and it works perfectly as of now
I didn't try Zigbee2MQTT because I heard it has issues with the Conbee 2 stick
however I want to keep my home as up to date as possible, and as far as I know the only zigbee platform that supports Philips Hue OTA updates is Zigbee2MQTT
is it worth moving to Zigbee2MQTT using the conbee ii stick or not ?
FWIW, I have zigbee2mqtt with Conbee II. No problems as such, but it is a hassle to set up.
I just received SkyConnect though. Does it support Green Power directly?
You nees to re-pair almost always when changing software or controllers.
That's a pity
Hi, question about ZHA quirks: I see in github that for my TRV (integrated via ZHA) a fix (link: https://github.com/zigpy/zha-device-handlers/pull/1082) has been produced but it's not working for me ... I'm not sure this has been "merged" in HA. How can I check, or is there a place where the zigpy releases and integration in HA is documented or described ?
Hi there, I do also have some question about zha quirks. Is there an option to point specific quirk for device? (i see that my device have few quirks and actual one does not work for it - tuya ts0012)
the quirk has to have your device's model and manufacturer id
none of the quirks in https://github.com/zigpy/zha-device-handlers/blob/dev/zhaquirks/tuya/ts001x.py define manufacturer id only model one and i see few quirks with same model id
i have as some people say another f*g tuya variance of double channel switch, and it does not work properly (when activating one switch both are enabled)
Quirks match based on signature as well. The current quirk will be listed in the device info page, as well as in the diagnostics JSON
i've got it but it seems it takes last quirk that has same model number
The ENDPOINTS part has to match exactly as well
not sure if exactly but that makes more sense, so i suppose i will need to report a bug?
If an existing quirk matches, your device is seemingly indistinguishable from another TS001x variant
What are its manufacturer and model IDs?
And what quirk is currently matching?
_TZ3000_jl7qyupf
zhaquirks.tuya.ts001x.Tuya_Double_Var05
https://zigbee.blakadder.com/Tuya_SML-02Z-L.html it should be supported from what i see
model: TS0012
It is "supported" according to the model id
But Tuya decides to change the firmware without changing the ID and then you have this
I know, i love "standards" 🙂
I had also saw that i can set switch mode per endpoint (to command or event) i assume if debug logs says attribute not supported it means that this device is unable to handle that settings? :/
Anyone have any luck using Tuya ZY-M100 presence sensors with ZHA? Or should I just start over and rebuild my mesh with z2m?
Luck in what? It works with ZHA
Lmao, I paired two last night, and had nothing but unavailable LQI and RSSI. Just checked it now and they both have illuminence and occupancy. Oh well, ignore me lol
Zigbee gremlins...
Hi, where can I find which zigpy version is used by my HA instalation, is there a way to find this ?
Definitely less functionality than with Z2M. I was contemplating changing around some different sensors and what not, would there still be any good reason for me to switch from ZHA other than the additional settings on the presence sensors? I don’t have any experience with Z2M but I’ve heard it can be a bit tougher to set up
TX !!!
Not having the functions now doesn't mean they won't be added in the future
Makes sense. I’ll stay put
Just curious, what are some zigbee devices you guys have really enjoyed using this past year?
https://www.zigbee2mqtt.io/devices/RTCZCGQ11LM.html is really neat
https://www.zigbee2mqtt.io/devices/GZCGQ01LM.html are handy for lighting automations
Yeah I have one of those Lux sensors in every room, love them.
I enjoy anything Tuya ||they bring me hours of entertainment watching people struggle with them||
Haven’t gotten around to anything in the tasmota / local Tuya land yet, but I might be ready to give some of that stuff a go
Haven’t exactly been thrilled with the newest Tuya integration and having to renew/extend an IOT developer license every 6 months to maintain functionality, so I’m definitely looking for a new way to deal with my Wi-Fi stuff
Honestly, before the somewhat recent Tuya integration change earlier this year, I had been using Tuya with HA for years without any issues. Every single device was brought into HA, and I never really had any issues to speak of. Now that the integration changed, it’s become a headache
The problem is that Tuya is an over-arching label applied to a wide range of devices made by many people
Some of it is really good, some amazing, and lots are made to a price point
If you get the good stuff you're fine, if you get the rest of it ...
I’ve gotten to the point that I’m trying to move most of my stuff over to zigbee
But tbh most of my Tuya based stuff has been more reliable than my zigbee stuff
Is your Zigbee stuff also Tuya?
Which may not be entirely zigbees fault, as I live in a townhouse and there are neighbors close enough to me that their networks could be causing the congestion
Or Sonoff?
Or Osram 😄
Nah, mostly Sengled bulbs and Lowe’s iris sensors
Wouldn’t touch an osram bulb again if someone paid me to
Are any Sengled bulbs routers?
Nah
Not the ones I have
Oh I have a few ikea plugs and one ikea repeater
So a few routers sprinkled around
The only Tuya devices are the ZY-M100 presence sensors I just added
I have a repeater in the middle of my house, and an ikea plug (router) in every room. I still get at least one or two bulbs a week that will randomly stop working. Their state will still report in HA, but turning them on/off doesn’t do anything until I’ve cut power to the bulb over and over again for like a minute
Wi-Fi stuff has been mostly reliable for me, but I just had to get another AP due to the congestion. Hopefully that’ll clear up any issues I’ve had. I think it’s gonna require me to pick a new zigbee channel though, which comes with its own headache
I am at wits end, need some help with Zigbee
Most of my lights turn on randomly, I am getting all kinds of routing errors, things just don't respond. All Sengled bulbs the ones that turn on randomly, usually at night, start up blue or flash red.
I have 138 zigbee devices, migrated to a SONOFF Dongle E from Hubszb.
I have like 50 router devices even though the sengled's are just end devices
EZSP obvioulsy
A lot of this in the logs:
2022-12-27 12:04:09.529 DEBUG (MainThread) [bellows.zigbee.application] Processing route error: status=EmberStatus.SOURCE_ROUTE_FAILURE, nwk=0xb58f
2022-12-27 12:04:37.858 DEBUG (MainThread) [bellows.zigbee.application] Processing route error: status=EmberStatus.MANY_TO_ONE_ROUTE_FAILURE, nwk=0x9e71
2022-12-27 12:04:37.916 DEBUG (MainThread) [bellows.zigbee.application] Processing route error: status=EmberStatus.MANY_TO_ONE_ROUTE_FAILURE, nwk=0xb569
2022-12-27 12:05:07.610 DEBUG (MainThread) [bellows.zigbee.application] Processing route error: status=EmberStatus.MANY_TO_ONE_ROUTE_FAILURE, nwk=0x8af3
2022-12-27 12:05:07.797 DEBUG (MainThread) [bellows.zigbee.application] Processing route error: status=EmberStatus.MANY_TO_ONE_ROUTE_FAILURE, nwk=0x9e71
2022-12-27 12:05:07.844 DEBUG (MainThread) [bellows.zigbee.application] Processing route error: status=EmberStatus.MANY_TO_ONE_ROUTE_FAILURE, nwk=0x2e1b
2022-12-27 12:05:09.107 DEBUG (MainThread) [bellows.zigbee.application] Processing route error: status=EmberStatus.MANY_TO_ONE_ROUTE_FAILURE, nwk=0x8af3
2022-12-27 12:05:37.556 DEBUG (MainThread) [bellows.zigbee.application] Processing route error: status=EmberStatus.MANY_TO_ONE_ROUTE_FAILURE, nwk=0x9970
2022-12-27 12:05:37.938 DEBUG (MainThread) [bellows.zigbee.application] Processing route error: status=EmberStatus.MANY_TO_ONE_ROUTE_FAILURE, nwk=0x9e71
2022-12-27 12:05:38.554 DEBUG (MainThread) [bellows.zigbee.application] Processing route error: status=EmberStatus.MANY_TO_ONE_ROUTE_FAILURE, nwk=0x8324
2022-12-27 12:05:38.684 DEBUG (MainThread) [bellows.zigbee.application] Processing route error: status=EmberStatus.MANY_TO_ONE_ROUTE_FAILURE, nwk=0xf683
Do you have source routing enabled?
Yes
Try disabling it
I thought source routing was basically needed for large meshes
zha:
zigpy_config:
source_routing: true
ezsp_config:
CONFIG_SOURCE_ROUTE_TABLE_SIZE: 150
CONFIG_MAX_END_DEVICE_CHILDREN: 0
50 routers isn't a lot
Just comment out anything related to source routing in your config and see what happens
43 routing devices, the coordinator, and 96 light
Doing it now
I am on a Pi4b with an NVMe drive. CPU and memory never gets high because its 8gb and quad core. The coordinator is on a 3' extension cord plugged into USB 2.0. All of my WiFi is broadcasting on channel 11 with ZHA on channel 15 so there shouldn't be much if any interference.
Once I disable source routing how long do you think it will take to fix the mesh?
I was on ZHA groups for my bulbs but that with adaptive lighting was killing the network. Constant busy. So I went back to ZHA groups and that went away.
2022-12-27 12:26:22.589 DEBUG (MainThread) [bellows.zigbee.application] Processing route error: status=EmberStatus.SOURCE_ROUTE_FAILURE, nwk=0xbb4c
2022-12-27 12:26:22.674 DEBUG (MainThread) [bellows.zigbee.application] Processing route error: status=EmberStatus.MANY_TO_ONE_ROUTE_FAILURE, nwk=0xf624
2022-12-27 12:26:50.681 DEBUG (MainThread) [bellows.zigbee.application] Processing route error: status=EmberStatus.MANY_TO_ONE_ROUTE_FAILURE, nwk=0xacc8
2022-12-27 12:26:50.726 DEBUG (MainThread) [bellows.zigbee.application] Processing route error: status=EmberStatus.MANY_TO_ONE_ROUTE_FAILURE, nwk=0x0232
2022-12-27 12:26:51.067 DEBUG (MainThread) [bellows.zigbee.application] Processing route error: status=EmberStatus.MANY_TO_ONE_ROUTE_FAILURE, nwk=0xb569
Removed all source routing but still getting some of these
Are you able to elaborate on that? I use ZHA and adaptive lighting as well, so I’m curious as to what issues you were having
So I had all of my lights in ZHA groups tied to rooms. So Dining Room, Living Room, etc. Then I had adaptive lighting set up for each room as well. In the config I would tell Adaptive Lighting to control the ZHA group. I would constantly get EmberNet NETWORK BUSY failing to enqueue commands.
When I go to light groups in native Home Assistant all of that goes away.
The other issue with ZHA groups which is probably tangential to this current problem is that if one light would turn on randomly (happens a lot here) then it would toggle the whole ZHA group to turn on.
That's one thing I still am uncertain of. Are zigbee groups more or less efficient in terms of coordinator use?
It's a network wide broadcast I think
Zigbee groups send broadcasts that bounce around. They'll "instantly" toggle a bunch of lights, but if you send them continuously, it'll cause unnecessary congestion
So at this point nothing is happening in my house. Any light group backed with zigbee is just not responding.
I toggled a group on and one came on nothing else. I toggled the same off and nothing happened. Other light groups do nothing too
Still have that HUSBZB-1?
I have that and I have the sonoff P version too
I think others have had better luck with sengled than I have. I ended up replacing them after they kept falling off network
I bought all 3 because I had no idea if that was the problem
But you are now using home assistant groups right?
I am using HA groups
If so that's different
At this point I would buy 100 new bulbs if I new what would work
It's the same as sending individual commands to each light
I think the individual is better with adaptive lighting because you end up DoS'ing yourself otherwise
If you've reset the HUSBZB-1 (or ran the ZHA migration where it did this for you), run a packet capture for a few minutes bellows -d /dev/serial/by-id/YourHUSBZB dump -c your_channel_number -w capture.pcap
You mean connect the hub to my local PC and do that?
It'll be accessible from within the HA container, or from any Python environment where you run pip install bellows
I did run the migrate radio functionality
In that case it's safe to do. People sometimes migrate without resetting the old radio, which causes massive problems when it's plugged in again and starts trying to control the same network
While the packet capture is running, try toggling individual lights a few times
When I went to the new radio it did say something about IEEE didn't match backup and it would overwrite. Not sure if that was OK. Assuming it overwrote the backup with the new dongle IEEE
Yep, that's normal. Did you check the box to overwrite the IEEE address?
I think it uses this chip: https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers?tab=downloads
Well this is fun
What did you replace them with?
Driver won't install
Hue, wasn't cheap
And they work directly with ZHA? No hue hub needed?
Would this have anything to do with the issue I’ve been having with adaptive lighting? Occasionally, when turning a light off that’s being adapted, the light will turn back on shortly after. Not really sure how to stop this from happening other than telling adaptive lighting to turn off when the bulb turns off
Correct. Buy a hue switch though so you can reset bulbs if necessary
That's been a problem for me as well
The way to solve this is to turn off adaptive lighting when you turn off the light group.
The little dimmer switch?
And don't use ZHA groups
Yeah
And that lets you reset bulbs? Like when they stop responding in HA?
Yeah that’s more or less what I’ve been forced to do
It allows for inclusion
Haven’t actually used lighting groups though, just entered each bulb in manually in Adaptive lighting
Ahh cool, didn’t know that. So it can trigger inclusion in HA? Not sure if I’m understanding it correctly
Essentially put zha or z2m into inclusion mode to allow devices to join but you need the bulbs to also initiate their inclusion. Most other bulbs you either turn on/off a number of times to initiate but hue requires either their hub to join then remove or easier is to use their switch and hold the top and bottom buttons for around 12 seconds to initiate
How do you choose which bulb to put in inclusion mode with the switch?
Is it a proximity thing?
Is there a good guide on installing Sonoff usb 3 P dongle with ZHA? I plugged it in and reconnected but they’re issues, mainly it keeps loosing devices daily. I want to reinstall it from scratch
@austere patio Do you know how to pass the device in Windows to Bellows? Its on COM3
I just can't figure out the right path
Just use COM3 as the path
You hold it within like 5 cm of the light
Maybe 10
Alright, I always thought it was\.\COM3 but that worked
Do I just open this in Wireshark?
Yeah. If you don't mind, can you send me a copy along with your ZHA network key?
Let me see how to personal message here
Nothing sensitive on my Zigbee network and I guess I can always regen if I care
Side note, what’s the easiest way to change zigbee channel? And is it possible without having to re-pair all of your devices?
Depends on your integration though. Z2M will require a few files to be edited.
So I have to install zigpy alongside ZHA?
It's already installed in the HA Docker container
But you'll need to install the above command line tool, the command is in the README
Do I need to disable ZHA before installing?
Yeah, they both can't access the radio
So disable ZHA, install zigpy command line tool, run the change channel command line, then enable ZHA? And just check to see if any devices have stopped responding, and just remove and re-pair those?
Alright cool, thank you so much. I run the install command in the terminal & ssh window, right?
Make sure you're using the "SSH & Web Terminal" addon (not the other one!). You can follow this chunk of instructions here: https://github.com/zigpy/zigpy-znp/blob/dev/TOOLS.md#in-home-assistant-os
So after having some problems with z2m in docker + tasmotized sonoff zb bridge I decided to give my drawer-sitting zzh! cc2652r dongle a try. My HA sits on Proxmox VM. I set the passthrough, ZHA integration perfectly auto discovers zzh! at ttyUSB0 (I opted for the by-id-string just to be on the safe side). The pairing of the routers (few sonoff zb minis, few tuya zb mini likes, few sonoff basic zb r3s) done flawlessly, end devices (like aqara pir, sonof pir, sonof th, xiaomi lux, etc.) also with no problems at all. Everything seems stable until after a few hours. ZHA fails to load and the logs say the coordinator is unavaliable: 2022-12-27 20:01:03.214 WARNING (MainThread) [homeassistant.components.zha.core.gateway] Couldn't start ZNP = Texas Instruments Z-Stack ZNP protocol: CC253x, CC26x2, CC13x2 coordinator. If I check the all hardware section in HA the ttyUSB0 is gone. same when checking proxmox - no such device on pass-through. Restart of HA and/or proxmox does not help. But if I re-plug the zzh! coordinator and then restart HA everything gets back on the right track. After a few hours it's all the same - coordinator not found. Anyone?
What host hardware, and what's the overall usb situation? Lots of things plugged in? Just one stick? Hubs? Extension cables?
Proxmox on Fujitsu Mini PC (intel i5, 16gb ram, ssd). No other USB devices.
I’m trying to disable protection mode in the add-on but I don’t see an option for it in the configuration page
It should be the last toggle (at the bottom), near the Start/Stop button: https://i.imgur.com/RCvplcz.png
Ahh I was looking in the config page. Thank you!
I tried doing the install command and it says zsh: command not found: $
The $ is just to denote a non-root shell. You run the stuff after it.
It’s telling me I should use a virtual environment instead of just installing it. Should I be conscerned? Lol
Nah, it's fine
It’s having me upgrade pip first I think
You can ignore that too
Then should I re-run the install zigpy command?
Just run zigpy alone to see if it installed. It should have.
Hey Guys,
to be honest I'm from Germany and my English is a bit bad... but yeah, I hope you will understand!
I've recently bought a Raspbee 2 and connected it to my Raspberry Pi, I've tried it in many configurations with ZHA in HomeAssistant, Zigbee2MQTT and now deCONZ with Phoscon. I made a group in Phoscon called "Deckenlampe" to control my ceiling lamp consisting of 6 "TRÅDFRI Lampe GU10 WS 400lm" lamps. I've done the same with ZHA and Zigbee2MQTT, but with that I created the group in HomeAssistant, but the problem is the same in all configurations.
Everytime when I change the brightness, the slider first go the desired position, bugs then back the first position and finally bugging to the right position, I'll send a video from it.
Do you have any idea how to fix it? Is there maybe a way to tell HomeAssistant or deCONZ that it should ignore refreshes from deCONZ for 2 seconds?
I've searched very much but didn't get any good idea how to fix it.
So I just got a second wireless AP, and I’m trying to find the best channel for my zigbee stuff when I install this second AP. Currently I’m on channel 20, and my hubz stick thingy is about 10 feet away from my WAP on Wi-Fi channel 11. I’m in townhouses and there are a ton of wireless signals around me, so many that it’s hard to get a consistent reading when using a Wi-Fi analyzer app, but I believe the second WAP will be installed about 30ft away from my zigbee coordinator, and set to channel 1, leaving channel 6 empty in my house, but still congested because of neighbors. My question is whether or not I should try to set the zigbee channel to something like 17/18 (in the middle of Wi-Fi channel 6), or change it from 20 to 15 so that it would only register interference from the sideband lobes of my further away AP, and no interference from the AP that it’s closer to
Both APs would be set to 20mhz channel width to minimize overlap with zigbee
If you still have that Python environment open, try the energy-scan tool. It'll show you the noise on each Zigbee channel.
zigpy radio znp /dev/cu.usbserial-1420 energy-scan
I tried this, and it gave me a bunch of error logs. Most pressing part was “no such file or directory: ‘/dev/cu.usbserial-1420’
The /dev/... part is specific to each computer and environment. You'll need to figure out which USB device your stick is: ls -l /dev/serial/by-id/. That should give you a symlink like /dev/ttyUSB1 or something.
came up with a different error, im trying to copy it to paste it in the other chat we have, but copy paste doesnt appear to work
zzh! + ZHA (Ha on Proxmox)
Is there an alternative for Mac for Flash-Programmer? to flash sonoff
I used a python library
Tradfri motion sensors - under Device Configuration, what's the difference between "Delay" and "Duration?" Thanks!
^-- Google not helpful here.
just do one at a time
Edit: Re: Delay vs Duration.
I'm messing around with the settings trying to understand how they work but not clear yet.
I think my Conbee II shit the bed. Anyway I can test this and confirm?
Anyone else install Inovelli Blue switches?
What makes you say that?
No response to devices, but I can see activity in MQTT Explorer. All lights just stopped working via HA or publish via MQTT Explorer
I assume you rebooted...?
If you can't send stuff but can receive stuff, that sounds like interference to me. Make sure your Conbee is on a USB 2.0 extension cable and away from 2.4GHz interference sources like SSDs, USB 3.0 ports, WiFi APs, etc.
Yea, rebooted a couple times now. Tried a different USB slot on the RPi (USB 2.0 not 3.0), tried moving the pi out of the server rack in case the enclosure was an issue, tried disconnecting any 2.4ghz devices near that I could to help with any interference too
I had to put mine on a 6' USB extension cord
Move away from the networking hardware.
It's not on an extension cable, but it never has been I've been running this setup for more than a year. Do you think if it's been fine this long, that an extension cable will solve anything?
Worth a shot
Mine had intermittent problems that were 90% solved by moving it away from the other hardware.
Definitely. Try it if you have one. I'm not familiar enough with Z2M to help debug this exactly but if you can receive updates but are unable to send commands, that's almost assuredly an interference problem.
The only major change I've done recently is patched it into the server rack through a dumb switch into a PoE switch, instead of directly into the PoE switch (and changed the cable to a slim gauge) - but this is just for network and power, I don't imagine it could cause these issues
Shit, I'll give it a shot. I don't have an extension cable with me but I'll find one on Amazon
Get a long one then
Change channels?
It absolutely could. You've added interference 😂
Long extension and change channels.
I had to connect all of mine end-to-end when testing the Conbee
the dumb switch is the interference?
A long-term solution would be to get a coordinator less sensitive to interference, like a CC2652, but an extension cable is cheaper and easier to set up
Do wifi survey to see where the traffic is since Zigbee uses the same 2.4GHz spectrum as wifi. Then change Zigbee channels away from it.
THere are a few good pages that discuss this.
I was looking at Tubes just now
3m extension cable otw
Tubes is a good way to go imo. support a member of the community and he's really responsive to issues
I have 2 “good” ones installed and 1 “bad” one installed all working fine. Have another in pieces flashed as a router left from troubleshooting a theory about the bad ones before the hw issue was fully known
How many devices on your network?
- Maybe 10-15 of those end devices with dead batteries 🤦♂️ or my neighbors Sengled that joins everyone I permit joins
😂
I'm still running into issues with flooding I think. Trying to split my network into two now to see if it fixes it
What integration are you using?
Z2m
Anyone know of a Switch that doesn't kill power to the bulbs, so that Smart Bulbs can be used, but will just pass through power at the "switch location on wall" ?
I have 4 canister lights in the kitchen, I'd like to individually control each bulb, but replace the 2(?) way switch on the wall to prevent power from being interrupted to the Smart Bulbs, but would be nice to have like a Zigbee Scene Controller there on the wall instead maybe, if possible
us or europe?
US
i think enbrighten and inovelli are the two that come to mind
I was looking at Enbrigten, the documentation I've read so far all mentioned only Permanent lighting (non-smart bulbs) since it turns on/off a relay in the switch to kill power to the fixture - unless there is some workaround for this outside of their documentation 🤔
inovelli best bet then w/ their 2 in 1 blue series
though they just came out and are still ironing out some issues
Also appear to be on Back Order
Hello, i am thinking to use Zigbee for my home automation and was thinking about how to build a strong network. I don't want to switch my physical switches, which i hear since the run on mains act as extenders. Can I instead install the switch relay in the light fixture and will it still act as an extender?
Assuming it has a neutral connected, generally yes
Hello, anyone with lidl zigbee?
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?
- Which Zigbee integration? ZHA, Zigbee2MQTT, deCONZ?
- What coordinator are you using (make and model, not a vague that Sonoff stick)?
- What device are you trying to add (again, make and model)?
ZHA
Radio type: ezsp
1 ) ZHA
- Model TYGWZ-01 manufactured by Lidl
- re add devices that already where working
What devices are you trying to pair?
a blinder, ms-108zr
I put device (that was working previously) in pairing mode, search in home assistant for new zigbee device and nothing happens
hello, happy holidays! having an issue with some HUE downlights. 2 of them check in as they should (last seen always within 5 min) but cannot issue any light_on/off calls. just wont turn on/off. but they do respond to group calls (they are part of a ZHA group, and if i turn on/off the group, so do they) any suggestions on troubleshooting something like this? ZHA/SONOFF -E adapter.
so you have Hue lights that only respond to group commands but not to any requests when you target them alone?
does a power-cycle help temporarily? also, do you have IKEA mains-powered devices on your network?
correct - power cycle on one of them helps temporarily, the other no change. no IKEA mains. lots of hue lights, 70 or so. inovelli wall switches (bad batch removed)
How long is "temporarily"?
it will respond to one or two commands directly, and no more
So the only routing devices on your network are Hue bulbs and Inovelli switches?
yes sir
i removed these bulbs, waited a good hour, and rejoined as well. i am going to try to update firmware on all the bulbs and see if there's any difference. anything you think i should try, i'm happy to
Do you have OTA enabled for Inovelli as well?
i disabled OTA for inovelli since one of their firmware updates killed my grouping; only do those manually. just enabled OTA on the hue bulbs, they seem to be updating which is sweet
I'm not aware of any bugs like this with Hue bulbs though, only IKEA and a few other manufacturers
okay good to know, appreciate the info
when updating the Hue bulbs, there are newer updates available here: https://github.com/TheJulianJES/zigbee-OTA/blob/b569796dcc29f8a4f96f17ef3ef996612be4c749/index.json
download all ending with "meethue.com" and put them in your OTA directory
(they've been pulled from the main repo temporarily until Z2M is able to correctly parse all images, it already works fine with ZHA though)
also, can you upload the signature of the Hue bulbs that stop responding to individual requests? (https://dpaste.org/)
How many inovelli switches?
Are you using binding? Does the group call work or are you referring to turning on/off from the switch with binding?
active inovelli switches on the network are 10 - so both work, the binding on the switch to the group, and issuing commands to the zha light group. just cant control the individual light
If you go through zha and turn on/off the group does it work? Reason I ask is that some people are experiencing flooding on the network that may degrade overall network performance
yup so if try to control the zha group directly from home assistant, it works fine
Interesting. Are you getting any errors in your logs? Also trying to find out if it's just an issue with z2m or zha as well
nothing crazy, couple warnings:
Updating zha sensor took longer than the scheduled update interval 0:00:30
i do get a ton of these whenever ZHA reboots, but i was told this is normal 'noise' that will be fixed in a later release:
[homeassistant.components.zha.core.channels.base] [0x8249:11:0x0300]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>')]
No errors when sending individual commands to the hue lights?
nothing i can see, i am watching the log.. i try to toggle the light in HA. the toggle moves to on for a sec, then goes right back to off. nothing in the logbook, nothing in the logs
You should see a similar DELIVERY_FAILED error
strange, i do not see that. last time that message popped up was 30 min ago, on reboot
did get this spicy one now:
NCP entered failed state. Requesting APP controller restart
but it's trying to update like 20 bulbs right now
What coordinator are you using?
SONOFF -E using ZHA
Ah, Sonoff's magic firmware
ha well, last time i mentioned it i got a similar response, so i flashed the firmware as per recommended by this chat (ty)
ncp-uart-sw_v6.10.3_115200.gbl
Hmm. I've only seen firmware crashes with Sonoff's FW, that's odd.
that firmware crash is the first time i seen it, i am pretty sure (with zero proof lol) it's related to the OTA updates i'm trying to do for the HUE bulbs
It'll re-connect and restart
yup i didnt even notice the downtime, it must of happened quick. firmware is being pushed out again, control of lights is good (except direct control of some bulbs as my original problem)
My nabu casa SkyConnect doesn't detect my small Aquara temperature sensors, but does see the larger aquara temp/tvoc sensors... What am I missing?
You're using ZHA?
And ... you're going to tell us the model number of those sensors this time?
I am using the SkyConnect 1.0 integration, unsure if it goes by another name but am happy to supply screenshots
That's likely to be ZHA, there's a little Zigbee Home Automation under SkyConnect
The Aqara sensors need to be reset in a specific way. Click the "add device" button in ZHA, then hold down the button on the sensor until the blue LED starts blinking. After it blinks for the third time, just let go and it should scan for and join your network.
The Zigbee2MQTT docs usually have pairing instructions on them, if you find your model number
wsdcgq11lm is the model number. I had to do a bit of translation
Ok, I have no idea WHY it worked now. I have pressed that button exactly like that while trying to add it before... but now it worked. /shrug
In Z2M if I receive an interview failed warning but everything seems to be correct and working appropriately do I need to do anything?
heyya gang
got some zigbee weirdness.
- running on ubuntu, using docker.
- deconz runs and sees /dev/ttyACM0
- ZHA can't see (Failed to connect) /dev/ttyACM0, when I take deconz out of the mix.
but the setup flow sees the conbee (shows sn, etc)
It's best to re-pair
Sounds like a permission problem to me
ok, puddly, how do I prove/fix that?
ZHA debug logging would tell you the exact error that is logged when HA Core tries to access the radio
ok, how do I enable ZHA Logging
thanks tinkerer
ok, now I have logs
Got this in the log:
serial.serialutil.SerialException: [Errno 1] could not open port /dev/ttyACM0: [Errno 1] Operation not permitted: '/dev/ttyACM0'
2022-12-28 14:38:42.439 DEBUG (MainThread) [zigpy.application] Failed to probe with config {'path': '/dev/ttyACM0'}
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/serial/serialposix.py", line 322, in open
self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK)
PermissionError: [Errno 1] Operation not permitted: '/dev/ttyACM0'
During handling of the above exception, another exception occurred:
I found the problem. Fresh new docker instance works, migrated docker and now works ok.
i need to configure the time that my curtain switch is in the open state, i have ms-108zr. Is there any command zigbee to configure or find what i need to tweak?
Did you remember to pass /dev/ttyACM0 through into the container?
I recently mistakenly activated both Z2M (installed and forgot about it when setting HA up) and ZHA, resulting in ZHA not starting.
I removed Z2M and ZHA was working fine again for a couple of hours.
Now when I got home again, the ZHA integration is still running, but ALL (22) connected devices are now unavailable.
Any ideas? Restart doesn't help.
Using the Sonoff -E dongle in a RPi, haos.
@jade mirage I converted your message into a file since it's above 15 lines :+1:
indicates that you do not have the necessary permissions to access the serial port at the specified path, /dev/ttyACM0.
how do I fix that?
Or didn't map it into the container
think it['s mapped to container, since zha config flow sees the SN
Z2M likely overwrote ZHA's network settings. Run the ZHA migration flow (click the Configure button on the ZHA integration card) and then select "re-configure the current radio". You can then restore an automatic backup from before you accidentally started Z2M with your radio.
To map a USB port to a container, you will need to use the --device flag when starting the container. For example, if you want to map the USB port at /dev/ttyUSB0 to the container, you can use the following command:
docker run -it --device /dev/ttyUSB0:/dev/ttyUSB0 my_container
@jade mirage I converted your message into a file since it's above 15 lines :+1:
Ahh! I remember reading this happening to someone else. Gonna try, thanks!
guys, I'm really unlucky, after I flashed my sonoff zigbee usb key, and restarted HA, I now finally seem to be able to "find" the fiest plug I try to pair, and :
2022-12-28 22:02:15Failed to interview '0xa4c138bbdb5cf26d', device has not successfully been paired
info 2022-12-28 22:02:15MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0xa4c138bbdb5cf26d","ieee_address":"0xa4c138bbdb5cf26d","status":"failed"},"type":"device_interview"}'
warning 2022-12-28 22:02:16Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
warning 2022-12-28 22:02:16Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
warning 2022-12-28 22:02:17Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
😦
Looks like either:
- There's no support for that plug yet
- You're on an ancient version of Z2M because you followed some random guide rather than the Z2M docs
this is the plug, and the dev stated in march he would at it to the supported devices
I installed Z2M using the addons menu
Doesn't mean you didn't get the wrong URL
@glossy lintel When using Discord's Reply feature it defaults to pinging the person you reply to, which can get frustrating for the target. Use Shift + click on the Reply option, or click @ ON to @ OFF to stop this - on the right side of the compose bar.
You have to change this every time (thank the Discord devs for that).
Check the version number of Z2M you have installed
1.28.4 commit: unknown
some guys states the plugs are working fine with version 1.25.0
https://www.zigbee2mqtt.io/devices/TS011F_plug_1.html suggests it should work then
But... Tuya
https://github.com/pcpgjanssen/zigbee2mqtt/blob/924a23eba29ac498173bd1ee0328d4408647e7fb/docs/devices/MS-108ZR.md this helps but since im not using zigbee2mqtt how can i send the command {"calibration_time": NEW_VALUE} using zha
this is not the plug, the plug is a NOUS A1Z (a tuya company still)
2022-12-28 15:07:32.703 DEBUG (MainThread) [zigpy_deconz.api] Command Command.read_parameter (1, <NetworkParameter.protocol_version: 34>, b'')
2022-12-28 15:07:34.508 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.read_parameter' command with seq id '0x02'
2022-12-28 15:07:34.512 DEBUG (MainThread) [zigpy.application] Failed to probe with config {'path': '/dev/ttyACM0'}
Traceback (most recent call last):
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 456, in wait_for
return fut.result()
asyncio.exceptions.CancelledError```
after changing from volume mount to device mount
this did the trick, thank you again!
I still can send these plugs back, but I'd need to figure out a way to get my meross plugs to connect my mqtt server then 😄
I'd also suggest that you take the time to read, rather than assuming...
White-label LELLKI TS011F_plug, NEO NAS-WR01B, BlitzWolf BW-SHP15, Nous A1Z
which tends to be even more of a pain in the back
Well, it's Tuya, so the odds of it working without problems ... not high at all
ok, I will send them back then. I don't want to start having even more issues
problem is, I couldn't get my 17 pre-HA meross plugs to pair with my mqtt server
it just don't works... so I was thinking about a replacement
and to be honest these plugs (A1Z) do have great reviews on amazon
Don't buy anything Tuya without careful research - and even then, you're likely better off with something else
Don't buy Sonoff sensors
Don't buy Osram's Zigbee 1.2 stuff
https://www.zigbee2mqtt.io/devices/SPE600.html if you're after an EU plug that does power monitoring
haha well I bought sonoff sensors, I bought tuya plugs 😄
thanks for the tip
return label for the plugs is printed....
/dev/ttyACM0 - SONOFF Zigbee 3.0 USB Dongle Plus V2, s/n: 20220816155607 - ITEAD
which ZHA radio type is it?
If you're being asked the radio type, communication with the radio isn't working, because auto-probing failed
But it would be an EZSP radio
It asks for the radio type only when it can't figure out what the radio type is by talking to the radio
ok, so I still have a problem communicating with it.
from inside HA, this is what I see:
drwxr-xr-x 2 root root 40 Dec 28 15:36 ttyACM0
does it think its a directory??
@jade mirage I see you're passing through the device in the volumes key. Try putting it in devices instead: https://docs.docker.com/compose/compose-file/compose-file-v3/#devices
Select the serial port for your Zigbee radio
Unknown error occurred
Serial Device Path
/dev/ttyACM0 - SONOFF Zigbee 3.0 USB Dongle Plus V2, s/n: 20220816155607 - ITEAD
Enter Manually```
logs say: 2022-12-28 15:59:01.989 DEBUG (MainThread) [zigpy.appdb] [0x5d6f:1:0x0000] Attribute id: 5 value: TS004F 2022-12-28 15:59:01.989 DEBUG (MainThread) [zigpy.appdb] [0x5d6f:1:0x0000] Attribute id: 1 value: 67 2022-12-28 15:59:01.989 DEBUG (MainThread) [zigpy.appdb] [0x5d6f:1:0x0000] Attribute id: 65506 value: 31 2022-12-28 15:59:01.989 DEBUG (MainThread) [zigpy.appdb] [0x5d6f:1:0x0000] Attribute id: 65508 value: 0 2022-12-28 15:59:01.989 DEBUG (MainThread) [zigpy.appdb] [0x5d6f:1:0x0001] Attribute id: 33 value: 194 2022-12-28 15:59:01.989 DEBUG (MainThread) [zigpy.appdb] [0x5d6f:1:0x0001] Attribute id: 32 value: 29 2022-12-28 15:59:01.989 DEBUG (MainThread) [zigpy.appdb] [0x5d6f:1:0x0000] Attribute id: 65503 value: yL+��+�+ 2022-12-28 15:59:01.989 DEBUG (MainThread) [zigpy.appdb] [0x7b33:1:0x0000] Attribute id: 4 value: innr 2022-12-28 15:59:01.989 DEBUG (MainThread) [zigpy.appdb] [0x7b33:1:0x0000] Attribute id: 5 value: SP 234 2022-12-28 15:59:01.989 DEBUG (MainThread) [zigpy.appdb] [0x7b33:1:0x0006] Attribute id: 16387 value: 1 2022-12-28 15:59:01.989 DEBUG (MainThread) [zigpy.appdb] [0x7b33:1:0x0b04] Attribute id: 1541 value: 1 2022-12-28 15:59:01.989 DEBUG (MainThread) [zigpy.appdb] [0x7b33:1:0x0b04] Attribute id: 1539 value: 1000
Hi,
I just updated to Core 2022.12.8 and I lost all my zigbee devices (they appear as unavailable). I can see them working in Z2M.
Any idea what can be the issue?
Are you using a Conbee?
Nope, a sonoff
The issue is not from the gateway since it's working fine in Z2M
The link from Z2M to HA seems to be broken somewhere
I tried to downgrade to 2022.12.5 but same issue
I'm looking for an alternative for the Popp ZB-shield (rebranded Elelabs ELR023, based on EFR32MG12) on my RPi 3 running HA supervised. Main reason I want something different is that I can't seem to get decent connections with remote buttons on ZHA (tried Ikea and INNR devices). I made an attempt to do this with Zigbee2MQTT but that didn't work. So I'd like to use a device that is fully supported on both ZHA and Z2MQTT. I was thinking about getting a SkyConnect but it is unclear to me if it is supported on Supervised if you only use the Zigbee and not multi-protocol. Can someone in the know tell me more about this?
The SkyConnect is based on the same chip. It's just a normal Zigbee stick unless you flash the multi-PAN firmware.
according to this: https://www.zigbee2mqtt.io/guide/adapters/#not-recommended that chip is 'experimental' for zigbee2mqtt. Is that outdated?
Support for EZSP radios is pretty new in Z2M so I don't think it is
How many routers do you have on your network? That coordinator should work fine.
Actually, I currently have about 20 lights and switches on a Philips Hue hub, and the ZB-shield is only communicating with an Aqara thermometer right now. They are running separate networks on different channels, which is not ideal of course for a mesh protocol that is in a frequency range that conflicts with WiFi. I want to switch everything over to a single controller but when I tried this I found that not all devices work as they should. I could connect and control light bulbs but the remotes I tried (IKEA tradfri button and Styrbar, Innr 5 button) kept disconnecting after a few seconds.
I'm not so deep into the Silicon Labs hardware, but are the 12 and 21 actually the same chip?
Oh, you're right, I transposed the digits! The SkyConnect is based on the EFR32MG21, not the EFR32MG12. They're different generations but it's not that much of a change, especially when your network consists of a few buttons.
Yeah, I was a bit surprised when the buttons didn't work, since everything else went pretty smoothly. But I tried to connect them many times. Sometimes they would not connect at all. Sometimes they would connect but disconnect after a few seconds. And a few times I got the Ikea Styrbar to connect for long enough to set up an automation that would make it switch a light on and off. But after a short while it would disconnect again and not be reconnectable unless I removed and reset it. I looked around a bunch of forums but didn;t find and answer, so if anyone has a suggestion I'm open to it.
@ember night have you looked at updating the firmware on the zb-shield?
I haven't yet digged in to that. I didn't log everything I did when I installed the whole HA system I have, I may or may not have checked for the most up to date firmware before I installed it. I certainly did not upgrade it after installation.
Thanks for that link. I did get a bit wary when I saw typos in the code there, even if it's only in comment lines...
Is there an easy way to check the current firmware version>
?
I just checked the user guide, no good. Let me check something though
hello, everyone. i have a gledopto 2id strip controller. in other hubs it shows up as two devices: a dimmer and a color rgb bulb. in zha it shows up as a dimmer and a switch. the rgb bulb is a switch instead of a bulb. the device when reconfigured does show the color endpoint and i can use the service to change the colors on the device. i started fixing this with a template but a very helpful individual in the templates channel mentioned that this may be fixable easier with something called a quirk?
from some googling it appears this device shows correctly in zigbee2mqtt but i'm using zha
@ember night I can't see anything in the help section of universal-silabs-flasher that would get the current version
@ember night you could try looking at the coordinator information, I'm not sure where that is in z2m
thanks gambl0r. I will look into it a bit more and report back here if I find out more
so, i found a quirk for another model from the same manufacturer. can somebody tell me if i'm reading this correct?
https://github.com/zigpy/zha-device-handlers/blob/dev/zhaquirks/gledopto/gls007z.py
there are three endpoints defined (12, 11. 13). this quirk removes 11 and 13? i think i would need to create a quirk that adds Color.cluster_id to endpoint 11. can anybody confirm that before i go and waste a bunch of time?
According to the fw update utility:2022/12/2 02:57:56 Elelabs_EzspFwUtility: Elelabs Zigbee adapter detected:
2022/12/29 02:57:56 Elelabs_EzspFwUtility: Adapter: ELR023
2022/12/29 02:57:56 Elelabs_EzspFwUtility: Firmware: 6.0.3-64
2022/12/29 02:57:56 Elelabs_EzspFwUtility: EZSP v6
So, I updated the firmware to 6.10.3-41, ezsp8. But since it is way past bedtime I will check later if it solved the problem. Thanks already!
In zigbee2mqtt, is there a configurable timeout for how long a device command will wait to be retried? I have 2 blinds that I added to an HA group, but the battery was removed from one of them for a few days while I waited for some hardware to mount them. When I popped the battery in, it kept opening and closing for a good ~10 minutes, presumably working through all the messages that had been sent to that group
in Ubuntu:
in docker HA:
what is wrong here??
trying to get sonoff zigbee stick recognized
wuth ZHA
@ember night no worries, hopefully it works correctly now
Why aren't you using the /dev/serial/by-id/xxx path? And Zigbee dongles are usually ttyUSBxx, anyway
becuase i'm an idiot, likely...
Someone is only an idiot if they refuse to learn alternative approaches and blindly insist their method is best 😉
failed to deploy a stack: Container home-assistant Creating Container home-assistant Created Container home-assistant Starting Error response from daemon: error gathering device information while adding custom device "/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20220816155607-if00": not a device node```
is why I was using something other thank /dev/serial/by-id/
Rosemary: I just seem to learn by doing it completely wrong, first
What is that pointing to?
/dev/ttyUSB0
Did you get that path from the hardware list or copy paste it from the docs page?
from /dev/serial/by-id
Double check on that page (it should open in your HA install)
I don't think that will be useful for a container install
Oh darn, I missed that bit
not useful... processor & cpu graphs
If it's a container install, did you consider just passing all USB devices through as a temporary measure? (i.e. make it privileged)
Also, was the stick plugged in before the container was started?
Bluetooth is progress!
bluetooth disappeared wuith reboot
mapping to ttyUSB0
ok, onboarding fails, but it finds ttyUSB0
Select a Serial Port
Select the serial port for your Zigbee radio
Unknown error occurred
Serial Device Path
/dev/ttyUSB0 - n/a, s/n: n/a
Enter Manually```
from HA Container:
bash-5.1# ls -la /dev/tty*
crw-rw-rw- 1 root root 5, 0 Dec 28 21:31 /dev/tty
crw-rw---- 1 root root 166, 0 Dec 28 21:40 /dev/ttyUSB0```
still gives me failure to connect
Today's status -> Tinkerer made me send my Tuya plugs back as it really seems they are crap / I got my sonoff zigbee usb stick updated thanks to atxbyea / I will now try to get my sonoff zigbee 3.0 devices to work with Z2M ^^
what an adventure
yayayayaya
Could someone give me an advice on a custom firmware that i'm making for TI CC2652P?
I already managed to get some endpoints of type Smart Plug working nicely each one with its onOff and Metering clusters and relevant attributes.
I also connected a mifare mfrc522 reader to my device and successfully handled it on SPI, my problem is:
How do i report a new mifare tag received by the reader to Zigbee2Mqtt?
I am searching in the ZCL specs, and such a cluster does not exist, in which attribute of which cluster could i put a new rfid code in order to report it?
Thank you for any advice
I'm looking for a suitable cluster in which i could report an arbitrary message in a standard way
Hi I am new here
@serene monolith I converted your message into a file since it's above 15 lines :+1:
anyone got any ideas whats going on here?
Have any one used the attached product before? Its a zigbee VRF controller for centralized AC
https://www.chinaglobalmall.com/products/614490606165
Tuya Smart Air Conditioning Gateway VRF Central Air Conditioning Controller ZigBee Air Conditioning Converter ZT05X10
just Tuya things, they don't follow Zigbee spec and ZHA trusts each device that it does follow Zigbee spec
so just ignore the extra entity?
ignore, disable, whatever
sweet ty
if it works it works, if it doesn't you'll need a custom quirk
do you have a link to the sensor since i didn't see that manufacturer id before
it was purchased off aliexpress
just one of the generic zigbee ones from there
so no linky
the box just has the zigbee and tuya logos
isn't there a link to aliexpress
hi, anyone using conbeeII ?
i have troubles after upgrading HA, now even after downgrading, nothing is working anymore
Conbee is very susceptible to interference. Put it on an extension lead to get it away from your machine if you haven't already
Did you reboot the host?
And if so, have you checked that the hardware address of the conbee is still correct?
i just used my old backup, here i have the path under dev/serial/by-id/usb-*
before(latest upgrade of HA) it was ``/dev/serial/tty*`
lol, reinstalling the integration with the oldest backup worked
Serial by ID is the one you want
i just got a sonoff 3.0 stick. do firmware updates change much? if so do you have a link to how to update?
is it worth buying into Zigbee? for now I only have plans to get 3 door sensors, which will be half the price if i go with BLE. i do have "zigbee" now as part of Hue but of course we don't count that. IDK if i'll ever add more "sensors" really. or should i future proof and go zigbee? has anyone had a similar experience?
hi hjf. hmmm - worth it? depends on your use case & the problems you are trying to solve. you may find your 3 door sensors grow exponentially, so maybe try to plan ahead so you dont re-do everything again. i'd only use bluetooth if i had no choice.
if i restore a backup from my existing ha to a new one with a different zigbee adapter am i going to have problems? i'm ok with repairing the hardware but i don't want to lose the entity id and names. using zha for both adapters
you can use the 'move radio' option. i've used it a few times, works really well, did not have to re-pair anything, and nothing was renamed. 130 devices
but yeah the restore should work the same
make sure the other radio is not on..
so restore a backup onto the new one and then move radio to put them on the new adapter.
you may want to do the migrate radio first, make sure everything is working as it should on your current HA setup. then you do your HA restore to your new instance. why are you moving your HA instance? just curious..
i have a supervised install on debian 10. i'm moving to a containerized install on 11 with a more recent zigbee adapter.
so the process should probably be to put the new radio on the old box, migrate, backup, shutdown. then put the radio on the new box and restore the backup.
yes, that's what i would do. when you say 'restore the backup' - i'm assuming you mean restoring your entire home assistant backup to the new containerized debian 11, nothing to do with the ZHA section radio restore (just to be clear)
yes. i mean to use the full backup facility and restore it. that'll take over my automations that use the entities as well.
I fixed my zigbee problem, had to remove the coordinator, delete zigbee.db, dance naked in the rain while asking for gods aproval. It worked. Now i have zigbee again. I think it was the dance...
lets see the dance pls. for science, of course
I would plug in the old adapter when restoring the full backup and then do the radio migration after everything is functional
@jade mirage I converted your message into a file since it's above 15 lines :+1:
My Zigbee Mess:
What ZHA sees:
Select the serial port for your Zigbee radio
Serial Device Path
/dev/ttyUSB1 - n/a, s/n: n/a
/dev/ttyUSB0 - n/a, s/n: n/a
/dev/ttyACM1 - SONOFF Zigbee 3.0 USB Dongle Plus V2, s/n: 20220816155607 - ITEAD
/dev/ttyACM0 - ConBee II, s/n: DE2433235 - dresden elektronik ingenieurtechnik GmbH
Enter Manually```
What doesn't work?
Hello everyone, does anyone know how to get Aquara devices connected to ZSH? I feel like I tried everything but I just can't get them to connect.
Things I've tried:
Bringing the sensor closer (like 1 cm from the radio)
Holding the Button until it quickly flashed three times, then letting go
Continuously pressing the button every second
All of the above combined.
Of course I'm searching for new Zigbee devices in HA.
For reference, I'm using https://www.amazon.de/Aqara-Temperature-Humidity-Sensor-Feuchtigkeitssensor/dp/B07D37FKGY and https://www.amazon.de/Aqara-Water-Leak-Sensor-Wassersensor/dp/B07D39MSZS . The HA device I'm using is the HA Yellow.
My Zigbee Mess:
from that point, nothing works
Have you tried installing a new battery? Sometimes the Aqara sensors ship with old batteries.
you don't need to pass devices through manually if you have privileged set to true (although IMO you should remove the privileged part)
so ZHA doesn't work if you use /dev/ttyACM1?
My Zigbee Mess:
Logs:
File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/__init__.py", line 59, in probe
await asyncio.wait_for(ezsp._probe(), timeout=PROBE_TIMEOUT)
<@&330946878646517761>
Done
The device draws a lot more current when actually scanning for a new network. It may have enough to blink the LED but when it scans for a network, it resets.
I'll try that, thank you
Everything else you're doing seems correct. Maybe move it further away?
Tediore: nope, priv is temporary trying to debug step
It doesn't work with both the Conbee and the Sonoff?
are they on USB extension cables?
yes
have you tried asking them nicely to work?
What happens when you select /dev/ttyUSB0 instead of /dev/ttyACM1?
same non-responsiveness
What is your setup in terms of operating system and host hardware?
bash-5.1# ls -la /dev/ttyA*
crw-rw---- 1 root dialout 166, 0 Dec 29 09:29 /dev/ttyACM0
crw-rw---- 1 root dialout 166, 1 Dec 29 09:29 /dev/ttyACM1
bash-5.1# ls -la /dev/ttyU*
crw-rw---- 1 root dialout 166, 1 Dec 29 09:29 /dev/ttyUSB0
crw-rw---- 1 root dialout 166, 0 Dec 29 09:29 /dev/ttyUSB1```
ok. ```
MAC OS running parallels
Parallels running Ubuntu
Ubuntu running Docker
Docker running my Home-assistant container (and related stuff)
I can see the devices at each layer of the mess
the new batteries didn't work, I also tried connecting it from further away, like 1 and 2 meters, but that didn't work either
supplemental info (deCONZ sees the ConBee II when i run that container)
So just to confirm, you click "add device" in ZHA, hold the button down until after the LED blinks three times, then just let go?
yes
Have you been able to join any other Zigbee device?
I've joined like 15 HUE Bulbs, 3 HUE motion sensors, 5 HUE Switches and one Tradfri Switch
So the Zigbee network is functional. Any neighbors that could also have Zigbee networks?
Don't think so, definitely none within the same house
Are you clicking the main "add device" button within ZHA or are you permitting joins through a specific router?
I had my HUE bulbs connected to my HUE bridge, but this Bridge isn't plugged in right now
I'm going to Devices --> add device --> Add Zigbee device
I also tried going to a HUE Bulb and connecting it from there
@austere patio any clue?
test
I just joined an Aqara temp sensor to my Yellow from a few rooms away and it joined on the first try with the "wait until after the third blink" method 🤷♂️
Bizarre. What are you trying to send?
Probably an image
"ok got the info"
So the command ran?
yes, with crash msgs
Well, did it indicate that the radio is in fact alive and able to respond to serial data?
Or did it fail to respond, just like in the ZHA debug logs?
2022-12-29 10:10:20.278 ubuntu-linux-20-04-desktop asyncio DEBUG Using selector: EpollSelector
2022-12-29 10:10:20.310 ubuntu-linux-20-04-desktop asyncio DEBUG Using selector: EpollSelector
2022-12-29 10:10:20.311 ubuntu-linux-20-04-desktop bellows.ezsp DEBUG Resetting EZSP
2022-12-29 10:10:20.312 ubuntu-linux-20-04-desktop bellows.uart DEBUG Resetting ASH
2022-12-29 10:10:20.312 ubuntu-linux-20-04-desktop bellows.uart DEBUG Sending: b'1ac038bc7e'
then error messages:
File "/usr/lib/python3.10/asyncio/tasks.py", line 456, in wait_for
return fut.result()
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
...
then
2022-12-29 10:10:25.318 ubuntu-linux-20-04-desktop bellows.uart DEBUG Closed serial connection
I'll need more than that, something from the middle
understood.
thank you so much, I got it working now. I needed to go the the other side of the flat and try it from there.
so weird
Interesting. Is your Yellow in a noisy environment, near any 2.4GHz WiFi APs?
yeah right next to one
I would move it somewhere else
also, my CM4 has WiFi, do I need to turn that off?
I don't think it's enabled
I have a WiFi variant as well and haven't had any issues
I'll do that within the next few days. Thank you so much :)
I moved from Deconz with Conbee2 to zigbee2mqtt with sonoff-P
And I notice a lot slower responses,
Especially when turning on scenes involving many light bulbs.
Even turning off all the lights in the house, it was immediate with DeConz, and now it's like going in "2-3 waves" until everything turns off (or changes), could take almost 10 seconds now
Does it make sense?
Try https://www.zigbee2mqtt.io/guide/usage/groups.html instead of turning them off one at a time
Hi folks. Anyone else running into challenges with OTA updates in Z2M for Hue bulbs? I was able to update bulbs that were on 1.88.1 to 1.102.2, but any bulb that's running 1.93.11 won't update. I get an error stating "Update of 'Living Room Left' failed (Image padding contains invalid bytes)"
I think this issue has been fixed in a recent Z2M release. Are you running the latest version?
thought I was, let me check to confirm
I'm using ZHA how do I go about changing a router device to a EndDevice, I've been having some issues where one or two of my bulbs go offline and subsequently take down multiple other sensors
Not possible
Running Z2M 1.28.4-1. Check for Updates in HA doesn't return any pending updates for Z2M.
Is there another way that could solve this problem
Why do the bulbs go offline?
That I dont know, the logs look normal to me
What bulbs are they and what coordinator are you using?
Innr bulb e14, conbee stick 2
I have 3 of those bulbs in the same light fixture if thats of any help
Is the Conbee on a USB 2.0 extension cable and away from USB 3.0 ports, SSDs, 2.4GHz routers, etc?
not yet but I've ordered one to try it
Anybody know of any EU voltage hot water heater switches/controllers that are local only? Everything I've found, zigbee OR wifi, has to go through Tuya or someone else's cloud.
At this point it's honestly looking like the least bad solution is a little switchbot.
I have good connection to other devices that are way further away though
if you are okay with wifi this might be worth a try
https://www.shelly.cloud/de/products/product-overview/shelly-plus-add-on
Did you mean to reply to me? That's a sensor rated in the milliamps and I'm looking for a way to control my hot water heater, which is a 4-5 kilowatt load.
I definitely would not trust Tuya to control a 4-5 kilowatt load
Yeah that was my reaction too. Even though plenty of other people are saying their houses haven't burned down there's a LOT of juice in a boiler's circuit. The only thing I've been able to find is potentially sonoff's 25 amp behemoth.
You can also DIY it by hooking a high-power relay/contactor that can trigger with mains up to the output of a lower power relay, but those are dangerous voltages and currents...
Yeaaaah, I'm comfortable rewiring switches and outlets but I stay away from anything that might attract Darwin and Ohm's attention.
I'm pretty comfortable not being path to ground.
Can I get some help with this please?
"Integration error: zigpy_config - Integration 'zigpy_config' not found."
I have created a zipgy_ota folder in config and added the following to the config.yaml : zha:
zigpy_config:
ota:
otau_directory: /config/zipgy_ota
ikea_provider: true
ledvance_provider: true
I dont get what I am doing wrong.
Move all of that under the zha: key
Your indentation has to be correct as well
Thank you.
Restarted HA but i still cant get a tradfri open/close to be visible in the seblu/zha-ikea-open-close-switch-for-covers-e-g-kadrilj-fyrtur.yaml automation. blueprint.
If you're trying to do an OTA update on a remote, it will likely take a few hours
Pull out the battery, put it back in, and it'll finish in a long while
Uhn, yeah. The bug should be fixed in the Z2M dev build. I thought Koenkk would wait another few weeks until the build is publicly released before re-adding the Hue images, but they're back in the repo now, so that's why you're seeing the issue.
I think 1.29 should include the bugfix and be released in a few days
For now, just don't update those lights
Thanks!
And the reason why only some of the bulbs updated is that the bulbs that previously ran 1.88.1 are older Hue bulbs (no Bluetooth, no attribute reporting, no dynamic scenes, ...). The newer ones were previously already on 1.93.11.
The 1.101.xx images are completely different for the generations of bulbs (Silabs for newer bulbs and TI/Atmel for older bulbs IIRC). But I guess Signify names the versions in a similar way to not cause any confusion about why some bulbs have way older versions than others
Gotcha. Good to know the new version of Z2M should fix it. I'm good with waiting.
https://github.com/Koenkk/zigbee2mqtt/issues/15805 and https://github.com/Koenkk/zigbee-OTA/issues/218 are the GitHub issues where this is tracked btw
thanks
Hey everyone, I'm currently using a Texas Instruments - LAUNCHXL-CC26X2R1 and I'm very happy with it.
Now a friend of mine would like to start with "Smarthome" and he would also like to convince himself of ZigBee.
Which ZigBee gateway with a similar (or better) range is currently recommended?
Buy something CC2652 based. This list is a good one, both Tube and Electrolama have been proven to have excellent customer service. The current generation of EZSP sticks (see here for some) are also a good choice for ZHA.
Anything CC2530 or CC2531 based should be avoided - they're old, slow, and only suitable for a dozen or so devices. The Sonoff ZBbridge isn't advised since it uses WiFi (built in interference causing stability/reliability issues), and the HUSBZB-1 uses an older chipset so should be avoided.
Finally, the ConBee range are fine with deCONZ, but experience with ZHA and Zigbee2MQTT appears to be mixed.
Hey folks. Is there a way that a zigbee button can be associated with a zigbee relay/switch and maintain that binding even if the coordinator dies? I found some reference to using zigbee light link, but it was vague
The idea here is to have a wall-paddle stay associated with a switch/light even if the mesh goes down in some way
I found this as well: https://www.zigbee2mqtt.io/guide/usage/binding.html#commands
How would I find a zigbee relay and toggle/paddle that would support end device binding with eachother?
is it "touchlink"?
Usually Zigbee 3.0 stuff is compliant, as long as you avoid Tuya
Sweet!
To use this functionality. Can I use zigbee2mqtt (via webgui) to bidn devices and then just have them work even if I shut down z2m
Yes
Thank you!
Do note that only some Zigbee 3.0 buttons support binding (in my experience at least).
Konke buttons don't, some Aqara buttons allow for it (although they make you use the whole remote for one light), IKEA has somewhat blocked functionality with recent firmware updates, and Hue buttons mostly work, but the newer ones with a shared on/off button send an alternating on/off command (instead of a toggle command), so you might need to press it twice in case you toggle it from HA.
I’ve been using a couple of 13 button zigbee switch from Samotech (though they don’t make them) and they can bind independently of coordinator. But best to initially register. It also created zigbee groups that ZHA can expose to automations.
my skyconnect is on the way. How hard is it to migrate from my current stick? Am I able to do a backup/restore? Or do I have to re-pair each device? Asking because I got a bunch of zigbee sensors for Christmas and I'll wait until after the skyconnect arrives to pair them if it's going to make more work
What stick are you currently using?
Sonoff
they make three sticks. Do you know if it's the "SONOFF Zigbee 3.0 USB Dongle Plus-P" or perhaps "-E" (instead of "-P")?
Anyway, you could probably migrate to the SkyConnect. ZHA has a nice UI for guiding you through the migration.
(I'm not sure if I'd migrate your complete Zigbee network from a "Sonoff Dongle -P" to the SkyConnect at the moment though)
It's listed as ZBdongle-P on Amazon, https://www.amazon.com/gp/product/B09KXTCMSC/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 -- does that help?
As far as not migrating, is the SkyConnect too unstable at this point?
I haven't read much about people's experiences just yet
No, it's been great mostly. It's just that the CC2652 isn't bad either (on which your Sonoff dongle is based upon).
Do you know if you're using ZHA or Z2M?
ZHA
I mainly got the skyconnect for the future Thread/Matter support. My Zigbee has been find with Sonoff. I don't have an extensive Zigbee network though, most of my stuff is Zwave so even if it does have issues it wouldn't be the end of the world for me
I think the migration (TI to EZSP) should work fine.
The multi-pan support is currently disabled (running Zigbee and Thread through a single radio) due to some end-devices dropping off when connected directly to the coordinator.
If you have two sticks, I'd recommend letting your Sonoff stick (CC2652 based) keep running the Zigbee network and using your SkyConnect for when you get Thread devices.
But again, migrating your Zigbee network to the SkyConnect should work fine. The Zigbee and Thread network will run on the same "radio channel" though. When you have two separate sticks (for two separate networks), you could avoid that.
I hadn't thought of keeping them separate. I'm going to show my ignorance when it comes to Matter then. How does that work for Zigbee based Matter devices? Would that work? Or does it require Skyconnect to manage the zigbee network?
It's a bit complicated. I'll try to keep my explanations somewhat basic though.
Zigbee has the "ZCL" (Zigbee Cluster Library) for the commands which describe what messages need to be sent in order to turn a light on/off for example.
Zigbee also features the "network part" (routers, end-devices, coordinator, network-ids, ...).
With Thread-based Matter devices, they become somewhat separate things.
Thread is just the "network part" (internally IPv6 based).
Matter describes the commands for how a light needs to be turned on/off.
Separating these two things allows manufacturers to also make WiFi-based Matter devices (no need to use Thread at all then, but the messages for turning on/off lights are the same).
There's no such thing as a "Zigbee-based Matter device". The Philips Hue Bridge supports Matter, the new IKEA bridge will too. They're basically translating Matter commands to their Zigbee network then.
All Zigbee hubs/bridges will connect over LAN or WiFi to your main network (instead of Thread though), so the SkyConnect won't be used for this.
The SkyConnect can be
- a coordinator for your Zigbee network (just like your Sonoff stick at the moment)
- a border-router for your Thread network (similar to what a coordinator is in your Zigbee network)
So in the second case, it connects your HA instance to your Thread network. This allows HA to send "Matter commands" (over SkyConnect via your Thread network to your Thread-enabled Matter devices).
thanks for that thorough explanation. So long story short, it should work fine with them being separate sticks?
Yes
(Having two separate sticks should also give you the best performance for both your Zigbee and Thread network.)
cool. And right now the Skyconnect doesn't have the ability to work as a Thread border-router right? That's still coming soon?
You should already be able to setup everything, but it's not user-friendly nor recommended at the moment.
(Firmware is here: https://github.com/NabuCasa/silabs-firmware)
I think for an end-user, installing the multi-pan implementation (which is currently pulled) even when you're not using the Zigbee part is the easiest option right now?
Yeah, installing the multi-PAN addon and configuring auto-firmware flashing is the easiest way to set it up right now
You won't be able to go back to Zigbee firmware without re-flashing it with a command-line tool but as long as you never set up the Zigbee side, it'll basically just be a Thread border router (leader?)
OpenThread RCP firmware is coming soon, which will be directly usable with the OpenThread addon
(ah, "Thread Leader" is probably the right term here. not too familiar with Thread naming yet 😄)
I need to learn a bit more about Thread/Matter. I've mostly lived in the zwave/zigbee world
For the most part, Matter over Thread is basically Zigbee, just with better security, hopefully a more rigid specification and certification process, and the ability to tunnel packets over IP (so you don't necessarily have to relay things back to the "coordinator" over Thread). Theoretically it'll be easier to deploy in split environments, like a distant detached garage.
I'm using Z2M w/ Sonoff ZBDongle-E and I've been having a problem where some devices completely vanish from my mesh. I haven't really tracked down a trigger at this point since I usually don't actually realize it until looking at the dashboard and realize something is missing, but at least a Third Reality Motion Sensor and a SmartThings Gen 2 Multipurpose sensor have completely disappeared at different times.
Any thoughts on what might be up or at a minimum how I might be able to see when something drops off? I've got alerting set up for entities that go unavailable, but these entities straight up get removed from HA and it's like they were never there. I had to go back and query Influx (and see it's been gone for 2 months) to prove I wasn't crazy.
Are you running the dev Z2M?
I'm not
Last I heard that was the one that it worked best on
As in the Edge branch? or...?
Yes, I think that's it.
If it's an add on you need to re-download it to update it as a note 🙂
Yeah, I know it shows up separately. Are there things in dev that they've not been merging back to master specifically for this coordinator?
The integration usually has no control over how the mesh operates so if things "drop off", they'll do that even if you switch versions
What routers are these devices joined through?
I can't say for certain, but likely either a Hue bulb or the coordinator itself
I've got a bunch of other similar SmartThings sensors that haven't had any issues (yet) also appear to be connecting via Hue bulbs at the present time
It shows up in Z2M -> Settings -> Raw -> Devices
Not sure if that means anything
Hi Guys, I am new to the Zigbee world! got Zigbee2MQTT going, and paired a Sonoff Zigbee smart plug. All working, however in the OTA section I get this "warning":
Firmware on '0x00197b0024514e05' is newer than latest firmware online.
-- What does this exactly mean?
It means your device came with a newer firmware than the one Z2M can download
what are some decent zigbee usb dongles for raspberry pi 3?
Buy something CC2652 based. This list is a good one, both Tube and Electrolama have been proven to have excellent customer service. The current generation of EZSP sticks (see here for some) are also a good choice for ZHA.
Anything CC2530 or CC2531 based should be avoided - they're old, slow, and only suitable for a dozen or so devices. The Sonoff ZBbridge isn't advised since it uses WiFi (built in interference causing stability/reliability issues), and the HUSBZB-1 uses an older chipset so should be avoided.
Finally, the ConBee range are fine with deCONZ, but experience with ZHA and Zigbee2MQTT appears to be mixed.
I only found the conbee II in a norwegian store is that good / okay?
That's not good
The good news is Zigbee dongles are not specifically for or not for a raspberry pi.
You're also going to save yourself a load of money by importing stuff
Yup. AliExpress is my source for everything. And outside of Chinese new year it's usually with me in 2-3 weeks.
i dont really want to wait for more than one week shipping
Get used to a bit of patience and you'll save loads
ok, so what are some good ones (that show up at your house) usb dongles from aliexpress
Sonoff's CC2652 based dongle is good and reasonably priced
Sonoff Zigbee Plus
The E Version. That's only got experimental support in some cases.
And the -E version also has magic firmware that crashes randomly sometimes. (Should still work mostly, but just get the -P variant)
So.... typical Sonoff then
does anyone have a link to an aliexpress store that is not sketchy
You don't necessarily have to get a coordinator off of AliExpress. Just stick to the CC2652, depending on your region you can get it off of Amazon or a local web store
This is one I've bought before according to my order history: https://a.aliexpress.com/_EyyGeCx
I have the -E version it is working great, no issue or crash, however I only have so far about 10 devices. so maybe it gets ugly soonish!
Thank you! so I guess it's safe to ignore this warning?
So just trying to even manually remove a device via Z2M keeps the HA entities in an unavailable state. I'm wondering how those entities ended up being removed from HA then if they still stick around in HA after a device leaves the network.
Have you tried force removing? that always removed them for me.
I'm just trying to determine what causes the entities to get removed from HA. Force remove works to get the Z2M device removed and I know I can manually remove entities
But I'm finding a couple of devices are vanishing from my mesh altogether as well as their HA entities
I actually found that it did rejoin at the end of November for a few days, dropped again for a day and a half, joined once more for 2 more days and has been unavailable for the majority of Dec
But when it drops, there's no "Unavailable" state history for the entity
I think my ZHA setup is ironed out enough by now to start migrating all my hue lights to ZHA and stop having two separate Zigbee networks running parallel. Two questions: 1 Is there a (semi) automated way to re-create scenes and controller actions defined in Hue or is it all manual? 2 Is there any use for the Hue hub(e.g. use as a repeater) or is it a brick after I migrate?
Hello,
I just bought the Sonoff | DIY ZBdongle-P Zigbee 3.0USB Dongle Plus
does it support Touchlink by default or do I have to flash it with another firmware ?
The -P uses Z-Stack firmware which supports TouchLink (and ZHA doesn't, Z2M does)
However, check that the firmware is 20220219 or later, as a TouchLink crash was fixed in that version.
Also, what's the reason you need TouchLink for? (just resetting some bulbs or for pairing?)
Home Assistant 2022.12.8, Zigbee2mqtt 1.28.4-1. My Zigbee2MQTT has been crashing nearly once a day, after months of working properly. It appears to try to restart when it crashes, and this is all that appears in the log: https://hastebin.com/nawaqatibe.rust. Looking at my HA log, the only issues I see with Z2M is https://hastebin.com/aliritisoc.css repeated pretty much nonstop; I'm wondering if that might be causing the crash and how to fix it? The bulbs in question are Sengled E11-N1EA bulbs
hi i purchased a tuya zigbee airkeeper from amazon and tried to connect it to HA running on Yelllow . it only shows the voc sensor.
i can manually -read- the other sensors but they don't show up on dashboard.
can I make them show up ?
Assuming you're running ZHA, then see if there's already an issue here: https://github.com/zigpy/zha-device-handlers/issues
If not, create one (and fill out the template with diagnostics data)
Tuya devices are a pain to work with against though.
well now i know.
i thought tuya was great
no idea if im using zha.
just vanilla zigbee that come with the yellow
hmm before i run off and see what an how zha is
i see some cluster thingies with the sensors populated
Tuya is not good, try to avoid it.
If it's wifi, really try to avoid it, Zigbee might be workable.
ok investigating.
so screw this. what does the people like?
which temp gizmo plays nice .
id like temp and humidity , voc and formaldehyde are ah, amusing I guess, since i am not in fact dead last i checked.
yeah its zigbee
Anyone have recommendations to replace my 3 day old sonoff temperature sensors? Constant connections issues, values freezing until pairing again and other one already used 20% battery edit: 30% battery
Edit2: 40% used, at this rate won't last till the end of the day
Something clearly wrong with it
I have a Philips Hue Ceiling Light that I “orphaned” and now I can’t reset it because
, I can’t reach the serial number because well… it’s a ceiling light and getting it off is my absolutely last resort and honestly pairing to the Philips Hue Hub and disconnecting ain’t worth that hassle… especially because if I want to connect the hub I’d have to make a raspberry pi wifi-lan bridge since I don’t have Ethernet where this lamp is positioned
, I lost the Philips hue remote and can’t find it anywhere,
so my last option before just giving in and removing the lamp and making a wifi-lan bridge is Touchlink
What is the best Zigbee stick? I have a conbee now.. the old one .. Im moving to Zigbee2mqtt .. in HA.. from Deconz
Hello all.... just grab a skyconnect module ... and I am trying to pair the xiaomi LYWSD03MMC
actually no success.... anyone managed to ?
you're trying to pair a Bluetooth sensor to a Zigbee stick...
that usually doesn't work
i'm trying to add a second zigbee device to a supervized install so i can migrate to it and then to a container install. I've added the dongle to the vm and can see it in lsusb and /dev but ha isn't detecting it. i've restarted the entire system, nothing. is there a special trick to getting it recognised?
@lucid pumice which ZigBee device?
new one is a sonoff zigbee 3.0
zbdongle-e or zbdongle-p?
p
Hi, I have plenty of this light switches in my house https://www.zigbee2mqtt.io/devices/TS0001_switch_module.html
From zigbee2mqtt I was able to configure the state after power on, but with ZHA the configuration is not shown in the device properties, so I tried to change the attribute power_on_state from the device ZigBee clusters but the value is not stored (if I click on read attribute the previous value is shown).
I know that the value I entered is right because I copied it from a device that was configured from zigbee2mqtt with the state I wanted.
I am doing anything wrong?
Sorry, I found the answer: #zigbee-archived message
Happy new year!
well, restoring a backup failed horribly. not only is everything no longer paired all the names have been lost so all my automations are broken.
Did you copy the invisible folders?
yes, did a full extract from the tar
And HA was shut down while you extracted it?
yes. I've found this in the logs No such file or directory: '/dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0014D96ABB-if00' which i think means i need to expose that device through the docker compose devices in order to get the current device working.
i think that means i must have configured it manually in the old version. enabling that mapping and the migrating to the same thing but auto detected brought back the device connectivity.
CC2531 ... 
I celebrate too early... The thing is that my devices have 2 switches and I am able to define the power_on_state value for the Endpoint1 TuyaZBOnOffAttributeCluster (Endpoint id: 2, Id: 0x0006, Type: in) but not for the Endpoint 2 TuyaZBOnOffAttributeCluster (Endpoint id: 2, Id: 0x0006, Type: in), I am not even able to read the value (the value that is obtained is None)
yeah, upgrading away from it
hey, Tinkerer: I got my z2M working
Is there a list of devices that have been verified/tested that are zigbee 3.0 compliant, most specifically with touchlink and not requiring a coordinator?
My main goal here is to retrofit in a 4 channel relay in a pull ceiling fan w/lights so i can adjust lights and speed with just 1 wire from switch. I'll add a couple of zigbee switches there that I want to bind to the relay and have work even if the zigbee mesh and coordinator dissapear.
Newer Hue lights with newer firmware can sometimes be reset if you power-cycle them five times
Hi does someone here know a good zigbee/zwave powerstrip?
- Want a large powerstrip (minimum 8 - maximum 20)
- Want a Small powerstrip (maximum 6)
- Every powerstrip could potentially have usb ports with fast charging
- Main Features I want are individual toggle On/Off and Power Monitoring for each outlet.
Is there a list of devices that have
Hi,
Trying to get an Aqara E1 curtain to work with ZHA, but it doesn't seem to cope well. Basically the only thing I can do is to close it fully by pulling the slider (even though the slider returns NaN).
Looking at Clusters, it is set to Alarms. I suppose I should change this to WindowCovering - but after that I'm lost.
Any advice, or pointers for further reading?
Using the Sonoff ZBDongle-E
I need to do some work with them. I have 2 but I need to get a rod that’s the same diameter all the way across
It’s on the list but I haven’t had time to do it
hey... my zigbee hue bulbs are telling me there's a firmware update... however, when I click to update it, it tells me:
"Update failed (image padding contains invalid bytes)
Any Ideas? (using Zigbee2MQTT)
I found this: https://github.com/Koenkk/zigbee-OTA/issues/218
but, I'm don't see the resolution other than... z2m doesn't like the padding in the format...
don't see/don't understand
FYI, this is mentioned in the GitHub issue you linked:
"Update to the latest dev or wait for the 1 Jan release to apply the updates."
(And that's the case. It'll be fixed with Z2M 1.29. For now, don't apply the affected updates)
Thanks! I don't know how to update to a dev version of Z2M, but I don't mind waiting. 🙂
I appreciate the quick summary, I was reading and reading and hadn't gotten to it yet.
Hi. I’m pretty new to discord, so if I’m doing something wrong, let me know 😅 This week I received my SkyConnect. Plugged it into my Pi4, unplugged my CC2531 and tried to configure everything with the SkyConnect. long story short: it works, but some of my smart plugs and led strips seem to ‘reset’ every 15 seconds? As if they were turned off and immediately on again? Sometimes it stops and seems to work fine, and then at seemingly random times and intervals starts to ‘flicker’ every 15 seconds again. Never experienced this with the CC2531, no other hardware changes or new deceives are involved. Could this be the SkyConnects fault, or is there something else to blame? Happened both in Zigbee2MQTT and ZHA (which were not enabled simultaneously).
When migrating to the SkyConnect, did you use the ZHA migration?
I don’t think so. Everything used to be in Z2M, I tried to clear everything in there first and rebuild it with the SC, when that caused above problems I retried with ZHA (which is new to me). I never migrated anything, just cleared the Z2M databases and repaired everything from scratch.
So Z2M uses hard-coded network settings for every coordinator unless you change them in your config file
When you "switched" from the CC2531 to the SkyConnect, the network settings were almost identical, save for the IEEE address of the SkyConnect, which cannot be changed (more than once)
So even though the device database was cleared, the network settings were likely the same. When you set up ZHA, did you click "erase network settings and form a new network"?
I’m not 10000% sure, but I think that’s what I did
Hi. I am running HASS in Docker.
I just purchased a Conbee II to replace by Sonoff ZBBridge. It worked well enough but I didn't like it relying on the Wifi to work.
Anyways, Migrate Radio in ZHA worked fine, everything I had still shows up fine.
All my sensors still work fine - I can see temperatures and everything.
But none of my switches work - all smart plugs and switches are failing.
Anything I can look at? Already restarted everything, nothing showing in the Logging screen.
Make sure to update the firmware on the Conbee before migrating
Though being unable to control devices probably is just interference. Is your Conbee on a USB 2.0 extension cable and away from USB 3.0 ports, SSDs, 2.4GHz WiFi, etc.?
Its on a 32ft extension cable running up the inside of the wall from the basement where I have the server
32ft? Is it an active extension cable?
https://www.amazon.com/gp/product/B005LJKEXS/ref=ppx_od_dt_b_asin_title_s00?ie=UTF8&psc=1
No, I was surprised it is not. It seems to be working but who knows this could be the issue too.
But I did not know about any firmware update... I can try that
Two other things of note
Radio type: deconz is showing under Network settings in ZHA. I assumed this would say Zigbee?
And also, if I Download Diagnostics and look at the JSON, I still see "sonoff zigbee dongle plus v2" and "sonoff zigbee dongle plus" listed, even though this should be removed.
Neither of those are a problem. The Conbee is a deCONZ radio (encompassing both the Raspbee and the Conbee).
Hi all, I'm hoping someone would be kind enough to advise me. I've had HA running on a Pi3 for several years. This week I purchased an Aqara temp sensor (and I'm dumb for thinking I could work around the "Aqara hub is required" notice so entirely my fault) and of course I couldn't use it.
My HA install is written directly to the SD card. Is there a device (Conbee II or something?) that I can connect up that's going to play nicely with the way I have installed HA and therefore allow me to connect the Aqara temp sensor to HA or am I better off finding an alternative sensor?
All these vendor specific apps/hubs etc are a minefield and frankly very frustrating. I'd prefer to get a vendor neutral solution. At the moment most of my devices connect via Wi-Fi which isn't ideal and I have Hue lights with the Hue hub which is Zigbee as far as I understand it?
Hopefully that makes sense and I haven't left out too much pertinent information.
Aqara sensors work just fine with just a non-hub Zigbee coordinator. Avoid the Conbee II and get a CC2652 or an EFR32 (the latter if using ZHA, which works well with both).
You don't need to buy an Aqara hub. Companies want you to buy their hub to get locked into their ecosystem, but Zigbee is Zigbee (mostly). Depending on which Zigbee integration you use, there are recommended Zigbee USB sticks you can get
@tidal portal Buy something CC2652 based. This list is a good one, both Tube and Electrolama have been proven to have excellent customer service. The current generation of EZSP sticks (see here for some) are also a good choice for ZHA.
Anything CC2530 or CC2531 based should be avoided - they're old, slow, and only suitable for a dozen or so devices. The Sonoff ZBbridge isn't advised since it uses WiFi (built in interference causing stability/reliability issues), and the HUSBZB-1 uses an older chipset so should be avoided.
Finally, the ConBee range are fine with deCONZ, but experience with ZHA and Zigbee2MQTT appears to be mixed.
Also, the whole point of this channel is vendor neutral solutions 😛
puddly: Updated the firmware, Re-Migrated radio and copied network to the same stick - Same issue.
I bought the Conbee II for ZHA because I saw some comments saying it was the "golden standard".
These comments are making me regret that choice I think...

