Success with Sonoff zigbee bridge and zigbee binding

Yes I saw this cool feature. I tried 2 sensors (aqara temperature and wireless wall switch) but none of them is working. Will try the third category in a few days: door sensor.

What kind of AqaraTemp are you using? Can you send more details?

Itā€™s the same as yours : WSDCGQ11LM

And after pressing the button on it for 5 seconds you can see messages in the console log?

How to see this map , were did you find anything about it ?

After upgrade to tasmota v9.2.0 you can find it in ā€œMain menuā€.

Udklip

i did upgrade and didnt find anything thats why I asked :laughing: :+1:

SORRY after i did paste this in console : Backlog Weblog 3; so65 1; Module 75

Udklip

nice but ,now TCP port don`t start up any more ??

so i can chose to have map or TCP port 8888 working

Yes. TCP/8888 allows openHAB to communicate directly with the radio module inside the zbbridge. Since then tasmota is just a ā€œserial to TCPā€ proxy, it wonā€™t know anything about zigbee, and wonā€™t be able to map the zigbee network.

1 Like

Iā€™ve unpaired my sensor and started again.
Here is the log with INFO level:

Dec 19 22:12:20 zbbridge1 ESP-MQT: tele/zbbridge1/RESULT = {"ZbState":{"Status":21,"Message":"Pairing mode enabled"}}
Dec 19 22:12:20 zbbridge1 ESP-MQT: stat/zbbridge1/RESULT = {"ZbPermitJoin":"Done"}
Dec 19 22:12:31 zbbridge1 ESP-ZIG: {"ZbEZSPReceived":"23000001718184C0AA04008D150004"}
Dec 19 22:12:31 zbbridge1 ESP-ZIG: {"ZbEZSPReceived":"2400718184C0AA04008D150001000000"}
Dec 19 22:12:31 zbbridge1 ESP-MQT: tele/zbbridge1/RESULT = {"ZbState":{"Status":34,"IEEEAddr":"0x00158D0004AAC084","ShortAddr":"0x8171","ParentNetwork":"0x0000","Status":1,"Decision":0}}
Dec 19 22:12:32 zbbridge1 ESP-MQT: tele/zbbridge1/RESULT = {"ZbState":{"Status":30,"IEEEAddr":"0x00158D0004AAC084","ShortAddr":"0x8171","PowerSource":false,"ReceiveWhenIdle":false,"Security":false}}
Dec 19 22:12:32 zbbridge1 ESP-MQT: tele/zbbridge1/8171/SENSOR = {"ZbReceived":{"0x8171":{"Device":"0x8171","ModelId":"lumi.weather","AppVersion":5,"Endpoint":1,"LinkQuality":52}}}
Dec 19 22:12:33 zbbridge1 ESP-MQT: tele/zbbridge1/8171/SENSOR = {"ZbReceived":{"0x8171":{"Device":"0x8171","BatteryVoltage":3.04,"BatteryPercentage":100,"Temperature":31.45,"Humidity":59.92,"Pressure":1012,"SeaPressure":1012,"Endpoint":1,"LinkQuality":52}}}
Dec 19 22:12:33 zbbridge1 ESP-MQT: tele/SonoffRelay1/SENSOR = {"ZbReceived":{"SonoffRelay1":{"Device":"0x3DFB","Name":"SonoffRelay1","Power":0,"Endpoint":1,"LinkQuality":34}}}
Dec 19 22:12:33 zbbridge1 ESP-MQT: tele/zbbridge1/RESULT = {"ZbState":{"Status":32,"ActiveEndpoints":["0x01"]}}
Dec 19 22:12:34 zbbridge1 ESP-ZIG: Zigbee Devices Data saved in EEPROM (529 bytes)
Dec 19 22:12:36 zbbridge1 ESP-MQT: tele/zbbridge1/8171/SENSOR = {"ZbReceived":{"0x8171":{"Device":"0x8171","Manufacturer":"LUMI","ModelId":"lumi.weather","Endpoint":1,"LinkQuality":50}}}
Dec 19 22:12:36 zbbridge1 ESP-MQT: tele/zbbridge1/RESULT = {"ZbState":{"Status":33,"Device":"0x8171","Endpoint":"0x01","ProfileId":"0x0104","DeviceId":"0x0302","DeviceVersion":1,"InClusters":["0x0000","0x0003","0xFFFF","0x0402","0x0403","0x0405"],"OutClusters":["0x0000","0x0004","0xFFFF"]}}
Dec 19 22:12:37 zbbridge1 ESP-MQT: tele/zbbridge1/8171/SENSOR = {"ZbReceived":{"0x8171":{"Device":"0x8171","Temperature":31.49,"Humidity":56.2,"Pressure":1011,"PressureScale":-1,"PressureScaledValue":10118,"SeaPressure":1011,"Endpoint":1,"LinkQuality":60}}}
Dec 19 22:12:39 zbbridge1 ESP-ZIG: Zigbee Devices Data saved in EEPROM (533 bytes)
Dec 19 22:12:39 zbbridge1 ESP-ZIG: auto-bind `ZbBind {"Device":"0x8171","Endpoint":1,"Cluster":"0x0402"}`
Dec 19 22:12:40 zbbridge1 ESP-MQT: tele/zbbridge1/RESULT = {"ZbBind":{"Device":"0x8171","Status":0,"StatusMessage":"SUCCESS"}}
Dec 19 22:12:40 zbbridge1 ESP-ZIG: auto-bind `ZbBind {"Device":"0x8171","Endpoint":1,"Cluster":"0x0403"}`
Dec 19 22:12:41 zbbridge1 ESP-MQT: tele/zbbridge1/8171/SENSOR = {"ZbReceived":{"0x8171":{"Device":"0x8171","Temperature":31.49,"Humidity":53.36,"Pressure":1011,"PressureScale":-1,"PressureScaledValue":10118,"SeaPressure":1011,"Endpoint":1,"LinkQuality":60}}}
Dec 19 22:12:42 zbbridge1 ESP-ZIG: auto-bind `ZbBind {"Device":"0x8171","Endpoint":1,"Cluster":"0x0405"}`
Dec 19 22:12:44 zbbridge1 ESP-MQT: tele/zbbridge1/RESULT = {"ZbBind":{"Device":"0x8171","Status":0,"StatusMessage":"SUCCESS"}}
Dec 19 22:12:44 zbbridge1 ESP-ZIG: auto-bind `ZbSend {"Device":"0x8171","Config":{"Temperature":{"MinInterval":30,"MaxInterval":3600,"ReportableChange":0.2}}}`
Dec 19 22:12:45 zbbridge1 ESP-MQT: tele/zbbridge1/8171/SENSOR = {"ZbReceived":{"0x8171":{"Device":"0x8171","Temperature":31.48,"Humidity":50.28,"Pressure":1011,"PressureScale":-1,"PressureScaledValue":10118,"SeaPressure":1011,"Endpoint":1,"LinkQuality":63}}}
Dec 19 22:12:47 zbbridge1 ESP-ZIG: auto-bind `ZbSend {"Device":"0x8171","Config":{"Pressure":{"MinInterval":30,"MaxInterval":3600,"ReportableChange":1}}}`
Dec 19 22:12:47 zbbridge1 ESP-MQT: tele/zbbridge1/RESULT = {"ZbResponse":{"Device":"0x8171","Command":"0402!06","Status":130,"StatusMessage":"UNSUP_GENERAL_COMMAND","Endpoint":1,"LinkQuality":63}}
Dec 19 22:12:47 zbbridge1 ESP-MQT: tele/zbbridge1/RESULT = {"ZbResponse":{"Device":"0x8171","Command":"0403!06","Status":130,"StatusMessage":"UNSUP_GENERAL_COMMAND","Endpoint":1,"LinkQuality":63}}
Dec 19 22:12:48 zbbridge1 ESP-MQT: tele/zbbridge1/8171/SENSOR = {"ZbReceived":{"0x8171":{"Device":"0x8171","Temperature":31.44,"Humidity":48.39,"Pressure":1011,"PressureScale":-1,"PressureScaledValue":10119,"SeaPressure":1011,"Endpoint":1,"LinkQuality":65}}}
Dec 19 22:12:48 zbbridge1 ESP-ZIG: auto-bind `ZbSend {"Device":"0x8171","Config":{"Humidity":{"MinInterval":30,"MaxInterval":3600,"ReportableChange":1}}}`
Dec 19 22:12:52 zbbridge1 ESP-MQT: tele/zbbridge1/8171/SENSOR = {"ZbReceived":{"0x8171":{"Device":"0x8171","Temperature":31.45,"Humidity":47.5,"Pressure":1011,"PressureScale":-1,"PressureScaledValue":10119,"SeaPressure":1011,"Endpoint":1,"LinkQuality":65}}}
Dec 19 22:12:54 zbbridge1 ESP-MQT: tele/zbbridge1/RESULT = {"ZbResponse":{"Device":"0x8171","Command":"0405!06","Status":130,"StatusMessage":"UNSUP_GENERAL_COMMAND","Endpoint":1,"LinkQuality":65}}
Dec 19 22:12:55 zbbridge1 ESP-MQT: tele/zbbridge1/8171/SENSOR = {"ZbReceived":{"0x8171":{"Device":"0x8171","Temperature":31.39,"Humidity":47.02,"Pressure":1011,"PressureScale":-1,"PressureScaledValue":10119,"SeaPressure":1011,"Endpoint":1,"LinkQuality":68}}}
Dec 19 22:12:58 zbbridge1 ESP-MQT: tele/zbbridge1/8171/SENSOR = {"ZbReceived":{"0x8171":{"Device":"0x8171","Temperature":31.34,"Humidity":46.58,"Pressure":1011,"PressureScale":-1,"PressureScaledValue":10118,"SeaPressure":1011,"Endpoint":1,"LinkQuality":68}}}

ZbEZSPReceived shows zigbee data is received from the radio module.

This is what I understand and I have no idea why it doesnā€™t work this way with my aqara sensors. The aqara bridge is not used in your setup?

How have you enabled info log level? First I thought the bridge is broken but then I expected that the Sonoff button also should not work should it?

No

Through the web menu ā€œConfigure Loggingā€ or through the consol with ā€œWeblog 4ā€

Indeed. Do you have another zigbee bridge ? You could try to turn it off when pairing.

Have several hue bridges active/online - so I should power off them?

Maybe your aqara device was paired to one of them and wants to reconnect.

Hm it was connected to the aqara bridge but this is powered of! Or is there something I have to do to unpair from the old bridge?

Donā€™t know if this is relevant, but i used touchlink to reset some bulbs before i could pair then to anew.

With the aqara sensors holding the pairing button for longer than your would think reasonable worked for me (with another coordinator though)

I have some success while connecting the Aqara Sensors to the bridge. It seems that my nearly activated Hue bridge is blocking the connection to the sonoff bridge.

So now I have successful connected the Aqara button and also a Osram Switch to it. But now I have the next challenge which I cannot resolve by myself after lot of investigation: Iā€™d like to control the Osram Switch over MQTT from Openhab. My problem is, that all connected sensors in the console of the tasmota bridge only show ā€œtele/tasmota/sensorā€. There is no difference between button or switch. how can i differantiate them in the things configuration?

Good news !
Thatā€™s the expected behavior, the device can be identified with the json payload.
You can use options to have a different topic per device:

and then configure your items and things like this:

Thanksā€¦with several threads and tries I am now able to check a sensor completely. Next step is the 2 way communication with a switch.

I handled it now completely in PaperUI with Regex and JSONPATH Transformation.

Sorry but I am still new here.
I have a Sonoff Zigbee Bridge with Tasmota and fail at the two points mentioned:

I tried this command
socat -dd pty,link=/dev/ttyzbbridge,raw,user-late=openhab,group-late=dialout tcp:192.168.1.100:8888

but I have still ā€œpermission deniedā€
socat[30212] E symlink(ā€œ/dev/pts/1ā€, ā€œ/dev/ttyzbbridgeā€): Permission denied

Any ideas?

and what do I have to set in the Serial Binding?

Update:

Hey have solved my problem and it goes even a little better with the help of this post you can set up the connection so that it is automatically established at system startup (Auto reconnect is easy by restart socat service when connection lost)

Hello,

Glad you made it work.
OpenHAB 3 is now released, and should support RFC2217 URI for Serial Binding.
It means you donā€™t need socat anymore, and you can simply use rfc2217://192.168.1.100:8888 as port for the serial binding configration.

I have not testedā€¦ has anybody feedback on this new feature ?

Oh damn I have OH3 in use unfortunately I have found nothing. But thanks for the tip will test that later.