drinfernoo

Well, I have to say that seems to go over my head 😅 I'm also not particularly keen in hardware modding my hub for the time being... But I could...

I've attempted to add one of my new motion sensors to my V1 bridge, and get the following state published: ```json { "event": "alarm", "available": true, "mac": "77C006C8", "device_class": null,...

Actually, I do seem to be getting some state reporting from these, but not ever an actual state change... ```bash State event data: [2021-05-08 21:46:02][77C006C8]AlarmEvent: sensor_type=unknown, state=unknown, battery=99, signal=24 {'event':...

Whoops, I didn't see the edit until today 🤦 I'll give a test in a bit!

Well, the PR we're working on does seem to have fixed all of the functionality of the V2 **sensors**, but the keypad is still a mystery to me. Are you...

So I've now successfully flashed my V1 bridge with the V2 Hub firmware from @AK5nowman, but just need to figure out how to receive things properly.

It does seem that yours reports everything out to me via the console, but it would still be ideal if we could get it working with WS2MQTT, so that we...

@AK5nowman Yeah, as this is not just a sensor, but a keypad with multiple kinds of events, there will probably be quite a bit of different logic now.

I sometimes do have this issue, but as @raetha points out, it seems that `paho` does indeed end up sending the messages later.

Ah, another thing... I have the "bridge" dongle flashed with [this firmware](https://github.com/AK5nowman/WyzeSense/blob/master/WyzeSenseUpgrade/firmware/hms_cc1310.bin). Is this PR intended to support that, then?