Weird striding on output (and protocol differences) on Kraken 2023 (non-Elite)

[aniongithub]

As I mentioned in the liquidctl PR thread, this code also seems to be failing in a similar place with the same error.

The call stack of the failure is:

readUntil (/workspaces/AIOLCDUnchained/driver.py:179)
deleteBucket (/workspaces/AIOLCDUnchained/driver.py:255)
deleteAllBuckets (/workspaces/AIOLCDUnchained/driver.py:266)
setupStream (/workspaces/AIOLCDUnchained/driver.py:461)
<module> (/workspaces/AIOLCDUnchained/rotating.py:15)

The cause of the failure is that deleteBucket calls self.readUntil({b"\x33\x02": self.parseStandardResult}). Unfortunately, when the reply is received,

msg = [117, 2, 123, 235, 198, 54, 205, 36, 236, 93, 134, 20, 178, 111, ...]
and
prefix = b'u\x02'

which doesn't match the parser prefix passed in via the dict. However, changing the dict key to b'u\x02' gets us past that point. However, setLcdMode then promptly fails too, passing in b"\x39\x01" while the message prefix (again) is b'u\x02'. After changing all message parser prefixes to match, I finally get something on the screen, but it seems like the stride is off, or something. I'm also happy to push my changes to a fork if that'd help.

Any help is much appreciated, it appears I'm pretty close to having a working custom rendered image on my AIO screen!

Output of rotating.py with changs described above.

[aniongithub]

bump

[brokenmass]

@aniongithub hi ! can you contact me on discord (brokenmass ) ?

[aniongithub]

Done, sent you a DM request!