Error Message Frozen/TargetUpdate wrong size (possibly resolved)

[securitycopper]

I'm trying to understand this, could it be related to calibration or priming needed? Still shows after calibration

ERROR opensleep::common::codec] Frozen/TargetUpdate wrong size: expected 6, got 2. Buffer: b"\xc0\x02"

I have yet to get the physical pumps / temperature to turn on.

I rebuilt the opensleep binary with latest but still get same error. Here is my mqtt view in case i configured something wrong.

[securitycopper]

So the system is now running, though i've customized the binary and need to retest with base repo code

Actions I took:

1. Clipped the front cover back into place fully
2. covered with the plastic lid loosely, room is a bit dark
3. Factory reset back to factory image
4. set up pod fully, let it prime, let it run till the next day (slept with it priming)
5. flashed the patched image (using my full workflow script that patches everything into the tar)
6. Came up and started heating based on my existing schedule

I see many other errors in the logs, but they may be related to changes I made to binary for more logging.

Unsure, maybe I had the bed in a bad priming state. maybe i had int erupted a prim happening from the app last time. keeping issue here in case it sparks ideas, if we know why it happens we can improve the logging

[LiamSnow]

Would love to see if you're getting more "wrong size" messages. All of the protocol is my reverse engineering work on my bed, so its not crazy that other firmware versions behave differently.

Looking at that specific error, it received 0xC0 0x02 which I don't really know what that could mean.

My comment on parse_target_update states it should look like 0xC0, 0x00, side, state, temp_high, temp_low (where I think 0x00 is just a filler). I'm not sure what 0x02 could indicate. Maybe its some sort of different response or failure mode?