Able to pair with two different devices but can't talk to them after

General support
1

Hey all,
New to zigbee2mqtt and hoping to get some help.

I’ve so far managed to pair my three Sengled E11-G13 lightbulbs and the Centralite Jilia Pearl Thermostat using CC2531 flashed with CC2531ZNP-Prod.hex. However none of the devices report their state or are able to be controlled, I realise the Thermostat is not supported but the lights should at least be visible in the MQTT browser I’d have thought, and the bulbs don’t respond to state on/off JSON messages in Node RED.
Hopefully, I’m doing something stupid and it’s an easy fix! Would appreciate any pointers and/or suggestions on how to get this working!

Here’s what I have in zigbee2mqtt/bridge/config

{
“version”:“1.8.0”,
“commit”:“da4d26a”,
“coordinator”:{
“type”:“zStack12”,
“meta”:{
“transportrev”:2,
“product”:0,
“majorrel”:2,
“minorrel”:6,
“maintrel”:3,
“revision”:20190608
}
},
“log_level”:“debug”,
“permit_join”:true
}

2

Does anyone have any ideas? I’ve not been able to make any use of zigbee2mqtt at all after weeks of bashing my head against it

3

How do you run zigbee2mqtt ? Your config looks quite different then mine. And I don’t see a reference to the mqtt broker.

4

Hi Francis, running it on he RPI4 debian with sysctl.
What I printed was the state of the MQTT broker for topic zigbee2mqtt, not the config, here’s the config:

homeassistant: false
permit_join: true
mqtt:
base_topic: zigbee2mqtt
server: ‘mqtt://localhost’
serial:
port: /dev/ttyACM0
advanced:
channel: 15
availibility_timeout: 120
log_level: debug
log_directory: data/log/

Devices yaml:

‘0xb0ce181403361148’:
friendly_name: Bedroom_bulb_1
‘0xb0ce18140335ef41’:
friendly_name: Bedroom_bulb_2
‘0xb0ce181403362894’:
friendly_name: Bedroom_bulb_3
‘0x000d6f000b056140’:
friendly_name: ‘Lower_floor_thermostat’

Here are the logs with some of the lights going on during that time and there’s no mention of them appearing on the log, which I would expect:

Jan 25 03:45:50 raspberrypi systemd[1]: Started zigbee2mqtt.
Jan 25 03:45:55 raspberrypi npm[494]: > zigbee2mqtt@1.8.0 start /opt/zigbee2mqtt
Jan 25 03:45:55 raspberrypi npm[494]: > node index.js
Jan 25 03:45:58 raspberrypi npm[494]: zigbee2mqtt:info 2020-01-25 11:45:58: Logging to console and directory: ‘data/log/’
Jan 25 03:45:58 raspberrypi npm[494]: zigbee2mqtt:debug 2020-01-25 11:45:58: Loaded state from file /opt/zigbee2mqtt/data/state.json
Jan 25 03:45:59 raspberrypi npm[494]: zigbee2mqtt:info 2020-01-25 11:45:59: Starting zigbee2mqtt version 1.8.0 (commit #da4d26a)
Jan 25 03:45:59 raspberrypi npm[494]: zigbee2mqtt:info 2020-01-25 11:45:59: Starting zigbee-herdsman…
Jan 25 03:45:59 raspberrypi npm[494]: zigbee2mqtt:debug 2020-01-25 11:45:59: Using zigbee-herdsman with settings: '{“network”:{“panID”:6754,“extendedPanID”:[221,221,221
Jan 25 03:46:01 raspberrypi npm[494]: zigbee2mqtt:info 2020-01-25 11:46:01: zigbee-herdsman started
Jan 25 03:46:01 raspberrypi npm[494]: zigbee2mqtt:info 2020-01-25 11:46:01: Coordinator firmware version: '{“type”:“zStack12”,“meta”:{“transportrev”:2,“product”:0,"maj
Jan 25 03:46:01 raspberrypi npm[494]: zigbee2mqtt:debug 2020-01-25 11:46:01: Zigbee network parameters: {“panID”:6754,“extendedPanID”:“0xdddddddddddddddd”,“channel”:15}
Jan 25 03:46:01 raspberrypi npm[494]: zigbee2mqtt:info 2020-01-25 11:46:01: Currently 4 devices are joined:
Jan 25 03:46:01 raspberrypi npm[494]: zigbee2mqtt:info 2020-01-25 11:46:01: Bedroom_bulb_1 (0xb0ce181403361148): E11-G13 - Sengled Element Classic (A19) (EndDevice)
Jan 25 03:46:01 raspberrypi npm[494]: zigbee2mqtt:info 2020-01-25 11:46:01: Bedroom_bulb_2 (0xb0ce18140335ef41): E11-G13 - Sengled Element Classic (A19) (EndDevice)
Jan 25 03:46:01 raspberrypi npm[494]: zigbee2mqtt:info 2020-01-25 11:46:01: Bedroom_bulb_3 (0xb0ce181403362894): E11-G13 - Sengled Element Classic (A19) (EndDevice)
Jan 25 03:46:01 raspberrypi npm[494]: zigbee2mqtt:info 2020-01-25 11:46:01: Lower_floor_thermostat (0x000d6f000b056140): 3157100 - Centralite Centralite 3-Series Pearl
Jan 25 03:46:01 raspberrypi npm[494]: zigbee2mqtt:warn 2020-01-25 11:46:01: permit_join set to true in configuration.yaml.
Jan 25 03:46:01 raspberrypi npm[494]: zigbee2mqtt:warn 2020-01-25 11:46:01: Allowing new devices to join.
Jan 25 03:46:01 raspberrypi npm[494]: zigbee2mqtt:warn 2020-01-25 11:46:01: Set permit_join to false once you joined all devices.
Jan 25 03:46:01 raspberrypi npm[494]: zigbee2mqtt:info 2020-01-25 11:46:01: Zigbee: allowing new devices to join.
Jan 25 03:46:01 raspberrypi npm[494]: zigbee2mqtt:info 2020-01-25 11:46:01: Connecting to MQTT server at mqtt://localhost
Jan 25 03:46:01 raspberrypi npm[494]: zigbee2mqtt:info 2020-01-25 11:46:01: Connected to MQTT server
Jan 25 03:46:01 raspberrypi npm[494]: zigbee2mqtt:info 2020-01-25 11:46:01: MQTT publish: topic ‘zigbee2mqtt/bridge/state’, payload ‘online’
Jan 25 03:46:01 raspberrypi npm[494]: zigbee2mqtt:info 2020-01-25 11:46:01: MQTT publish: topic ‘zigbee2mqtt/bridge/config’, payload '{“version”:“1.8.0”,“commit”:"da4d
Jan 25 03:56:17 raspberrypi npm[494]: zigbee2mqtt:debug 2020-01-25 11:56:17: Saving state to file /opt/zigbee2mqtt/data/state.json

It seems to be working in terms of the backend that’s running on the pi, but it’s almost like there’s something with the radio link. (all the 4 devices and the dongle are withing 5 feet of each other).

5

If you public ‘status’ to zigbee2mqtt/Bedroom_bulb_1/get , do you get a response ?

6

I’ve looked around the docs for the status message formatting but couldn’t find anything when I send the raw “status” nothing happens except the message is added to that topic. Nothing in the logs.

7

Strange. You should get a status reply

image
image635×585 17.4 KB

8

Ok that helps as it shows something is not right with my zigbee2mqtt instance, thanks.
Gonna update to latest and see if I can figure out what’s wrong