Unless I am mistaken the WXKG11LM is an Aqara button.
Please see:
Also these buttons worked fine in 86.4, returning bool.true when the button was pressed.
thanks
thats the one i have it does also have aqara printed on it the closest thing i can see in the logs is:
2019-03-03 19:09:42 DEBUG (MainThread) [zigpy.zcl] [0x9359:1:0x0006] ZCL request 0x000a: [[<Attribute attrid=0 value=<zigpy.zcl.foundation.TypeValue object at 0xb0b28d50>>, <Attribute attrid=0 value=<zigpy.zcl.foundation.TypeValue object at 0xb28617b0>>]]
2019-03-03 19:09:42 DEBUG (MainThread) [zigpy.zcl] [0x9359:1:0x0006] Attribute report received: 0=Bool.false, 0=Bool.true
You said the pairing button was a pin holeā¦ none of the aqara devices are like that. Only the Mija devices. That model should be an aqara buttonā¦
Mine has that small and large buttons not a pinhole ā¦
2019-03-03 14:53:20 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event zha_event[L]: unique_id=0x8074:1:0x0006, device_ieee=00:15:8d:00:02:13:49:c3, command=attribute_updated, args=attribute_id=0, attribute_name=on_off, value=Bool.false>
2019-03-03 14:53:20 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event zha_event[L]: unique_id=0x8074:1:0x0006, device_ieee=00:15:8d:00:02:13:49:c3, command=attribute_updated, args=attribute_id=0, attribute_name=on_off, value=Bool.true>
you should be getting theseā¦
Sorry for the confusion, it is in fact a small button around 1/8" in size. I use a paper clip to push it and that led to my incorrect statement. I do have the button shown in the link.
thanks again.
mine is the exact same button as that i never get the zha_events like yours im using an xbee as the radio
In January from the very same switch event looked like this - I see naming has changed, but that time they worked ā¦
2019-01-25 21:58:09 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event zha_event[R]: unique_id=zha_event.lumi_lumi_sensor_switch_aq2_021315fc_1, command=attribute_updated, args=attribute_id=0, attribute_name=on_off, value=Bool.false>
2019-01-25 21:58:09 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event zha_event[R]: unique_id=zha_event.lumi_lumi_sensor_switch_aq2_021315fc_1, command=attribute_updated, args=attribute_id=0, attribute_name=on_off, value=Bool.true>You need to set homeassistant.core to debug to see them in the log
In order to avoid collisions we had to reformat the events. They shouldnāt change again.
homeassistant.core is already set to debug. the closets thing i can find in the log to yours is as follow:
2019-03-03 20:27:23 DEBUG (MainThread) [zigpy.zcl] [0x9359:1:0x0006] ZCL request 0x000a: [[<Attribute attrid=0 value=<zigpy.zcl.foundation.TypeValue object at 0xacb4ce90>>, <Attribute attrid=0 value=<zigpy.zcl.foundation.TypeValue object at 0xacbca0f0>>]]
2019-03-03 20:27:23 DEBUG (MainThread) [zigpy.zcl] [0x9359:1:0x0006] Attribute report received: 0=Bool.false, 0=Bool.true
what version of HA
0.88.1 running in docker
Give me a screenshot of the device in the config panel
yeah that should just workā¦ have you tried the event tool and subscribed to zha_event
i tried subscribing to zha_event and i get nothing
Iām at a lossā¦ that makes no sense.
Good to know its not just me that has no clue. Is it something related to zigpy possibly?
noā¦ if the attr reports come in then it is all ZHAā¦