Python Plugin: Zigbee2Mqtt Topic is solved

[MarFan]

No Zigbee Hardware Device at all ... any debug ideas anyone??

Do you have messages regarding the python library installed correctly (or missing).

[upwindanderl]

No Zigbee Hardware Device at all ... any debug ideas anyone??

Do you have messages regarding the python library installed correctly (or missing).

How can i figure this out
I only did the python library install like this way: Installation

[Dnpwwo]

@upwindanderl,

Go to the 'About' page in the Web UI or look at the Domoticz log during startup. If Domoticz finds a version it can use it will report it in both of those places. If Domoticz reports a Python version then that is not the problem here.

If the Python version is not reported then have a look at this: https://www.domoticz.com/wiki/Using_Python_plugins

[MarFan]

Good news, the latest Zigbee2Mqtt Main version (0.1.7) contains the include_device_information setting.
So DEV is not needed anymore

[prelude]

I try to take Zigbee2Mqtt plugin on the use but something is wrong and i cannot figure out what so maybe someone can help me a bit.

Im running domosticz on docker as well as rabbitmq and zigbee2mqtt. Currently seems that zigbee2mqtt talks with a rabitmq (i see xiaomi temp sensor messages on log files) and also i see from Domosticz log files (zigbee2mqtt) Heartbeating...(zigbee2mqtt) MqttClient::Ping seems to work fine.
But i do not get any devise to visible on domosticz device page.

Logs and configs:

zigbee2mqtt configuration.yaml

Code: Select all

homeassistant: false
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://rabbitmq'
  include_device_information: true
serial:
  port: /dev/ttyACM0
devices:
  '0x00158d0002320bef':
    friendly_name: '0x00158d0002320bef'
    retain: false

domosticz setup:



Domosticz log:

Code: Select all

2018-10-16 22:04:02.658 (zigbee2mqtt) Heartbeating...
2018-10-16 22:04:02.658 (zigbee2mqtt) MqttClient::Ping
2018-10-16 22:04:12.681 (zigbee2mqtt) Heartbeating...
2018-10-16 22:04:12.681 (zigbee2mqtt) MqttClient::Ping

zigbee2mqtt log:

Code: Select all

zigbee2mqtt:info 2018-10-16 19:06:19 MQTT publish, topic: 'zigbee2mqtt/0x00158d0002320bef', payload: '{"humidity":92.88,"linkquality":86,"pressure":1015,"device":{"ieeeAddr":"0x00158d0002320bef","friendlyName":"0x00158d0002320bef","type":"EndDevice","nwkAddr":23243,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.weather","status":"online"}}'

Any idea what i should to check first?

[upwindanderl]

@upwindanderl,

Go to the 'About' page in the Web UI or look at the Domoticz log during startup. If Domoticz finds a version it can use it will report it in both of those places. If Domoticz reports a Python version then that is not the problem here.

If the Python version is not reported then have a look at this: https://www.domoticz.com/wiki/Using_Python_plugins

@Dnpwwo THANK YOU SO SO MUCH !!!!!
Exactly this was my problem at all, and your wiki link helped out.
In the end everything like in the wiki mentioned was ok, but then i tried the python3-DEV and now i got the ZIGBEE2MQTT Hardware thing
THANKS !!!!

[gerbenvanasselt]

I am experiencing the same as Prelude. Does anyone have any suggestions?

Verstuurd vanaf mijn ONEPLUS A6003 met Tapatalk

[MikeF]

Have you ticked 'Accept new Hardware Devices Allow for 5 Minutes' in Settings?

[EddyG]

It works perfectly, but I have a few questions/remarks.
The WSDCGQ11LM (Xiaomi Aqara temperature, humidity and pressure sensor) is setup as device "Pressure", it should be setup as device "Barometer".
Request: from the same device there should be a possibility to setup Temp and Hum as 1 device.
Only the "Cube" has a signal strenght in Domoticz.
It would be nice it state and linkquality of router could be vissible as custom device in Domoticz.

[MiloshCZ]

@EddyG: I have allready reported issue about Signal Quality: https://github.com/stas-demydiuk/domoti ... n/issues/5

[gerbenvanasselt]

Hey MikeF, yes I tried allow option in setting. But nothing happens. I am trying it with tradfri bulbs. They are listed in the configuration.yaml and domoticz says it is reading the devicelist. But there no devices available.

Anyone has any clue's? Would be very helpful.

Thanks

Have you ticked 'Accept new Hardware Devices Allow for 5 Minutes' in Settings?

Verstuurd vanaf mijn ONEPLUS A6003 met Tapatalk

[misko903]

Maybe a Nuki lock support?
https://nuki.io/en/shop/nuki-bridge/

works on Zigbee too...

[upwindanderl]

Wooohoo! I love this plugin... so much easier now to handle the aqara devices!
Thanks for the help.

How is it now with some devices which are already in the zigbee list but not in the plugin?!
I'm definitly someone who would give some donation or at least two three four beers (paypal...) if there would be some work on

For me it would be fine with:
OSRAM SMART+ (devicelist model: AB3257001NJ)
and the
Xiaomi Aqara wireless switch (devicelist model: WXKG11LM)

[prelude]

Have you ticked 'Accept new Hardware Devices Allow for 5 Minutes' in Settings?

I try it and it did something but still no devices on domosticz:

Code: Select all

2018-10-17 23:08:50.781 (zigbee2mqtt) MqttClient::Ping
2018-10-17 23:08:53.357 Status: New sensors allowed for 5 minutes...
2018-10-17 23:09:00.806 (zigbee2mqtt) Heartbeating...
2018-10-17 23:09:00.806 (zigbee2mqtt) MqttClient::Ping
2018-10-17 23:09:10.781 (zigbee2mqtt) Heartbeating...
2018-10-17 23:09:10.781 (zigbee2mqtt) MqttClient::Ping
2018-10-17 23:09:20.803 (zigbee2mqtt) Heartbeating...
2018-10-17 23:09:20.804 (zigbee2mqtt) MqttClient::Ping
2018-10-17 23:09:30.774 (zigbee2mqtt) Heartbeating...
2018-10-17 23:09:30.774 (zigbee2mqtt) MqttClient::Ping
2018-10-17 23:09:40.795 (zigbee2mqtt) Heartbeating...
2018-10-17 23:09:40.795 (zigbee2mqtt) MqttClient::Ping
2018-10-17 23:09:50.814 (zigbee2mqtt) Heartbeating...
2018-10-17 23:09:50.814 (zigbee2mqtt) MqttClient::Ping
2018-10-17 23:10:00.783 (zigbee2mqtt) Heartbeating...
2018-10-17 23:10:00.784 (zigbee2mqtt) MqttClient::Ping
2018-10-17 23:10:10.806 (zigbee2mqtt) Heartbeating...
2018-10-17 23:10:10.806 (zigbee2mqtt) MqttClient::Ping
2018-10-17 23:10:15.472 (zigbee2mqtt) MQTT message: zigbee2mqtt/bridge/log {'type': 'pairing', 'message': 'device incoming'}
2018-10-17 23:10:20.832 (zigbee2mqtt) Heartbeating...

and bit better log from dockers:

Code: Select all

zigbee2mqtt    |   zigbee2mqtt:info 2018-10-17 20:10:15 Device incoming...
zigbee2mqtt    |   zigbee2mqtt:info 2018-10-17 20:10:15 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"device incoming"}'
domoticz_1     | 2018-10-17 23:10:15.472  (zigbee2mqtt) MQTT message: zigbee2mqtt/bridge/log {'type': 'pairing', 'message': 'device incoming'}
zigbee2mqtt    |   zigbee2mqtt:info 2018-10-17 20:10:15 MQTT publish, topic: 'zigbee2mqtt/0x00158d0002320bef', payload: '{"pressure":1012,"linkquality":52,"temperature":25.46,"device":{"ieeeAddr":"0x00158d0002320bef","friendlyName":"0x00158d0002320bef","type":"EndDevice","nwkAddr":59898,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.weather","status":"online"}}'
zigbee2mqtt    |   zigbee2mqtt:info 2018-10-17 20:10:15 MQTT publish, topic: 'zigbee2mqtt/0x00158d0002320bef', payload: '{"temperature":25.46,"linkquality":52,"humidity":48.39,"device":{"ieeeAddr":"0x00158d0002320bef","friendlyName":"0x00158d0002320bef","type":"EndDevice","nwkAddr":59898,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.weather","status":"online"}}'
zigbee2mqtt    |   zigbee2mqtt:info 2018-10-17 20:10:15 MQTT publish, topic: 'zigbee2mqtt/0x00158d0002320bef', payload: '{"humidity":48.39,"linkquality":52,"pressure":1012,"device":{"ieeeAddr":"0x00158d0002320bef","friendlyName":"0x00158d0002320bef","type":"EndDevice","nwkAddr":59898,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.weather","status":"online"}}'

[MarFan]

Maybe a Nuki lock support?
https://nuki.io/en/shop/nuki-bridge/

works on Zigbee too...

Before it is posible to have this in the plugin, it must have support in the Ziggbee2MQTT stick.
So please start first here https://github.com/Koenkk/zigbee2mqtt/w ... ew-devices

[MarFan]

I try it and it did something but still no devices on domosticz:

Did you restart Domoticz (sudo service domoticz restart) ?
I sometimes also have the behaviour that I have to restart first before a new device is added.

[prelude]

Did you restart Domoticz (sudo service domoticz restart) ?
I sometimes also have the behaviour that I have to restart first before a new device is added.

Yep, no help from there.

[gerbenvanasselt]

Did you restart Domoticz (sudo service domoticz restart) ?
I sometimes also have the behaviour that I have to restart first before a new device is added.

Yep, no help from there.

I am going to try this solution with node-red. Because the python plugin is not working yet. Hope it will in the nearby future.



https://diyprojects.io/test-zigbee2mqtt ... 8yXKk9Nfqs



Verstuurd vanaf mijn ONEPLUS A6003 met Tapatalk

[dextm80]

https://diyprojects.io/test-zigbee2mqtt ... 8yXKk9Nfqs



Verstuurd vanaf mijn ONEPLUS A6003 met Tapatalk

Difference about your diy and original Xiaomi Gateway? It s costs 20 euros

[gerbenvanasselt]

https://diyprojects.io/test-zigbee2mqtt ... 8yXKk9Nfqs



Verstuurd vanaf mijn ONEPLUS A6003 met Tapatalk

Difference about your diy and original Xiaomi Gateway? It s costs 20 euros

But what, if you don't want to put you're data on a Chinese server? As far as I know you can not control the sensors without using the Xiaomi server. All traffic goes through the're servers.

Verstuurd vanaf mijn ONEPLUS A6003 met Tapatalk


!Update!
Found out that I had an old version of the plug-in installed. Pulled the update from Git and now I can control my tradfri dimmed bulb. I Hope the others Tradfri devices will be supported as well.

Thanks @Stan for this amazing plugin.