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

Share your Projects!
1669

If you think you got an issue, I suggest you open one in GitHub. A post here is not actionable. My two cents

1670

Well if there is an issue than @vijaykbhatia should open it because he‘s able to provide more details. I was just replying to his posting.

1671

Sorry all, I didn’t think there is an issue with the add on likely just my set up. Was unsure on best practice. Will tinker some more to figure it out before opening issue in github. Thanks for all the advice.

Looks like someone beat me to it anyway. Can’t beleive I didn’t see this
https://github.com/danielwelch/hassio-zigbee2mqtt/issues/237

1 Like
1672

Now that you mention it, It is true that my lights do sometimes loose sync with the controller. I do remember sometimes switching on the light on the front and I’m noticing the fronted will not display the current state. I half one IKEA bulb and a led stripe by OSRAM.

1673

Is there anyone who is using zigbee2mqtt with either rasbian buster and/or a raspberrypi 4 successfully? I have trouble getting it to work after moving from my pi3 to my pi4 for no obvious reasons and I am trying to figure out if this is a general problem or maybe just my faulty pi4?

1674

Where are your logs???

1675

Koenkk saved the day, I needed an extensioncord and also needed to deactive the network scans. Now it works properly.

1 Like
1676

Connected my symfonisk remote from the dev version but any thoughts for an automation for controlling the volume?

1677

I migrated from using Sonoff sockets with Tasmota to zigbee2mqtt with Innr SP120 sockets. However, the sockets do not work reliably. If I switch them on/off with home assistant, in some rare cases, the sockets do not turn on. I have to press on and off multiple times until they eventually turn on or off.

I guess there is some issue with the signal strenght. However, I expect home assistant to reliably show the status of the sockets in case they did not switch on properly. But the button / slider stays on even if the socket did not turn on.

Anybody having similar issues with the status in home assistant together with zigbee2mqtt?

1678

Hi all,

I run HassIO with the Zigbee2MQTT add-on. Currently it is version 1.6.0.

I used to have logging messages. Not sure when they disappeared but my log entries from the add-on page are blank.

I noted that in the configuration there is no line for log-level and I’m assuming this is because info is the default (???)

Anyway, I tried changing the configuration to include the “log-level”: info configuration under the advanced section, but the text stays red and won’t allow me to save it.

How can I get the logging reinstated as I have some new devices I want to add in to Zigbee2mqtt?

Thanks,
Pete

1679

There is a zigbee2mqtt package that let you change loglevel from the HA frontend.

1680

I did not have that issue yet, but maybe reinstalling the addon is a good idea.

1681

Do you see any logging at all, for example when restarting the addon?

I’ve been experiencing some delay when logs are loaded, did you just try and wait some more to see if it shows up?

1683

Thanks francisp. I’ve seen the configuration for changing the log level and I might end up playing with that. It’s strange though why my logging has just stopped. Was hoping to work that out.

Thanks h4nc. I upgraded to the latest version, but it did not help. BTW the co-ordinator I bought from you is awesome. It’s working really well.

No logging at all for the plug in. Unfortunately, I don’t know when it stopped logging as it just works and I haven’t added any devices for some time, so haven’t looked at it.

1 Like
1684

Just an update. … a full restart of my server resolved the logging problem

1 Like
1685

A post was split to a new topic: Node Red consuming lots of CPU

1686

v1.7.0 was released today :partying_face:

1687

I installed it this morning. Had no problems :slight_smile:

1688

I currently have 1 coordinator (CC2530):and a couple of WEMO globes & Xiaomi which which work fine until I reboot Hassio. When I reboot Hassio I loose all the Zigbee paired devices. This happened when I went from 1.4 to 1.6 & 1.7. Currently running Home Assistant 0.101.3

These are my setting in zigbee2mqtt;

“data_path”: “/share/zigbee2mqtt”,
“devices”: “devices.yaml”,
“groups”: “groups.yaml”,
“homeassistant”: true,
“permit_join”: false,
“mqtt”: {
“base_topic”: “zigbee2mqtt”,
“server”: “mqtt://core-mosquitto”,
“user”: “myusername”,
“password”: “mypassword”
},
“serial”: {
“disable_led”: true,
“port”: “/dev/ttyACM0”
},
“advanced”: {
“pan_id”: 6754,
“channel”: 11,
“network_key”: [],
“availability_blacklist”: []
},
“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 after the reboot the WEMO lamp is unknown.

zigbee2mqtt:info 2019-11-19T01:18:43: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{“type”:“entity_not_found”,“message”:{“friendly_name”:“0x94103ef6bf442bc7”}}’
zigbee2mqtt:error 2019-11-19T01:18:43: Entity ‘0x94103ef6bf442bc7’ is unknown

1689

Hey guys, maybe it is a config error by my side, but i tryed a lot.

i have Trouble with the mqtt server.
I can´t log in with the zigbee2mqtt addon.

log zigbee2mqtt

./run.sh: line 16: [Info] Configuration backup found in /share/zigbee2mqtt/.configuration.yaml.bk. Skipping config backup.: No such file or directory
[Info] Socat is DISABLED and not started
2019-11-22T15:43:37: PM2 log: Launching in no daemon mode
2019-11-22T15:43:37: PM2 log: App [npm:0] starting in -fork mode-
2019-11-22T15:43:37: PM2 log: App [npm:0] online

[email protected] start /zigbee2mqtt-1.7.1
node index.js
zigbee2mqtt:info 2019-11-22T14:43:43: Logging to directory: ‘/share/zigbee2mqtt/log/2019-11-22.15-43-41’
zigbee2mqtt:info 2019-11-22T14:43:43: Starting zigbee2mqtt version 1.7.1 (commit #unknown)
zigbee2mqtt:info 2019-11-22T14:43:43: Starting zigbee-herdsman…
zigbee2mqtt:info 2019-11-22T14:43:44: zigbee-herdsman started
zigbee2mqtt:info 2019-11-22T14:43:44: Coordinator firmware version: ‘{“type”:“zStack12”,“meta”:{“transportrev”:2,“product”:0,“majorrel”:2,“minorrel”:6,“maintrel”:3,“revision”:20190608}}’
zigbee2mqtt:info 2019-11-22T14:43:44: Currently 0 devices are joined:
zigbee2mqtt:info 2019-11-22T14:43:44: Zigbee: disabling joining new devices.
zigbee2mqtt:info 2019-11-22T14:43:44: Connecting to MQTT server at mqtt://192.168.178.52:1883
events.js:174
throw er; // Unhandled ‘error’ event
^
Error: Connection refused: Not authorized
at MqttClient._handleConnack (/zigbee2mqtt-1.7.1/node_modules/mqtt/lib/client.js:1076:15)
at MqttClient._handlePacket (/zigbee2mqtt-1.7.1/node_modules/mqtt/lib/client.js:365:12)
at work (/zigbee2mqtt-1.7.1/node_modules/mqtt/lib/client.js:283:12)
at Writable.writable._write (/zigbee2mqtt-1.7.1/node_modules/mqtt/lib/client.js:294:5)
at doWrite (/zigbee2mqtt-1.7.1/node_modules/readable-stream/lib/_stream_writable.js:428:64)
at writeOrBuffer (/zigbee2mqtt-1.7.1/node_modules/readable-stream/lib/_stream_writable.js:417:5)
at Writable.write (/zigbee2mqtt-1.7.1/node_modules/readable-stream/lib/_stream_writable.js:334:11)
at Socket.ondata (_stream_readable.js:709:20)
at Socket.emit (events.js:198:13)
at addChunk (_stream_readable.js:288:12)
Emitted ‘error’ event at:
at MqttClient._handleConnack (/zigbee2mqtt-1.7.1/node_modules/mqtt/lib/client.js:1078:10)
at MqttClient._handlePacket (/zigbee2mqtt-1.7.1/node_modules/mqtt/lib/client.js:365:12)
[… lines matching original stack trace …]
at addChunk (_stream_readable.js:288:12)
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.

log MQTT Mosquito
1574433963: Socket error on client , disconnecting.
1574433972: New connection from 172.30.32.1 on port 1883.
1574433972: Socket error on client , disconnecting.

Mosquitto config:

{
“logins”: ,
“anonymous”: true,
“customize”: {
“active”: false,
“folder”: “mosquitto”
},
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”,
“require_certificate”: false
}

addon config:
{
“data_path”: “/share/zigbee2mqtt”,
“devices”: “devices.yaml”,
“groups”: “groups.yaml”,
“homeassistant”: true,
“permit_join”: false,
“mqtt”: {
“base_topic”: “zigbee2mqtt”,
“server”: “mqtt://192.168.178.52:1883”,
“user”: “myuser”,
“password”: “mypw”
},
“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”: {},
“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
}
}

May be someone has a good idea.
thanks a lot.