Zigbee binding

Tags: #<Tag:0x00007fe054d2a398> #<Tag:0x00007fe054d2a1e0>

(Kim Andersen) #1907

I believe @chris already know about the difficulties with the xiaomi devices. There are a few topics about them. Problem is, they´re not plain zigbee. And I doubt Chris can do anything about it.

(stephan) #1908

I read that - that’s why I was so surprised that the binding explicitely offers that adding of xiaomi devices:

Perhaps other devices are also usable…

(Marcin O) #1909

Could somebody support me, how to set up aqara wireless wall switch? It is discovered as a thing, but it is not working.


(Kim Andersen) #1910

Some may work fine, others dont. The window/door sensor is one I havn´t been able to get to work.

(Jared Frank) #1911

Hey Chris - whenever you get back from your vacation - I just wanted to say thank you - the active power polling has been working in the newest library release. I did want to check with you on the polling interval though. Currently its only updating about once per minute. Is there somewhere I can set that to be more frequent as it was when it was working a few months back? Thanks again for all of your efforts!

(Thomas Weißschuh) #1912

This PR should make it work: https://github.com/openhab/org.openhab.binding.zigbee/pull/346
(It does for me)

(Thomas Weißschuh) #1913

Do yours have the modelId lumi.sensor_magnet.aq2 and hardwareVersion 2?
This one worked out of the box for me.

(Kim Andersen) #1914

I have 9 of these sensors, and have not been able to add it to a zigbee network:

Which one did you manage to add?

(Thomas Weißschuh) #1915


(Kim Andersen) #1916

Ahh okay, thanks for the information.

(Jared Frank) #1917

Has anyone else noticed their color bulbs going to an “UNDEF” state in the most recent version of the code? I’ll work on getting some debug code but I’m hoping this maybe obvious enough as I have never seen an UNDEF state before - only null. Items do this constantly and seem to go to and from the state without any interaction - I’m dead asleep at the time block I pulled this log from.

Edit: logs uploaded. You can see the channel converter setting it to UNDEF.

2019-01-31 17:13:26.011 [DEBUG] [converter.ZigBeeBaseChannelConverter] - 8418260000092447: Channel zigbee:device:86496f67:8418260000092447:8418260000092447_3_color updated to UNDEF


2019-01-31 03:39:15.227 [vent.ItemStateChangedEvent] - raw_TV_CC changed from 0,0,0 to UNDEF
2019-01-31 03:39:17.306 [vent.ItemStateChangedEvent] - raw_TV_CC changed from UNDEF to 0,0,0
2019-01-31 03:40:58.228 [vent.ItemStateChangedEvent] - raw_Dine1_CC changed from 0,0,0 to UNDEF
2019-01-31 03:41:01.185 [vent.ItemStateChangedEvent] - raw_Dine1_CC changed from UNDEF to 0,0,0
2019-01-31 03:41:57.221 [vent.ItemStateChangedEvent] - raw_Dine3_CC changed from 0,0,0 to UNDEF
2019-01-31 03:42:38.743 [vent.ItemStateChangedEvent] - raw_Dine3_CC changed from UNDEF to 0,0,0
2019-01-31 03:43:00.454 [vent.ItemStateChangedEvent] - raw_Desk2_CC changed from 0,0,0 to UNDEF
2019-01-31 03:43:20.079 [vent.ItemStateChangedEvent] - raw_Entry_CC changed from 0,0,0 to UNDEF
2019-01-31 03:43:52.149 [vent.ItemStateChangedEvent] - raw_Desk2_CC changed from UNDEF to 0,0,0
2019-01-31 03:44:08.144 [vent.ItemStateChangedEvent] - raw_Entry_CC changed from UNDEF to 0,0,0
2019-01-31 03:44:09.205 [vent.ItemStateChangedEvent] - raw_Dine2_CC changed from 0,0,0 to UNDEF
2019-01-31 03:44:39.002 [vent.ItemStateChangedEvent] - raw_Dine2_CC changed from UNDEF to 0,0,0
2019-01-31 03:44:42.069 [vent.ItemStateChangedEvent] - raw_Desk1_CC changed from 0,0,0 to UNDEF
2019-01-31 03:45:32.841 [vent.ItemStateChangedEvent] - raw_Desk1_CC changed from UNDEF to 0,0,0

(stephan) #1918

Hi Thomas,
I have the same version as yours.
I got them only with a chinese manual. So I tried pressing the button quite unregularly and after some time for one out of three devices a switch channel was discovered but it does not show any reaction dependent on the magnet.
Could you provide a short “manual” how you got them working:-)

(Thomas Weißschuh) #1919

I did nothing special.
Press the reset button, pair it via the UI.
Then wait for some time until discovery is complete. (May be up to 10 minutes)

(stephan) #1920

How long did you press the button and how often?
Which channels were detected?

(Thomas Weißschuh) #1921

Once for about 3 seconds. As indicated in the manual:
(Bottom of page two)

How long did you press the button and how often?

Only one: zigbee:device:ZigbeeCoord2:XXXXXXXXXXXXXX_1_switch

(Hans) #1922

I would also hook up with this question. Any one set up this device correclty?

(Hans) #1923

did anyone get the following device correctly set up?

My channels seems to be correclty set up, but the channel “occupancy” is never changed, doesnt matter if someone is in the same room or not?

(Lucky) #1924

Add a DateTime item and a rule when it’s triggered so you know if it’s been triggered at all. If the DateTime item has changed at all, then you know that the PIR is working. Most PIR sensors have a sleep time so you probably need to configure that.

(Ted Correll) #1925

Hi all. I’m new to Zigbee, and when I was researching what devices to get, I missed the supported devices section. I bought a couple of Centralite temperature + humidity sensors. The temperature is being reported, but humidity isn’t showing up at all. There are also fields for “Battery Voltage” and “Battery Alarm”. Both of which I believe are being properly displayed. I have removed and re-added the sensors, to see if that would get either to show the humidity. Is there interest in working towards making them supported? Any help would be great! I have the event logs from when I re-added the sensors, if that would be useful.

(Chris Jackson) #1926

Did you get this working? Looking at the XML it looks like a reasonably standard switch/level control server.

If it’s not working, can you provide a debug log - depending on what that shows, a sniffer log might help, but I don’t think it is needed here…