kricon

> Current 0xAA decoding - byte 3 bit 6-7 may be partition number but needs confirmation: Confirmed: ``` 2224.73: 11111111 1 10000010 11111111 11111111 11111111 11111111 11111111 11111111 11111111 [Module/0x05]...

> There are also a few ranges of status messages that will probably get filled in - for example, in printPanelStatus2() it's likely that all messages in the 0xF9 -...

Command 0x94 seems to be used for requesting and getting data from RF module to panel. Probably similar to 0x8D. Note that this is mostly dump from notes of logs...

Does anyone have panel version `v4.60` or above with an PK5500 keypad? They include new section `[898]` for automatic Wireless enrollment without manually enetering ESN. Hopefully, you can enter it...

I've found out that on PC5010 v2.00 panels you can have multiple users having same access code - event buffer will log only the lowest one. Update for 0x94 panel...

Auto-Disarm feature exists only on PC1616/PC1832/PC1864 panels, I've verified it with PC1832 v4.24, works exactly as you described. Thanks for contribution with tracking all messages from PC5200, I've included it...

Im slowly learning a little, now I understand the "_switch (panelData[4] >> 2)_" line and bit shifting thing. Its all clear now, sorry if I confused you. This is what...

> Glad it's of use! And yes, testing with the panels and modules would be great - the example sketches cover common use cases and at this point the develop...

I saw it and like the new version-identifing you made in new version. What about the other suggestions, for blynk and unlocker sketches? Will you include new tamper data I...

Sure I can output the logs! Actually, I wanted to test that when I get my hands on PK5500 because it have PGM output which can be assigned to any...