David Conran

Thanks for that. The `24` in your IP output looks like it's the number of bits in the protocol. So, that at least it gives me something to hunt for...

I've looked & looked at my code. I can't see the mistake, but it seems there is. I'll take another look tomorrow with fresher eyes

Oooh. That's very useful. I'll try to look into that later. Oh. It's not a dynamic array. Just a pointer to the array. Hence should be safe in a struct

Oh wait. State. That's a static sized array.

Quick question, if you change the "bits" in decode, does that always appear in your IP output?

The compiler should be throwing errors left, right, and centre if something tries to write to `kStateSizeMax`. Yes, it's a `const`. It should NEVER change. The fact it is, is...

I'll try to review this on Tuesday (GMT-10). I'm busy till then.

Per the issue templete you partially ignored: https://github.com/crankyoldgit/IRremoteESP8266/blob/master/.github/ISSUE_TEMPLATE/problem-report.md#output-of-raw-data-from-irrecvdumpv2ino-or-v3-if-applicable ----------- #### Output of raw data from [IRrecvDumpV2.ino](https://github.com/crankyoldgit/IRremoteESP8266/blob/master/examples/IRrecvDumpV2/IRrecvDumpV2.ino) or [V3](https://github.com/crankyoldgit/IRremoteESP8266/blob/master/examples/IRrecvDumpV3/) (if applicable) _Include some serial text of the raw dumps of what...

Thanks for that. I'm assuming those are captures when using the physical remote. Does the "Mesg Desc:" match up with what you would expect given the state of the remote?...

Can you capture the results using another the other ESP running IRrecvDumpV2c etc? They should be the same, and produce the same output. The code base isn't any different