Did you get a battery report at some point?
It was, as that is where I got all of mine from. But supply seems to have dried up and I can't see them on Amazon anymore. Still available from Aqara site though.
I can share the driver code that mostly works (community modified curtain driver) if that would help identify any differences?
Not with your driver. Do with veeceeoh driver.
1 Like
@mike.maxwell A quick press on the button elicits an FF01 with voltage of 170C -> 3.095v, but doesn’t set a current state.
Also not seeing the error lately.
This must be a completely different firmware than the unit I have, mine reports battery on the 01 tag, now I understand why I've avoided these for so long...
The payload is one byte short for either encoding type 41, or 42
poking around some more
1 Like
Are there plans to add support for the Aqara WXKG11LM Mini Pushbutton?
Ok I
- Used veeceeoh driver. Worked
- Switched to Device and cleared everything
- Switched to your driver, Configured, turned on debug
- Closed/Open with magnet Got state
- Quick press. GOT 100% battery
- Looked in log, got same error.
Maybee that’s why veeceeoh driver searches for the 0x21 in the FF01 payload and uses the next two bytes?
Can’t trust length.
1 Like
can you post the logs when you got the battery report?, maybe I can just ignore that bad payload...
Looks Like I wrote the driver for it, but forgot to add it to the build.
2 Likes
What's the old saying? Oh yeah, no good deed goes unpunished. 
4 Likes
That does sound like a very intentional/specific work-around...
LOL. We will catch it next round! Thanks.
Hi, aqara built in driver works fine with E1 switch. Any chance to have the decoupled mode working with built in driver ? Best.
no idea what this is...
Logs were getting very big and confusing so I cleaned them up and (of course) now I can NOT replicate.
However, here’s a response from a button press.
[trace][raw:37D801000076050042166C756D692E73656E736F725F6D61676E65742E61713201FF421D0121170C0328260421A83305213C00062402000000000A210000641001, dni:37D8, endpoint:01, cluster:0000, size:76, attrId:0005, encoding:42, command:0A, value:lumi.sensor_magnet.aq2, clusterInt:0, attrInt:5, additionalAttrs:[[value:! (&!¨3!<�$
!d, encoding:42, attrId:FF01, consumedBytes:32, attrInt:65281]]]
It appears that in this case the FF01 is buried in the additionalAttrs
In the failure it WAS the base attrid
battery comes in on cluster 0, I tag decoded the frame you sent after adding the missing byte at the end, the battery tag isn't in that frame, so i'm feeling like I can completely ignore this specific frame in the driver.
I'm going to guess it's smart-bulb mode.
Sounds like he means bulb mode? As on Zooz and Inovelli. @amaduhi - is that what you're referring to, set the switch to bulb mode so that you can use it w/smart bulbs?
" * Versatile Control Options:Offers both wired and wireless control, catering to diverse smart home setups."
Yes smart bulb mode or wireless mode.
