Bless you no, @antonical, a humble ex-Chemical Engineer, so pretty clueless on electronics and control, and I would always defer to giants like @Topaz and @toadhall for this kind of thing.
Having said that, here’s what NASA.ptc has to say about 0x8001 (in case you haven’t downloaded SNET-Pro2 yet):
<Enum>
<Item Value="0">
<String>OP_STOP</String>
</Item>
<Item Value="1">
<String>OP_SAFETY</String>
</Item>
<Item Value="2">
<String>OP_NORMAL</String>
</Item>
<Item Value="3">
<String>OP_BALANCE</String>
</Item>
<Item Value="4">
<String>OP_RECOVERY</String>
</Item>
<Item Value="5">
<String>OP_DEICE</String>
</Item>
<Item Value="6">
<String>OP_COMPDOWN</String>
</Item>
<Item Value="7">
<String>OP_PROHIBIT</String>
</Item>
<Item Value="8">
<String>OP_LINEJIG</String>
</Item>
<Item Value="9">
<String>OP_PCBJIG</String>
</Item>
<Item Value="10">
<String>OP_TEST</String>
</Item>
<Item Value="11">
<String>OP_CHARGE</String>
</Item>
<Item Value="12">
<String>OP_PUMPDOWN</String>
</Item>
<Item Value="13">
<String>OP_PUMPOUT</String>
</Item>
<Item Value="14">
<String>OP_VACCUM</String>
</Item>
<Item Value="15">
<String>OP_CALORYJIG</String>
</Item>
<Item Value="16">
<String>OP_PUMPDOWNSTOP</String>
</Item>
<Item Value="17">
<String>OP_SUBSTOP</String>
</Item>
<Item Value="18">
<String>OP_CHECKPIPE</String>
</Item>
<Item Value="19">
<String>OP_CHECKREF</String>
</Item>
<Item Value="20">
<String>OP_FPTJIG</String>
</Item>
<Item Value="21">
<String>OP_NONSTOP_HEAT_COOL_CHANGE</String>
</Item>
<Item Value="22">
<String>OP_AUTO_INSPECT</String>
</Item>
<Item Value="23">
<String>OP_ELECTRIC_DISCHARGE</String>
</Item>
<Item Value="24">
<String>OP_SPLIT_DEICE</String>
</Item>
<Item Value="25">
<String>OP_INVETER_CHECK</String>
</Item>
<Item Value="26">
<String>OP_NONSTOP_DEICE</String>
</Item>
<Item Value="27">
<String>OP_REM_TEST</String>
</Item>
<Item Value="28">
<String>OP_RATING</String>
</Item>
<Item Value="29">
<String>OP_PC_TEST</String>
</Item>
<Item Value="30">
<String>OP_PUMPDOWN_THERMOOFF</String>
</Item>
<Item Value="31">
<String>OP_3PHASE_TEST</String>
</Item>
<Item Value="32">
<String>OP_SMARTINSTALL_TEST</String>
</Item>
<Item Value="33">
<String>OP_DEICE_PERFORMANCE_TEST</String>
</Item>
<Item Value="34">
<String>OP_INVERTER_FAN_PBA_CHECK</String>
</Item>
<Item Value="35">
<String>OP_AUTO_PIPE_PAIRING</String>
</Item>
<Item Value="36">
<String>OP_AUTO_CHARGE</String>
</Item>
<Default>
<String>Unknown</String>
</Default>
</Enum>
<Range Min = "0" Max = "254"/>
So on the one hand I can see exactly where your 0,1,2,5 values are coming from (e.g. 5 = Deice, aka defrost), and it is well-known that a Samsung defrost cycle (at least on pre-Gen 7 units) lasts ~5-8 minutes (see Samsung ASHPs: Anatomy of a Defrost for the gory details). And on a cold night like last, 5 defrosts is quite believable (and not abnormal).
But 0x8001 = 39 is a new one on me. You can see that the NASA.ptc list goes up to 36, even though values up to 254 are allowed if I interpret the last line correctly. How are you reading this value (given that you don’t use SNET-Pro2)? Via your MIM-B19N and Modbus? In which case I’d be out of my depth, sorry… 