Zigbee2MQTT

[Teon]

I'm trying to flash a CC2531 with the CC Debugger and Downloader-cable.
I'm following: https://koenkk.github.io/zigbee2mqtt/ge ... c2531.html
After connecting just the debugger to pc: LED RED (=ok)
After connecting just the CC2531 stick to pc: LED on stick is green (=ok)
Drivers are correctly installed and shown in Windows 10 Device manager. Both Debugger and CC2531 USB Dongle are shown as Cebal controlled devices.
After connecting CC debugger --> Downloader cable CC2531 --> CC2531 USB sniffer: LED on debugger is red. LED on stick is green, so no device is detected by debugger.
After pressing reset on debugger the LED on the sniffer goes off. The debugger LED is red.

USB-cable is ok, tried multiple.
Debugger is ok. Tried 2.

Looks like the cables and downloader cable are ok. Is my sniffer broken?

Thanks for your help!

[EddyG]

After pressing the reset button, the led on the debugger should go green.
Is the cable between the debugger and CC2531 correct connected?

[sylar]

Hi there.
zigbee2mqtt just introduced group support in its last version (see https://github.com/Koenkk/zigbee2mqtt/b ... /groups.md). I guess this is not yet supported by the plugin? Is this something which could be easily added?
The plugin could then create one new device per group, or either automatically create a scene.

[gerbenvanasselt]

Hi there.
zigbee2mqtt just introduced group support in its last version (see https://github.com/Koenkk/zigbee2mqtt/b ... /groups.md). I guess this is not yet supported by the plugin? Is this something which could be easily added?
The plugin could then create one new device per group, or either automatically create a scene.

After updating zigbee2mqtt from in opt/zigbee2mqtt/ my zigbee shephard is not running anymore. It does not start any more. Even NPM start gives some errors. Anyone having the same experience or found a solution. I am thinking about reinstalling the zigbee2mqtt but maybe there is another solution.'

Code: Select all

pi@raspberrypi:/opt/zigbee2mqtt $ npm start

> [email protected] start /opt/zigbee2mqtt
> node index.js

  zigbee2mqtt:info 2019-1-31 15:24:26 Logging to directory: '/opt/zigbee2mqtt/data/log/2019-01-31.15-24-26'
/opt/zigbee2mqtt/lib/extension/devicePublish.js:13
    zigbeeShepherdConverters.toZigbeeConverters.on_off,
                                                ^

TypeError: Cannot read property 'on_off' of undefined
    at Object.<anonymous> (/opt/zigbee2mqtt/lib/extension/devicePublish.js:13:49)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object.<anonymous> (/opt/zigbee2mqtt/lib/controller.js:13:32)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2019-01-31T14_24_27_339Z-debug.log

[sylar]

Had a lot of trouble when updating too. I found that a simple reboot could help sometimes, without having any idea why...

[gerbenvanasselt]

Had a lot of trouble when updating too. I found that a simple reboot could help sometimes, without having any idea why...

Tried that several times, but after a reinstall and editing the configuration.yaml npm start works again.

thanks

[sylar]

Did you have to re-pair all devices, or was it sufficient to restore the configuration.yaml (more generally, the data/ folder) to have everything back to normal?

[data]

I have installed zigbee2mqtt, mosquitto as well as the python plugin for domoticz.
So far, everything looks good, I can pair devices and see messages in the log.
However, I see no new device in the list.
Do I have to make anything else to get my devices?

I tried with an IKEA Tradfri 1000lm LED as well as the tint from Aldi (Müller Licht).
I have also verified, that both devices are supported in the plugin.

[StasDemydiuk]

Did you check Domoticz devices page for your new devices?

[data]

Well, yes, sure. That's why I wrote that I don't see the paired device in the list.

[StasDemydiuk]

Could you please share your Domoticz log, maybe plugin has issues connecting to MQTT server

[data]

Ok, I'll post it tomorrow or wednesday, when I have some time.
I am using the lights at the moment

But I can see the messages from zigbee2mqtt / mosquitto in the domoticz log, so I don't think it is related to the mqtt server.

Can you please post a few lines from your log - how it should look like when you pair / add a new device.

[jvbussel]

I also wondered if the paired zigbee devices should show up beneath devices in Domoticz when the zigbee2mqtt bridge was used. But didn’t saw anything. What else should I do?
Then I saw the following in the Domotics log: (Zigbee2MQTT) Failed to connect to: localhost:1833, Description: Connection refused

I tried if the mqtt daemon gave a response by issueing:

mosquitto_sub -h Localhost -t "#" -v

And did saw a response. Currently I do not have a clue on what to do to fix this connection refused issue.
Does anyone have a tip?

[salopette]

you have to customize the data / configuration.yaml

# Required: Home Assistant integration (MQTT discovery)
homeassistant: false

# Required: allow new devices to join.
# WARNING: Disable this after all devices have been paired!
permit_join: true

# Required: MQTT settings
mqtt:
# Required: MQTT base topic for zigbee2mqtt MQTT messages
base_topic: zigbee2mqtt
# Required: MQTT server URL
server: 'mqtt://localhost:1883'
# Optional: MQTT server authentication user
user: my_user
# Optional: MQTT server authentication password
password: my_password
# Optional: MQTT client ID
client_id: 'MY_CLIENT_ID'
# Disable self-signed SSL certificates
reject_unauthorized: true
# Optional: Include device information to mqtt messages (default: false)
include_device_information: true

[jvbussel]

I do think I did not configure any authentication for mosquitto. That’s why I did not enter a username/password in configuration.yaml

The mosquitto client showed output on all my domoticz devices without passing credentials either.

[salopette]

I also do not have a login for mqtt,
But if you have login you have to install it in domoticz plugin

[jvbussel]

In the mosquitto configuration file there is currently allow_anonymous true

That’s why I did not fillin the username/password.

You are correct, when you do configure username/password you have to supply them in the Domoticz plugin. However this is not the case for now.

[data]

@Stas
Just wanted to give you an update: It works.
I made a fresh install of domoticz and upon starting, it immediately got it's devices from the stick and made them available in the devices overview.

The only thing not working is the link quality indicator. It remains always at 0.

[peerke72]

Í just got my Zigbee2MQTT installed and it is running finally.

I was wondering if it's normal the Raspberry Pi 3 CPU usage increases from average 2% before installation, to approximately 25% after installation of ZIgbee2MQTT. Or does this suggest something is wrong ?

[Smiggel]

Hi guys,

I have a CC2531 USB stick running using the https://github.com/Koenkk/zigbee2mqtt guide. I have also installed the Domoticz plugin (https://github.com/stas-demydiuk/domoti ... qtt-plugin) installed. I have a total of 2 Xaomi doorsensor connected and 5 Xiaomi temp/hum/bar sensors connected. They all work just fine after having paired them.

However, I notice sometimes one of the temp/hum/bar sensors suddenly stops with updating. I have no errors in my logs and the other sensors continue without problems. It's also not always the same sensor. One time it was the sensor on the attic and then it suddenly it's the sensor in the bedroom. It's not just for one hour, but for over 12 hours or so. When I push the rest button of the sensor, it starts to work again. I did not have this issue with the Xaomi hub (v2) installed.

Can someone tell me what could be causing this problem? Does anyone else experience these kind of issues?