So I recently got a Raspberry Pi 4, CC2531 usb stick which I flashed with the zigbee2mqtt firmware and have been trying to get Hass.io set up to connect with some Xiaomi sensors (Also Ikea but for now the Xiaomi).
At first I flashed the Hass.io 3.3 beta image to micro SD card, booted up and then installed the Mosquitto broker addon and the zigbee2mqtt addon. As far as configuring, I followed the documentation for each addon and looked up a few guides but I’m not sure if I’ve got things set up correctly. I’m not getting any errors and the log for the zigbee2mqtt addon shows: zigbee2mqtt:info 8/24/2019, 2:10:10 PM Successfully reenabled joining over and over.
When I try to pair a Xiaomi DJT11LM vibration sensor I literally get no response at all from the zigbee2mqtt addon. I’ve read that it’s “difficult” to pair and I’ve tried many times, including pressing every 1 second for twenty seconds after holding for 5, but not matter what I do, it simply isn’t showing up in the addon logs.
Due to WiFi not working on the Hass.io beta image for the Pi 4, I’ve also tried (my current setup) installing Raspbian lite and then installing Hass.io using the instructions here: https://github.com/home-assistant/hassio-installer
I got Hass.io up and running, installed the addons and tried pairing and still nothing.
Here’s what I’ve got in the addons and config files:
zigbee2mqtt addon:
{
"data_path": "/share/zigbee2mqtt",
"devices": "devices.yaml",
"groups": "groups.yaml",
"homeassistant": true,
"permit_join": true,
"mqtt": {
"base_topic": "zigbee2mqtt",
"server": "mqtt://192.168.0.83:1883",
"user": "mqtt",
"password": "ali4395"
},
"serial": {
"port": "/dev/ttyACM0"
},
"advanced": {
"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": []
},
"ban": [],
"whitelist": [],
"queue": {}
}
LOG on restart:
./run.sh: line 16: [Info] Configuration backup found in /share/zigbee2mqtt/.configuration.yaml.bk. Skipping config backup.: No such file or directory
2019-08-24T17:56:28: PM2 log: Launching in no daemon mode
2019-08-24T17:56:28: PM2 log: App [npm:0] starting in -fork mode-
2019-08-24T17:56:28: PM2 log: App [npm:0] online
> [email protected] start /zigbee2mqtt-1.5.1
> node index.js
zigbee2mqtt:info 8/24/2019, 5:56:31 PM Logging to directory: '/share/zigbee2mqtt/log/2019-08-24.17-56-30'
zigbee2mqtt:info 8/24/2019, 5:56:31 PM Starting zigbee2mqtt version 1.5.1 (commit #unknown)
zigbee2mqtt:info 8/24/2019, 5:56:31 PM Starting zigbee-shepherd
zigbee2mqtt:info 8/24/2019, 5:56:33 PM zigbee-shepherd started
zigbee2mqtt:info 8/24/2019, 5:56:33 PM Coordinator firmware version: '20190608'
zigbee2mqtt:info 8/24/2019, 5:56:33 PM Currently 0 devices are joined:
zigbee2mqtt:warn 8/24/2019, 5:56:33 PM `permit_join` set to `true` in configuration.yaml.
zigbee2mqtt:warn 8/24/2019, 5:56:33 PM Allowing new devices to join.
zigbee2mqtt:warn 8/24/2019, 5:56:33 PM Set `permit_join` to `false` once you joined all devices.
zigbee2mqtt:info 8/24/2019, 5:56:33 PM Zigbee: allowing new devices to join.
zigbee2mqtt:info 8/24/2019, 5:56:33 PM Connecting to MQTT server at mqtt://192.168.0.83:1883
zigbee2mqtt:info 8/24/2019, 5:56:33 PM zigbee-shepherd ready
zigbee2mqtt:info 8/24/2019, 5:56:33 PM Connected to MQTT server
zigbee2mqtt:info 8/24/2019, 5:56:33 PM MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
zigbee2mqtt:info 8/24/2019, 5:56:33 PM MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.5.1","commit":"unknown","coordinator":20190608,"log_level":"info","permit_join":true}'
Mosquitto broker addon:
{
"logins": [
{
"username": "mqtt",
"password": "mqtt"
}
],
"anonymous": true,
"customize": {
"active": false,
"folder": "mosquitto"
},
"certfile": "fullchain.pem",
"keyfile": "privkey.pem"
}
LOG on restart:
[17:55:29] INFO: Setup mosquitto configuration
[17:55:29] WARNING: SSL not enabled - No valid certs found!
[17:55:29] INFO: Found local users inside config
[17:55:29] INFO: Initialize Hass.io Add-on services
[17:55:29] INFO: Initialize Home Assistant discovery
[17:55:29] INFO: Start Mosquitto daemon
1566665729: mosquitto version 1.6.3 starting
1566665729: Config loaded from /etc/mosquitto.conf.
1566665729: Loading plugin: /usr/share/mosquitto/auth-plug.so
1566665729: |-- *** auth-plug: startup
1566665729: ├── Username/password checking enabled.
1566665729: ├── TLS-PSK checking enabled.
1566665729: └── Extended authentication not enabled.
1566665729: Opening ipv4 listen socket on port 1883.
1566665729: Opening ipv6 listen socket on port 1883.
1566665729: Opening websockets listen socket on port 1884.
1566665729: Warning: Mosquitto should not be run as root/administrator.
1566665729: New connection from 172.30.32.1 on port 1883.
[INFO] found mqtt on local database
1566665730: New client connected from 172.30.32.1 as mqttjs_81c9a613 (p2, c1, k60, u'mqtt').
1566665735: New connection from 172.30.32.1 on port 1883.
CONFIGURATION.yaml:
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
# base_url: example.duckdns.org:8123
# Text to speech
tts:
- platform: google_translate
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
So I’m hoping if someone can help and let me know if there’s anything in my config that isn’t right or needs to be corrected?
Also, the log entry from zigbee2mqtt suggests that my CC2531 is connected and responding correctly:
zigbee2mqtt:info 8/24/2019, 5:56:33 PM Coordinator firmware version: ‘20190608’
But is there a way to check that i’ve installed the firmware correctly and that the stick itself isn’t faulty? The LED on the stick is a solid red colour. At one point shortly after flashing I think, it was flashing on and off green.
Also wondering if the Pi4 or Hass.io beta image or Rasbian Lite is fully compatible with the CC2531? Are the drivers known to be working? Is my inability to pair any sensors (also tried an Ikea lightbulb) due to a config problem or is the Pi4 not there yet in terms of support.
Any help would be great as I’m totally stuck trying to figure out why my CC2531 stick doesn’t seem to respond. Thanks