@kenjustken42 Sorry about this! This looks like a known bug with our SMBus analyzer, and we’re planning on implementing a fix in the next official release of our software.
Having said that, you can implement the fix in the current version of the software by following the steps we’ve highlighted below.
Hopefully that works out for you in the short term, at least until we officially implement the fix.
To address the 2nd issue - the first transaction seems to be getting decoded. Could this be an artifact of the above mentioned bug? (i.e. issue appears after real-time decoding, but saving/re-opening the capture file causes the first transaction to be decoded properly).
Thanks for the the heads up on your 3rd point as well. Feel free to get that posted in the Issues section of our SMBus GitHub repository below, and/or our feature requests site so that we can properly log your feedback. I can do so as well on your behalf if you prefer!