Beacon and reply

[plambrechtsen]

With my feeder associated to my hub when the feeder boots I see a standard Beacon request directly to my hub then association request. So I assume your door hasn't been associated yet.

Hub: 801f12fffee88dd9
Feeder: 162e02c0f9d5b370

Beacon request:
63 cc 00 ff ff 80 1f 12 ff fe e8 8d d9 16 2e 02 c0 f9 d5 b3 70 07 2f

Association request
63 cc 01 ff ff 80 1f 12 ff fe e8 8d d9 16 2e 02 c0 f9 d5 b3 70 01 00 04 30

I have a slack channel of other folks working on reverse engineering the hub if you are interested.

[mretallack]

What is interesting is that both your (and mine) beacon request contains 2f as the last byte. As per the MiMi protocol, this should be the channel the device is working on and is treated as a pure byte.

It has been confusing me why its 0x2f instead of 0x0f. The stack usually would dismiss this. I did think this was some sort of corruption in my feeder, but now I have seen yours it would suggest something else is going on.

I think my next step is to get my own hub so I can see the paring sequence.