#zigbee-archived

1 messages ยท Page 140 of 1

jolly narwhal
#

reverting to stable fixed that

#

so still haven't migrated to 1.19, might later this week

sour shadow
#

I had planned on trying it this weekend, guess I'll hold off and see what's going on ๐Ÿ˜„

ivory hound
#

any new info about low level stack bug in the SiLabs EFR32 used by IKEA devices that causes them to crash?

jolly narwhal
#

what is this IKEA crash ?

#

๐Ÿ˜„

fleet lodge
#

"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.

sour shadow
#

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 ๐Ÿ˜‚

fleet lodge
#

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

cunning trellis
ivory hound
#

is still true

#

hardware has not changed ๐Ÿ™‚

cunning trellis
#

I was hoping for firmware tweaks ๐Ÿ™‚ I'll be going with the latest 1.2 then

ivory hound
#

and software usually ask for more not less

cunning trellis
#

the CC2531 should be able to run my 9 device network ๐Ÿ˜‰

ivory hound
#

yah that should not be a problem

ruby field
#

anyone know if changing zigbee usb stick requires re-pairing of all devices?

#

Using Zigbee2MQTT

thick plover
#

is there a way to remove devices from your MQTT broker?

#

i.e. I have a double up in devices...

forest cobalt
ruby field
#

where do I find the version?

thick plover
#

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

forest cobalt
#

lol... use something like MQTT Explorer, find the duped topic (which shouldn't be there) and then publish an empty message to it.

sour shadow
#

MQTT Explorer even lets you delete retained messages in the UI, there's a button for it

thick plover
#

ah cool, will open that up

ruby field
#

looks like I'm repairing everything AGAIN ๐Ÿ˜ฆ

sour shadow
#

What stick are you going from and going to?

#

Because, maybe not

ruby field
#

just got a Electrolama zig-a-zig-ah! (zzh!)

#

CC2652R

#

coming from the sonoff USB C2531 I think

sour shadow
#

Then look at the top pinned message

sour shadow
#

Well, is that the top pinned message?

#

Unless you stand on your head, it should be

ruby field
#

ok ok.. settle I'm not on discord often ๐Ÿ˜ฆ

sour shadow
#

That's the one, and it covers _ ... snapshot the device state and move your network between any supported hardware and firmware versions._

ruby field
#

have you used it?

sour shadow
#

No, but many people have without issues

#

Also, what have you got to lose?

ruby field
#

Awesome..

fringe vault
#

Cool, Lidl has some gardening "computer" over Zigbee

#

actually a water valve, nothing more ๐Ÿ˜„

#

โ‚ฌ 24,99 in Belgium

violet dagger
#

damn, i hoped it would do all the gardening

fringe vault
#

๐Ÿ˜›

cunning trellis
#

Surgery completed successfully, my CC2531 is now running 20201127

blissful nacelle
#

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

jolly narwhal
#

unplug it, see which one vanishes

#

or read from lsusb if you are lucky

#

and use persistent paths, not transient ones...

blissful nacelle
#

do I simply mount the desired device?

jolly narwhal
#

ls -lla /dev/serial/by-id/

#

use the one that corresponds to your zigbee stick

blissful nacelle
#

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?

jolly narwhal
#

use that path for mapping the usb stick

blissful nacelle
#

k, thanks for the help

jolly narwhal
#

/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0

thick plover
#

Whats the best method of tracking power consumption? Voltage? Watts?

jolly narwhal
#

wattage

#

watts == power spent \ generated

#

V * I = P

thick plover
#

Thanks mate

livid abyss
#

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...

sour shadow
#

It should work regardless - Z2M is Z2M

earnest sigil
#

Anyone got any recommendations for door contact sensors that will happily use hue bulbs as routers?

forest cobalt
#

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.

livid abyss
#

But I won't have z2m in my integrations list, as it's just messages that come via mqtt, right?

forest cobalt
#

Correct. You don't need the integration as all your devices are done through MQTT discovery.

sour shadow
#

Firmware: Zigbee2MQTT 1.18.3
for instance, under Device Info

sour shadow
#

You've set up the required integration input?

livid abyss
#

No, not sure what you mean exactly...

sour shadow
#

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
livid abyss
#

Ok, yes it has a dropdown I set to z2m.

sour shadow
#

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

livid abyss
#

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...

austere patio
earnest sigil
#

Well apparently Xiaomi battery stuff will only connect to Xiaomi stuff

sour shadow
#

Nah

earnest sigil
#

Though will happily connect to my non-xiaomi coordinator so ๐Ÿคท

sour shadow
#

I have Xiaomi battery stuff connected to non-Xiaomi stuff

#

Indeed, I have no mains Xiaomi stuff ๐Ÿ˜‚

earnest sigil
#

Hmm ok was going by what some guy was saying in here yesterday

sour shadow
#

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

earnest sigil
#

Hmm ok. Last time I looked they were all connected directly to the coordinator despite me repairing them

sour shadow
#

Do they work?

earnest sigil
#

Yeah but I doubt if I put some further away they would. Plus I've temporarily moved the coordinator more central with a cable

sour shadow
#

If you put them further away they'd route differently shrug

#

Moving stuff around after you've paired it though, that's a recipe for pain

earnest sigil
#

Oh

#

I was still wondering whether to keep the coordinator in my office in the corner of the houee or move it central

sour shadow
#

Mine is in the corner, not ideal, but it all works just fine

earnest sigil
#

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

sour shadow
#

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

earnest sigil
#

Hmm these just wouldn't pair no matter what I did

sour shadow
#

Go read the pinned message on Xiaomi

earnest sigil
#

Moved the coordinator and bam

#

These were hue

sour shadow
#

Well, who knows then

earnest sigil
#

Yeah

#

It's like they ignored all the other bulbs around them and needed the coordinator to be closer

livid abyss
#

With z2m, can I pair devices via a router instead of the coordinator? Like with ZHA.

forest cobalt
#

Yes

livid abyss
#

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

dry fossil
#

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.

forest cobalt
#

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.

livid abyss
#

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

dry fossil
#

it shouldn't need to be close unless it's one of those weird devices that uses sound as well.

livid abyss
#

Hmm, either with router close or not it does not pair, just blinks. I had it paired via ZHA before.

forest cobalt
#

What kind of bulb is it?

#

Plus, what channel is your Z2M mesh on?

livid abyss
forest cobalt
#

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.

livid abyss
#

Hmm, I just paired my first 6 devices, so I guess it would be an ok time to do it now

forest cobalt
#

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.

livid abyss
#

Thanks, I'll look it up

silk stream
#

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```
gentle flint
#

Either it's loosing connection to usb (bad power supply) or multiple instance are running at the same time. Check syslog

silk stream
atomic thicket
#

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

atomic thicket
#

The logs say nothing...

austere patio
#

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.

wintry horizon
#

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.

silk stream
wintry horizon
silk stream
atomic thicket
wintry horizon
austere patio
#

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.

wintry horizon
silk stream
#

any other ideas what might be going on with my setup? or things i could prod to debug further?

dry fossil
silk stream
#

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
austere patio
#

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?

gentle flint
#

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.

solid inlet
#

Ok, I got the one mesh part but... What if having several coordinators on different zigbee channels?

jolly narwhal
#

There is no advantage to that

#

It will create interference

#

And your meshes will be weaker

jolly narwhal
solid inlet
#

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...

sour shadow
#

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

jolly narwhal
#

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

frosty shore
#

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?

frosty shore
#

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!

sour shadow
#

Mostly in these cases the only things you can do are:

  1. Get involved in future betas (I have a separate install for testing betas with)
  2. Ensure the issue is raised with the dev of the other software
frosty shore
sour shadow
#

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

cunning trellis
#

yep, I was just about to note that ๐Ÿ˜‰

sour shadow
#

It also looks like they all have old coordinator firmware

cunning trellis
#

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 )

sour shadow
#

Yeah, I wonder if the 2019 firmware has bugs... oh, hang on, what am I saying ablobjoy

cunning trellis
#

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.

sour shadow
#

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

cunning trellis
#

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

sour shadow
#

They're really small, and easy to hide in the post

frosty shore
#

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?

sour shadow
#

Ah, you're an add-on user...

#

As far as I know, no

frosty shore
#

no for it shouldn't break or no for it's not drop in replacement? :D

sour shadow
#

No, it shouldn't break

#

But, I'd take a snapshot first, just in case

thick plover
#

lil help before the wife kills me?

#

Tried to restart z2m and it died in the arse and will not restart

sour shadow
#

Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)

thick plover
#

any idea how I can fix that?

#

think it could be looking at the wrong port?

thick plover
#

ha

#

read the docs

sour shadow
#

And a few thousand Google hits on it too ๐Ÿ˜„

thick plover
#

Fuck Google, I come to the pros for help

sour shadow
#

The CC2530/31 are well known for locking up and requiring removed and re-inserted

thick plover
#

I have a zig zah hah or whatever

sour shadow
#

But, if you're using the /dev/tty* path, that can change

thick plover
#

yeah thats what I was using

sour shadow
#

If you're on the pre 2021 firmware with the ZZH then that also has lockup bugs

thick plover
#

should be the most recent (or whatever was most recent 6 weeks ago when I got it)

sour shadow
#

Should be and reality often differ

thick plover
#

this is true

sour shadow
#

Check the path first, and switch to using the long one, /dev/serial/...

thick plover
#

/dev/ttyUSB0 potentially

cunning trellis
#

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

thick plover
#

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
cunning trellis
#

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

sour shadow
#

ls -al /dev/serial/by-id/

cunning trellis
sour shadow
#

Or just use the fact that these days you get a unique path all the time anyway

thick plover
sour shadow
#

There you go, you have a nice long unique path already

thick plover
#

so if thats in my config, why is it not working

#

is there a way to display the full path?

sour shadow
#

Well, the problem is you're not using it

#

You're using /dev/ttyUSB0

thick plover
#

I am lost mate.

cunning trellis
#

Use /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0

thick plover
#

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

cunning trellis
#

Yeah, it'll rotate the log. You can find old logs in the /log folder

thick plover
#

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...

sour shadow
#

Check your container config

#

You have to pass that device in

thick plover
#

ah

sour shadow
#

Bet you're not ๐Ÿ˜‰

thick plover
#

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

cunning trellis
#

Learning by figuring it out yourself ๐Ÿ‘
(with some helpful pointers, of course)

thick plover
#

so where do I find the container config usually? is that the one inside the actual container?

sour shadow
#

Well, how are you running it?

thick plover
#

compose

sour shadow
#

Then your compose file...

thick plover
#

hmmm the new file path is listed there...

sour shadow
#

Did you rebuild the container?

thick plover
#

no...

#

not going to lose everything am i?

sour shadow
#

docker-compose up -d zigbee2mqtt

thick plover
#

hmmm now its just sitting as restarting...

sour shadow
#

You can watch the logs

thick plover
#
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?

sour shadow
#

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?

thick plover
#

yes

sour shadow
#

Then explain it to me ๐Ÿ˜‰

#

Because I don't think you do

thick plover
#

one side is the container, one side is my pi

#

the : splits it yeah?

sour shadow
#

Yes

thick plover
#

WOWEE

sour shadow
#

So, the left side is the path on the host, the right side is the path in the container

thick plover
#

following

sour shadow
#

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'

thick plover
#

uhm, thought you guys said to?

sour shadow
#

๐Ÿ˜‚

#

Well, yes, but no

thick plover
#

fkn hell mate, english!

sour shadow
#

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

thick plover
#

ah

sour shadow
#

So, you know, in the container you kinda have to use that

thick plover
#

and I pass that path via the compose file?

sour shadow
#

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

thick plover
#

oh

sour shadow
#

So, the container sees /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 as /dev/ttyUSB0

thick plover
#

ok

#

so I should be putting /dev/ttyUSB0 in the config.yaml?

sour shadow
#

Yes, since that's the path in the container

thick plover
#

and in the docker-compose file the 'host' path?

sour shadow
#

Your compose file is fine

violet dagger
#

i think you need a venn diagram

sour shadow
#

And possibly a little more time with the Docker docs

thick plover
#

i won't need a venn diagram when I've got a bullet in the head

violet dagger
thick plover
#

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

obsidian sandalBOT
#

Remember, a few hours of trial and error can save you several minutes of reading the documentation.

thick plover
sour shadow
#

Looks good

thick plover
#

I wonder what else could be the problem then ๐Ÿ˜ฆ

sour shadow
#

Push the reset button on the stick, try again

#

Basically, follow all the FAQ steps

thick plover
#

yeah just power cycled the pi

sour shadow
#

You may still need to push the reset button, not entirely sure

thick plover
#

ok

sour shadow
#

Or flash it with the current firmware

thick plover
#

ok its working now

#

not feeling very enlightened this time tho

cunning trellis
#

But you did learn something!

thick plover
#

yeah that I am a dumb c***

jolly narwhal
#

nothing new then

#

๐Ÿ˜„

sour shadow
#

That you don't yet understand Docker "enough"

cunning trellis
#

And that you need a few more hours of trial and error ๐Ÿ˜‰

thick plover
#

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

long junco
#

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.

sour shadow
#

The Sonoffs are known for being junk

thick plover
#

thanks for putting up with my shit lads

#

that was frustrating, literally started working as the wife walked in from work ๐Ÿ˜„

nimble light
#

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.

austere patio
#

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)

sour shadow
#

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

austere patio
long junco
long junco
# sour shadow The Sonoffs are known for being junk

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.

sour shadow
#

The problem is the device isn't reporting/responding

austere patio
long junco
#

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

austere patio
#

Hmm, that shouldn't be showing up then if battery reporting wasn't setup properly

#

Could just be a weird sensor

long junco
#

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!

livid abyss
#

When I change the 'friendly name' in z2m via the web gui, will that be reflected in HA?

sour shadow
#

Yes

#

Assuming of course you enable that when renaming it ๐Ÿ˜‰

#

Turn it on, and as it suggests, it'll update the HA entity

livid abyss
#

Is that in the z2m settings or HA? Can't find it in z2m...

forest cobalt
#

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.

livid abyss
#

I was looking the settings, thanks!

graceful notch
#

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

sour shadow
#

Sure, pull the battery out

#

You need it to be talking on the mesh regularly so it doesn't fall off

graceful notch
#

yeah, it might just be something I notice now, because I'm adding more devices in one time

analog flicker
#

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

forest cobalt
#

It should, yes. Although, Aqara devices are notorious for not reconnecting automatically when separated from their parent router.

austere patio
graceful notch
#

that's good to hear @austere patio

#

I should worry less ๐Ÿ˜‰

dry fossil
#

Zigbee is designed to be incredibly efficient anyway, so once an hour is nothing.

#

Once a minute would still last forever.

graceful notch
#

now to figure out what I can do with the vibration sensors ๐Ÿ˜„

dry fossil
#

Use them as a trigger for mood lighting and romantic music in the bedroom, of course.

forest cobalt
graceful notch
#

that's what I already had in mind, for the glass breaking

dry fossil
#

Ya huh... 'glass breaking'

graceful notch
#

or opening windows

#

I could also mount one on the dogs bench

#

and try one in my car, if the signal is strong enough

dry fossil
#

So you know how many reps it pressed?

forest cobalt
#

lol

dry fossil
forest cobalt
#

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).

graceful notch
forest cobalt
#

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.

graceful notch
#

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

forest cobalt
#

Yup. I've not tried it with any Aqara devices, but my Samsung devices work fine disconnecting/reconnecting to the mesh.

graceful notch
#

I'll try that and post the results here

dry fossil
frail shell
#

downside of replacing the Xiaomi zigbee hub with a usb stick is editing the automations (maybe) but the stick itself seems extremely stable

dry fossil
#

This is the way.

nimble light
austere patio
#

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

tawdry raft
#

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?

forest cobalt
#

Which integration are you using? (Z2M/ZHA/something else)?

tawdry raft
#

ZHA with a conbee2

austere patio
#

I believe there was a zigpy issue opened about this exact problem a while ago

#

Changing the battery or something fixed it, iirc

molten linden
#

My smartthings buttons do this when battery is low

tawdry raft
sand egret
#

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)

nimble light
austere patio
molten linden
nimble light
austere patio
#

Ah, I forgot they released that

#

Won't work, unfortunately. You'll have to edit the package directly within the HA container ๐Ÿ˜ฆ

sand egret
nimble light
austere patio
#

You can, it's just a bit of a chore

nimble light
#

copy the source to custom_components?

molten linden
#

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.

austere patio
sand egret
#

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? :/

austere patio
#

Do you have a coordinator?

sand egret
#

The hive hub is the coordinator I was pairing to.

#

(which obv isn't running HA :D)

austere patio
#

So you're trying to use the CC2531 as a router and want to talk to the Hive hub's network through it?

sand egret
#

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

austere patio
#

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

sand egret
#

yeah makes sense

austere patio
#

So you can use the CC2531 as a coordinator and just make a new network

sand egret
#

Can I NAT the two controllers or something? Or proxy devices from one network onto the other?

austere patio
#

Nope

#

Very bad things start to happen when two devices on the network both say they're 0x0000

sand egret
#

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

austere patio
#

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

sand egret
#

Ok, guessing you;d have to write firmware to do that too.

austere patio
#

There is sniffer firmware but no software that can hook the traffic into e.g. zigpy and then expose it in HA

sand egret
#

not just void OnRecieve(message) { othernetwork.send(message.source, message.data); } etc

austere patio
#

You'd likely have much more luck just migrating the entire Zigbee network to HA ๐Ÿ˜†

sand egret
#

yeah I will do that if there's no off the shelf sw to do it ๐Ÿ˜„

austere patio
#

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.

sand egret
#

Yeah read that - I don't, not yet. Thanks for helping!

austere patio
#

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 ๐Ÿ˜„

nimble light
austere patio
#

Did you get into the HA OS shell?

#

Or are you still at the login screen?

nimble light
#

I run login, it asks me core-ssh login:

austere patio
#

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

nimble light
#

core-ssh login: root Login incorrect

nimble light
austere patio
#

Lemme give it a try

austere patio
heavy latch
austere patio
#

Have you unplugged it and plugged it back in?

heavy latch
#

I didn't, and it's in a place which cant be knocked.

austere patio
#

No I mean have you tried unplugging it and restarting Z2M

heavy latch
#

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 ๐Ÿ™‚

austere patio
#

Your coordinator shouldn't not respond to a SYS.Version request

#

Is this a Z2M startup log?

heavy latch
#

it was just the log

austere patio
#

So Z2M is functional?

#

Does it work after you restart Z2M but not touch the hardware?

heavy latch
#

yep

#

and yep ๐Ÿ™‚

austere patio
#

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

heavy latch
#

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

heavy latch
austere patio
#

Are you triggering a ton of lights at once?

heavy latch
#

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

velvet anchor
#

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?

fringe zephyr
#

I want to get an Ikea dimmer switch and bulb. Do I need a hub to do that?

#

If so any recommendations?

forest cobalt
#

@fringe zephyr Click the pushpin icon at the top of the window. Second message in is what you want to start reading.

velvet anchor
#

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

forest cobalt
velvet anchor
forest cobalt
#

Damnit. I thought they had that by now.

#

Yeah, I don't see anything about it in the github issues.

velvet anchor
#

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

forest cobalt
#

It might be a 2021.6 issue. I'd try posting an issue in github as it might get more visibility by the devs.

velvet anchor
#

I'm guessing maybe started with 2021.5 but thanks, i'll post on gh

thick plover
#

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?

velvet anchor
#

just a follow up. reverted HA to 2021.4.0 with no change. reverted deconz to amd64-2.11.01 and colorloop is back. ๐Ÿ™‚

humble summit
#

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?

sour shadow
#

Are their lights Zigbee? Their range looks rather like WiFi...

humble summit
#

Thats what the support guy said

humble summit
sour shadow
#

It's Zigbee Jim, but not as we know it

humble summit
#

Great reference

sour shadow
#

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

humble summit
#

Haha thank you for the reassurance.

sour shadow
humble summit
#

How do a go about trying to control the lights with a zigbee adapter then?

sour shadow
#

Step #1 - try to pair it with the adapter

#

Oh, and those visually look very similar to Gledopto and Nue smart lights

humble summit
#

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

nimble light
# austere patio You can omit the `login` part, the SSH addon just gives you a normal shell to be...

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."

sand egret
#

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?

sterile sleet
#

2531 is one of the worst coordinators afaik

sour shadow
#

Yes, but it's ok as a router

sand egret
#

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)

sour shadow
#

Well, it's either an end device, or a router

#

It's the Zigbee chip that'd handle that though

sand egret
#

Stuff like lightbulbs are routers, but also things that can be controlled right?

sour shadow
#

Yes, and they're not end devices

#

See the pinned message about how Zigbee works

sand egret
#

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

sour shadow
#

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

sand egret
#

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? ๐Ÿค”

violet dagger
sand egret
#

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!

heavy latch
#

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.

sand egret
#

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 :/

sour shadow
#

If that's a CC2530/31 then those are known to be crappy

heavy latch
#

LAUNCHXL-CC1352P-2 recommended by yourself a long time ago ๐Ÿ™‚

#

I've got a tube poe coordinator on it's way like

sour shadow
#

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)

heavy latch
#

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.

arctic locust
#

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
#

Ah, thought maybe it was another mob that installed

#

or do they do installs too?

humble summit
#

installs too

eternal phoenix
#

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?

eternal phoenix
#

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?

sour shadow
#

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

thick plover
#

I set groups up in z2m but they never made it to HA as entities

sour shadow
#

See the links above

thick plover
#

๐Ÿค“

eternal phoenix
#

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

sour shadow
#

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

thick plover
#

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
sour shadow
#

Did you restart HA after adding that?

#

Did you check the topics are correct?

thick plover
#

I restarted the template entities

#

wait.... maybe its groups I am meant to...

#

hmmm nope

thick plover
obsidian sandalBOT
#

@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.

thick plover
#

woops

#

my bad

sour shadow
thick plover
#

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

jolly narwhal
#

you use the website ?

thick plover
#

I READ THE DOCS MKAY

jolly narwhal
#

you haven't memorized them ?

#

shame

thick plover
#

my brain is already full of shit

#

๐Ÿ˜„

#

its all so tiresome. i will try this another time.

austere patio
eternal phoenix
sour shadow
#

That's about reporting when a device causes a state change - the remote you've bound to the light

austere patio
arctic locust
#

--> what is the best way to post a log?

austere patio
#

Can you post the whole thing, up to the error message?

#

Or just the lines with zigpy or zha

arctic locust
#

sure, I just realised, that the log start on the top... ๐Ÿ˜†

austere patio
#

Is there any more?

arctic locust
#

one second

austere patio
#

Hmmmm. Thanks, I'll take a look.

arctic locust
#

there must be a better way to sort the log then "Ctrl+F"...?

#

thanks a lot!

austere patio
#

Hmmm. Did you do any sort of backup/restore with this thing?

#

The launchxl kit

arctic locust
#

yes, I transfered from CC2531 to TI Launchboard

#

correct

austere patio
#

Yeah, that didn't work too well ๐Ÿ˜†

arctic locust
#

oh...

austere patio
#

Did you copy over the NVRAM directly?

#

That's what looks like what happened

arctic locust
#

no, I delted the Integration and installed it new, the choose the new Launchpad

austere patio
#

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

arctic locust
#

not on purpose...

austere patio
#

Were you previously able to use it with the old home assistant?

arctic locust
#

yes

#

only update to 2021.6.1 killed it

austere patio
#

That is very surprising

#

When did you migrate from the CC2531?

arctic locust
#

May this year

austere patio
#

Did any devices transfer with the migration?

arctic locust
#

all, I had to rename the entities after and it worked

austere patio
#

So to be clear, you never ran anything like zigpy_znp.tools.nvram_write?

arctic locust
#

no

austere patio
#

Just flashed the LAUNCHXL board with firmware and changed the entry in .storage?

arctic locust
#

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

austere patio
#

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?

arctic locust
#

correct

austere patio
#

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?

arctic locust
#

I used UNIFLASH

austere patio
#

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?

arctic locust
#

of course

austere patio
#

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?

arctic locust
#

I bought it way earlier, but the rest is correct

austere patio
#

No flash or NVRAM backup/restore with the CC2531?

arctic locust
#

correct

austere patio
#

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

arctic locust
#

I added the Launchboard May 1st this year (it was in the closet for some time)

austere patio
arctic locust
#

I try, but it will be tomorrow or Sunday, I'll get back to you! thanks a lot!

austere patio
#

Sure thing. Thanks again for the help.

solar oriole
#

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.

torn pawn
#

Anyone here buy this bad boy and get it to work in home assistant?? Iโ€™m using conbee 2.

nimble light
austere patio
austere patio
arctic locust
#

i used it before in a FHEM setup, so it was used before.

austere patio
#

Hmm, I wasn't aware of that platform. What does it use to talk to the Zigbee board?

arctic locust
#

it's mostly in German, that's maybe the reason. It uses Zigbee2mqtt

austere patio
#

Was the CC2531 you were using before flashed with 3.0.x firmware or was it the default Z-Stack Home 1.2?

graceful notch
#

ooh just discovered that the aqara motion sensor also has luminance and temperature

austere patio
graceful notch
#

aha that's good to know

#

I have a bunch of temp sensor though, so not that I would rely on it ๐Ÿ™‚

graceful notch
#

ooh nice

#

with what app did you do the graph ?

austere patio
graceful notch
#

ah I was thinking of putting the mqtt messages immediately to a db and use grafana for it

austere patio
#

That'd work too and probably be a bit easier ๐Ÿ˜†

graceful notch
#

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

austere patio
#

That's alright, your NVRAM backup is really all I need to get it working

arctic locust
#

๐Ÿ™‚

austere patio
#

It just seems that somehow either Z2M or some sort of cosmic rays managed to make your LAUNCHXL's settings a mixture of both

arctic locust
#

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?

austere patio
#

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.

arctic locust
#

if this help, then I can go forward with this!

austere patio
#

Hmm. There are a few more fixes, not that simple.

arctic locust
#

ok, what can i do to help here?

austere patio
#

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 ๐Ÿ˜†

arctic locust
#

ok, gonna try it, thanks a lot!!

arctic locust
#

and thanks again!

austere patio
#

If HA started then it should be working. You should see sensor updates and be able to control devices if everything is 100% working.

arctic locust
#

jup everything works like it should!

muted nest
#

Just got an email that slaesh is now available again

dry fossil
#

Been a long time since I heard anyone promote that stick. Weren't there people having support issues?

muted nest
#

i dont know, i read some issues about that stick too

simple sentinel
#

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

muted nest
#

my zzh is on the way i hope it works fine ๐Ÿ™‚

simple sentinel
#

My Slaesh stick might hit the second hand market soon as I am waiting for one of tube's POE numbers

#

high hopes

muted nest
simple sentinel
#

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

muted nest
#

ok

simple sentinel
#

twitter is a good place too apparently

#

but yeah, times are hard, apparently

#

for everyone from PS5 producers to zigbee enthusiasts

stable ermine
#

Yup. It'll take a little while for supply chains to level back

simple sentinel
#

too, bad cause I love my gadgets ๐Ÿ˜ฎ

stable ermine
#

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?

digital relic
#

anyone use the v2 Hue dimmer switch to reset bulbs? was it successful?

quick terrace
#

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?

mellow valve
#

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?

formal pasture
#

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!

molten linden
# muted nest ok

Module manufacturer is not very clear โ€œthis month or next monthโ€ ๐Ÿคท๐Ÿผโ€โ™‚๏ธ so hopefully by mid/late July I guess

formal pasture
#

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!

formal pasture
#

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.

gentle flint
livid abyss
#

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.

graceful canopy
#

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?

graceful canopy
#

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

quick terrace
graceful notch
#

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)

sour shadow
#

Higher is better

#

LQI is a measure of many things, depending on the device, and is often just a vague indicator

oblique root
#

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

faint vine
# oblique root Hi everyone, just a quick question. I have about 20 xiaomi window/door sendors s...

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

sour shadow
#

I've had no issues with Ikea, Gledopto, Innr, Salus, or DIY ones

oblique root
oblique root
sour shadow
#

If you turn the power off to them, yes

#

Not if you use the button on them/Zigbee commands to turn them off though

faint vine
sour shadow
#

As long as a Zigbee router has power it will continue to route traffic

#

Otherwise the mesh would spend more time broken than working...

oblique root
obsidian sandalBOT
#

@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.

faint vine
#

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.

sour shadow
#

Does the Logbook show them turning off, or HA doing something and then them turning off

faint vine
#

Both, intermittently it seems, sometimes it says "Turned off by Alfie" and other times it just says "Turned off"

sour shadow
#

The first says that Alfie did that (probably using the UI)

#

The second says that HA detected it turning off

faint vine
#

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.

sour shadow
#

Check the link quality

#

That'd be a pretty bad bit of design though ๐Ÿ˜„

faint vine
#

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 ๐Ÿ˜‚

sour shadow
#

Yeah, that's fine

faint vine
#

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

sour shadow
#

So, something external to HA turned it off

faint vine
#

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

frail shell
#

update : a driver package seems required when using the zigbee stick in a synology

faint vine
#

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

oblique root
#

Maybe a dumb idea, could it be related to mqtt? Maybe they share topics with other devices? Is that even possible?

faint vine
#

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 ๐Ÿ™‚

frail shell
#

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 ?

livid abyss
#

Nobody has an idea how I can get a sensor to reconnect to the network if resetting it does not work?

graceful notch
#

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..

solid inlet
graceful notch
#

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 ๐Ÿ™‚

hardy crane
#

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

solid inlet
#

Thanks, I will keep this in mind ๐Ÿ™‚

graceful notch
#

no problem, i have made a git repo that's public, but the more feedback i have, the better it can become

frail shell
#

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 ?

dry fossil
#

Ignore the link quality. Does it work?

frail shell
#

yes it works

#

but my devices 4 meters away from it don't have a connection anymore

dry fossil
#

Those two things aren't related.

#

Re-pair the things that don't work. Stop worrying about LQI numbers if things work.

frail shell
#

in the other room i don't have signal anymore between the stick and the Xiaomi door sensor

dry fossil
#

Re-pair the things that don't work

frail shell
#

ok

wide saffron
graceful notch
#

it worked fine for me

#

just need to be nearby the bulb like within 1m range

digital relic
#

I'd check the HD website, and even look at your nearby towns to see if one is still in stock.

frail shell
#

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

frail shell
#

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

hardy crane
#

Ideally you want to be pairing them at the place they are going to be put

#

plugs, lights, mains switches take your pick

frail shell
#

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)

dry fossil
#

The 'pair in situ' rule is so it picks up the best router, not just the one you were nearest when you paired.

frail shell
#

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)

frail shell
#

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)

dry fossil
dry fossil
frail shell
#

the netherlands

golden vessel
#

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.

frail shell
hardy crane
#

I believe I've seen the BlitzWolf BW-SHP13 on sale on Banggood

frail shell
#

50% cheaper then the xiaomi

hardy crane
#

Maybe I should get a few myself

tall nacelle
#

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?

obsidian sandalBOT
sour shadow
#

As mentioned, the integration you use matters

#

The stick is not that important (for this anyway)

tall nacelle
frail shell
#

Hey Tinkerer : small update , i managed to get the stick working on a synology too , i had to install a driver package

sour shadow
#

Did you read the bot message?

#

Please read them...

tall nacelle
#

I did, but I assumed mentioning Conbee II implied I was using DeConz integration. My bad

sour shadow
#

Well, no, because you can use that stick with all three options

tall nacelle
#

ok, I didnt know, sorry

sour shadow
#

If nobody here knows, the people on the deCONZ Discord should know

obsidian sandalBOT
#

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.

tall nacelle
#

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

sour shadow
#

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

tall nacelle
#

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

sour shadow
#

The feature has to be enabled I believe

tall nacelle
#

ok ill dig further, thx for the help

graceful notch
#

@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

tall nacelle
#

thx dude. I dont currently, but maybe its time to switch over

graceful notch
#

what do you use atm ?

tall nacelle
#

Im not entirely sure ๐Ÿ˜„ I just use the Deconz integration?

#

no mqtt

graceful notch
#

ah I prefer the mqtt way, don't ask me why ๐Ÿ™‚

sour shadow
#

Z2M > ZHA >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> deCONZ
(IMO)

austere patio
tall nacelle
#

I struggled to find a reason to increase complexity by adding mqtt in the past. This is a compelling reason though ๐Ÿ™‚

graceful notch
#

oh also something you need to do

#
  "hue_power_on_behavior": "recover"
}```
tall nacelle
#

thanks

graceful notch
#

Just tested and it works with those settings

tall nacelle
#

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'

modern kite
#

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

austere patio
rich mirage
#

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

mellow geode
#

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?

mellow valve
#

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?

mellow valve
#

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"?

mellow geode
#

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)

thick plover
alpine hill
#

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

sour shadow
#

What sensor?

alpine hill
#

Aqara motion sensor

sour shadow
#

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

alpine hill
#

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.

sour shadow
#

Just keep in mind that for the rest of that minute, the motion sensor is blind to any further movement

solid inlet
#

For what reason is there such timeout enforced by the vendors?

violet dagger
#

battery saving

solid inlet
#

aha, ok

alpine hill
#

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)

sour shadow
#

So see the issue I linked for the UI setting shrug

alpine hill
#

That is not the problem?

violet dagger
#

you need to do a hardware modification to make the aqara motion sensor more responsive

sour shadow
#

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?

alpine hill
#

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.

sour shadow
#

Ah, right, so with HA the assumption is that you have the deCONZ UI

alpine hill
#

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

sour shadow
#

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

dark tusk
#

@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.

glad plume
#

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.

wide quiver
#

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.

forest cobalt
#

Unless you have your Hue devices directly connected to a Zigbee coordinator using ZHA/Z2M/deCONZ.

glad plume
alpine hill
glad plume
#

That made the Zigbee2mqtt work:

  new_api: true```
sour shadow
#

new_api went away some time ago, are you still on an ancient version?

exotic crater
#

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)

graceful notch
#

delete and re-pair ?

exotic crater
graceful notch
#

I have only paired 1 , so I wouldn't know why

#

maybe it's already broken ๐Ÿ˜„

rich mirage
#

I also had the same issues with the cr2351. in fact it was worst. and I used to get LQI of 40 to 150

exotic crater
graceful notch
#

you use zigbee2mqtt, deconz, .. ?

exotic crater
graceful notch
#

how many devices do you already have and does the log from zigbee2mqtt show something ?

exotic crater
exotic crater
exotic crater
graceful notch
#

if it's working, that's what counts ๐Ÿ˜„

mellow geode
frail shell
#

i ordered a BW-SHP13 plug from banggood and will use it as a zigbee repeater

#

they're just 10 euro atm

rich mirage
#

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...

frail shell
#

are you using the zigbee version of a sonoff device?

rich mirage
#

yes

#

sonoff temp sensor and door sensor

frail shell
#

sorry i don't have experience with that version myself

austere patio
#

Just install the required Python packages and you can run the main script on Windows

drifting drum
#

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

sour shadow
#

Make sure you're running the latest version of Z2M too

#

1.19.1 I believe

frail shell
#

Hello everyone , i wonder about the security of a zigbee network

jolly narwhal
#

If you lock the door no-one will get in

frail shell
#

it uses a shared key

#

lol atx true

jolly narwhal
#

Sure, but unless a device is paired it cannot talk

frail shell
#

yes indeed

#

and a new device can't be added from a distance

#

a malicious device

autumn warren
#

Are older Zigbee bulbs not supported by ZHA? I have two bulbs that can be found by the Hue app but not by ZHA

dry fossil
#

The age is almost definitely irrelevant. The model, and whether there's a quirk for it, is what matters.

autumn warren
#

Model 9290022268

Where would I see if there's a quirk for it?

dry fossil
#

I'll let a ZHA user answer that. I use Z2M.

forest cobalt
#

What channel are you using @autumn warren?

dry fossil
#

Sorry, couldn't resist ๐Ÿ˜„

autumn warren
#

Not sure, tried looking in HA but didn't see anything regarding that

#

Nwk: 0x6b06 if that means anything

forest cobalt
#

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?

autumn warren
#

A while ago yeah, but even after adding to Hue app and deleting they don't show in ZHA

forest cobalt
#

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.

autumn warren
#

Well I have a Bridge, so I'm assuming the app connects the bulb to that

forest cobalt
#

If the bridge is on and connected, it should, yeah.

#

But those BT bulbs are just a pain in the butt.

autumn warren
#

I've reset it twice, should I try it more?

forest cobalt
#

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. ๐Ÿ˜ฆ

autumn warren
#

Just looked that up, yeah I'll give it a shot

#

Thanks!

forest cobalt
#

Anytime!

austere patio
dry fossil
#

All we need now is his physical location and we can attack his network.

drifting drum
drifting drum
drifting drum
sour shadow
drifting drum
#

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!

frail shell
#

people i wonder if there is a way where i can check my shared key in Zigbee2mqtt

jolly narwhal
#

check what ?

frail shell
#

the network key

#

zigbee2mqtt seems to crash when i specify one in the config

sour shadow
#

"Seems to" ๐Ÿค”

frail shell
#

yes it crashed

sour shadow
#

Well, what does the log file tell you?

frail shell
#

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

sour shadow
#

You have a CC2531 stick with an old (2019) firmware on it

#

There's an issue in the Z2M repo about it