Zigbee2MQTT not working anymore Topic is solved

[Hesitated]

Hi,

Yesterday I thought that only adding a new motionsensor was not working, today I discovered that Zigbee2MQTT isn't working at all..

My config:

Code: Select all

homeassistant: false
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://localhost'
  user: sameUser
  password: samePassword
serial:
  port: /dev/ttyACM0
devices:
  '0x00158d0003f11c5e':
    friendly_name: TempSensorWoonkamer
  '0x00158d0002f82c3c':
    friendly_name: Switch1
  '0x00158d00034925f0':
    friendly_name: Switch2
  '0x00158d00033efd25':
    friendly_name: Switch3
  '0x00158d0004184f53':
    friendly_name: TempSensorStudeerkamer
  '0x00158d00045195c5':
    friendly_name: MotionSensor1
  '0x00158d00044943fa':
    friendly_name: MotionSensor2
  '0x7cb03eaa00a7759c':
    friendly_name: '0x7cb03eaa00a7759c'
  '0x00158d00044d60fc':
    friendly_name: MotionSensor3

Code: Select all

systemctl status zigbee2mqtt.service

returns:

zigbee2mqtt.service - zigbee2mqtt
Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2020-04-05 13:14:48 CEST; 53min ago
Main PID: 25795 (npm)
Tasks: 23 (limit: 4915)
CGroup: /system.slice/zigbee2mqtt.service
├─25795 npm
├─25809 sh -c node index.js
└─25810 node index.js

Apr 05 13:51:41 domoticz npm[25795]: zigbee2mqtt:info 2020-04-05 13:51:41: MQTT publish: topic 'zig

Code: Select all

sudo journalctl -u zigbee2mqtt.service -f

returns:

-- Logs begin at Sat 2020-04-04 21:31:18 CEST. --
Apr 05 14:09:35 domoticz npm[25795]: zigbee2mqtt:info 2020-04-05 14:09:35: MQTT publish: topic 'zigbee2mqtt/MotionSensor2', payload '{"battery":100,"voltage":3005,"illuminance":10,"illuminance_lux":10,"linkquality":15,"occupancy":false}'
Apr 05 14:10:22 domoticz npm[25795]: zigbee2mqtt:info 2020-04-05 14:10:22: MQTT publish: topic 'zigbee2mqtt/TempSensorWoonkamer', payload '{"battery":86,"voltage":2975,"temperature":19.57,"humidity":38.29,"pressure":1014.1,"linkquality":15}'
Apr 05 14:13:35 domoticz npm[25795]: zigbee2mqtt:info 2020-04-05 14:13:35: MQTT publish: topic 'zigbee2mqtt/MotionSensor3', payload '{"battery":100,"voltage":3025,"illuminance":23,"illuminance_lux":23,"linkquality":2,"occupancy":true}'

So this looks good, but running

Code: Select all

mosquitto_sub -d -u sameUser -P samePassword -t /#

only shows:

Client mosq-Vbwr5gEfnmyqEJcaQE sending CONNECT
Client mosq-Vbwr5gEfnmyqEJcaQE received CONNACK (0)
Client mosq-Vbwr5gEfnmyqEJcaQE sending SUBSCRIBE (Mid: 1, Topic: /#, QoS: 0, Options: 0x00)
Client mosq-Vbwr5gEfnmyqEJcaQE received SUBACK
Subscribed (mid: 1): 0
Client mosq-Vbwr5gEfnmyqEJcaQE sending PINGREQ
Client mosq-Vbwr5gEfnmyqEJcaQE received PINGRESP

And therefore Domoticz receives nothing too...

However if I send this:

Code: Select all

mosquitto_pub -d -u sameUser -P samePassword -t /zigbee2mqtt/MotionSensor3 -m "Test message"

It gets send and received:

Client mosq-Jjra6Mz97fdXCC3ozf received PUBLISH (d0, q0, r0, m0, '/zigbee2mqtt/MotionSensor3', ...
12 bytes))
Test message

Where did I mess up?

[HFman]

This makes 2 of us... suddenly after 3 weeks.. stopped.
excatly same case, did you figure it out ?

[HFman]

mmm working agian. Before didn't have this problem. But seems something to do with starting squenze.
I stopped domoticz and restarted. then it works fine again.
But from cold boot not...

[Hesitated]

I stopped domoticz and restarted. then it works fine again.
But from cold boot not...

Thnxs for sharing!

Never thought of restarting Domoticz seperately...

Strange though that mosquitto_sub does show the messages either:

Code: Select all

mosquitto_sub -d -t $SYS/#

[Dave21w]

Gentlemen, you have just solved my pairing issue that i have just posted about, my devices that were already paired were functioning normally and early today I had paired some other devices but could not pair the Xiaomi Door/Window contact, tried everything (well obviously not) apart from restarting the Domoticz service after which it paired straigh away - very strange, especially as I could see the device in the logs.

Thanks
Dave