#zigbee-archived
1 messages ยท Page 140 of 1
I had planned on trying it this weekend, guess I'll hold off and see what's going on ๐
any new info about low level stack bug in the SiLabs EFR32 used by IKEA devices that causes them to crash?
"SI Lockup Bug"
I have not heard of Ikea publishing firmware that fixes the issue in EmberZNet firmware. @austere patio has kept me educated here and would likely know of the update if there were one. But to my knowledge, this has not been fixed.
I did a bit of research on this because I was curious. I think the TI article you're referencing is this one (https://www.ti.com/lit/an/swra427d/swra427d.pdf?ts=1622564745835) where they are pushing 400 nodes with CC2530's in 2014. The technology has come a long way since. I think the SI article you're referencing is this one (https://www.silabs.com/documents/login/application-notes/an1138-zigbee-mesh-network-performance.pdf) and I'm having a hard time finding a date on this one.
Both articles post very positive results.
I feel good about pushing 1,000 devices on a network, but I think it would be difficult to even provision 1,000 devices in such a density. I think most use-cases would call for separate networks on separate coordinators. It's an interesting thought exercise for sure.
I doubt in a hobby setup anybody is going to get close enough to 1K devices for it to matter
I mean, if you had 20 devices per room, you'd need a very big house to hit that ๐
100% agreed. But for those with commercial aspirations, I think choosing Zigbee as a communications protocol is sound architectural decision for handling 100's of low-powered sensors
I might try doing an upgrade of my CC2531 with a spare Pi laying around tonight. Any chance if you know if this is still true? Zigbee 3.0 firmwares are not recommended for the CC2530 and CC2531 (since those are not powerful enough) (coming from https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator#im-using-a-cc2530-or-cc2531-which-firmware-should-i-use)
I was hoping for firmware tweaks ๐ I'll be going with the latest 1.2 then
and software usually ask for more not less
the CC2531 should be able to run my 9 device network ๐
yah that should not be a problem
anyone know if changing zigbee usb stick requires re-pairing of all devices?
Using Zigbee2MQTT
is there a way to remove devices from your MQTT broker?
i.e. I have a double up in devices...
thanks.
Send a null (empty) message to the MQTT topic.
where do I find the version?
you are gonna have to spoon feed that to me mate lol
fwiw, i only use MQTT to get z2m to talk to HA
I have never really touched anything bar the config file
lol... use something like MQTT Explorer, find the duped topic (which shouldn't be there) and then publish an empty message to it.
MQTT Explorer even lets you delete retained messages in the UI, there's a button for it
ah cool, will open that up
looks like I'm repairing everything AGAIN ๐ฆ
just got a Electrolama zig-a-zig-ah! (zzh!)
CC2652R
coming from the sonoff USB C2531 I think
Then look at the top pinned message
ok ok.. settle I'm not on discord often ๐ฆ
That's the one, and it covers _ ... snapshot the device state and move your network between any supported hardware and firmware versions._
have you used it?
Awesome..
Cool, Lidl has some gardening "computer" over Zigbee
actually a water valve, nothing more ๐
โฌ 24,99 in Belgium
damn, i hoped it would do all the gardening
๐
Surgery completed successfully, my CC2531 is now running 20201127
how do I recognise which of my serial ports point to my zigbee stick? Have 2 usb devices one of which is my ssh which my whole pi is running of
The offered options are:
/dev/ttyUSB0 - USB Serial, s/n: n/a
and
/dev/ttyAMA0 - ttyAMA0, s/n: n/a
unplug it, see which one vanishes
or read from lsusb if you are lucky
and use persistent paths, not transient ones...
How do I do that?
do I simply mount the desired device?
and found out its the ttyUSB0 based on unplugging it
that command returned this:
lrwxrwxrwx 1 root root 13 Jun 2 14:58 /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 -> ../../ttyUSB0
should I do anything more?
use that path for mapping the usb stick
k, thanks for the help
/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
Whats the best method of tracking power consumption? Voltage? Watts?
Thanks mate
So, most blueprints for z2m don't work if I use z2m and HA core in docker, is that correct?
To say, they are made for the z2m version that can be integrated in HA with supervisor and all? I'm somewhat confused...
It should work regardless - Z2M is Z2M
Anyone got any recommendations for door contact sensors that will happily use hue bulbs as routers?
Nope. First, ANY bulb as a router is generally a bad idea. Get some real mains powered devices as you're going to have nothing but problems relying on just bulbs as routers.
But I won't have z2m in my integrations list, as it's just messages that come via mqtt, right?
Correct. You don't need the integration as all your devices are done through MQTT discovery.
If you look at the
-> Devices view you'll see it listed against individual devices when you look at them
Firmware: Zigbee2MQTT 1.18.3
for instance, under Device Info
You've set up the required integration input?
No, not sure what you mean exactly...
That blueprint looks to take an input that says what kind of Zigbee integration you're using
input:
integration:
name: Integration
description: Integration used for connecting the remote with Home Assistant. Select one of the available values.
selector:
select:
options:
- deCONZ
- ZHA
- Zigbee2MQTT
Ok, yes it has a dropdown I set to z2m.
Then it's probably worth asking for help on that thread, since entities are entities, so it's likely a problem relating to that blueprint
I have one automation that works, but is not reliable. I have to press the button 2-5 times sometime for it to trigger. I thought it was just the zigbee hardware, but z2m sends its mqtt messages every time, and I can see the state change in HA also every time. I have no idea how to check what's going on...
Have you had problems already with your Aqara stuff interacting with Hue bulbs?
Well apparently Xiaomi battery stuff will only connect to Xiaomi stuff
Nah
Though will happily connect to my non-xiaomi coordinator so ๐คท
I have Xiaomi battery stuff connected to non-Xiaomi stuff
Indeed, I have no mains Xiaomi stuff ๐
Hmm ok was going by what some guy was saying in here yesterday
Well... as in the pinned messages, Xiaomi stuff (like many other brands) isn't exactly standards compliant
That thread is worth a read though
Mine route through Gledopto, Ikea, Innr, Lidl, Hive, and some Salus stuff - plus the DIY routers
Hmm ok. Last time I looked they were all connected directly to the coordinator despite me repairing them
Do they work?
Yeah but I doubt if I put some further away they would. Plus I've temporarily moved the coordinator more central with a cable
If you put them further away they'd route differently 
Moving stuff around after you've paired it though, that's a recipe for pain
Oh
I was still wondering whether to keep the coordinator in my office in the corner of the houee or move it central
Mine is in the corner, not ideal, but it all works just fine
I had real problems pairing some of my hue bulbs until I moved the coordinator
Like 5 or 6 that just wouldn't pair. And then I moved the coordinator to the lounge and they all joined quickly
https://camo.githubusercontent.com/44d64fc8b311038cbd50fc20950abd298812a671c839a0b7d9e6fce0f10564bb/68747470733a2f2f692e696d6775722e636f6d2f386f65307554512e706e67 mine is pretty much where the green humidity symbol next to 45% is
I have devices in just about every room in the house, routers scattered around, everything works
Pretty much every window has a Xiaomi sensor on it, only a handful connect directly
Hmm these just wouldn't pair no matter what I did
Go read the pinned message on Xiaomi
Well, who knows then
Yeah
It's like they ignored all the other bulbs around them and needed the coordinator to be closer
With z2m, can I pair devices via a router instead of the coordinator? Like with ZHA.
Yes
Do I need to do anything special? I held my Ikea wall plug next to the bulb for pairing, but nothing happened...
I reset the bulb of course
Why are you trying to pair to a specific device? Pair your device where it's actually going to be positioned, allow the mesh to figure out what its parent should be.
Yeah, what Mono said... Pairing directly to a router should really only be done in edge cases. It's only part of the Zigbee spec because of those rare cases. Plus, there is zero guarantee that when you pair a child to a router, that'll it'll actually stay on that router.
The pairing info says to keep the bulb close to the coordinator, I can't do that so I thought I'd bring a router close to the bulb...
So just keeping the router close should work? I remember with ZHA I had to start the pairing specifically for a router in HA, but can't find such an option in z2m
it shouldn't need to be close unless it's one of those weird devices that uses sound as well.
Hmm, either with router close or not it does not pair, just blinks. I had it paired via ZHA before.
It's this one https://www.zigbee2mqtt.io/devices/LED1546G12.html. I didn't change the channel, so it should be 11 I think?
Ahhhh... good old Ikea bulbs. Yeah, I've never had good success with them on 11. 15, 20, or 25 are the channels they like.
What sucks is that if you have an established mesh, changing channels can be a PAIN.
Hmm, I just paired my first 6 devices, so I guess it would be an ok time to do it now
Yeah, I'd go with 15 to start (but, be aware of what your WiFi AP channels are set to). If your WiFi channels are low (1,6,11, etc), you'll want to go with 20 or 25 for your Zigbee channel.
Thanks, I'll look it up
hi friends! i have a husbzb-1 running with zha on my raspi (docker). it worked fine for a while, then it randomly stopped working, then i stopped using HA for a while - now i'm trying to get back into using it, upgraded, but zigbee still isn't working. i can see my zigbee lightbulbs on the map, but triggering them in lovelace doesnt actually do anything. there's also a few worrying lines in the log (lemme dig em out real quick)
2021-06-02 12:39:38 ERROR (bellows.thread_0) [bellows.uart] Lost serial connection: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2021-06-02 12:39:38 ERROR (MainThread) [bellows.ezsp] NCP entered failed state. Requesting APP controller restart
2021-06-02 12:58:02 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xF607:1:0x1000]: Couldn't get list of groups: ApplicationController is not running
2021-06-02 12:58:02 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xF607:1:0x1000]: Couldn't get list of groups: ApplicationController is not running```
Either it's loosing connection to usb (bad power supply) or multiple instance are running at the same time. Check syslog
syslog as in /var/log/syslog on the host? what am i looking for?
Hi everyone, I have issues getting zigbee to function after a (presumed) SD card crash. I set up a completely new rig with RPi4 and SSD. Everything went fine up to the point where I installed mosquitto broker and zigbee2mqtt
The devices just won't pair, sometimes I get the ID, but it says it's unsupported. This was not an issue before...
The logs say nothing...
If you run dmesg you should see lines referring to the USB device. Usually when it disconnects there is something logged.
If not, make sure that you are not running two HA instances (e.g. two containers by accident?) and that only one process is using the serial port.
hey guys. I just got some LED1924G9 Ikea bulbs and these ones wont do anything but say unsupported even though they are supported on z2mqtt https://www.zigbee2mqtt.io/devices/LED1924G9.html i do have some other ikea bulbs but they were a different model number but they work perfectly.
hmmm not seeing anything suspicious in dmesg: https://pastebin.com/iXZ8jr6f
also only see one docker container running -
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
16d7369132eb homeassistant/raspberrypi4-homeassistant:stable "/init" 3 hours ago Up 2 hours home-assistant```
https://gyazo.com/310b7da3ade7d5d48d9dad8ecc61275a anyone have any recommendations on how to fix this?
lsof|grep tty gives me this, but idk what to make of it:
bash 776 pi 1u CHR 4,1 0t0 5745 /dev/tty1
bash 776 pi 2u CHR 4,1 0t0 5745 /dev/tty1
bash 776 pi 255u CHR 4,1 0t0 5745 /dev/tty1```
Ah, silly me RPi4 and interference.... used an USB extension cable and everything works...
anyone have any paths to put me down for this? ๐ฆ
I'd check if it's already supported in the dev branch. If not, Z2M requires every possible device to be explicitly supported, even if it's a minor variation of an already functional device so you likely need to just copy/paste its model info into some file.
i see. its just weird. the model number does match exactly.
any other ideas what might be going on with my setup? or things i could prod to debug further?
I've seen the logs claim something's unsupported when the interview went wonky. If you're sure that model is supported, just keep trying. My IKEA devices took soooo many attempts to pair (30+ per device, I was ready to throw myself out of a window that day).
digging into this some more, everything seems to fail with. 2021-06-02 17:17:03 DEBUG (MainThread) [homeassistant.components.zha.entity] light.bathroom: turned on: {'on_off': ControllerError('ApplicationController is not running')} now only to figure out why it isnt running lol
2021-06-02 17:11:35 ERROR (bellows.thread_0) [bellows.uart] Lost serial connection: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2021-06-02 17:11:35 DEBUG (MainThread) [bellows.ezsp] /dev/ttyUSB1 connection lost unexpectedly: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2021-06-02 17:11:35 ERROR (MainThread) [bellows.ezsp] NCP entered failed state. Requesting APP controller restart
2021-06-02 17:11:41 DEBUG (MainThread) [bellows.ezsp] Resetting EZSP
2021-06-02 17:11:41 ERROR (bellows.thread_0) [bellows.uart] Lost serial connection: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2021-06-02 17:11:41 ERROR (bellows.thread_0) [bellows.uart] Lost serial connection: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2021-06-02 17:11:41 DEBUG (MainThread) [bellows.ezsp] /dev/ttyUSB1 connection lost unexpectedly: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2021-06-02 17:11:41 ERROR (MainThread) [bellows.ezsp] NCP entered failed state. Requesting APP controller restart
2021-06-02 17:11:41 ERROR (bellows.thread_0) [bellows.uart] Lost serial connection: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
``` guess it boils down to the same thing again
I believe you're using a Pi as well. Do you have it plugged into a USB 2.0 port (not 3.0)? With an extension cable? And you're not running a SSD off of the USB ports as well, right?
What pi is this? And depending how are you running docker, it may not deal correctly with usb hot-plugging. That error indicates that it cannot communicate with the usb adapter. Replug adapter and reboot the host.
Ok, I got the one mesh part but... What if having several coordinators on different zigbee channels?
There is no advantage to that
It will create interference
And your meshes will be weaker
And stop using non persistent paths to the adapter
Aha. Ok, sound like a bad idea then. I am still trying to build some kind of "redundancy" into this. If the coordinator fails everything does until new one in place. Perhaps there is no way to do that...
Buy a spare coordinator, take backups when you add a new device, and in the unlikely event of your coordinator failing swap in the replacement and restore the backup

I have slapped and spanked my coordinators for almost three years
they have never failed
probably never will
but now I have a spare, just because I wanted to try a second model
Sorry, don't slap me too hard (I tried to find discussion related to this, but failed);
Is there a workaround how to get the Ikea Fyrtur covers to work with the 2021.6.0 version? After I updated into this version, my Home Assistant does not want to play together with Zigbee2mqtt, with the covers and I'm unable to control or even monitor the status of these covers from HA.
Log error: https://paste.ubuntu.com/p/rjNHY4G2bt/
I don't know if I should do something about this, is it something I could/should fix via configurations or is this a bug in HA/zigbee2mqtt/somewhere?
Thanks :) I did read the Breaking Changes thoroughly yes, but failed to find what should I as user to actually do in order to keep it working. But I'll follow this issue for the time being!
Mostly in these cases the only things you can do are:
- Get involved in future betas (I have a separate install for testing betas with)
- Ensure the issue is raised with the dev of the other software
For the record, fix can be found here: https://github.com/Koenkk/zigbee2mqtt/releases/tag/1.19.0
I know 1.19 has caused issues for a few folks, but I don't know how widespread it is
That looks to only be CC253x users
yep, I was just about to note that ๐
It also looks like they all have old coordinator firmware
I did a repairing round through the house and it works stable again. But I only have 9 devices, if you have way more that might not be an option ๐
Upgraded firmware too indeed, never did that before (which means I was running 20190109 )
Yeah, I wonder if the 2019 firmware has bugs... oh, hang on, what am I saying 
But as I didn't have a CC download cable, I just sticked with it. Performed surgery on the device yesterday (had to do some magic with dupont cables that were having too large connectors), now it works again.
Anybody with one of those should have a flash cable/capability anyway
Or should be planning on replacing it with something that's actually good
I was thinking about the latter, but hey: "it still works" ๐คทโโ๏ธ
If I buy a new device, I need to be able to hide the purchase from Ms Hmmbob ๐ ๐
/kidding
does it break something if I uninstall the current z2m 1.1.18.1-1 and install the new 1.19.0-1 from another source? I mean, do I need to backup the configurations or something?
or should it be "drop in replacement"-ish?
no for it shouldn't break or no for it's not drop in replacement? :D
lil help before the wife kills me?
Tried to restart z2m and it died in the arse and will not restart
Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
And a few thousand Google hits on it too ๐
Fuck Google, I come to the pros for help
The CC2530/31 are well known for locking up and requiring removed and re-inserted
I have a zig zah hah or whatever
But, if you're using the /dev/tty* path, that can change
yeah thats what I was using
If you're on the pre 2021 firmware with the ZZH then that also has lockup bugs
should be the most recent (or whatever was most recent 6 weeks ago when I got it)
this is true
Check the path first, and switch to using the long one, /dev/serial/...
/dev/ttyUSB0 potentially
I've mapped mine to /dev/zigbee (and the zwave adapter to /dev/zwave obviously), so there can be no mistakes. Need to find the tutorial on how i did this though
please pass on when you do!
[ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=DC:A6:32:73:88:C2 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=9d036fca-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[ 0.001808] printk: console [tty1] enabled
[ 1.438681] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 36, base_baud = 0) is a PL011 rev2
[ 5.054774] usb 1-1.2: ch341-uart converter now attached to ttyUSB0
I am guessing that ttyUSB0 is where it is
which is what is in the config.yaml also
/dev/ttyUSB0 is listed in the config yaml
permit_join: true
mqtt:
base_topic: zigbee2mqtt
server: 'mqtt://localhost'
user: '!secret mqtt_user'
password: '!secret mqtt_pass'
serial:
port: /dev/ttyUSB0
I've got this in /etc/udev/rules.d/10-local.rules on my Docker host:
SUBSYSTEM=="tty", ATTRS{idVendor}=="0451", ATTRS{idProduct}=="16a8", SYMLINK+="zigbee"
SUBSYSTEM=="tty", ATTRS{idVendor}=="0658", ATTRS{idProduct}=="0200", SYMLINK+="zwave"
This makes my adapters always come back online under /dev/zigbee and /dev/zwave respectively, regardless of which port or order they are plugged in
ls -al /dev/serial/by-id/
Or just use the fact that these days you get a unique path all the time anyway
returns lrwxrwxrwx 1 root root 13 Apr 18 19:15 usb-1a86_USB_Serial-if00-port0 -> ../../ttyUSB0
There you go, you have a nice long unique path already
so if thats in my config, why is it not working
is there a way to display the full path?
I am lost mate.
Use /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
also, my z2m log is fkn massive, how can I just restart and see what the log spits out about the restart?
using docker...
docker start zigbee2mqtt -a
got it
Yeah, it'll rotate the log. You can find old logs in the /log folder
Zigbee2MQTT:error 2021-06-03 18:55:51: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0'
still...
ah
Bet you're not ๐
I doubt I am because I didn't know I had to, nor how to HAHAHA
I love coming here, always turn up with a problem, feel like a dumb / shit c*** and then leave feeling enlightened
Learning by figuring it out yourself ๐
(with some helpful pointers, of course)
so where do I find the container config usually? is that the one inside the actual container?
Well, how are you running it?
compose
Then your compose file...
Did you rebuild the container?
docker-compose up -d zigbee2mqtt
hmmm now its just sitting as restarting...
You can watch the logs
Zigbee2MQTT:error 2021-06-03 19:02:21: Failed to start zigbee
Zigbee2MQTT:error 2021-06-03 19:02:21: Check https://www.zigbee2mqtt.io/information/FAQ.html#help-zigbee2mqtt-fails-to-start for possible solutions
Zigbee2MQTT:error 2021-06-03 19:02:21: Exiting...
Zigbee2MQTT:error 2021-06-03 19:02:21: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0'
again, the same thing
is it a permissions thing by any chance?
No
It's a layer 8 thing
devices:
- /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0:/dev/ttyUSB0
Do you understand what that line is doing?
yes
Yes
WOWEE
So, the left side is the path on the host, the right side is the path in the container
following
So, with that in mind, why the f**k did you tell Z2M to use the the path on the host
Zigbee2MQTT:error 2021-06-03 19:02:21: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0'
uhm, thought you guys said to?
fkn hell mate, english!
You have to pass that path to the container, since that path will never change
However, you can call it whatever the hell you like in the container
You called it /dev/ttyUSB0
ah
So, you know, in the container you kinda have to use that
and I pass that path via the compose file?
Ok, step back a moment
devices:
- /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0:/dev/ttyUSB0
^-- path on the host --------------------------^ ^- path in the container
You already passed a path to the container
oh
So, the container sees /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 as /dev/ttyUSB0
Yes, since that's the path in the container
and in the docker-compose file the 'host' path?
Your compose file is fine
i think you need a venn diagram
And possibly a little more time with the Docker docs
i won't need a venn diagram when I've got a bullet in the head
where'd you find that pic of me?
still failing to understand how this has occured though considering I have not touched a single thing, the device has not power cycled since it was set up etc etc
Remember, a few hours of trial and error can save you several minutes of reading the documentation.
so this compose file https://pastebin.ubuntu.com/p/XzQPcjR6cS/
and this z2m config file https://pastebin.ubuntu.com/p/rKFsD5RKjR/
should be working
Looks good
I wonder what else could be the problem then ๐ฆ
yeah just power cycled the pi
You may still need to push the reset button, not entirely sure
ok
Or flash it with the current firmware
But you did learn something!
yeah that I am a dumb c***
That you don't yet understand Docker "enough"
And that you need a few more hours of trial and error ๐
haha
I was refreshed on some things
and always turn it off and on again
and now I have to figure out how the hell to reset / unpair an old philips hue LED strip
I have a Sonoff zigbee door sensor connected on ZHA, which works fine, but goes unavailable overnight or if we don't open the door. Opening the door then triggers it, so I suspect it's just not sending to HA when nothing happens. I am sure I have seen something about changing the timeout, but I can't find it. Please could someone point me in the right direction. Ideally I just want to override the time on this one sensor, the others are all Aqara and work fine as they send the battery status every couple of hours.
The Sonoffs are known for being junk
thanks for putting up with my shit lads
that was frustrating, literally started working as the wife walked in from work ๐
Hello. Does anyone know if there is a way to trigger (via a service call?) the ZHA Integration's "Update configuration" event (reachable via UI: Configuration-->Integrations-->ZHA/Configure-->Update configuration). This seems to fix my problems when my Sonoff ZB Bridge drops out with "[bellows.ezsp] NCP entered failed state. Requesting APP controller restart". Thank you.
This is very much not a solution ๐
That error is logged only when serial communication with your bridge is broken
So the underlying problem needs to be fixed (i.e. reposition the bridge or get a better wireless router)
Or replace it with something that doesn't use WiFi, since WiFi and Zigbee on one device, that close together, that's not a good plan
Try opening/closing the door to keep the sensor awake (or maybe clicking the button if there is one) and then clicking the "reconfigure" button in the device page. ZHA should have setup reporting for the battery status, which would cause the sensor to check-in periodically and let ZHA know that it's alive.
That works OK except it normally goes off when we are asleep.
I know that is why I only have 1. I am currently waiting on the some replacement aqura ones, but in the meantime wondered if I could tweak something to stop HA assuming it's gone away. It's sitting within 2 metres of a Router in a switch.
The problem is the device isn't reporting/responding
Right. But the problem seems to be that the device was never fully initialized by ZHA and didn't setup some sort of periodic reporting. Does it have a battery status?
It does, but it only seems to report it when the door opens/closes
I will have another go at pairing it to see if that helps. I have tried that a few times before though
Hmm, that shouldn't be showing up then if battery reporting wasn't setup properly
Could just be a weird sensor
Yes, don't worry when the slow boat from China delivers my new pack I will replace it and put it in the "don't buy the VERY cheap" stuff pile!
When I change the 'friendly name' in z2m via the web gui, will that be reflected in HA?
Yes
Assuming of course you enable that when renaming it ๐
Turn it on, and as it suggests, it'll update the HA entity
Is that in the z2m settings or HA? Can't find it in z2m...
It's in Z2M when you click on the Rename button in the UI.
It's a per device "setting" that doesn't stay sticky.
I was looking the settings, thanks!
is there a way to make the aqara switch not report every hour the battery state ?
feels a bit overkill and draining more battery than needed
Sure, pull the battery out
You need it to be talking on the mesh regularly so it doesn't fall off
yeah, it might just be something I notice now, because I'm adding more devices in one time
If I take a device out of range (like miles) and bring it back, will it automatically reconnect or would I need to repair it?
Specially an aqara zigbee vibration sensor
It should, yes. Although, Aqara devices are notorious for not reconnecting automatically when separated from their parent router.
You can't configure the attribute reporting interval for Aqara sensors but I wouldn't worry about it. I think I change my batteries like once every two years.
Zigbee is designed to be incredibly efficient anyway, so once an hour is nothing.
Once a minute would still last forever.
now to figure out what I can do with the vibration sensors ๐
Use them as a trigger for mood lighting and romantic music in the bedroom, of course.
They do great as glass break sensors. ๐
that's what I already had in mind, for the glass breaking
Ya huh... 'glass breaking'
or opening windows
I could also mount one on the dogs bench
and try one in my car, if the signal is strong enough
So you know how many reps it pressed?
lol
This is your only bad idea so far. You don't want to use a mesh device if it's going to be out of range of the mesh.
I use presence sensors in both of our cars. They actually work better than I thought they would initially.
BUT... I also have some really good routers as well (CC2652P2).
any specific reason for that? (my brain is gone for the rest of the day)
Some devices (specifically Aqara and Xiaomi and maybe a few others) have issues reconnecting to their parent router if disconnected for an extended period of time.
oh
that's actually something I can try
just move one sensor away for a day
and see what gives
and do that routine for a couple of days
Yup. I've not tried it with any Aqara devices, but my Samsung devices work fine disconnecting/reconnecting to the mesh.
I'll try that and post the results here
I didn't give more information because it was already given: #zigbee-archived message
downside of replacing the Xiaomi zigbee hub with a usb stick is editing the automations (maybe) but the stick itself seems extremely stable
This is the way.
I know it would be a dirty solution, but only until my zzh! CC2652R stick arrives. The Sonoff ZB Bridge is actually placed right beside the Wifi router, it shows a perfect connection - (100%, -10 dBm), but still drops out constantly...
You might be able to use https://github.com/walthowd/ha-constant-modifier to tweak https://github.com/zigpy/bellows/blob/dev/bellows/zigbee/application.py#L32-L34
The radio library should auto reconnect on its own, it probably just takes too long when the bridge disconnects so frequently
So reduce MAX_WATCHDOG_FAILURES to 0 or 1 so it immediately resets instead of taking a minute
Hey, since a while I have the problem that I get multiple events (up to five or six events per click) with my various IKEA buttons/remotes. Do you have any tips on what I can do about this?
Which integration are you using? (Z2M/ZHA/something else)?
ZHA with a conbee2
I believe there was a zigpy issue opened about this exact problem a while ago
Changing the battery or something fixed it, iirc
My smartthings buttons do this when battery is low
Yes, have found here (https://community.home-assistant.io/t/zha-multiple-events/120878/2) and here(https://github.com/dresden-elektronik/deconz-rest-plugin/issues/4227) some on the subject and already tried various things (battery change, ha restart, raspi restart, device reset) but all have not helped. Got a new symfonisk remote today and it has the same problem.
Is it possible to run a router firmware e.g. on CS2531 with zha/zigbee2mqtt?
Seems like it should be possible to connect and send messages to other nodes as a router in general for zigbee...
(as opposed to controller)
OK, I will try. What exact integration name should I put in the configuration.yaml bellow the "constant_modifier:"?
I think this will work: ```yaml
constant_modifier:
bellows.zigbee.application:
MAX_WATCHDOG_FAILURES: 0
yes, google cc2531 router firmware.
And I guess the manifest.json with a "version" is now needed as well?
Ah, I forgot they released that
Won't work, unfortunately. You'll have to edit the package directly within the HA container ๐ฆ
thanks - I've tried https://github.com/Koenkk/Z-Stack-firmware/blob/master/router/Z-Stack_Home_1.2/bin/CC2531_router_2020_09_29.zip which paired with my hive hub controller ok - but had no usb serial. Also tried now the CC2531-router-diag-usb.hex one from ptvo.io - can't pair, but does has usb serial, however zha fails to connect to it (maybe because it's not paired to network?)
I am on a Home Assistant OS and cannot access the source files...
You can, it's just a bit of a chore
copy the source to custom_components?
I've never used the ones with serial enabled. I think you can hit one of the buttons to reset/get it in pairing mode.
It's not a component but a Python package that ZHA indirectly uses. You might be able to put the bellows subdirectory of https://github.com/zigpy/bellows/ into the /config/deps/ folder and edit that, but I think the version number being 0.25.dev0 might make HA re-install it? I have instructions for getting into the appropriate container here (just ignore the installation stuff): https://github.com/zigpy/zigpy-znp/blob/dev/TOOLS.md#in-home-assistant-os
Maybe it just doesn't want to pair today - I want to use the router on the pi I'm running HA on as the means of HA talking to the zigbee network....is that really supported? :/
Do you have a coordinator?
So you're trying to use the CC2531 as a router and want to talk to the Hive hub's network through it?
yes...not sure if that's compatible
I mean you should be able to talk to other devices on the network as a router - but idk you probabbly won't be able to intercept all the messages which might be needed for HA to monitor all the devices on there
It's not, unfortunately. I believe the router builds of the CC2531 firmware only spit out diagnostic info. Even if it were to work, ZHA and all the other Zigbee solutions expect to have control over the coordinator
yeah makes sense
So you can use the CC2531 as a coordinator and just make a new network
Can I NAT the two controllers or something? Or proxy devices from one network onto the other?
Nope
Very bad things start to happen when two devices on the network both say they're 0x0000
Sure I get that - and this is probabbly needlessly painful - but can you have e.g. a device with 2 zigbee radios on both networks as a router, and spoof traffic from one network to the other?
Just wondering if there's a way to get Hive cloud and HA both able to control the devices on the network
In theory yes but the transmit part of the firmware is not easy to write
You can use a CC2531 as a sniffer and just work with the raw Zigbee traffic if you're looking to hack something together yourself
But you won't be able to transmit, only receive
Ok, guessing you;d have to write firmware to do that too.
There is sniffer firmware but no software that can hook the traffic into e.g. zigpy and then expose it in HA
not just void OnRecieve(message) { othernetwork.send(message.source, message.data); } etc
You'd likely have much more luck just migrating the entire Zigbee network to HA ๐
yeah I will do that if there's no off the shelf sw to do it ๐
None that I'm aware of. If you have a large (25+ device) network the CC2531 won't perform all that well as a coordinator due to range issues and firmware stability. The channel's pinned messages have various recommendations for more capable hardware.
Yeah read that - I don't, not yet. Thanks for helping!
That and it having firmware glitches that cause it to lock up, plus it being its own USB controller, cause it to just completely die unless you cut power every once in a while
But it's worth the $5 you probably paid for it ๐
What credentials should I use at this step?: 2. Drop into a regular shell by running login. root does not work, nor my HASS user...
I run login, it asks me core-ssh login:
Does root not work? In my VM it just logs in without a password.
Maybe for the SSH addon you have to do some configuration to generate credentials
core-ssh login: root Login incorrect
I'll check that
hmm... I am just using an ssh-rsa key, no other credentials..
`authorized_keys:
- "ssh-rsa AKDJD3839...== my-key"
password: ''
`
Lemme give it a try
You can omit the login part, the SSH addon just gives you a normal shell to begin with
zigbee2mqtt on hassos, usb coordinator CC1352P-2. Stopped working, here's the log, what is the cause? https://ghostbin.co/paste/vrfw
Have you unplugged it and plugged it back in?
I didn't, and it's in a place which cant be knocked.
No I mean have you tried unplugging it and restarting Z2M
To get it working again, I tried toggling a switch a few times from the z2m gui and then it works again. Or restartin z2m will make it work again yeah
but until I do that, my switches etc dont work, which is no good for the wife ๐
Your coordinator shouldn't not respond to a SYS.Version request
Is this a Z2M startup log?
it was just the log
So Z2M is functional?
Does it work after you restart Z2M but not touch the hardware?
Without actual debug logs for Z2M and herdsman it's hard to tell
But if it's not a hardware problem then it's a Z2M problem and since I don't use Z2M I probably can't be of much help
I can get the debug logs, turned on debug last time it happened
Hmm I dont know where the logs are,
the logs I can find just show Starting zigbee-herdsman and thats it
Which is kind of pointless...
the logs in the gui always start with a blank screen, then messages gradually start coming in. Nothing historic
Ah log location was changed...
https://ghostbin.co/paste/hcz4
Are you triggering a ton of lights at once?
I wasn't, but maybe the wife pressed the hallway light too many times in a row. She keeps pressing the left switch when she wants to press the right switch (upstairs/downstairs lights)
She's a nightmare even with regular light switches, click click click. She's great at "testing" stuff
I'm having an issue with hue bulbs no longer working with effect: colorloop. The bulbs are connected via deconz with a conbee II.
Version core-2021.6.0
Installation Type Home Assistant Container
Anyone have similar hardware that can test?
I want to get an Ikea dimmer switch and bulb. Do I need a hub to do that?
If so any recommendations?
@fringe zephyr Click the pushpin icon at the top of the window. Second message in is what you want to start reading.
For background, I had colorloop working fine, but it stopped working about 3 weeks ago.
service: light.turn_on
target:
entity_id: light.living_room_lamp_1
data:
brightness: 255
effect: colorloop
will turn the bulb on, but the effect doesn't start
Can you issue the color loop effect through the Deconz UI?
Phoscon doesn't yet have light effects built into the UI.
Damnit. I thought they had that by now.
Yeah, I don't see anything about it in the github issues.
I had searched myself and didn't see anything. I also posted in the forums the other week and got 0 responses
I just don't know where to go from here
seems odd that everything is working, except for effects
It might be a 2021.6 issue. I'd try posting an issue in github as it might get more visibility by the devs.
I'm guessing maybe started with 2021.5 but thanks, i'll post on gh
if a device (in this case a zigbee wired light switch) isn't listed in the z2m supported devices, can it still be integrated to z2m?
just a follow up. reverted HA to 2021.4.0 with no change. reverted deconz to amd64-2.11.01 and colorloop is back. ๐
Hey guy's, My house came with downlights from this company: https://gosmartlighting.com.au.
I really want to use my downlights with home assistant but their app (eco1) doesnt integrate, it's google home and alexa capabilities are prettly limited (on/off)
They came with a remote. Is there anyway that i can get the signal from the remote to use with a zigby adapter and home assistant?
Are their lights Zigbee? Their range looks rather like WiFi...
Thats what the support guy said
"Our products use a form of ZigBee with an added security layer"
Great reference
It depends whether it's really Zigbee, or whether they really did modify things
If it's really Zigbee, and their support staff are clueless/brainwashed by their marketing department, you're going to be ok
Haha thank you for the reassurance.
https://zigbeealliance.org/zigbee_products/?product_type=certified_product&se=gosmartlighting
- but there's a non-zero chance they're rebadging something made by somebody else
How do a go about trying to control the lights with a zigbee adapter then?
Step #1 - try to pair it with the adapter
Oh, and those visually look very similar to Gledopto and Nue smart lights
You can eyeball a large number of devices at https://www.zigbee2mqtt.io/information/supported_devices.html and https://zigbee.blakadder.com/
You beauty, thanks so much mate.
Im going to grill the support guy, see if it is a rebranding and if i can get some decent info out of him
it doesn't allow to execute this command in the shell that I am in:
~ $ docker exec -it homeassistant bash -bash: docker: command not found
In the docs of "Home Assistant Add-on: Terminal & SSH" it says:
"Regardless of how you connect (using the web terminal or using an SSH client), you end up in this add-on's container. The Home Assistant configuration directory is located on the path /config."
So... lets say I plug a CC2531 into a sbc, code a program with zigbeeNet/zipPy to throw some gpios/be a zigbee switch/light.
Which firmware do I need so that it exposes a usb serial I can communicate on and connects as end-device/router?
2531 is one of the worst coordinators afaik
Yes, but it's ok as a router
https://www.zigbee2mqtt.io/information/supported_devices.html#custom-devices-diy may have useful links
Yeah thanks, I'm just tinkering so far. But is there a firmware which has a usb serial that I can use to make my sbc a zigbee device.
I get I can just send mqtt over traditional network - but I want to play with a sbc as a zigbee node being a end-device (+router probabbly)
Well, it's either an end device, or a router
It's the Zigbee chip that'd handle that though
Stuff like lightbulbs are routers, but also things that can be controlled right?
end-devices don't route other nodes traffic, I get that.
I just don't care if I make it a router or end device - I just want to write some code to control some stuff and show up as a zigbee device.
I'm confused about which firmware I need to pick - I need it to have a usb serial so I can interact with it from the code, but I don't want it to be a contoller - so I think I need a router firmware with usb serial? I haven't found one so far
Did you explore any of the options in the link I posted?
There's links there to descriptions, with links again to more information, including firmware
What you're talking about doing isn't going to be trivial though, I hope you've got some significant development experience, or are willing to learn
yeah I'm a swe
Thanks - the only compatible ones I can see there is https://www.zigbee2mqtt.io/devices/ti.router.html which points to Koenkk/Z-Stack-firmware...
Recommended for CS2531 is home1.2 - I flashed CC2531_router_2020_09_29.zip, but I didn't get any usb serial on /dev/serial and nothing showed up on dmesg that looked bad...
I was expecting /dev/AMTTY0 (or whatever it comes up as) ... should I have got that with that firmware? ๐ค
https://ptvo.info/zigbee-configurable-firmware-features/ offers uart in router firmware
Ok, with that I can't use the usb port right? I'd have to wire up the debug connector pins to the sbc and learn how to talk over uart? I was hoping there was a firmware for easy plug in usb->get /dev/AMTTY0->xyz.connect("/dev/AMTTY0").ZigbeeStuff(...)?
Useful information about the board on there though thanks!
Last night my zigbee network stopped behaving itself again, posted here but it was quite late at night. Anyhoo, z2m on hassos with a TI coordinator. Here's the logs around that time. Any ideas? https://ghostbin.co/paste/hcz4
restarting z2m and everything works again, or toggling something repeatedly via the z2m gui usually kicks it back into life too.
It's weird because I flashed z-stack home1.2 CC2531 coordinator, and I got a usb serial
but when I flashed z-stack home1.2 CC2531 router, I didn't get a usb serial :/
Which of the many "TI coordinator" options?
If that's a CC2530/31 then those are known to be crappy
LAUNCHXL-CC1352P-2 recommended by yourself a long time ago ๐
I've got a tube poe coordinator on it's way like
Make sure you're on the 2021 firmware, there's a known lockup bug on the 2020 firmware (at least for the CC2652, but I'd not be surprised if it's the same)
Aye, I'm on the latest, I think january 2021
If it's a usb issue (hassos is in a VM) then hopefully the tube poe one will resolve that, also considering moving z2m to docker failing that.
It's occasional, usually only once per week or 10 days, sometimes after only a couple of days.
which company was it?
Hi, after update from core-2021.5.5 to core-2021.6.1 ZHS cant not be loaded anymore:
log: Couldn't start application
14:04:45 โ (ERROR) /usr/local/lib/python3.8/site-packages/zigpy/application.py
what am i missing?
rolling back to latest snapshots and it works again
@thick plover
installs too
hello. We have moved our Hue setup over to Zigbee2MQTT, but an issue we have is that when switching on/off/etc many lights at once, some of them have a serious and random delay? This never used to happen on Hue? Is there something that can be done to fix this?
those are at the network level? I previously read the groups section in the second link and it came off as just a way to expose things to HA, basically an equivalent of HA's light groups. But it's actually not?
No, it's not
The result is that there's a single broadcast message on the mesh, telling every member of group whale to do something
I set groups up in z2m but they never made it to HA as entities
See the links above
๐ค
thanks Tinkerer, that's very useful. Have you also ever used the front-end of Z2M to bind zigbee devices? I can't get mine working due to a ridiculous bug where it resets the input every few seconds
Yeah, it's a known bug - I don't know if it's fixed in 1.19, or if it'll be a later release
hmmm so adding the following to my light.yaml does not throw anything up in the entities.... no doub't I am doing something wrong...
- platform: mqtt
schema: json
name: office_lights_z2m
command_topic: "zigbee2mqtt/Office_Lights/set"
state_topic: "zigbee2mqtt/Office_Lights"
brightness: true
I restarted the template entities
wait.... maybe its groups I am meant to...
hmmm nope
will double check that now
@thick plover When using Discord's new Reply feature it defaults to pinging the person you reply to, which can get frustrating for the target. Click @ ON to @ OFF to stop this - on the right side of the compose bar.

i usually turn it off
off topic here, but when the heck is the HA website going to get a dark mode? kills my eyes
you use the website ?
I READ THE DOCS MKAY
my brain is already full of shit
๐
its all so tiresome. i will try this another time.
The Z-Stack coordinator firmware lets you pick the logical device type at runtime and add endpoints/clusters. I've never tried turning the CC2531 into an end device myself but the entire management and testing command set is mapped out in https://github.com/zigpy/zigpy-znp/. Take a look in the docs folder for Z-Stack docs. There's a SYS.GPIO command as well.
Can you get a more complete error message? https://www.home-assistant.io/integrations/zha/#debug-logging
This here seems to imply that Hue bulbs do not support stage changes? https://www.zigbee2mqtt.io/information/binding.html
But the default reporting on Hue coloured GU10s seems to report everything? https://i.imgur.com/mWNyQ9r.png Am I misunderstanding something, or is the information outdated?
That's about reporting when a device causes a state change - the remote you've bound to the light
I think I see the problem. There are two SSH addons: "Terminal & SSH" (official) and "SSH & Web Terminal" (community). The former is pretty much useless and gives you SSH access to the /config/ folder. The second one is what I was using: https://github.com/hassio-addons/addon-ssh/blob/main/ssh/DOCS.md
i hope i got the right section:
--> what is the best way to post a log?
You can use https://paste.ubuntu.com/
Can you post the whole thing, up to the error message?
Or just the lines with zigpy or zha
Is there any more?
Hmmmm. Thanks, I'll take a look.
Yeah, that didn't work too well ๐
oh...
Did you copy over the NVRAM directly?
That's what looks like what happened
You want this one instead: https://github.com/zigpy/zigpy-znp/blob/dev/TOOLS.md#network-backup-beta
no, I delted the Integration and installed it new, the choose the new Launchpad
Right but the NVRAM state of your adapter doesn't match its architecture. It looks like you copied the NVRAM from a CC2531 straight to this board
not on purpose...
Were you previously able to use it with the old home assistant?
May this year
Did any devices transfer with the migration?
So to be clear, you never ran anything like zigpy_znp.tools.nvram_write?
no
Just flashed the LAUNCHXL board with firmware and changed the entry in .storage?
flashed it correct
and then deleted the integration and installed it new, choose the new controller and renamed the entities
so no editing in any files
Hmm. And you're saying that devices that were on your CC2531 network "moved" to the LAUNCHXL's network without you having to do anything other than rename entities? You didn't have to re-join them to the network?
correct
I am not seeing how that's possible, since a freshly-flashed LAUNCHXL board would be given completely random network settings when ZHA starts up with it, same way the CC2531 was given completely random settings
Did you use UNIFLASH or some other tool?
I used UNIFLASH
Since you're saying it's working with a previous release of Home Assistant, could you gather a debug log with it successfully starting up with the old version?
Parsed NIB: CC2531NIB is not supposed to happen for a LAUNCHXL board ๐ค
This thing is in a bad state. So to confirm: you bought a LAUNCHXL board some time in May, flashed it with Z-Stack 20210120 with UNIFLASH, added it ZHA, then this upgrade broke it? You didn't use Z2M at any point or do any sort of backup/restore stuff beyond editing the serial port path in .storage?
I bought it way earlier, but the rest is correct
No flash or NVRAM backup/restore with the CC2531?
correct
Do you know roughly when you would have added it to ZHA? I'm just trying to figure out what package version would have been responsible for setting up your board, to see what could have gone wrong
I added the Launchboard May 1st this year (it was in the closet for some time)
Thanks for the info. If you want to give it a try, can you follow the installation instructions in https://github.com/zigpy/zigpy-znp/blob/dev/TOOLS.md (to get access to zigpy-znp's tools, which can also be run on a separate computer) and make a complete NVRAM backup (https://github.com/zigpy/zigpy-znp/blob/dev/TOOLS.md#nvram-backup )? That way I can make a copy of your coordinator to see what can be done about this problem...
I try, but it will be tomorrow or Sunday, I'll get back to you! thanks a lot!
Sure thing. Thanks again for the help.
Hey, yesterday I installed home assistant for the first time, and I'm confused because this led strip (https://www.zigbee2mqtt.io/devices/HG06104A.html) didn't work as expected. I'm using zigbee2mqtt on another machine and I'm using the mqtt integration. While all other devices(sensors) directly showed up and showed all desired data, I could not interact with the led strip. The toggle just jumps back to off and nothing happens. Now the documentation mentions a manual configuration, and when I use this, I'm able to control the strip through HA. Is this the way to go or should this work "out of the box"? Because the documentation states, "MQTT discovery is preferred" and I'm concerned that I misconfigured something.
Anyone here buy this bad boy and get it to work in home assistant?? Iโm using conbee 2.
just did the backup: https://paste.ubuntu.com/p/TpJ6DBsnSy/
@austere patio - spot on. Thank you.
I am inside:
โ ~ docker exec -it homeassistant bash bash-5.0# ls
What should I do next?
I think you wanted to tweak the watchdog timeouts within bellows for your WiFi bridge, so edit /usr/local/lib/python3.8/site-packages/bellows/zigbee/application.py and maybe reduce MAX_WATCHDOG_FAILURES to 0 so that it starts reconnecting sooner
Thanks, I think I can see how to fix this strange problem. Did you buy this LAUNCHXL board used by any chance? UNIFLASH doesn't wipe the board's flash by default when you flash new firmware and seems to retain old settings.
i used it before in a FHEM setup, so it was used before.
Hmm, I wasn't aware of that platform. What does it use to talk to the Zigbee board?
it's mostly in German, that's maybe the reason. It uses Zigbee2mqtt
Was the CC2531 you were using before flashed with 3.0.x firmware or was it the default Z-Stack Home 1.2?
ooh just discovered that the aqara motion sensor also has luminance and temperature
Temp readings are for the processor and don't really correlate with indoor temperature very well but the light sensor is pretty useful
aha that's good to know
I have a bunch of temp sensor though, so not that I would rely on it ๐
Here's what mine looked like last year: https://i.imgur.com/T7NEGRr.png
Just a one-off script with https://matplotlib.org/
ah I was thinking of putting the mqtt messages immediately to a db and use grafana for it
That'd work too and probably be a bit easier ๐
yeah, I don't like matplotlib in python ๐
that requires my brain to function well
just wondering what db i would use for it
probably mariadb
i can not say fore sure...
That's alright, your NVRAM backup is really all I need to get it working
๐
It just seems that somehow either Z2M or some sort of cosmic rays managed to make your LAUNCHXL's settings a mixture of both
as i am far from being knowledgeable i would love to blame something else ๐
so procedure would be fixing the NVRAM and loading it back onto the LAUNCHXL?
Yeah, but I suspect you're not the first one with this problem so I'd like to automate it
If you want to do it yourself it's not difficult at all
You just edit the JSON that you sent me and add a few bytes to the end of two entries: 000000000000 at the end of NIB and 00 at the end of the first TCLK_TABLE entry. Then write it back and things should work, but I haven't tested it 100% just yet.
if this help, then I can go forward with this!
Hmm. There are a few more fixes, not that simple.
ok, what can i do to help here?
Ok, it appears to be fixed from my tests. It'll take a few days for the changes to be included in HA but if you want to try upgrading to the latest HA release again, you can pull the absolute latest changes by following these instructions: https://github.com/zigpy/zigpy-znp#testing-dev-with-home-assistant-os
If you made any network changes since taking that NVRAM backup (i.e. adding/removing devices), it'd be a good idea to do the NVRAM backup once more
You should also see significant performance improvements because your LAUNCHXL board was previously being detected as a CC2531 and its maximum concurrency was limited to two requests, instead of 16 ๐
ok, gonna try it, thanks a lot!!
just upgraded to core-2021.6.2 and it works, any easy way to check if everything is now as it should be?
and thanks again!
If HA started then it should be working. You should see sensor updates and be able to control devices if everything is 100% working.
jup everything works like it should!
Just got an email that slaesh is now available again
Been a long time since I heard anyone promote that stick. Weren't there people having support issues?
i dont know, i read some issues about that stick too
the hardware works like a dream; some people have had trouble with receiving their orders in a timely manner.
So Slaesh sticks are fine but you might be in for an emotional roller coaster getting a hold of it
my zzh is on the way i hope it works fine ๐
My Slaesh stick might hit the second hand market soon as I am waiting for one of tube's POE numbers
high hopes
tube's POE? what is that?
how long has it been out of stock?
He was saying that the chip drought means he won't be releasing much more for a while :/
tube is a regular in this channel, so he usually let's us know when he has new wares
ok
twitter is a good place too apparently
but yeah, times are hard, apparently
for everyone from PS5 producers to zigbee enthusiasts
Yup. It'll take a little while for supply chains to level back
too, bad cause I love my gadgets ๐ฎ
Is anyone familiar with the Enbrighten Zigbee Smart Light Outlet Receptacle? Looking at using one to serve as a router to replace a plug-in one: https://www.amazon.com/dp/B0842BDN9R/ Do you know any other similar zigbee receptacle?
anyone use the v2 Hue dimmer switch to reset bulbs? was it successful?
I'm cobbling together my first ZHA stack and getting unexpected results. I have sourced a Hama 00176592 radiator thermostat via the Blackadder list: https://zigbee.blakadder.com/Hama_00176592.html which promises battery, thermostat and temperature. It is linked to ZHA via a flashed Sonoff bridge and (eventually) showed as the correct Zigbee ID. So far, so good - I think the communication is working.
However, the device only shows basic Device/Zigbee info and what looks like generic ZHA options (reconfigure device, zigbee device signature, manage clusters, view in visualisation, remove device). Could anyone help me get to the heating specific stuff please?
The integration I'm using for my ConBee II is called "Zigbee Home Automation". Isn't that ZHA? I've been having some errors and some experts in another channel are saying they are coming from deCONZ and I would be better off moving over to ZHA. But... am I not already?
Hi! I have a zigbee device that died and still present in the zigbee (zha) integration. Any way to delete it? It doesn't have any information listed in the device, so I don't even have an IEEE address to use zha.remove with. Thanks!
Module manufacturer is not very clear โthis month or next monthโ ๐คท๐ผโโ๏ธ so hopefully by mid/late July I guess
Separate issue from above: I have 3 historically-working zigbee devices that simply appear dead to the coordinator. They are three different types of devices. One is bound to a switch and still turns on and off with that switch. Two are identical to other devices in the same room. I checked on the topology map and all three are very well connected. I've power cycled my home assistant as well as (separately) the circuits for those devices. For the two that have buttons, they turn on/off as expected. In other words, they all respond to each other and to physical inputs like normal, but the coordinator doesn't see any of it.
Any ideas? Thanks!
I've been doing a cleanup of old/disabled/etc. devices and it appears that there are actually 5 zigbee devices "offline," all different types, all behaving identically, and all of which went offline at roughly the same time.
I turned on zigbee logging and at least one of the nodes shows up with this message periodically: 2021-06-05 19:37:10 DEBUG (MainThread) [bellows.zigbee.application] Received incomingManyToOneRouteRequestHandler frame with [0x002b, aa:bb:cc:dd:ee:ff:gg:hh, 2] where that's the ieee id of the device.
Must be a tuya rebrand. May need to open request to zha-device-handlers to have it added, but must identity correct quirk. Apparently there multiple devices with excat same model and manufacturer but having different controls
I switched to z2m with the slaesh stick this week, and all has been fine for a day or two, but now my sonoff temp and door sensors start disconnecting from the network. Everything is within 10 m from the coordinator, I have several Ikea plugs as routers. Any way to find out what's going on? How do I get the sensors to reconnect? Reset does not seem to work.
My ikea remote is turning on/off my xiaomi power plug and there is no automation in Home assistant (using zigbee2mqtt)
This behavior is happening without me stipulating it.
Why?
Seems like it happened in the past: https://github.com/Koenkk/zigbee2mqtt/issues/2772
Ok I figured it out it was all bound to the default group
So I created a new bind group and now it does not control the power outlet
neat feature, but silly that everything is added to a default bind group
Cheers for that. You're saying that the device does not follow the Tuya standard and needs some tweaks to communicate with HA? I'll put in the request on Github and see what comes out. The Hama is only a PoC to get to grips with ZHA since I'm fairly new to HA. I might switch to a different model/make if the Hama is a dead end.
is a higher linkquality better or worse? as my sensors that are nearby the stick are in the 100 range and when I move one of them outside, it goes in the 200 range (and i don't see anything failing)
Higher is better
LQI is a measure of many things, depending on the device, and is often just a vague indicator
Hi everyone, just a quick question. I have about 20 xiaomi window/door sendors spread over 3 floors. Some of them keep failing. It is only those farthest away from my conbee stick. If I understand correctly, using a powered zigbee device like a powerplug, should increasr the range, as zigbee is some kind of mesh network. Does any zigbee powerplug work? Or should I get a xiaomi one to be more compatible with the sensors? Thanks
I bought these ones which are working as repeaters for my Xiaomi window/door sensors, https://www.aliexpress.com/item/ZigBee-Smart-Plug-16A-UK-Socket-Tuya-Smart-Life-APP-Work-With-Alexa-Google-Home-Assistant/1005002427778624.html?spm=a2g0s.9042311.0.0.683d4c4d0ofu4z
So the answer to your question is yes in theory.
That said I've got a problem with those, they seem to be turning themselves off within a few seconds of me turning them on, so anyone that knows about what could be causing that would be appreciated
See the pinned messages - not all routers will work
I've had no issues with Ikea, Gledopto, Innr, Salus, or DIY ones
Thanks! I will look into those.
I plan to only use them as repeaters. If they turn off, do they also stop the โrepeaterโ function?
If you turn the power off to them, yes
Not if you use the button on them/Zigbee commands to turn them off though
I think so, the one that is acting as a repeater is on my dishwasher which is running atm, but I'll test it properly for you once the cycle is finished
As long as a Zigbee router has power it will continue to route traffic
Otherwise the mesh would spend more time broken than working...
Thanks!
Thatโs trueโฆ thanks!
@oblique root When using Discord's new Reply feature it defaults to pinging the person you reply to, which can get frustrating for the target. Click @ ON to @ OFF to stop this - on the right side of the compose bar.
Not sure how to debug them turning themselves off on their own though. I've disabled all automations, I turn it on, it stays on for a few seconds, then just turns itself off again.
Does the Logbook show them turning off, or HA doing something and then them turning off
Both, intermittently it seems, sometimes it says "Turned off by Alfie" and other times it just says "Turned off"
The first says that Alfie did that (probably using the UI)
The second says that HA detected it turning off
I wonder if it could be a signal thing, like the plug automatically turns off if its out of range? It is quite far from the USB receiver.
I'm guessing that's the number on the visualisation? reports 71/23, and has a green line, which I assume means it's ok
I brought it closer to the USB stick to test and it stayed on, then I put it back where it was originally and it still stays on, so either signal or it's drunk ๐
Yeah, that's fine
weirdly, it looks like the fault started at 6:08:37am this morning, when everyone was asleep, it turned itself off (home assistant says "Turned off", no username.) Meanwhile another one entered the same broken state at 8:49:28am. I don't have any automations on these plugs apart from monitoring the load and sending notifications, wonder if they are faulty
So, something external to HA turned it off
which is fun, because I own no other smart hubs, and the only thing that could turn it off apart from home assistant would be the physical switch on the plug
update : a driver package seems required when using the zigbee stick in a synology
I have a fun experiment idea, I have one more that is brand new in box, not paired to anything. I'm going to get it out, plug it in, hit the button on the side to turn it on, and see if it turns itself off. If it does I know they are defective and will have to return
Maybe a dumb idea, could it be related to mqtt? Maybe they share topics with other devices? Is that even possible?
next time it happens, I'll try turning the computer off and see if it still turns itself off when I physically press the switch too, that'll answer that question, good suggestion ๐
with mqtt2zigbee i can easily make a backup of my devices , they're all listened in the config file, so when i move the docker container to a different system i don't have to connect all my devices again ?
Nobody has an idea how I can get a sensor to reconnect to the network if resetting it does not work?
if anyone is interested in putting mqtt messages in a database instance (python & docker based), I'm currently working on a tiny project and looking for feedback, testing..
Why? What besides perhaps history would be the point? Not using mqtt yet, but will soon, so just curious ๐
history and statistics if you want @solid inlet
you could use the data to build a grafana dashboard
but for this moment I only just started capturing the timestamp, topic, clientid and the complete payload msg
haven't done anything else with it yet ๐
Anyone running deCONZ noticed lights becoming unavailable for some amount of time (~30mins) on 2021.6.0. Lights that have had 100% uptime suddenly drop out
Thanks, I will keep this in mind ๐
no problem, i have made a git repo that's public, but the more feedback i have, the better it can become
Hello everyone, i seem to have a very bad signal between the ZZH stick and the Xiaomi components , is this normal
distance between the stick and the first xiaomi component is 2.5 meters, link quality is 65 ?
Ignore the link quality. Does it work?
Those two things aren't related.
Re-pair the things that don't work. Stop worrying about LQI numbers if things work.
in the other room i don't have signal anymore between the stick and the Xiaomi door sensor
Re-pair the things that don't work
ok
Did you figure this out? So far Iโm not having any luck either
I actually found the v1 at my Home depot, still for sale. They had three. I haven't tested it yet, but it is definitely the v1, because it has the words 'ON, OFF' on it.
I'd check the HD website, and even look at your nearby towns to see if one is still in stock.
mono you were right , i had to walk closer to the zzh stick , paired them again , and when i walk back i have link quality of 18 but it seems to work
pairing them in the other room doesn't seem to work
people a question : i'm looking for a nice tiny device that can act as a signal repeater , a light switch or something like that , is there someone that has experience with a certain device
Ideally you want to be pairing them at the place they are going to be put
plugs, lights, mains switches take your pick
i think i'm gonna order a cheap plug and use that as a repeater
yes but i can't pair them here in this room , link quality is 7 but the xiaomi component works great , even with this bad signal (if the signal indicator is correct)
Exception being if you only have the coordinator and no routers, which I think is true for Daniel.
The 'pair in situ' rule is so it picks up the best router, not just the one you were nearest when you paired.
ah!
and what if i add a router in the near future , would it automatically use the new device as a signal repeaters
true Mono : i don't have any zigbee routers (yet)
is there anyone who has a link of a good shop that sells a great working zigbee plug (so that i can use it as a router)
It would use what it thinks is the 'best' one (usually the closest/strongest from where it is).
You'll have to say where you are, since plugs differ in many countries.
the netherlands
Hey. In ZHA, is there any way to trigger a clustter attr get in an automation? I would like to update the active_power more frequently than the default 30s for a specific device.
https://www.zigbee2mqtt.io/devices/ZNCZ04LM.html that could maybe act as a stable router
I believe I've seen the BlitzWolf BW-SHP13 on sale on Banggood
50% cheaper then the xiaomi
Maybe I should get a few myself
Im using a conbee II key, and today I had a powercut (HA is on a UPS so stayed up). But all my Hue bulbs came back at full brightness, and the plugs all reverted to ON. Hue devices have a feature to remember their previous state I think, but apparently it didnt work for me today. Anyone found a solution to this?
Zigbee :bee: - please remember to mention whether you're using zha (https://www.home-assistant.io/integrations/zha), deCONZ (https://www.home-assistant.io/integrations/deconz), zigbee2mqtt (https://www.zigbee2mqtt.io), or even something else.
Looking for devices? See https://zigbee.blakadder.com/ and https://www.zigbee2mqtt.io/information/supported_devices.html.
As mentioned, the integration you use matters
The stick is not that important (for this anyway)
ok im confused. I asked in #integrations-archived and you suggested I use #zigbee-archived?
Hey Tinkerer : small update , i managed to get the stick working on a synology too , i had to install a driver package
Did you read the channel topic?
Did you read the bot message?

Please read them...
I did, but I assumed mentioning Conbee II implied I was using DeConz integration. My bad
Well, no, because you can use that stick with all three options
ok, I didnt know, sorry
If nobody here knows, the people on the deCONZ Discord should know
deCONZ by dresden elektronik is a software that communicates with ConBee/RaspBee Zigbee gateways and exposes Zigbee devices that are connected to the gateway. Our #zigbee-archived channel is a good place to ask about using it with Home Assistant, but they also have their own Discord server.
ok thanks, Im fitting an extractor fan this week so will involved turning off lighting circuit. Good time to do some testing and see if it happens again
It should, it's a safety feature, so that if the power goes out when it's dark you have lights when the power comes back on
Why it wouldn't be return to the previous power state by default I don't know... probably some lawyer somewhere decided this was easier
But like you say, Hue added the return to previous state feature
So not entirely sure which part of the puzzle is stoping that from kicking in
The feature has to be enabled I believe
ok ill dig further, thx for the help
@tall nacelle if you use zigbee2mqtt
cache_state: true
cache_state_persistent: true
cache_state_send_on_startup: true```
this should do it
haven't tested it yet
thx dude. I dont currently, but maybe its time to switch over
what do you use atm ?
ah I prefer the mqtt way, don't ask me why ๐
Z2M > ZHA >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> deCONZ
(IMO)
deCONZ should give you access to the clusters so if you go to the OnOff and LevelControl clusters on your devices, they should have start-up attributes you can set. Assuming your bulbs and switches are Zigbee 3.0.
I struggled to find a reason to increase complexity by adding mqtt in the past. This is a compelling reason though ๐
thanks
Just tested and it works with those settings
didnt see your reply earlier, until now. Could you give me a bit more info on where I access this plz? Im using DeConz integration, but my main access route to it is via Phoscon app. I can also use the VNC tool into deconz, but Im not seeing any cluster stuff there either
actually Ive now found a 'Cluster' tab in VNC, but no matter what node I select it just shows 'Please select a cluster to get further info'
Hey all. I have a zzh! with zha integration. Any tips for pairing a IKEA E1743 dimmer switch? It pairs, but doesnโt throw any zha_events like the 5 button remote.
Nevermind. I managed to pair properly by trying to keep it alive by pressing buttons throughout until successfully
Never used deCONZ but from what I've seen of its UI, I think you have to select a device, find the endpoint with either an on/off or level control cluster, then change that attribute
so I'm back with in need of help, i have some sonoff devices that keep going unavailable/unknown. This time I do have an LQI and RSSI number, instead of the previous unknow. all my devices have LQI 255, one of the diveces that drop last shown LQI of 243
This time I have LQI and RSSI numbers with the husbsz-1 compared to using a CR2351
LQI of 255 probably means that it has no idea of what the link quality actually is
and RSSI isnโt exposed on Texas Instrument chips
Which devices keep going unavailable?
And which routers are you using?
Also, did u have the issue on your TI stick previously?
When I first got a ConBee II, I followed the instructions and loaded ZHA to manage it. I've been wanting to test out deConz instead, but when I try to install it via the UI it asks for a "Host" and shows a suggested port of 80. I cannot find any documentation on what host it would want. the word "host" doesn't even show up in https://www.home-assistant.io/integrations/deconz/. ANy pointers on moving forward?
Oh i think I see. There's a separate add on that probably configured the integration
Is there any way to figure out which Zigbee device caused this err?
`Logger: zigpy_deconz.uart
Source: /usr/local/lib/python3.8/site-packages/zigpy_deconz/uart.py:94
First occurred: June 5, 2021, 12:13:44 PM (1 occurrences)
Last logged: June 5, 2021, 12:13:44 PM
Unexpected error handling the frame: 'NoneType' object is not iterable
`
And, is it weird that I'm not using deConz, but rather ZHA, and I get error messages referring to "zigpy_deconz"?
Since deCONZ here refers to the protocol of the Conbee stick
Itโs basically the name of the library (that lets ZHA communicate with Conbee sticks)
https://www.legrand.com.au/path-file/449
Interesting new product available here (Australia). I wonder if theyโre z2m friendly
Hey there, is it possible to configure "duration" for a motion sensor connected to Deconz? I mean the duration the sensor triggers. Not the parameter in automations
What sensor?
Aqara motion sensor
That sensor has an internal 60 second timeout, if you set the integration lower than that then you can expect the occupancy state to continually go on and off
No. At the moment its integrated via homebridge (but i want to go with HA in futuere). Default is 2 Minutes and i can set it down to 20 sec (which works nice). Also 1 minute would be better than default. It is possible to set it via Homekit and ioBroker as far as i know.
Google found me https://github.com/dresden-elektronik/deconz-rest-plugin/issues/3640 which looks to have the UI settings you're looking for
Just keep in mind that for the rest of that minute, the motion sensor is blind to any further movement
For what reason is there such timeout enforced by the vendors?
battery saving
aha, ok
That's another problem. I can confirm that the sensor is not blind after that time. 20 seconds work. They are set to this at the moment and also work in HA. I just need the possibility to set this (for newly learned sensors)
So see the issue I linked for the UI setting 
That is not the problem?
you need to do a hardware modification to make the aqara motion sensor more responsive
I'm not sure what the problem is... you say you've found the UI setting, you say the sensors work, so ... what are you after?
No i dont need any hardware modifiation i just want to change a setting
It is possible to change the value within Deconz (GUI), but i am running headles (in Phoscon you can't change this). In the past i changed it via Homekit (Homebridge Plugin changes the value within Deconz).
Also ioBroker can change the value in Deconz. HA seems to be the only where it is not integrated.
All my existing sensors are changed to 20 seconds.
When i go with HA as my only software i need to change this settings through the HA GUI because newly added sensors have 2 minutes default.
Ah, right, so with HA the assumption is that you have the deCONZ UI
Even with that it should be possible to manage these settings centralised. Isn't it the reasion for that kind of software? Other solution also integrate these settings
Well, there's nothing stopping somebody doing that - but nobody has decided to invest the time and effort into it
Given that HA has a native Zigbee integration, I'd not expect it's not high on the list of things any core developer wants to do
@molten linden I just want to say thanks for making great hardware. My first few weeks with my tube zigbee coordinator has been great. I purchased some of the TRADFRI dimmable bulbs and switch combos from IKEA and it has been a great experience.
Zigbee2MQTT is dropping this error and cannot be opened.
21-06-07 12:36:11 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.9:8099 ssl:default [Connect call failed ('172.30.33.9', 8099)]
Where should I change this SSL:Default setting? Thank you.
Hi, I'm facing issues with my Hue integration since I updated to 2021.6. Is this the right place to ask for help? Thanks.
That would be #integrations-archived
Unless you have your Hue devices directly connected to a Zigbee coordinator using ZHA/Z2M/deCONZ.
This is since 2021.06.2 update only. It was working for months before. Any Idea?
there is deconz.configure service where i can do exactly that
502: Bad Gateway
That made the Zigbee2mqtt work:
new_api: true```
new_api went away some time ago, are you still on an ancient version?
Hey guys I am trying to use my 5th aquara switch for an automation but this one only shows the single click option. It is exactly the same build as the other three and for the other ones I get "single click double click and long press" in the dropdown. any guesses? (integreated via Zigbee2mqtt modell number is WXKG11LM for all of them)
delete and re-pair ?
Hm I will try that but I still wonder why that happend. Single click works fine though
the devices that keep going unavailable are sonoff temp sensor and door sensors
I don't have any routers, just the coordinator, the farthest sensor from the coordinator is around 8m or 20ft
I also had the same issues with the cr2351. in fact it was worst. and I used to get LQI of 40 to 150
I have tryed a nother one and that one only shows battery voltage and linkquality... and for the other one repairing did nothing
you use zigbee2mqtt, deconz, .. ?
Zigbee2mqtt and for my other buttons it worked great. they do exactly as i wanted
how many devices do you already have and does the log from zigbee2mqtt show something ?
the number of devices should not be the problem I am currently runing 4 repeaters and i will have a look at zigbee2mqtt in a sec it restarts atm
The log is clean of errors. I suspect that they changed something in an update... I will check that later i guess
c0 Never minde.... the one only stating battery etc. just got all the actions whilest I was clicking it against boredom... I realy dont know why but hey...
if it's working, that's what counts ๐
Although the CC2530/CC2531 are bad, all Texas Instruments chips calculate LQI lower than EZSP-based chips. (I wouldn't even look at LQI -- doesn't correlate to if my devices actually work well).
Also, try updating the firmware on your HUSBZB: https://github.com/walthowd/husbzb-firmware
Sonoff sensors are also known to not work well sometimes.
i ordered a BW-SHP13 plug from banggood and will use it as a zigbee repeater
they're just 10 euro atm
ouchie, I wich I knew about sonoff not working properly. I will try upgrading and see if that help. Just need to figure how to upgrade on win 10 if possible...
are you using the zigbee version of a sonoff device?
sorry i don't have experience with that version myself
You can run the Python script in the repo directly
Just install the required Python packages and you can run the main script on Windows
Hi there! New on this discord ๐
I recently upgraded my HA install (HA OS) from 2021.5.x to 2021.6.2 and my covers stopped responding. I'm controlling them with the zigbee2mqtt addon. They appear in the addon and I can control them from there but the entities in HA don't respond. Other Zigbee2mqtt entities still work, like lights or switches.
I'd be grateful if someone could me find where I should file an issue ๐
I'm guessing it's not an issue with Z2M directly since the covers work fine there ๐ค
I asked in #integrations-archived but someone pointed me to this channel
Hello everyone , i wonder about the security of a zigbee network
If you lock the door no-one will get in
Sure, but unless a device is paired it cannot talk
Are older Zigbee bulbs not supported by ZHA? I have two bulbs that can be found by the Hue app but not by ZHA
The age is almost definitely irrelevant. The model, and whether there's a quirk for it, is what matters.
Model 9290022268
Where would I see if there's a quirk for it?
I'll let a ZHA user answer that. I use Z2M.
What channel are you using @autumn warren?
Not sure, tried looking in HA but didn't see anything regarding that
Nwk: 0x6b06 if that means anything
Nope. That's not it. If you're using a default ZHA install, you're on channel 11 (you'd know if you changed the channel) ๐
Ok, so, were the bulbs originally on a Hue hub?
A while ago yeah, but even after adding to Hue app and deleting they don't show in ZHA
The Hue app or the Hue bridge? The app connects to the bulb using BlueTooth, so it wouldn't wipe the Zigbee settings.
You'll want to attach them to a Hue hub and then wipe them from there. It might take a couple times as some bulbs are fussy.
Well I have a Bridge, so I'm assuming the app connects the bulb to that
If the bridge is on and connected, it should, yeah.
But those BT bulbs are just a pain in the butt.
I've reset it twice, should I try it more?
I had to run huethief on a few of mine like 3 or 4 times for them to finally pair to Z2M.
That's about the only advice that I can give, unfortunately. ๐ฆ
You could also try huethief.py and see if that works better: https://github.com/vanviegen/hue-thief
Anytime!
If you're using Z2M and didn't change the default, you're using a very public shared key
All we need now is his physical location and we can attack his network.
Interestingly, as per https://github.com/zigbee2mqtt/hassio-zigbee2mqtt/releases there's indeed v1.19.1-1 while I'm still running 1.18.1-1.
I have the addon set to auto update, I tried forcing a reload of the addons but the supervisor doesn't show me any update :/ I'll try uninstalling it maybe.
Ok so I had to remove the addon repository from HA and re-add it in order for HA to find the new version :/
I followed the instructions on this issue and so far so good, thanks for pointing me to the update! ๐
So, you're still using the deprecated add-on repository ๐
yeah seems so. I was able to update and now I'm having trouble with some covers reporting an inverted state.
That's an issue I think I had at the very beginning too but I can't remember how I solved it. I'm trying to use invert_cover in the config but it doesn't seem to affect anything
anyway, gotta go to work now, I'll check this later. Thanks again!
people i wonder if there is a way where i can check my shared key in Zigbee2mqtt
check what ?
"Seems to" ๐ค
yes it crashed
Well, what does the log file tell you?
reading the docs , i think i made a mistake in my config file
the error i get is : error 2021-06-08 13:56:18: Configuration is not consistent with adapter state/backup!
the container keeps restarting at the moment , and runs fine when i remote the network key under "advanced" in my config file
i used network_key: GENERATE in my configuration.yaml
