Zigbee2mqtt: getting rid of your proprietary Zigbee bridges (Xiaomi, Hue, TRADFRI)

Hi! Thank you for the info, how did you force removed the sensors? I am trying to remove them from the devices menu in configuration but if I reboot they appear again, and they are still not working properly.

Easiest way is using zigbee2mqttassistant :

image

1 Like

i’ve used this metod

1 Like

Thank you all, it works!

1 Like

I just use a USB extension cord for the atenna and then added a few ikea zigbee repeaters. Was cheap and easy and meant I didnt have to mess with a working solution :wink:

3 posts were split to a new topic: ZHA - pairing Ikea router

Admittedly, I haven’t read the entire topic and doing a search hasn’t given me the answer but…

I thought I saw somewhere that the HUSBZB-1 stick will now work with Zigbee2MQTT.

Is that correct or am I only imagining that I saw it?

It is not on the list of supported adapters

1 Like

You may be thinking of conbee support.

1 Like

I saw that but since I could have sworn I saw support was added for the HUBZ stick I figured I’d ask here in case the docs hadn’t been updated or some such.

Maybe but that doesn’t ring a bell.

But I think I had it backwards…

It must have been that the ZHA component had added experimental support for the TI zigbee radios that I was thinking of.

up to now I have always used a CC2531 coordinator with zStack12 (revision ': 20190608) I have several Hue / ikea lights and xiami and mija sensors everything works discreetly, only occasionally some sensor loses the connection and I have to reset it. I wanted to try a new key with cc2530, programmed as coordinator and with the same firmware, I only change the configuration inherent to the new hardware and leaving unchanged network key and channel, but unfortunately the various peripherals do not connect to the new coordinator, I had to restore the old one cc2531. Is there a way to reset all peripherals from zigbee2mqtt before using new hardware? I read that the Hue are problematic to reset. Or if you have any advice on how to use the new cc2530 usb without having to reset anything I would be grateful.
this is the old config:

data_path: /share/zigbee2mqtt
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://homeassistant'
  user: user
  password: password
serial:
  port: /dev/ttyACM0
  disable_led: true
advanced:
  availability_timeout: 60
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blacklist:
    - '0x00158d0002xxxxx'
ban: []
whitelist: []
queue: {}
socat:
  enabled: false
  master: 'pty,raw,echo=0,link=/dev/ttyZ2M,mode=777'
  slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
  restartdelay: 1
  initialdelay: 1
  options: '-d -d'
  log: false

and this should be the new one

data_path: /share/zigbee2mqtt
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://homeassistant'
  user: user
  password: password
serial:
  port: /dev/ttyUSB0
advanced:
  availability_timeout: 60
  rtscts: false
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blacklist:
    - '0x00158d0002d6xxxx'
ban: []
whitelist: []
queue: {}
socat:
  enabled: false
  master: 'pty,raw,echo=0,link=/dev/ttyZ2M,mode=777'
  slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
  restartdelay: 1
  initialdelay: 1
  options: '-d -d'
  log: false```

I read on another post that it’s not advisable to mix ZLL and ZHA devices on the same mesh, yet there are a lot of posts here that suggest people are doing just that. What is the current recommendation? I struggle with poor signal between my mainly Xiaomi sensors so it would be great to add my 5 hue bulbs to the mesh to improve coverage.

Hi all,
Is the conbee2 stick support already in the stable channel or only on the dev channel? Thanks

Hi !

If you are using @danielwelch’s Zigbee2mqtt Hassio addon, which is tracking the latest version of @Koenkk’s Zigbee2mqtt (today at 1.14.1), experimental ConBee support has been added and is worked on since release 1.12.0. If you want to track progress, follow this GitHub issue on Koen’s zigbee-herdsman library.

So I would answer : “yes” to your question. However, I was not able to make it work in my config as it looks like the Hassio addon does not want to see my adapter. I might give it another shot if I have time this week to dig further. In the meantime I’m using the “native” ZHA integration.

Edit: I might have found why I was not able to make it work, see this GitHub issue.

Hope this helps :slight_smile:

Thanks for the info. I am using the HassIO addon. I was asking because I was not able to start z2m too using the conbee2 stick. Using a CC2531 works with no problem.
I am guessing same issue with the github issue you linked to.

After the update zigbee2mqtt from 1.14 to 1.14.1 https://www.zigbee2mqtt.io/devices/ptvo.switch.html
I observe the following two errors:

  1. The zigbee2mqtt add on https://github.com/danielwelch/hassio-zigbee2mqtt needs to be restarted in order to get the PTVO devices connected. Only after this restart you see the linkquality signal.

  2. The PTVO switch does not respond to commands from Hassio.
    I get the following error

zigbee2mqtt:error 2020-07-19 09:28:02: Failed to call 'EntityPublish' 'onMQTTMessage' (AssertionError [ERR_ASSERTION]: Endpoint name 'bottom_left' is given but device has no such endpoint
    at Zigbee.resolveEntity (/zigbee2mqtt-1.14.1/lib/zigbee.js:202:25)
    at EntityPublish.onMQTTMessage (/zigbee2mqtt-1.14.1/lib/extension/publish.js:59:44)
    at Controller.callExtensionMethod (/zigbee2mqtt-1.14.1/lib/controller.js:360:44)
    at Controller.onMQTTMessage (/zigbee2mqtt-1.14.1/lib/controller.js:254:14)
    at MQTT.emit (events.js:315:20)
    at MQTT.onMessage (/zigbee2mqtt-1.14.1/lib/mqtt.js:95:14)
    at MqttClient.emit (events.js:315:20)
    at MqttClient._handlePublish (/zigbee2mqtt-1.14.1/node_modules/mqtt/lib/client.js:1269:12)
    at MqttClient._handlePacket (/zigbee2mqtt-1.14.1/node_modules/mqtt/lib/client.js:409:12)
    at work (/zigbee2mqtt-1.14.1/node_modules/mqtt/lib/client.js:320:12))

Looking at the MQTT explorer I see no abnormalities

Screenshot 2020-07-19 at 09.32.09

By the way my other IKEA Zigbee devices all function normally

What I have tried so far:
-switch to zigbee2mqtt edge
-remove/reinstall device
-various restarts

and then I found this help:
https://github.com/Koenkk/zigbee2mqtt/issues/3877

but how to change the configuration manually in Hassio?

I have zigbee2mqtt, HA and mosquitto all running on one computer now but the location isn’t great for the ZigBee network, so I am considering moving zigbee2mqtt to another computer located closer to the battery-powered sensors, or alternatively adding another router.

Two general questions;

  1. Can I migrate zigbee2mqtt to another computer just by moving the CC2531 and copying the config, state and database files over?
  2. Is a RPi 2 good enough to run zigbee2mqtt? The broker will not move. Will I notice the extra latency when controlling from a zigbee button to HA?

I run my zigbee2mqtt on a RbPi 1 :slight_smile:

Good, because my spare pi is actually a rev 1 model B also! I forgot it doesn’t have WiFi though. So is the performance ok?

Performance is OK.