#zigbee-archived
1 messages ยท Page 16 of 1
Zigbee routers... always Zigbee
I found with contact that sometimes they "don't like" a battery and after 1h or so they will disconnect
another reason could be a low LQI
Other than having your WiFi on the same channel (numbers differ!) as Zigbee, your WiFi is irrelevant
I thought that might be a dumb question but had to ask. Thanks for the clarification.
@austere patio you might not have the answer to this, but might find it interesting.... If no one has any idea I'll try to contact with Sonoff but I don't have any expectations with them
Good excuse to move off conbee
But as said above itโs prob just a mesh / router issue
I'll have to do some more research, it sounds like this should all be compatible. I bought the ConBee like a year ago and just got around to getting a ZigBee network setup. The aqara sensors just came this weekend so figured I could still return if there was a compatibility issue.
Iโm not saying they shouldnโt work on conbee. Iโm saying conbee is an inferior setup to a cc2652 coordinator
https://www.zigbee2mqtt.io/information/supported_adapters.html a lot of us use devices off that list for z2m or zha and have great meshes
I had a few aqara devices when I was using the conbee II
I'm using the ZHA integration. Is that not recommended?
I don't know I never tried to use ZHA, I went straight away with Z2M as I saw it has much better compatibility and features on devices
I'll give that a go tonight. Thank you all!
even funnier than this... I can also pair it on channel 19 and 21, so I guess I'll just switch to 21 as I live in a house with not much wifi interference and both 20 and 21 had similar results in terms of energy: https://dpaste.org/XNaU7
would it be too bad just to switch to 21?
ZHA is fine, so is Zigbee2MQTT, both are recommended over deCONZ
The ConBee really requires a USB extension cable
I have a less than ideal setup of using an old Windows tablet with a virtual machine and the USB stick popped right in there. I will give this a try first
Less than ideal ... that's a pretty big understatement
Yes, yes. I have been waiting for inventory to grow on some new hardware. I had planned on using it until I could get my hands on a home Assistant Yellow and a CM4 but I'm growing impatient.
that's not really an upgrade man
cm4 isnt really a great setup whether in a yellow or anything else. get yourself a nuc or a decent used laptop or even a thin client. something that can ssd boot and has a bit of processing power and ram
and spending an extra $20 or so to buy another coordinator to replace the conbee with something like the sonoff p dongle off the list i linked above would be something i'd do in your shoes as well
Thanks for all the recommendations! It's a surface so I am enjoying the SSD but the pain has been using a single USB port, no Ethernet, and keeping the screen on 24/7.
sometimes the interview process of battery powered devices fails - on some sensors like the aqara stuff you can keep pressing the reset button every 1sec (wakes up the device) to make it more consistent but I dont know if that works with your sensor.
Had a similar issue happen with a zwave device. I was able to just tell HA to re-interview and it fixed itself.
Trying "reconfigure" on a zigbee device to see if that solves it. One of my motion sensors isn't displaying temp despite it being capable.
The device reconfiguration failed. Additional information may be available in the logs.
๐ฆ
what is the best wifi channel(s) to use if zigbee network is on 15?
thank you - so with three wifi APs, 11-1-11 is the way?
Did you not look at the chart he linked?
Zigbee channel 11 with WiFi channels 6 and 11 would be better, but if you don't want to switch from zigbee channel 15 then a two-channel reuse plan with WiFi channels 1 and 11 or 6 and 11 would work
yea and it looks like channel 6 sides are on 15 on the graph. thatโs why iโm asking, because i am unclear. thanks for the help tho, super helpful ๐๐ป
condescending much lol
exactly
if you looked at the chart you wouldn't have chosen 1 so..
1 and 6 are equal if zigbee channel 15 is used
exactly
15 is smack dab inside the 1 spectrum
No, 11 is
The chart shows 20MHz channel width
i dont see why you'd choose channel 1 and 11 over channel; 6 and 11 though
which is what i was expecting as the best solution given no other interference from neighbors etc
WiFi channels 1 and 6 are the same as far as channel 15 for Zigbee is concerned
i looked at this
you saying channel 1 and 6 is the same assumes that both channels 1 and 6 have no interference from neighbors or anything else using 40mhz though
That's the same chart on the page I linked
so in my eyes im seeing an obvious benefit to avoiding channel 1 on wifi for now and future (in his scenario)
I'm talking strictly within their setup
And assuming 20 MHz channel width on 2.4GHz which is the sane choice
he doesnt live in a bubble though
They could be in the boonies
you can facepalm all you want dude
Hello im using a nodon relay to open my garage door, but i just added the relay to the zigbee2mqtt and I dont know how to use it.
Can somebody help me?
What do you mean you don't know how to use it?
the relay is always in ON
and when i try to switch it to OFF, the relay automatically forces the ON mode
I connected the button of mainboard of the garage, it should work as a one click switch from the garage, like a wall switch (im not sure if im making myself clear enough)
I should be able to click one time in the relay and act as a one time command to the garage door
but is not doing it
I could send a video but I dont have permissions i think
you have over there the weird thing that is doing to me
I've been foiled by an outdoor wall, was droping a sonoff temp/humidity sensor outside, but detection is failing.... ๐
Gents
Help me, my mind is going to shit. Aqara Smart Plug vs Ebyte E72-based Zigbee Router. eByte E72 (i.e. TI CC2562P-2) will presumably have = or > performance because we can adjust to ~ +5 /+9 / +15/ +20 dBm vs with stock Aqara Smart Plug, it is listed as max transmit 10 dBm. Does this sound correct? Assume PCB antennae for both routers.
In general that's correct
I just bought 2 Aqara water leak sensors. One connected to ZHA fine. The other is not being seen at all when trying to connect. The blue light flashes and everything. I think it may just be a faulty device.
moved it, and i now have temp/humidity readings!
Humidity 54.1%
Temperature 53.1 ยฐF
I bought 7 and gave up and returned one for not working
A week ago 4 stopped working after a power outage. I try repairing every few days and so far Iโve gotten 2 out of the 4 to repair but itโs taken many tries over days
So keep trying ๐คท๐พโโ๏ธ
Some of mine need an offset between 0.5 - 1 degree and between 1-3% for humidity.
I saw that workaround with a template sensor, however I don't really like it, because it does not show up in the Device, only as an entity and that makes the whole thing more complicated and cluttered.
I know Z2M can set offsets for them, but it might just do that internally and report another value.
I could use some help with my setup. Using HAOS with Conbee II. Connected my zigbee (mostly lamps) with zigbee2mqtt and using Homekit via (HASS Bridge).
Using scenes from Homekit to control the lightning.
My problem: The scenes randomly turns off/on the included lamps. It looks like lamp is turned of in Homekit but it's still on. So have to manually switch that lamp on and off again in order for it to turn off. This happens to random lamps, but it happends everytime. Using the HA app works better, but has same problem when turning off/on a room. Any ideas on where I could start debugging this issue?
Should I try a new Zigbee stick? Are there "extenders" for zigbee? Maybe try zha instead? Any suggestions would help a lot!
yes, yes, yes
- For controlling multiple lights at once a Zigbee group can help.
- Put the ConBee on a USB extension cable
- You can configure the lights to report their
OnOffstate periodically so that Z2M knows they're really on/off vs whatever it thinks
i wish there was a way to do some ESP hacking with addressable leds but with zigbee :/
i'm such a wifi hater
Any more suggestions what to try? See above (using conbee 2 stick now updated with latest firmware).
Removed all integrations, added just three IKEA lightbulbs using ZHA (switched from z2m as a test) to a room. Using switch in UI (lovelace) for whole room (only three lamps), lamps randomly don't follow the command for on/off. Using just one lamp, it always works.
Is it a hardware problem?
It's a Conbee problem
As mentioned above, try putting the Conbee on an extension cable, but really your solution is to replace the device
It's already on a extension, so I'm investing in a new device then. What would be the best buy today?
Most mains powered devices are a Zigbee router, for the exceptions see this community wiki page.
Whoops, wrong one
Thank you - will order right away!
hello I have a nodon Relay, but is not working properly
is doing that weird thing, i cant switch it off!
im using Zigbee2mqtt and HA
zigbee2mqtt says that the device availavillity is disabled
i will try tx
Does anyone know if Hue sync box can work with all my zigbee lights in HA? Or does it pair directly with Hue lights only? Or if this DIY solution using Hyperion may work with all lights? Or it might not even be feasible to include lights that arent directly behind the TV, IDK ๐
what is your gear? in general the sync box is not needed at all
I have 3 hue play bars, (2 behind the TV) and otherwise 4 RGB bulbs and a RGB light strip in the room
It would be if you want it to be "reading" what's on the TV
I think from memory the Hue Bridge is the one that links up the gradient strip or play bars and the sync box, and I don't know if those will work without the bridge. I know my Ambilight TV (it has the gradient strip more or less built-in), has to talk to the Hue Bridge in order to communicate with the play bars
that also depends on his gear. I have no use for it as I get the framebuffer directly out of the tv to hyperion
you can control hue entertainment stuff with https://github.com/jdmg94/Hue-Sync all day
emulated hue and others also do entertainment but don't support led "zones" as hue calls it. hue-sync can talk these zones by utilizing the entertainment api v2
Nice
Oh I thought you meant my zigbee gear
My TV is a samsung 55" 8000 series
3-4 years old i guess
so I would say try emulated hue, you shouldn't even need a hue bridge for this to work
if you have a android box or tv you might also get them to export the frames to hyperion
its easy to then select a hue bridge in hyperion
hyperion just doesn't support entertainment api v2 so in my case I just output to file and read it with hue-sync
oh wow interesting, will test out a bit later
Evening automaters. I have a weird case that I need to vent.
Today we had a power outage, not for more than 10mins but I wasnt home and had forgotten to make sure my HA box turned on again when the power returned. So the zigbee network was down for probably around 1,5-2h.
Somehow, two of my remotes (one Ikea on/off and one Ikea 5-button) managed to bind themselves to a wall plug (Aqara) close by in this time. I cant figure out how this happens, or how to revert it. Not without removing and re-pairing that is.
ZHA? Zigbee2MQTT? deCONZ?
oh yeah sorry, zigbee2mqtt
this have happend once before a couple of months ago. Same thing then, paired itself with an Aqara plug that was connected to....my server....that was a bit of a drag.
your remotes bound to a wall plug that was close, isn't that what you want? ๐
i vaguely remember reading to turn off (or unplug) your coordinator for a couple hours to get your mesh to "re-mesh". I suspect this is very vendor dependent though.
Hii,
question about zigbee, if i add a new device, will my older device re-route to a better route ?
i added a smart plug to try to improve my wireless sensor range, but they arn't connecting to it and one that would have a much better signal is not changing
It depends entirely on the "older device"
the devices chooses the route ? not the main router
Yes, the devices are entirely in control of how they connect
You can re-pair them with only your chosen router as an option - both ZHA and Zigbee2MQTT support that - but it won't stop them changing their connection later
ah, how can i do that ?
i am using zigbee2MQTT
one device has a signal of 12 and is offline for a while now
yes
There's a drop down there
Click it, and then select the router you want it to use
Then click Permit Join and repeat the pairing process on the device
ahh ok ok thanks !
its 50 devices max ? or i can have more or do a need a new coordinator for more
You can have a few hundreds
The limit is how many connect directly to the coordinator, which is why you have routers
ah perfect !
time to invest.. or is it worth waiting for the new threads / (forgot the name)
Zigbee stuff isn't going to magically stop working just because Thread is finally on the horizon
i mean future proofing
You're using HA... who cares?
It's not like that Zigbee stuff is going to stop working on you, or stop you from also using Thread
Zigbee works today. Thread ... will work at some point in the future
I'm looking for radiator valves. Anything I should look out for when choosing?
ok ok thanks ๐
have a few devices in z2m stuck w/ ota at "remaining time N/A"
any idea how i can restart or clear the ota?
ZHA question - i noticed for every zigbee group i created, example: light.silicon_labs_ezsp_kitchen_zha_group_0x0007
now there is a corresponding "switch"
switch.silicon_labs_ezsp_kitchen_zha_group_0x0007
is this normal?
don't know about normal, but all of my light groups are without matching switches
so strange, they just came up out of nowhere - i want to delete them but not sure what function they have..
I suppose your groups contain devices with switch controls
thank you
Donโt delete them ๐คฆ๐ปโโ๏ธ
They are more efficient entities
They communicate Via multicast
Much better for the network and they give you device actions / triggers for the groups
Hi all,
I want to submit a support request for a zigbee device that doesn't function within ZHA.
It's a funky AliExpress motion sensor and I was wondering what's the correct process to go about sending a support request for that device.
Reading in the blog for ZHA discusses sending logs and signatures of devices but I don't want to send that to the GitHub page and just to get shut down cuz I didn't fill it out correctly
Look at the way other device support requests are filled out and do the same thing. For example, https://github.com/zigpy/zha-device-handlers/issues/1918
Thankyou!
just as a "oh this might be worth mentioning", noticed lately i'm having to restart HA a bit or some my zigbee devices don't respond
e.g.: i have a power strip for my indoor garden and an automation based on time to turn on/off the lights and twice now in 2 weeks i've had to restart HA and power it on or off manually because the automation didn't kick in
and i couldn't control it via HA before a restart
What Zigbee integration are you using and with what coordinator?
Bets on CC2531
sonoff 3.0 usb dongle
as far as the integration, how would i find that out?
i guess just the 'integrations' in settings
If you don't know, you're probably using ZHA
i didn't do anything fancy tbh, just out of the box
If you configure the Zigbee integration and look at the network settings, what is the "Radio type"?
znp
Hmm, I'm not aware of any known issues with it. Is your stick on a USB 2.0 extension cable and away from USB 3.0 ports?
no extension, but let me verify the port it's in
trying to identify in terminal
lsusb isn't showing any usb 3.0
just the device ids, so i'm thinking it doesn't have usb 3.0
not giving up just yet though
ok so i've got this on an inspiron 15 3000
has 2 usb 3.1 ports it says, 1 2
watch i have it in the only usb 2.0 port ๐
LOL
yep!
i had it in the 2.0 port
Anything plugged into those 3.0 ports?
well the sonoff dongle now ๐
thanks a lot for mentioning that i would have never thought of it
could explain a bit
Wait no, you want to keep it away from 3.0 ports ๐
You can just hotplug it if you're not running a hypervisor that makes it complicated, ZHA will auto-reconnect in a few seconds
And keep it away from active 3.0 ports in general, even if it's not using the port
seems the link quality improved since changing the port
i could just upgrade the antenna on it too couldn't i?
It usually doesn't make a difference. The next time you're unable to reach the strip, can you enable https://www.home-assistant.io/integrations/zha/#debug-logging (probably via the https://www.home-assistant.io/integrations/logger/#service-set_level service call so you don't have to restart HA) and then save the debug log before restarting? Reboots usually shouldn't fix anything related to sending data over Zigbee.
thanks a lot
i'll do just that
is there a setting in the config to enable debug without editing the yaml?
You should be able to take the logs: portion of the YAML config and instead send it via that logger.set_level service call in the second link
trying to locate it all in my HA now
appreciate the help too thanks a lot
there's 432 gigs free on that box
so i'm just setting default log level to debug now
i'll keep an eye on disk usage
actually nevermind i'm seeing this go south fast based on just the stream queue size values lol
i have one of these handy ๐
gonna compare the network visualization before/after
wow so the suggestion is to get this as far from the 3.0 port as possible
interesting
i have a 20 ft usb extension cable
i could use that
I don't think 20 feet is a spec-compliant USB cable...
A couple of feet is more than enough, just as long as they aren't right next to one another
good to know
Whats the best way to ensure that if a light is on it stays at 1% always?
@fallow warren I had a quick search and found this: https://community.home-assistant.io/t/remapping-light-brightness-range/204436/25
you just need the formula to specify that 1% range
hi all, I have an existing aeotec zwave.. if I add a separate zigbee(sonoff) how difficult is say zwave devices talk to zigbee devices. or I should not even think of this at all? Thanks
However, you can absolutely use HA as the "bridge" - that's very much the point of HA
I for long enough used a Z-Wave button to control a WiFi light, through an automation
that's awesome ๐
i'm having trouble finding many zigbee neutral-not-required devices :/
https://www.zigbee2mqtt.io/supported-devices/ is my go-to list
it's not so much the device/zigbee as ones that don't require a neutral wire
i have old electric in here ๐ฆ
Sure, but ... that list has loads
ohhhh!
So does it mean if you know how to use zwave you'd know ZigBee. Automation works the same? Just select the appropriate device accordingly) thanks
The underlying technology is irrelevant to HA
The only thing that matters is the domain of an entity, whether that switch is Zigbee, Z-Wave, WiFi, or something else .... it's all the same switch.turn_on service call
Can my zwavejs talk to the ZigBee counterpart. Considering I just upgraded to Js. Do I need mqtt js?
However, you can absolutely use HA as the "bridge" - that's very much the point of HA
No, Z-Wave JS can't talk to Zigbee
Z-Wave JS talks with HA
HA talks with Zigbee, or WiFi, or a cloud service, or ...
HA is your hub, the central brains. HA can talk with anything you connect to it.
Ok got it HA is the broker
Can someone please tell me where to find (Youtube, Internet, etc) how to configure (Link, specific settings, notifications, etc) and what all these #zigbee-archived2MQTT settings are for, I can't find them anywhere. Thank you!!
I'm sorry but I don't see it, I have searched the entire page and in the search engine and I can't find it. I mean end point
cluster
Temperature
Attribute
measuredValue
minimum interval
maximum interval
minimum change
etc
Why i can not share images here?
Please use imgur or other image sharing web sites, and share the link here.
Image posting is blocked in most channels to discourage people from sharing text as images. Sharing text as images assumes that everybody sees the world as you do, which isn't the case. Some people are colour blind, or have visual impairment that means they can't make sense of an image of text.
Those are part of the Zigbee spec, and aren't something that the Z2M docs cover
good morning! silly question.. troubleshooting some warnings, trying to find a device with a specific NWK, ie: 0xCD37, or IEEE ie: 00:17:88:01:0b:e7:04:d3 - how can i find the device associated with this in HA/ZHA? other than opening each device manually..
Hi, I have a few tuya smart covers (ts0601_cover) that after updating seems to have stopped working. I can control them through zigbee2mqtt frontend but home assistant only shows linkquality when in the past they would show up as covers.
What would people recommend for a Zigbee button array I could put on the wall to control on/off states through HA. I guess 3-4 buttons would be enough. Nothing fancy. I am using deConz.
add this via hacs: https://github.com/dmulcahey/zha-network-card
then set up a new dashboard panel view with just that card. you'll get a table with all your devices can include NWK AND IEEE to make searching for them easy
Hi how do I factory reset zigbee dongle ? Iโm running zha but want to swap to mqtt
thank you so much! this is amazing
pretty sure when you setup Z2M it will nuke whatever is there and create the new network
It didnโt :/ not showing at all
I need a temperature sensor to put outdoor (will be covered, so indoor sensors work too). The only requirement would be high accuracy. Any suggestions? US market
What do you mean "not showing at all"? Also, you'll need to remove ZHA first before moving to zigbee2mqtt
I have removed ZHA in devices & Services, installed mosquitto and zigbe2mqtt trying to start addon nothing happens i get 502 bad gate
Anything in the z2m log?
its on port: /dev/ttyACM0
maybe if i change the port? But how do i do it?
log says:
gbee2MQTT:error 2022-11-16 17:40:48: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-11-16 17:40:48: Failed to start zigbee
Zigbee2MQTT:error 2022-11-16 17:40:48: Exiting...
Zigbee2MQTT:error 2022-11-16 17:40:48: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
What adapter are you using?
SONOFF Universal Zigbee 3.0 USB Dongle Plus
P or E?
That's why then
But also possibly the path you used which seems strange. Look for it at /dev/serial/by-id/
Also, you'll need to add
serial:
adapter: ezsp
in the z2m config. That stick only has experimental support with z2m though.
not sure how to find it
I assume you're running HA OS?
I think there's a way to see it somewhere in the Supervisor menu, but I have no clue since I run HA Container
so after /dev/serial/by-id i got usb-ITED_SONOFF zigbe etc all (full name _) and thats it
Yeah, use that path
And also update your config accordingly with what I showed above
i always have something different -_- that all the yt videos.. There is no path after that command just full name of device.
i can find it there and its /dev/ttyACM0 which i am using
is there any way i can factory reset that dongle? maybe will be easier
I'm saying use the /dev/serial/by-id path that you found instead of /dev/ttyACM0
i did it now, exact same error
Did you also do this? #zigbee-archived message
|| I know you didn't because that error wouldn't appear if you did ||
@lusty trench I converted your message into a file since it's above 15 lines :+1:
sorry i am still learning ha
It needs to be the entire /dev/serial/by-id/SONOFF... path
"adapter ezsp" doesn't seem right either
And
"adapter ezsp"
``` should be
"adapter": "ezsp"
I thought HA switched from JSON to YAML for add-on configs ๐ค
well it is same problem error
Share your current z2m config and the error
i think it will be easeir to just buy new dongle ;D
@lusty trench I converted your message into a file since it's above 15 lines :+1:
Zigbee2MQTT:error 2022-11-16 18:07:36: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-11-16 18:07:36: Failed to start zigbee
Zigbee2MQTT:error 2022-11-16 18:07:36: Exiting...
Zigbee2MQTT:error 2022-11-16 18:07:36: Error: Error while opening serialport 'Error: Error: Is a directory, cannot open /dev/serial/by-id'
i have changed it like you said
but after reseting add-on it comes back
No, you haven't
The adapter: ezsp part is missing and you're still not using the full /dev/serial/by-id path
For example, the path for my adapter is
/dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_080368199893eb118330214f3d98b6d1-if00-port0
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
READ THIS CAREFULLY
Refusing to start because configuration is not valid, found the following errors:
- Your YAML file: '/config/zigbee2mqtt/configuration.yaml' is invalid (use https://jsonformatter.org/yaml-validator to find and fix the issue)
If you don't know how to solve this, read https://www.zigbee2mqtt.io/information/configuration.html
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
at least different error ๐
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! zigbee2mqtt@1.18.1 start: node index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zigbee2mqtt@1.18.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-11-16T18_09_56_537Z-debug.log
Why are you using JSON in z2m's configuration.yaml? I mean, you can, but it's strange
well i just installed it from the add-ons it was like that
Got it
honestly there is another Zigbee2MQTT i installed Zigbe2mqtt
difference in capital lettes
weiord maybe i should try install the one with capital letters?
I have no idea. There's only one zigbee2mqtt add-on that's current
Anyway, I've given you the answers that you need
i really appreciate them
Also, make sure to put a comma at the end of "port": "/dev/serial/by-id/...", like "port": "/dev/serial/by-id/...",
Tbh though, you might as well just stick with ZHA. Like I said before, that adapter only has experimental support in z2m. The P version is well supported, not the E
i wish to stay with ZHA but some devices functions are not supported on zha ;/
ok managed to move forward but receive that now.:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
READ THIS CAREFULLY
Refusing to start because configuration is not valid, found the following errors:
- serial.adapter should be equal to one of the allowed values
If you don't know how to solve this, read https://www.zigbee2mqtt.io/information/configuration.html
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Where did you get the add on version from?
Because there's the old one and the new one, and the new one uses a YAML config with a nice entry form on top of it.
okay something weird happened i removed old version installed 1.28 and here is the thing none of the addons actually working, but i am able to acces zigbe2mqtt interface ๐
Tuya?
Yep
I managed to run this now, but facing another issue ๐ฆ
Cannot find entities from devices in m2qtt
zha and m2qtt appear to show those differently (as I discovered recently lookint at z2m vs zha blueprints for zigbee)
Thatโs weird I paired all devices but Iโm unable to add them anywhere as there is no entities
disabled? (make sure you turn off the filter)
They itโs not appear anywhere.
I got it, had to log in mqtt mosquito with my host ip
I've noticed this warning is popping quite often in my logs, what does it mean? https://github.com/zigpy/zigpy-zigate/blob/3e89e5d8b5eadc457acef6cbf9bda1f3694cff6a/zigpy_zigate/types.py#L200
It means you should switch to a better coordinator ๐
There is no concurrency limiting for the zigate because it does not appear to properly notify the application that a packet was sent
Do you get the warning when you turn a lot of devices on or off?
Have you tried updating its firmware to the most recent release?
Yes it may happen in such scenario, but will have to verify. Firmware is relatively fresh as I upgraded it one month ago when zha stopped working due to upgrade need.
Then you must be using a ZiGate v1?
Is there a v2 ๐
https://github.com/fairecasoimeme/ZiGate
โ ๏ธ The JN6518 coordinator firmware (ZiGate v1) is in maintenance mode. Pull-requests and occasional critical bug fixes may be released, but no ongoingactive development is currently being done.
There is but if you're going to be buying a new coordinator, do not buy another ZiGate
I switched from deconz, after fighting with blinking lights. I was mostly happy with it. Seems I was wrong
If you have a Conbee then it is a better solution
Is there some comparisons of coordinators? Which are trash and which not?
ZiGate << Conbee < EFR32 <= CC2652
There's unfortunately no auto migration from the ZiGate (unless you also buy a network sniffer like the nRF52840 to capture the network key when joining a new device) so you will have to re-join all of your devices
Why efr32 not at the end? Isnโt that the logical upgrade from the cc2652?
I guess I'll try to return it, wonder how French law is going to handle it.
You don't have to rejoin them monthly?
Not if you use a coordinator that isn't the ZiGate ๐
CC2652 has fewer quirks, though the ones it does have make it incompatible with some devices
Specifically referring to zha and current device support?
No, there's a firmware bug that prevents battery-operated IKEA devices from being joined straight to the coordinator. Also a bug with Inovelli switches running old firmware. Neither affects the Silicon Labs radios.
Not affecting the inovelli blue with latest stable fw then?
I think Inovelli fixed it in their latest firmware
Thank you all.
I've been trying to get zigbee2mqtt to work. At this point it spits out an error something to do with "zigbee herdsman" Anyone have any ideas on how to troubleshoot this thing?
Possibly, if you share the error message
Zigbee2MQTT:error 2022-11-16 16:24:05: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-11-16 16:24:05: Failed to start zigbee
Zigbee2MQTT:error 2022-11-16 16:24:05: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2022-11-16 16:24:05: Exiting...
Zigbee2MQTT:error 2022-11-16 16:24:05: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:103:27)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:132:29)
at Zigbee.start (/app/lib/zigbee.ts:58:27)
at Controller.start (/app/lib/controller.ts:101:27)
at start (/app/index.js:109:5)
What adapter are you using?
That Nortek USB stick that has Z-wave and a Zigbee controller. But I also have a Sonoff USB 3.0 Zigbee Dongle Plus E put it is not plugged in at the moment.
you'll need this in your z2m config:
serial:
adapter: ezsp
Regardless of which of those two adapters you use (both of which aren't great choices for z2m btw)
Or zwave for the nortek lol
What adapters to you recommend?
Anything CC2652-based like the P version of the Sonoff adapter you have or many of @molten linden 's offerings
The P version of the Sonoff adapter is apparently prone to a rare NVRAM corruption issue though
I haven't seen it happen though
Or keep your current adapter and use ZHA instead of z2m
I have a sonoff P version, and I heard the E version was supposed to be better so I bought one of those. I haven't trird to upgrade the firmware though
Well that changes things
The P is well-supported in z2m
The E is essentially the same as the P but with a different chipset family
Not sure if the E version has the same NVRAM bug though...have you seen it on the E @austere patio ?
Ok, so help me understand. I was at one point using the ZHA integration. Worked well, but I have a couple of weird little "friends of Hue" devices like little dimmers you put over a regular light switch. I could never get them to pair with the ZHA. And I recently redid my network and put everything in a rack that I had to put in a back corner of my house. Because of that I wanted to try and get rid of the HUe Bridge controllers. And that is why I thought z2m would be a good choice cause it supports more devices. What say you? Is the effort to switch to z2m worth it?
z2m supporting more devices is a common misconception
There's no official device support list for ZHA because anything that follows the zigbee spec will work with ZHA automatically. Anything that doesn't requires a quirk to be written for it. Zigbee2mqtt requires explicit support for every device even if it follows the zigbee spec, so it has a supported device list.
Arguably z2m supports more non-spec-compliant devices because more people work on z2m than ZHA
Regardless, it's up to you. I prefer zigbee2mqtt, but others prefer ZHA
|| and some even prefer deconz ||
The E is the Same module that sonoff has used since the Wi-Fi bridge. Over usb it should be okay. But not as good as the efr chip I use or that are in the yellow/sky connect
Ok, thanks for helping me understand. Maybe the battle with z2m for me is not worth the fight. When ZHA worked well for most everything.
Question, I had previously deleted ZHA when I was trying to setup the z2m. Now I reload or re-install the ZHA integration it is finding some sort of ghost configuration from previous. Now I'm not sure it is working correctly.
Does anyone know of how to clear out any "ghost" zigbee config from HA so I can start fresh?
are you able to delete the devices?
No apparently Im not able to delete old "ghost" devices. I was able to finally get the ZHA working agian I just started over adding devices. But I still show these "ghost" devices.
Anyone have a solution for z2m when OTA gets stuck?
i've had 4-5 of my devices stuck at Reamining time N/A and can't get them out
I have an E with ZHA, and when i looked a month ago when i picked it up, there wasn't a "newer" firmware than the one that was on it. I re-flashed it.
Ok, thanks.
Ive been digging in logs for maybe a week now my zigbee setup seems to have a 5 second delay when activating door sensors etc. I see this. Line 4190: 2022-11-16 09:40:15.775 DEBUG (MainThread) [zigpy_znp.zigbee.application] Request failed (Unsuccessful request status code: <Status.MAC_NO_ACK: 233>), retry attempt 3 of 5
Line 4194: 2022-11-16 09:40:16.387 DEBUG (MainThread) [zigpy_znp.zigbee.application] Request failed (Unsuccessful request status code: <Status.MAC_NO_ACK: 233>), retry attempt 4 of 5
Line 4198: 2022-11-16 09:40:16.998 DEBUG (MainThread) [zigpy_znp.zigbee.application] Request failed (Unsuccessful request status code: <Status.MAC_NO_ACK: 233>), retry attempt 5 of 5
Im having a hard time finding how to troubleshoot this, after the 5of 5 it does the action trigger
I should also mention that on a fresh reboot the first action of a sensor its instant.
is it possible to manage z2m groups through HA?
In the UI, or via automations?
Z2M's own UI handles it, or you can use https://www.zigbee2mqtt.io/guide/usage/groups.html#mqtt-commands
Hey I swapped my ZHA to Zigbee2MQTTand it seems to be slower ? For some reason ? Not sure if it due to the signal or hardware aspect ? Same devices were perfect with ZHA
or your coordinator is not the best for Z2M
Which one do you recommend ? I am on zigbee dongle 3.0 E
Sorry what pins do you mean ? Is that the one recommended ? https://www.ebay.co.uk/itm/294857501334?mkcid=16&mkevt=1&mkrid=711-127632-2357-0&ssspo=03uzigtbrlm&sssrc=2349624&ssuid=jrg_iIEjQTq&var=&widget_ver=artemis&media=COPY
Afternoon.
Currently setting up my friends HA. He had a ConBee II Stick which was absolutely useless at keeping connected to anything even after upgrading the firmware. He has now bought a Sonoff Zigbee 3.0 USB Dongle Plus.
This is running in a VM in Proxmox and setup the same way my VM is setup with the USB Device being passed through to the HomeAssistant, he is also running the exact same model of server as me and Proxmox version.
However when adding the Sonoff Zigbee USB it shows as there and you press "Configure" and it then spins and asks about "Erase network settings and form a new network"
You select that option and it just spins and then will just show a blank box.
zigpy.exceptions.FormationFailure: Network formation refused: there is too much RF interference. Make sure your coordinator is on a USB 2.0 extension cable and away from any sources of interference, like USB 3.0 ports, SSDs, 2.4GHz routers, motherboards, etc.
It's in the loft!
It is plugged into a powered USB Hub with the only extra thing plugged into that hub is a ext hard drive.
have you tried bypassing the USB hub and use a short (relatively) extension cable only?
what type of external drive?
the error message even mentions external drives...
also check the wifi channels in use and use the pinned message to pick a Zigbee channel w/ less interference if it isn't an RF noise issue from where the stick is
I just recieved the Aqara smart pet feeder c1 in the mail. It's not yet supported by ZHA. What would you guys recommend on doing to get the basics working, or figuring out what commands it needs zigbee wise to send that to zigpy?
They are already doing something for Zigbee2MQTT https://github.com/Koenkk/zigbee-herdsman-converters/pull/4775
Mine gets here today
i should have basic functionality all set by the end of the weekend
Did they send you one to play with?
As a YouTuber or something I think that makes sense but as a dev I think itโs fine to be donated devices for including support
The external hard drive would be the problem. Move the stick onto its own dedicated USB 2.0 extension cable. This error is being presented by the firmware, it's not something that can be bypassed with software.
I'm not sure who has access to the pins, but the Sonoff -E or -P stick isn't clear in the pins when i looked.
Which of the many pins are you referring to?
you use this all the time, and the pins are just random quotes as opposed to an organized FAQ/Suggestion
the second pin about the usb stick cabling is good, and direct information
If you find people using them, and not asking questions, assume i'm the outlier opinion
Well, that's kinda how pinned messages work, but I still haven't a clue what the heck you're talking about when you talked about E or P
sonoff -e stick vs sonoff -p stick
Right... what's the question?
Two pinned messages talk about choice of stick, which explain when you'd only want CC2652 vs when you could use either
Neither name the Sonoff sticks though
yah, though they are common and readily available, and for example the last comment was someone trying to figure out -e on z2m - #zigbee-archived message
maybe it's confirmation bias on my part, anyways maybe my suggestion is just to add a sonoff-stick sticky/pinned
"Call-service error. Failed to deliver packet: <TXStatus.NWK_BT_TABLE_FULL: 210>"
Technically node-red, but probably more relevant here. I think I'm swamping the light.turn_on call-service, which should be delivering commands via ZHA over a ConBee II. I'm calling it (up to) ~70 times in ~3 seconds, which works fine sometimes, but usually throws up a couple of these TXStatus.NWK_BT_TABLE_FULL errors, usually after at least 10 commands if at all. The target entities are a mix of bulbs, dimmers, and light groups. I can mostly send all messages with ~50ms delay between them, but I have to rate limit them to 1Hz to consistently not get this error. Telling the node to queue messages changes nothing, and a cursory look at zigpy_deconz tells me it should be attempting to 'limit concurrency' as well. Google tells me preciously little too...
- does this retry after an error? I'm not noticing any issues but that's likely because I can't even tell what issue I should notice.
- which call even failed? I'm targeting entities dynamically and I don't trust node-red's debug/logs to represent reality with its async message handling
- is this NWK_BT_TABLE diagnosable?
how can I go about debugging this? ๐
Well, the E isn't a CC2652, and hence not recommended for Z2M 
nevermind, carry on
Hi all, can anyone give me some tips with Zigbee? Basically, I have an external MariaDB server and i want to update the database at 10 minute intervals. The Zigbee sensors just update whenever a change in level is detected. (Temp, humidity, etc.) Ive tried scan_interval and commit_interval but can't seem to get the change to work. If anyone can point me in the right direction that would be great
performing discrete time simulations for uni
without going into too much detail, we just want discrete, uniform time samples from these temperature sensors
Some Zigbee sensors support having their reporting configured
Most don't
If you're really lucky, you've got ones that do... but the only way to find out is to try and configure them to report at a fixed interval. How you do that depends on whether you're using ZHA or Zigbee2MQTT, or even deCONZ
Im on ZHA. so even force_update on HA's end wouldn't really be a workaround ?
sorry im also quite new to HA, reading through as much documentation as I can
The thing is, you can do what you want on the HA end, but it still needs the sensors to send data
If nothing changes, there's nothing to write to the database
most sensors will update periodically or when there is a change
None of my Xiaomi Aqara sensors support having what they do changed. The Mijia light sensor does, as does my Develco/Frient multi-sensor
even if you can update how often, they will still report on any change of what they are sensing.
Maybe use node red or something the buffer the changes to only send every 10 minutes. ๐คท๐ผโโ๏ธ
I received advice from here earlier this week on optimizing my ZigBee network and am looking for a little more. My aqara sensors disconnect daily despite adding a USB extender to my coordinator, changing from ZHA to Z2M, and changing channels. Any other suggestions?
We're using Aqara Temperature/Humidity Sensors, as well as the smart plugs. Ill take a look into that suggestion, tyty @molten linden @sour shadow
Well, then there's nothing you can do about changing how they report
you can also use the filter component - you can create entities that only update based on a time pattern.
i was reading something about that earlier
just black list the original zigbee entities from recorder - and log the filtered ones to the db
definitely need to look into that more then
I did this for a sensor that would spam the db every 2 seconds
If discrete time is relevant, this isn't that. But in that case it's probably better to get all samples and interpolate as needed afterwards.
Why not use Zigbee groups?
Somewhere in there I say that I do. Just not all. I keep a central state object and push changes to all changed light( group)s when relevant, so for the most part their settings are not alike
All lights that react alike are in groups
70 unicast/broadcast requests in three seconds is pretty much saturating the channel
I am aware, I don't mind that it saturates or that there are delays, I just don't know what fails or how to rate-limit it reasonably so I can't really recover from it gracefully
You can reduce the concurrency with a config option (it's currently set to 8) but that's about all you can do, the radio library asks the radio to send a packet, and if it fails that's the status code. There is some retrying built into portions of ZHA.
zha:
zigpy_config:
max_concurrent_requests: 8
Assuming you're talking about zigpy, its concurrency seems to delay a message rather than throw an error. So this error is different from that, no?
The default for zigpy-deconz is somewhat arbitrary, it's what I settled on after turning a bunch of lights on and off really fast. Anything much higher leads to errors but 8 for me seemed to get it to reliably send things.
That error specifically is one I've not encountered yet:
BT_TABLE_FULL:
Indicates that an attempt to send a broadcast frame or member mode multicast has failed due to the fact that there is no room in the BTT.
This is caused by the group commands you're sending
Perhaps more artificial limiting is needed for broadcast/multicast frames...
I can try to rate limit the group messages specifically, I am willing to assume those are significantly less likely to be sent simultaneously. except on startup/reload, but then such delays are acceptable.
I meant within the radio library specifically, it's not something that you really should be handling in automation code. If you want to try to apply a patch to the radio library, it should be easy to implement.
Agreed but I can easily filter them in my node-red pipeline, it's no hassle to test whether a dumb solution is acceptable short-term
I think this should work: https://dpaste.com/A6TWLYSHY
How many concurrent group commands are you sending?
9 on a fresh start
After reading up Iโm super curious why you need to do a service call so often to so many bulbs.. are you trying to recreate the wheel with hass and zigbee instead of using like e1.31 / dmx for led lighting control?
You could also switch to a different radio with firmware that better handles this stuff, like the Sonoff stick v2 or the SkyConnect
I'll have to test it though, I don't think any of the libraries are configured to deal with so many concurrent broadcasts
I'm not lighting strips, just (mostly) Hue bulbs pretending they are strips
Wonโt this contribute to them failing early?
If you had Wi-Fi bulbs they could run wled and be controlled by xlights or dmx or lots of other ways
Artnet etc
I'm not sure what you're imagining, but each burst of commands is triggered by a human action and acts on each bulb at most once, there's just a lot of activity happening on the network.
Above I read 70 commands in 3 seconds iirc
so if I refresh my node-red and it tells all bulbs what color they should be, that's ~70 commands at once. but averaged over a day, it's not that much
I don't think the LEDs care that much if they're being controlled ๐. Maybe thermal stress over long periods of time if you keep them outside and continuously cycle them between freezing cold and too hot to touch but I'd imagine Hue bulbs will be fine.
could've swore my parents told me to stop playing with the lights when I was young because that's hell on energy costs and bulb lifetime ๐คฃ
are you saying either of these may be a drop-in replacement with better results, or..?
Hue entertainment API does 25 updates per second
Interesting cuz it still manages to suck compared to ledfx/wled-sr/Hyperion lol
I've not seen how exactly that method works. Maybe they're tweaking the member/non-member broadcast radius, or not even using broadcast...
@grim igloo works fine for me
I can vouch for the sonoff zbdongle-e with RCP firmware and the silabs-multiprotocol addon on ZHA, flawless
Different hardware and firmware. The Conbee firmware is entirely closed source, effectively undocumented, and not configurable. Those other radios at least have things you can tweak and they have fewer routing problems than the Conbee.
just don't try to flash the skyconnect firmware onto the zbdongle-e, the pinout is different, you will need to either compile your own or find someone who has
Did you migrate from an existing ZHA installation?
yeah, was previously using zbdongle-p, then zbdongle-e with NCP firmware
Any stability issues with the RCP firmware so far?
none, completely stable
Awesome
Are you also running the Thread half of the firmware with Matter, or just the Zigbee half?
What is this doing that stock firmware isnโt? Multi protocol?
I'm running the openthread border router as well, but have yet to connect any devices to it
@grim igloo zigbee + thread on the same radio
same as skyconnect
Same thing the si labs chip is doing in the yellow?
Iโm still curious what limitations that has. Isnโt it using like โdowntimeโ to sneak in between each other (thread and zigbee)?
It just passes the raw radio data for both protocols through to software
Zigbee and Thread are both built on top of 802.15.4, which handles the hard part. It's no different from having two Zigbee networks nearby sharing the same channel (or even two devices from the same network on the same channel)
The RCP multi-PAN firmware moves the Zigbee half of the firmware to the computer, theoretically giving you much bigger table sizes and such, since you're not limited to a microcontroller in the same way
It's ARM-only though, so you'd either need a Yellow/Pi or run it via qemu
or supervised on an arm sbc
And the compute or io for this is low enough to where a pi running hass and multiple addons doesnโt skip a beat?
depends on your hardware I guess, I'm running supervised on an orange pi 4 lts, with emmc, it's lightning fast
So HA OS really doesn't work on the orange pi?
it might, if you don't want wifi at all
Weโve determined in #installation-archived that he just hates himself and likes supervised
WiFi for a server ๐คข
But nah, if it really doesn't work then you're the only HA Supervised user I've met that actually has a valid reason for running Supervised over HA OS ๐คฃ
as this has an external antenna
Isnโt a server with a wlan interface just as susceptible to penetration as if thatโs how it connected to your lan though?
by who? my neighbours?
Lol
I don't think the wifi comment was related to penetration?
That, and also || hehe penetration ||
Nobody mentioned anything about it
I did?
Let's keep it Zigbee...
Before that I mean
I may have seriously hurt my HA trying to update this live. ZHA got an error "Failed to set up" and after restarting the web ui doesn't seem to work anymore and core won't reload. /config/.storage/core.entity_registry got corrupted and rebuilding core fixed the rest. I'll try again tomorrow with a proper snapshot (and hopefully a fresher head) ๐
Hi, I have a Nortek GoControl passed through as /dev/ttyUSB1, I try to enable it and I keep getting "Failed to connect"
Make sure you are connecting to the correct tty for itโฆ meaning zigbee and not zwave
I cant get the "Blue print to work with Aqara vibration sensor for automation to trigger notification or other action when Dishwasher or washing Machine is done" to work. Can anyone help me what i am doing wrong?
There's this power outlet Zigbee 3.0 from Connecte that requires a firmware upgrade to support 'turn on after power outage'. Connecte says that you can't do that from Z2M but you need to use any other Zigbee hub. Why would any other hub work and not Z2M?
Quick question: Within Z2M is there a way to see which device runs what zigbee version?
I heard that when a zigbee device is introduced into the network that does not support version 3.0 the network defaults to an older zigbee standard - there a way to check if that is happening in my network?
I cant get the Blue print to work with
Is this a good device for starting a Zigbee network? https://www.amazon.se/Sonoff-Universal-Zigbee-Gateway-Hemassistent/dp/B09KXTCMSC/
Yes
I use it myself its great, one word of advice if you end up buying it from another vendor - there are two different models that look the same - the ZBDongle-P which is fully supported by things like Z2M - and the ZBDongle-E which is the new one based on a different chip which is not yet fully supported by things like Z2M - just a heads up
I bought it and according to the spec it should be the P version
Iโm having issues with my Centralite thermostats where after some time I am unable to change the set temperature, even though they are reporting back the current temperature. Does anyone have suggestions on how to troubleshoot this kind of issue? Leaving and rejoining the network fixes it temporarily, but then it continues to happen 2-3 days later. Iโve got Aqara temperature sensors and Aqara door sensors that continue to work just fine with my TubesZB CC2652P2 coordinator, and the thermostats continue to accurately report the current temperature. Today the thermostat closest to the coordinator (~144 LQI, same room) is unable to be set- Iโm just struggling trying to figure out what logs or place to look in order to track this issue down- thanks for any help
oi! you can enable debug logging, but have you looked at the logs as is in system -> logs?
to enable debug logs you can add these to your configuration.yaml
alogger:
default: info
logs:
homeassistant.core: debug
homeassistant.components.zha: debug
bellows.zigbee.application: debug
bellows.ezsp: debug
zigpy: debug
zigpy_deconz.zigbee.application: debug
zigpy_deconz.api: debug
zigpy_xbee.zigbee.application: debug
zigpy_xbee.api: debug
zigpy_zigate: debug
zigpy_znp: debug
zhaquirks: debug
Nothing in the zigbee2mqtt logs related to the thermostat, I will try enabling debug-- thanks for your help
That logging config is for ZHA
sorry i didnt see he was z2m ๐ฎ
give this a peek
https://www.zigbee2mqtt.io/guide/configuration/logging.html
Hi everybody, i have question about zigbee2mqtt. I just switched from ZHA to Z2M and from Deconz to SonOff dongle. I want to install some sensor at the cottage and i read there that i can install a remote coordinator with an Sonoff Zigbee Bridge (it's already flashed with tasmota, and was operationnal when i switched to Deconz), i thought opening a port on the cottage router and using a duckdns adress to access it remotly, bu before doing it (idon't want to break my home zigbee network) is it something that would work?
I don't have a HomneAssistant instance at the cottage, and don't plan to do it because the cottage is offgridd, i have fiberoptic internet, but i'm on solar panel with not that much power.
The Sonoff Zigbee Bridge already has issues communicating over a local network over WiFi, I don't expect it to work very well when you expose it to the public internet (!) and then add in the latency of routing it over the internet
I think you'd have better luck running Z2M itself on a SBC in the cottage with a normal USB coordinator and then having it either connect to a remote MQTT broker, or run two MQTT brokers (one in each location) and bridge them with a site-to-site VPN
Thanks puddly for your advise, i don't need to have real time information from the sensors, i need only temperature reading like 3 or 4 time in a day, planning to set a rule to restart every hour the bridge to bypass the communication issue. I'm aware of the reliabilty issue of this bridge, i just want to know theroricly if that gone work, and if it's gone break my main zigbee network if i add this line in the configuration.yaml :
serial:
port: >-
/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_50c51a8a011aec11a00d77e5f01c6278-if00-port0
port: 'tcp://mycottage.duckdns.org:9999'
adapter: ezsp
Theoretically all the things connect, as will random port scanners who will stumble upon your bridge ๐. Z2M supports multiple installations. If you give them a different base MQTT topics, the two are entirely independent.
For energy saving purpose, my modem and router are set turn on every hour for 5 minutes when i'm not a the cottage, all automation equipment are shutdown when i'm a the cottage, that's why i'm not shy to opening a port.
Sensor readings come in from sensors somewhat randomly so I'm not sure if keeping the Zigbee coordinator online for only 8% of the time will be enough to receive reports reliably, and to also keep a sensor joined to the network (since its only parent router will be shut off 92% of the time)
An alternative would be to use a powered USB hub with an always-on 5V supply. Coordinators draw like 50mA when they're not transmitting. If you keep your networking equipment and SBC shut down to conserve power, that should keep the Zigbee network operating. But you'll still run into the issue of receiving reports while the power is off.
I was planning to put the Bridge under power all the time when i'm not at the cottage, it's because of it's low consumption that i'm considerating this option. Instead of powering up my internt 5 minutes every hour, i can change that for 30 minutes every 2 or 3 hours. the 8% uptime, i can live with raising it up to 30%.
All my automation hardware are under Tasmota and have integreted rule to work even when there's no internet, the internet is there for monitoring purpose only (keeping my water from freezing ), the main usage of the power is for the heater, and when there's not enought power, the propane heater kick off. All device are routed to my home SBC for monitoring via MQTT. Work fine. But i need more temperature sensor without adding more energy usage. It's complicate but i like that.
I dunno if I would trust Zigbee for something like remote temperature monitoring to prevent pipe freezing where you have to shut down equipment to keep it running ๐ . Maybe with a hardwired backup thermostat...
It's complicate but i like that.
ah yes, nothing quite like a healthy dose of Stockholm syndrome
thanks for this raph. enabled, but somehow after enabling (and restarting z2m).... the thermostat now correctly changes... so I'll have to keep testing, but these debug logs are definitely where to look- thank you.
I am certain it is zigbee on this port
I've had this working on hassos but when I switch to a container it does not work
then you are outside of the scope of zigbee and it is something w/ your configuration
What does ls -l /dev/serial/by-id/ show on the host? The /dev/ttyUSB* mappings aren't stable, use the by-id symlinks.
total 0
lrwxrwxrwx 1 root root 13 Nov 18 02:41 usb-Silicon_Labs_HubZ_Smart_Home_Controller_8130032E-if00-port0 -> ../../ttyUSB0
lrwxrwxrwx 1 root root 13 Nov 18 02:41 usb-Silicon_Labs_HubZ_Smart_Home_Controller_8130032E-if01-port0 -> ../../ttyUSB1
I'm pretty sure /dev/ttyUSB0 is the Zigbee half
I can try 0 again but it doesn't seem to work either
If you use /dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller_8130032E-if00-port0 instead of /dev/ttyUSB0, the path won't change even if you plug in different devices or the kernel decides to reorder the ports
I do have a hardwire thermosthats, the temp sensor, are only for monitoring, meaning to know how the exterior temp affect all part of the cottage, in the objective to know where to install heating element to optimize energy, etc... To know if the heating work at it should when i'm not there etc... Isaid Monitoring, i should have said Analizing.
Thanks everybody for your advise
Anybody got experience with the "new" Aqara P1? I heard that some people have problems with the sensor not picking up motion and was wondering if thats just user error because they did not adjust the sensitivity setting or if its a real problem?!
I've got one, and it's working fine
Detection range is 5 meters... which is as far away as I can get from it while still being in line of sight
Are you using Z2M by any chance?
Yes
Because the old motion sensors (and other aqara sensors for that matter) dont show up in the OTA section - can the new once receive firmware updates?
ahh ty I am an idiot
Guess I will get one to see if it works well - I hope they do because on paper they do everything the hue one can do but at like half the price
Can someone please remind me why it was a general consensus to avoid WiFi devices in favour of Zigbee/Z-Wave? I got the idea but I wanted to remind myself a summary.
The biggest gripe I had with the old one was that the cooldown was way to long and the new one fixes that.
- WiFi stuff often requires cloud, and support is hit and miss
- Zigbee/Z-Wave is 100% local and (other than Tuya and Sonoff) will always work
- Battery life for WiFi sensors is ... shocking
What about Wifi but local? I'm just trying to find some light switches in the UK, and the Shelly brand gets recommended often. But everything they do is WiFi I think. Although someone told me it was WiFi but local.
(might be better to ask in #hardware-archived?)
WiFi switches ... if they're local, they're ok
Personally, if you're thinking of Zigbee sensors, get Zigbee switches too
Well a lot of people use the wifi router/modem/firewall that their ISP gives them. Those things cannot handle a lot of concurrent devices which has caused a lot of problems for a lot of people.
yeah my plan was everything zigbee. Just confused about all the recommendations of Shelly. But ok, will keep looking.
Some people love their cheap WiFi devices, but if you do that you're missing the opportunity to build a healthy Zigbee mesh
i do like the configurability of my tasmota switches/lights though
yeah, exactly. I was planning to rely on switches as my routers tbh
i just use zigbee smart plugs to build out the mesh
that was 2nd option, but really can't think of uses for the plugs yet tbh. So switches were more straight forward and something I def had a use for. Plus they are spread more across the house.
which ones?
If you are interested I use wifi devices (sonoff, shelly, etc) for like power metering outlets and suff like that and I use Zigbee for Lights and Sensors. I found that if you have a zigbee ceiling light in every room the mesh is strong enough to handle all the sensors.
i don't have a use for the plugs either. they're just sort of hidden away
a combination of linkind and sonoff S31 zb
that's cool. I was planning to keep all lights dumb, but all switches smart really. But aiming for the same as you're saying.
If you use light switches for your mesh you might need some other zigbee routers because light switches are way lower than lights and not as centralized. So depending on your situation you MAY need to add another router device from time to time.
they don't necessarily need to be centered in the room to be effective
true. Will see once it's in place. But I prefer adding an extra plug here or there to complement, than adding 6 zigbee spotlights. I think that would be much more expensive and wouldn't give me extra functions for them.
I have lots of spotlights in the house, and having to pay premium for each just seems dumb, when I don't need colours or fancy stuff on them.
i'm also not sure why it would matter that they're lower than the lights
Helps the packets flow downhill
xD
if anything, centered on the wall is arguably better because of the donut effect
for a sec I considered if it wasn't a joke
tends to be more stuff in the way lower down, but that probably doesn't affect signal strength too much
its was more like - they are more likely to be obstructed by something when they are lower.
i suppose
I guess you are right but the Ikea bulbs cost like 10 bucks (no colours) (less when there on sale).
And then you can dim them :)
unless they're already on a dimmer
true
fair enough. I guess both ways work. But I already got all my dimmable dumb spotlights anyway, so too late. ๐ Now I have to find the proper switches, which is my current mission.
My recommendation goes to either the aqara wall switches and if you want to keep your existing switches you can go with the hue wall switch modules.
I have not used the hue once but I have heard good things and I guess they work just like the sonoff minir2's
nvm scratch that
they very much do not work like the sonoff minir2s and are not for your use-case
Dimmable switches? I have a handful of Klemko's D-PAF-ZG-250 and they're been the most stable thing in my network. is a bit specific though
even when the switch itself is not dimmer, when they're smart, can you dim through the hub/app if the bulbs allow it? Or does it need to be a dimming module?
As far as I am aware the aqara switches are just switches not dimmers.
anyone know a place to better understand ezsp_config parameters (ZHA)? i enabled source_routing, and was suggested the following parameters:
ezsp_config:
CONFIG_SOURCE_ROUTE_TABLE_SIZE: 165
CONFIG_APS_ACK_TIMEOUT: 1600
CONFIG_ADDRESS_TABLE_SIZE: 16
CONFIG_APS_UNICAST_MESSAGE_COUNT: 12
would love to know what they are doing before enabling..
I wouldn't change anything unless you have a need for it
But all of the parameters are documented here: https://www.silabs.com/documents/public/user-guides/ug100-ezsp-reference-guide.pdf
thank you for the link! understood - trying to figure out what i need to make this 120 device network stable. hoping that tweaking some of these parameters will do it
I would start with source routing alone and maybe set the source route table size to 120 while leaving everything else at the default value
Which stick are you using?
great, will try that now. i am using the SONOFF zigbee 3.0 -E adapter
Ah, the one with all the firmware problems ๐
you guys generally donโt like this stick right? im happy to throw it in the garbage if thereโs an optimal option
oh hi ๐
The hardware is fine, Sonoff just doesn't publish what exactly they tweaked
More than a few reports of the firmware crashing with an assertion failure in the Home Assistant issue tracker, which I've never seen with any other stick using the same chip
ahh i see - thankfully none of that yet here.. but i can also flash it with whatever is best, is there a version you feel is most stable now?
(firmware)
This worked for another user, which enforces the firmware defaults for the Sonoff stick:
zha:
zigpy_config:
ezsp_config:
CONFIG_ADDRESS_TABLE_SIZE: 16 # FW: 32, ZHA: 16
CONFIG_MULTICAST_TABLE_SIZE: 8 # FW: 8, ZHA: 16
CONFIG_PACKET_BUFFER_COUNT: 250 # FW: 250, ZHA: 255
CONFIG_SOURCE_ROUTE_TABLE_SIZE: 16 # FW: 200, ZHA: 16
CONFIG_TRUST_CENTER_ADDRESS_CACHE_SIZE: 2 # FW: 0, ZHA: 2
See if that helps. If not, maybe try it with source routing.
Btw puddly, this doesn't really work in isolation. it seems the BT table only has 4 slots (for me?) so whatever delay I put here doesn't fix the errors. But if I set zha.zigpy_config.max_concurrent_requests = 4 in addition to the second delay per group message (0.5 doesn't work), it does work without errors. That does have the tendency to jam up, however.
is this something everyone with 100+ device mesh needs to be looking into?
If it works, don't change anything ๐
that's not a fun answer -.-
If it works and you want it to not work, try random config you find online
i'd rather know what to expect when planning out a network with 100+ devices costing anywhere from $15 to $70 each
instead of running into hurdles as they come
ez, just split up your network
i thought splitting up network was bad because of the CTS (clear to send) or w/e where the radios wait for the channel to be clear before sending (please correct me with the proper term here)
I'm joking, I haven't no idea
Hmm. Maybe try using a second semaphore just for broadcasts? (untested) https://dpaste.com/7RP8XDFDQ
thanks ๐
Some people have no issues with 200 devices. Others have problems with 50. If there was some optimal configuration we would definitely use it but it's seemingly trial and error ๐คทโโ๏ธ
yeah i get that
i just like absorbing knowledge i might need in the future instead of trying to go looking for it whenever i need it
If you want to play around with the config, by all means give it a try. You (probably) won't break anything that won't be fixed by stick reboot.
i'm on z2m i wouldnt know where to start :x
around ~50 devices so far working well but will be replacing zwave switches with zigbee to bind to zigbee bulbs in the future along with a shitload more sensors
PR is up in quirks. It will be in a release soon. Everything except scheduling is done and tested
I just ordered a hub like 5 minutes ago ๐
Imma cancel that right now. Thanks for taking the time to scroll back and mention me
๐ i replied almost immediately IIRC saying I was gonna do it ๐
Yeah i saw that, but i thought you were talking to the other guy about that dongle
honestly the hub would not have helped... I have no clue how the dude in the z2m PR decoded this. They did some crazy shit
at least i don't think it would have
maybe they work at aqara and just know a lot of us dont use their hub lol
Do you have a link to that PR? Maybe i can force that in to my installation right now and maybe save my marriage
he married a cat
hehe found it, nvm
My cat scratches the bedroom door, resulting in my wife going nuts. I kinda promised her i'd fix it by tonight
I bought the wrong hub on our version of ebay, so that won't work either
im curious.. is this splitting feeding into multiple times a day for a diet or old cat or something?
yeah i had to stop free feeding cuz one is a pig
My cat would eat itself to death without any hesitation. 'yolo'
what are you guys planning to do with it with home assistant that you couldnt do with a non-IoT feeder?
Create the possibility for my wife to hit a button to distract the cats instead of hitting me to force me to get up and feed them
nope, I must be misdiagnosing something because I can still throw this off after mashing buttons, even if it obviously behaves as intended. but it does seem essentially robust under normal use, so I'm happy with this
ah yeah
Hey, so I was wanting to make some components which I can't buy where I live, and was wondering where can I find the first steps on how to do it? Right now would be a pressure sensor, I could just modify a door sensor, which I did, but, would be cool to be able to code the chip and build from the scratch, if possible.
for zigbee or? sounds like a esphome project which would be using wifi
No, I have done with esphone, but now I would like to try doing with ZigBee, is possible?
Zigbee isn't really suited for DIY projects due to its rigidity so there's no user-friendly SDK for it, but the manufacturer SDKs (like from Silicon Labs) aren't too bad
would you use this over the bluetooth variant?
I ordered the parts to try it
worst case I can use BT if I can't get the zigbee to work.
but I was looking at the source and it also doesn't look super complicated with the nordic sdk zephyr stuff
yeah i've been wanting to automate a garden for a long time and finally got a bluetooth mesh going with bt proxies but i still like the idea of anything else before going bt lol
Too bad is that complicate, but I will take a look into silicon labs, smart homes are so much better with diy, and ZigBee is such a good protocol for it... Sad
dunno, you might be looking for a problem most people don't have. in the case of sensors, dumb tends to be good enough and usually off-the-shelf is competitive in price with DIY and a lot less effort
Right now, I want a sensor to detect when some one is on the sofa , presence sensors just are not enough, it lose the presense if you fall sleep. And such sensor is not possible to buy where I live. Also, is cool to build stuff
well, as you said, it's possible to do that a lot easier but you want to do it the hard way because it's fun
a cheap solution is probably using esphome, a esp8266 or esp32, and an ultrasonic sensor. i have been meaning to try one myself but that is more for #diy-archived channel and no zigbee :/
Yea a ultrasonic would work, prob would need at least 2, right now I'm building the sensor using door sensors and modding it, the proto worked, I prefer not depend of wifi
not the cheapest, but damn if it isn't easy
https://home-assistant-guide.com/guide/how-to-build-the-easiest-zigbee-chair-occupancy-sensor/
saves that for later
More or less what I have done
fyi. My feeder identifies itself as lumi.sen_gas.hrcn01
Did they ship it with the wrong firmware?
No clue what I can do with that Lolol
me neither. custom quirk no bueno without changing the make and model.
Also, i sent you a dm for a free beer
appreciate it but no need!
I'll take it
Did you do a firmware update with the bridge?
I donโt have a Xiaomi hub at all
FYI, @ย Otnow on GitHub can fetch Aqara OTA updates (without having the product or a hub) in case there are any new versions available
Do you have a suggestion for a zigbee compatible blinds wand?
Hi. Looking for recommendations for UK zigbee light switches please.
So many options, just on Amazon... MOES, MoesGo, Aqara, Xenon
I understand the Aqara ones only work with their hub.
I'm advised the others need a Tuya compatible zigbee hub.
And that I could not just use the zigbee hub in an Amazon Echo (not dot).
I've migrated my setup to zigbee2mqtt and noticed that when light is powered and connects to the network it state is displayed as schrodinger light, neither on or off. Is it somehow possible to feth the status automatically? I failed to find this on the Internet.
trying to flash a SONOFF ZBDongle-E with @austere patio universal-silabs-flasher. a little nervous on the proper command to flash it with https://github.com/xsp1989/zigbeeFirmware/blob/master/firmware/Zigbee3.0_Dongle-NoSigned/EZSP/ncp-uart-sw_v6.10.3_115200.gbl - anyone done this confirm the right command?
universal-silabs-flasher --device /dev/... flash --firmware firmware.gbl should work
If you're using ZHA, backups are taken automatically
I was testing this with the SkyConnect and I can't do anything to ever break a stick, even if you unplug it during flashing. The worst that will happen is that it'll be stuck in the bootloader, which the flashing tool handles.
nice - that is reassuring! i wont test it ๐
Anyone ever faced issue installing Conbee 2 stick on HAOS? I connected it to the Rpi 4 which is running HAOS. ZHA integration is automatically prompted by integration discovery. I try to configure it, fails with below logs.
Couldn't start deCONZ = dresden elektronik deCONZ protocol: ConBee I/II, RaspBee I/II coordinator (attempt 3 of 3)
Error setting up entry ConBee II for zha
Exact same error as this thread: https://community.home-assistant.io/t/zha-integration-not-starting-after-upgrade-firmware-of-conbee-2/490700/2
will the zigbee team announce whenever the 6.7 or 7 versions of the firmware will be recommended for ZHA use? just curious how that works, what announcements to look out for..
Any will work, I've been running the latest beta firmware without issues
You can always downgrade if it doesn't
oooo so what do you think? go all the way (7)? or stick with 6.10?
Give 7 a try
7.0.2 or 7.1.1?
Biggest number ๐. I'm not really sure, I've yet to have any negative experiences with any of the firmwares.
you a lucky man! ok will go all the way, lets see ๐ฎ
MAC_CHANNEL_ACCESS_FAILURE means the Conbee is experiencing so much interference that it won't transmit data. Put it on a USB 2.0 extension cable and move it away from SSDs, USB 3.0 ports, SBCs, etc.
when you say USB 2.0 extension, can it be this https://www.amazon.com/gp/product/B09TNLVF5C/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 plugged into a USB2.0 port? or there's something in the USB 3.0 cable spec that causes interference?
A 3.0 cable turns into a 2.0 when it's plugged into a 2.0 port. It's specifically active USB 3.0 ports.
its the usb3 port itself from what I can read so a 500mm or 1000mm extension cable really does matter.
Thanks, will try it out.
What would be a reasonable distance between these devices? I tried a 1.5 feet extender to no avail. There are no WiFi devices in the vicinity (at least not in 10 feet range) of the Conbee Stick. All devices close by are wired including the Rpi running HAOS.
I usually use a three or five foot extender. Is it near any other 2.4GHz mesh networking equipment? Power supplies? Motherboard IO panels? Bluetooth? The Conbee is (sometimes annoyingly) sensitive so it just needs to be placed correctly.
Ok, then I will have to wait for the new (longer) cable to arrive next week. Thanks for your reply, I will try this out next week.
Iโm trying to bind my inovelli blue switches to a zigbee group of hue bulbs
When I click the Bind Group button, ZHA just throws up a spinner on the button and hangs
Iโm trying to tail the logfile but thereโs so much noise in there that iโm not having any luck making sense of where things are hanging ๐ฆ
Any tips?
@austere patio getting some fun errors now after, trying to revert back to 6.10
2022-11-19 14:23:58 rktestbench bellows.ezsp.protocol[2217] WARNING Couldn't set EzspConfigId.CONFIG_ADDRESS_TABLE_SIZE=16 configuration value: EzspStatus.ERROR_OUT_OF_MEMORY
2022-11-19 14:23:58 rktestbench bellows.ezsp.protocol[2217] WARNING Couldn't set EzspConfigId.CONFIG_MULTICAST_TABLE_SIZE=16 configuration value: EzspStatus.ERROR_OUT_OF_MEMORY
2022-11-19 14:23:59 rktestbench bellows.ezsp[2217] INFO NCP entered failed state. No application handler registered, ignoring...
Error: Failed to probe running application type
2022-11-19 14:24:03 rktestbench concurrent.futures[2217] ERROR exception calling callback for <Future at 0x7f6de52a2530 state=finished returned NoneType>
Traceback (most recent call last):
File "/usr/lib/python3.10/concurrent/futures/_base.py", line 342, in _invoke_callbacks
callback(self)
File "/usr/lib/python3.10/asyncio/futures.py", line 399, in _call_set_state
dest_loop.call_soon_threadsafe(_set_state, destination, source)
File "/usr/lib/python3.10/asyncio/base_events.py", line 795, in call_soon_threadsafe
self._check_closed()
File "/usr/lib/python3.10/asyncio/base_events.py", line 515, in _check_closed
raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed
what went wrong with 7? ๐
would not start
@fast sentinel I converted your message into a file since it's above 15 lines :+1:
should i be resetting the dongle when i do the firmware update?
You were right. For testing I moved the Rpi running home assistant to my study room and placed it on bed connected via a long LAN cable (and not many devices in vicinity). vola, Conbee 2 was configured successfully. Thanks a lot for the hint.
Did you disable ZHA?
Have you enabled OTA updates for the Inovelli switches?
nope - i shutdown the HA instance, did the firmware update, plugged it back in and booted up - it failed to start with that error
@fast sentinel I converted your message into a file since it's above 15 lines :+1:
Interesting. I'll have to pick up a Sonoff stick to try this out then, maybe they're using some chip with less memory.
Install the unreleased version from the Git repo and try it once more: pip install --upgrade git+https://github.com/puddly/universal-silabs-flasher
wahoooooo that allowed me to flash. maybe 7.1.1 is too large for this SONOFF stick?
If you want to try it again, try with CONFIG_ADDRESS_TABLE_SIZE set to 8 and try reducing other values that the firmware complains about when starting up ๐
i removed all those settings, should be whatever default.. only thing enabled now is source_routing: true
but it wont start up anymore in ZHA. i tried to use 'migrate radio', then choose existing but: "Lost connection: SerialException('device reports readiness to read but returned no data (device disconnected or multiple access on port?)')"
Couldn't start EZSP = Silicon Labs EmberZNet protocol: Elelabs, HUSBZB-1, Telegesis coordinator (attempt 1 of 3)
Error setting up entry SONOFF Zigbee 3.0 USB Dongle Plus V2 for zha
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
yes im fully up to date
you need to set CONFIG_SUPPORTED_NETWORKS to 2
so under
ezsp_config:
CONFIG_SUPPORTED_NETWORKS: 2
?
yeah, that should work
bellows always tries to force that to 1 and that should normally work. However, the firmware is compiled with the options set to 2 and -- for whatever reason -- trying to set it to 1 on 7.x versions, crashes the dongle
also, if you ever want to downgrade back to a 6.x version, you'll need to flash this https://github.com/xsp1989/zigbeeFirmware/blob/master/firmware/Zigbee3.0_Dongle-NoSigned/EZSP/nvm3_initfile.gbl (after you've flashed 6.x) to completely wipe the NVRAM.
Otherwise, an assert will trigger on 6.x
so i am back on ncp-uart-sw_v6.10.3_115200.gbl
all those errors are on 6.10.3_115200.. the param did not work.
to confirm.. i need to flash again the nvm_3initfile since i went back to 6.10 ?
Setting CONFIG_SUPPORTED_NETWORKS to 2 is only required on 7.x firmware.
not following though, what exact errors did you get on 6.x?
If the dongle starts at all, you don't need the init file (and it won't help then). It's only needed if you flashed 7.x and downgrade back to 6.x
so i first flashed 7.x, which ZHA would not start.. before you mentioned the settings : CONFIG_SUPPORTED_NETWORKS: 2
i already had gone back to 6.10, and also ZHA would not start
yeah, that's expected then. You'll need to open the dongle and hold the BL button. Then press the reset button briefly (still continue to hold the BL button). After a few seconds, you can also let go of the BL button.
The stick should stop "boot-looping" and now be in the bootloader mode where you can either flash 7.x firmware again or flash the "init file" (but make sure you have a network backup)
got it.. what do you suggest, 7x or 6.10?
Hey, did anyone get the new Aqara c1 feeder to work? The Switch doesnt do anything but Identify works
since your Zigbee network is already down, you can try 7.x of course (with the "supported networks set to 2" thing). I'd generally suggest 6.10 though
ok will try 7 for kicks.. but when i boot up HA, what do I do? choose 'migrate' radio? or should it just start up?
It should just start up if you flash back 7.x firmware, as the network info is still present
(make sure to set the supported networks parameter to 2 though)
getting this when trying to go to 7x, or flash anything at all (6.10, or that init )
raph@rktestbench:~$ sudo universal-silabs-flasher --device /dev/ttyACM0 flash --firmware ncp-uart-sw_7.1.1.0_115200.gbl
2022-11-19 15:45:28 rktestbench universal_silabs_flasher.flasher[2940] INFO Probing ApplicationType.GECKO_BOOTLOADER
2022-11-19 15:45:31 rktestbench universal_silabs_flasher.flasher[2940] INFO Probing ApplicationType.CPC
2022-11-19 15:45:31 rktestbench universal_silabs_flasher.cpc[2940] WARNING Failed to parse buffer bytearray(b':'): ValueError('Invalid flag')
2022-11-19 15:45:31 rktestbench universal_silabs_flasher.cpc[2940] WARNING Failed to parse buffer bytearray(b'\n'): ValueError('Invalid flag')
2022-11-19 15:45:35 rktestbench universal_silabs_flasher.flasher[2940] INFO Probing ApplicationType.EZSP
Error: Failed to probe running application type
2022-11-19 15:45:40 rktestbench concurrent.futures[2940] ERROR exception calling callback for <Future at 0x7f8701881b10 state=finished returned NoneType>
Is the stick currently in bootloader mode? (did you hold down the BL button + pressed the RESET button + waited 2 seconds + let go of the BL button)
yessir, the device comes up as "QinHeng USB Single Serial " instead of the full name (SONOFF BLABLA)
i'll try again
I've used this flasher: https://github.com/agners/silabs-flasher and the elelabs flasher also works fine IIRC (https://github.com/Elelabs/elelabs-zigbee-ezsp-utility/)
If puddly's doesn't work, one of the above should
(also, what OS are you on?)
im using ubuntu desktop 22 (as a vm)
PRโs are up and I linked them here yesterday
yikes:
sudo silabs-flasher --device /dev/ttyACM0 flash --firmware ncp-uart-sw_7.1.1.0_115200.gbl
Trying to connect using EZSP...
Failed communicating using EZSP, assuming we are in bootloader.
Failed to launch the bootloader. Bootloader banner did not appear.
is there a delay between the last two lines? try holding the BL button + press reset once, so the bootloader message appears again (and the flasher hopefully recognizes it)
oh man my heart skipped lol
Firmware update [#######-----------------------------] 19%
well that's just awesome, started right up
thank you so much for your time
i am seeing 328 occurrences of this:
[0x2663:11:0x0300]: async_initialize: all attempts have failed: [ControllerException('duplicate 117 TSN'), 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>')]
[0xE06A: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>')]
[0xC4D6:11:0x0008]: 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>')]
[0xC4D6:11:0x0300]: async_initialize: all attempts have failed: [TimeoutError(), 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>')]
[0x2663:11:0x0008]: async_initialize: all attempts have failed: [ControllerException('duplicate 119 TSN'), 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>')]
but things are responding, i'll wait for the network to rebuild
where's the tip jar? ๐
the duplicate TSN stuff should be fixed soon-ish. The DELIVERY_FAILED just means the radio couldn't deliver the message properly.
oh great to know! safe to ignore for the time being then?
how big is your network?
Oh, I completely forgot to make a release with this change ๐คฆโโ๏ธ
Those are a known issue and will only affect startup
120 devices at the moment, probably 160 by the time i'm done
i can ignore this? it's strange since i have not specified these parameters:
Couldn't set EzspConfigId.CONFIG_MULTICAST_TABLE_SIZE=16 configuration value: EzspStatus.ERROR_OUT_OF_MEMORY
Couldn't set EzspConfigId.CONFIG_ADDRESS_TABLE_SIZE=16 configuration value: EzspStatus.ERROR_OUT_OF_MEMORY
There are defaults that are chosen. Try changing them to half in your config.
Hey puddly, can you help me to fix my yellow zigbee, I keep getting the error: โ silabs-firmware git:(main) universal-silabs-flasher --device /dev/ttyAMA1 --baudrate 115200 --bootloader-baudrate 115200 \
flash --allow-cross-flashing --firmware EmberZNet/NabuCasa_EZSP_v6.9.2.0_PA32_ncp-uart-hw_115200.gbl
2022-11-19 22:20:13 a0d7b954-ssh universal_silabs_flasher.flasher[803] INFO Probing ApplicationType.GECKO_BOOTLOADER
2022-11-19 22:20:15 a0d7b954-ssh universal_silabs_flasher.flasher[803] INFO Probing ApplicationType.CPC
2022-11-19 22:20:19 a0d7b954-ssh universal_silabs_flasher.flasher[803] INFO Probing ApplicationType.EZSP
Error: Failed to probe running application type
Run pip install --upgrade git+https://github.com/puddly/universal-silabs-flasher and then add --yellow-gpio-reset after flash
It seems the Yellow's Zigbee radio can sometimes lock up (when trying to flash) and needs a GPIO reset
the 7.x firmware in xsp1989's repo seems to be compiled with different options (and not with what's mentioned in the README for the 6.x firmware). So yeah, like puddly mentioned, 8 for both of those parameters should work (as that's the default)
ok, i try
a read of the config with bellows should let you know what options were set as then you can know what to put in the config
same error
Sent you a DM
bellows -d /dev/ttyAMA1 -b 115200 config -a
https://dpaste.org/7WhH2/raw is likely the output you'll get with 7.1.1
of those parameters, you only need to set the following in your config:
- CONFIG_MULTICAST_TABLE_SIZE to 8
- CONFIG_ADDRESS_TABLE_SIZE to 8
- CONFIG_SUPPORTED_NETWORKS to 2
- CONFIG_SOURCE_ROUTE_TABLE_SIZE to 128 (you don't need to do this, as the default is lower, but you probably want to set this to 128)
all others basically match the default (or bellows "doesn't set them/so uses what the firmware uses")
thank you so much, that removed any warnings
CONFIG_SOURCE_ROUTE_TABLE_SIZE - does this mean the max amount of devices?
bizarre binding problem:
I run ZHA, I have a group with a Leviton light switch (on/off, no dimmer) and four Hue bulbs. I also have a Hue RWL020 remote. When I bind the remote to the group (whether I bind both the OnOff cluster or both OnOff and LevelControl), the bulbs turn on and off perfectly but the light switch will only turn on, not off.
Not sure where to start poking at the problem? I've tried unbinding and rebinding a few times now.
Or would life be better if I just gave up, rebound the remote to the coordinator, and stuck with automations?
My guess would be fw issue with the Leviton
I'm thinking the same way but I don't think Leviton has firmware available and I haven't seen any relevant-looking config clusters ๐
at least it makes me feel better about returning the two Leviton switches I hadn't installed yet and buying a bunch of Inovelli Blues...
they don't as far as I know, but the fact they are doing works with HA for z-wave lends some hope that it will come at somepoint
bleah, yea, I just put it back over to triggered automations
not great, but if it turns out to be a reliability problem I'll just shove an Inovelli switch in there instead
It controls the size of the source routing table (if you enable source routing) ๐ . The total number of devices isn't a single setting, it depends on the type of device, how it's joined, etc.
(and possibly swap out the remote since it seems like the first-gen Hue remotes are known for jank anyway)
lol, tried a different brand remote from elsewhere in the house out of curiosity
and it worked perfectly
so it seems to be that first-gen Philips remote and not the Leviton switch
anyone have a strong opinion on surface-wall-mountable dimmers/remotes?
The Phillips ones are nice because they do a passable imitation of a real light switch (with a Decora plate). I got one of https://www.amazon.com/AduroSmart-ERIA-Wireless-Dimming-Switch/dp/B07HJHJWGT/ but I don't really like it because it's small enough that it's hard to find in the dark.
Second-gen hue remotes are still jank via a hue hub, but fine over zha. Haven't bound them, tho
they also have a single power button, brightness up/down, and a mystery button, though, right?
They still have only one binding table space right? ๐ฆ
The Hue button is technically the off button per the command sent. What i do is toggle the light when it seeโs ON.
I honestly prefer the new remotes, their quality is much better and the toggle is nicer than On / Off.
I love it because the new Philips Hue remotes have the holes to be mounted on the elecric boxes. And as you say, it completely replace the switch. So what I do is simply short the switch and replace it by a Philips Hue remote. It look very sleek.
The RWL022 (newer ones) shouldnโt be that limited IIRC. However, binding on/off is a bit annoying, as the shared on/off button will alternate between on/off (and doesnโt send toggle commands)
So sometimes, you have to press the on/off button twice
Itโs not an issue when using the Hue Bridge, as dimmers joined to those never do direct binding
lol thatโs...
Same issue on the Smart Button btw
Honestly they should have made the thing toggle. Is that a possible command?
Yes
I think there are some reasons why itโs like that though (edit: meh, Iโm unsure)
haha
Dunno, how would I check?
anyone home? trying to pass conbee 2 to docker from a mac mini
using this docker cmd:
docker run -d \
--name HomeAssistant \
-p 8123:8123 \
--privileged \
--restart=unless-stopped \
-e TZ=America/Chicago \
--device /dev/tty.usbmodemDE24332351 \
-v /Users/efelton/config:/config \
-v /etc/localtime:/etc/localtime:ro \
ghcr.io/home-assistant/home-assistant:stable
but ZHA does not see it
Try to bind it to more than 1 device and if it still control all of them at the same time you know then.
I wish you could bind like 30 lights to a remote to control them if HA goes down. ๐
Put all the lights in a group and bind the remote to the group
Not that I would do it ๐
but-you-could
Oh wait, but where does the group logic reside? You donโt need a coordinator for groups?
Groups are stored on the devices they know what groups they are in.
Got it. They then reply to their appropriate broadcast?
yep
ZHA may not auto-detect the serial port but try manually configuring /dev/tty.usbmodemDE24332351 in the setup screen
guves failed to connect
What radio type do you select?
deconz
Enable https://www.home-assistant.io/integrations/zha/#debug-logging and you should see the error message. It's likely a device permission issue.
I have a couple of philips motion sensors; both the same model. one was added to ZHA a while ago, and one today. The one today has extra options on the device page (Hue Motion sensitivity and led trigger notification), and the battery % actually works! - is there a way to get the same options on the other sensor (both are SML002).
I have a few zigbee switches connected via Z2M, which have been working great. Suddenly they are not working, and the entity state is "Restored". In the Z2M log the button pushes are working fine, but in HA it's broken - nothing on "action" nor on MQTT. Anyone got an idea on how to remedy this?
Anyone know if I can move a zigbee network from a homey pro to zigbee2mqtt without having to rebuild it all?
Does the Homey have a Zigbee stick you can remove?
is this an appropriate place to ask for help when a zigbee device is not pairing/joining properly? I'm a noob, so it's my first try and my first sensor.
zigbee2mqtt
SONOFF Zigbee 3.0 USB Dongle Plus-E
right next to it when I tried the first time, and now in the next room
That's ... not a great choice of coordinator for Zigbee2MQTT
For ZHA, sure, but not Z2M
It's not?
That's what I said
Because support is still experimental
The adapters below are experimental, don't use these if you want a stable setup.
ok - that sucks. I'm not realistically able to get any new gear for quite some time
Then consider switching to ZHA
Anyway, when you try to pair the device, does the logs in z2m page show something with respect to that device?
Also:
- Did you leave it at the default channel of 11, or pick one that's clear of WiFi?
- Did you put it on a USB extension cable?
- I was not aware I had the option of changing the channel
- yes
I made a post on the forums with some screenshots: https://community.home-assistant.io/t/noob-question-sonoff-humidity-temp-sensor-not-returning-any-data/491661
In the z2m page, is the permit join enabled?
The default channel of 11 is usually a bad choice
It does pair after a few attempt
but no data is available, aside from signal quality
no battery/humidity/temp
and this line stands out in the log: > Zigbee2MQTT:error 2022-11-20 13:01:40: Configure failed: Error: Bind 0x00124b00251d224b/1 msTemperatureMeasurement from '0x84b4dbfffecc16b2/1' failed (Route error)
You've got an error in the middle of that, it's not good
Also, those sensors have a track record of being ... not awesome. It's pretty common for them to stop reporting
What would switching to ZHA entail? is that a different option to Z2M ?
ok. So basically un-install the zigbee2mqtt add-on, and install a ZHA add-on?
I'll give it a shot ๐
Well, ZHA isn't an add-on, but yes
oh?
See the link
Zha is integral part of HA
#integrations-archived integrate Home Assistant with devices or services, or provide functionality within Home Assistant.
#add-ons-archived provide additional software or services, which an integration could possibility integrate with. Add-ons are for Home Assistant OS and Supervised only, other install methods can install software other ways.
I'll read up and give it a try
but uninstalling the z2m add-on is the first step, right?
Yep
Although may not be required, but do restart HA, just to ensure device is not busy
ok. The first step show in the documentation says "From the Home Assistant front page go to Configuration and then select Integrations from the list."
and I feel a bit dumb not seeing where "Configuration" is on the page ๐
start setting up a new integration
If I google screenshots I can see "Configuration" as a left-side tab. But it's missing in my interface
Settings -> Devices & Services . Click Add integration and type zigbee
I'm not on the same network as the home setup with my discord browser tab. But I found the settings now I think. I'll see what happens ๐
I have a lot of projects on hand, and I have a few hurdles googling i was hoping maybe someone can help me out with.
I already have a variety of Z-wave and Zigbee devices in my home with a Futurehome smarthub.
I want to transition completly to homeassistant due to local handling and wider device support, futurehome still isnt fully working properly with most of the devices. Thermostats show up 3 times etc.
I have HA in a VM on my server, and it is talking to the Futurehome hub via their API and an Add-on - but it's clunky and doesnt support all devices or commands.
What different categories of Z-wave/Zigbee adapters are there? I though i had to use USB-Adapter in my server, but.. Are there Z-wave/Zigbee "Hub"'s that you connect directly to the router, which my server/HA can access and fully access/manage as if it was a physically attatched like a USB adapter?
Hope my question makes sense.
I'm in Norway.
For Zigbee, you want something CC2652 based. You can get network connected Zigbee coordinators such as https://www.tubeszb.com/shop/coordinators/2, but see https://www.zigbee2mqtt.io/guide/adapters/#recommended for a longer list
You can use a CC2652 based coordinator with either Zigbee2MQTT or ZHA
Ah i see! So its called a coordinator. I'll read more on those devices, and Z2MQTT/ZHA now, thanks:)
The pinned messages have some good information
If you want, you can try to (remove and) re-pair the first motion first sensor.
Reconfiguring might work but idk in this case
Qnect SH-ZS01, anyone tried this temp sensor in HA?
happy sunday! looking for some insight.. i upgraded my coordinator (SONOFF ZPDongle-E) firmware to 7.1.1 yesterday, been working well so far but having a very weird issue . If i remove a bad device (ie: unresponsive motion sensor), then re-pair it, it does not create a new unique device; it seems to re-use whatever device/entity names it had before, and never updates data for the device even though check in time updates.. example - unresponsive motion sensor stuck motion "ON"; i remove it, then re-pair to network, the motion value is still stuck on "ON" and never goes off (tape covering sensor, def no motion). only time i was able to re-pair a motion sensor and it worked, the device was detected as 'unk unk vendor' - i added it this way just to test and it worked..
something to do with unique ID's? should i be purging devices/entities data somewhere other than 'remove device' ?
how are you removing the device?
if you use remove device just wait a minute or 2 before pairing it again
go to the device, click the 3 dots, then click the 'remove' red button
got it, will try that. thank you! i ordered one of the tubeszb coordinators, hoping to have a better time with it
this should work fine on 6.10
7.x is still kinda screwy
yeah i am thinking of flying back to 6.10
i cant just go back by flashing directly right? i need to flash something to clear nvram first?
do you like 6.7 at all or just keep it on 6.10 and thats it? curious on your thoughts..
Any idea why my light(s) wont toggle on or off? They were working after initial setup then they just stopped working. Brightness still works, same with color. Just no toggle functionality
Do they work in the Z2M dashboard?
Everything but the on/off toggle works
And that's in the Z2M dashboard?
yes
Check the log file for Z2M
Zigbee2MQTT:debug 2022-11-20 17:57:40: Saving state to file /config/zigbee2mqtt/state.json
Zigbee2MQTT:debug 2022-11-20 18:01:10: Received MQTT message on 'zigbee2mqtt/Liams Room Light/set' with data '{"state":"OFF"}'
Zigbee2MQTT:debug 2022-11-20 18:01:10: Publishing 'set' 'state' to 'Liams Room Light'
Zigbee2MQTT:info 2022-11-20 18:01:10: MQTT publish: topic 'zigbee2mqtt/Liams Room Light', payload '{"brightness":61,"color":{"h":32,"hue":32,"s":82,"saturation":82,"x":0.4599,"y":0.4106},"color_mode":"color_temp","color_temp":370,"linkquality":134,"state":"OFF"}```
Am I missing something? Looks like it's saying it's off when it isn't?
Zigbee2MQTT:debug 2022-11-20 18:04:17: Received MQTT message on 'zigbee2mqtt/Liams Room Light/set' with data '{"state":"OFF"}'
Zigbee2MQTT:debug 2022-11-20 18:04:17: Publishing 'set' 'state' to 'Liams Room Light'
Zigbee2MQTT:info 2022-11-20 18:04:17: MQTT publish: topic 'zigbee2mqtt/Liams Room Light', payload '{"brightness":61,"color":{"h":32,"hue":32,"s":82,"saturation":82,"x":0.4599,"y":0.4106},"color_mode":"color_temp","color_temp":370,"linkquality":138,"state":"OFF"}'
Zigbee2MQTT:debug 2022-11-20 18:04:18: Received MQTT message on 'zigbee2mqtt/Liams Room Light/set' with data '{"state":"ON"}'
Zigbee2MQTT:debug 2022-11-20 18:04:18: Publishing 'set' 'state' to 'Liams Room Light'
Zigbee2MQTT:debug 2022-11-20 18:04:18: Received Zigbee message from 'Liams Room Light', type 'readResponse', cluster 'genLevelCtrl', data '{}' from endpoint 1 with groupID 0
Zigbee2MQTT:info 2022-11-20 18:04:18: MQTT publish: topic 'zigbee2mqtt/Liams Room Light', payload '{"brightness":61,"color":{"h":32,"hue":32,"s":82,"saturation":82,"x":0.4599,"y":0.4106},"color_mode":"color_temp","color_temp":370,"linkquality":138,"state":"ON"}'```
Seems its broken in some way
Setting it to off returns on?
Unless i'm understanding it wrong?
Have you tried power cycling the bulb?
Won't make any difference
didnt think so
The light seems like it's turning on when you set its color
Which would be typical
Since in the payload you're setting both the state, the brightness, and the color
I'm only pressing the on/off switch ๐คทโโ๏ธ

Configuration got renamed