SwiCago

@kayno @lekobob, great progres guys..soon we will know then the mitsu devs lol In kumo cloud, it also periodically sent 0x09 and 0x05...but i didn't see it send stuff based...

@kayno, so the timer bytes are only for reading right now? No setters yet?

@kayno yes, that might be the case, however powering off for 15min will clear any lock out settings/modes...i locked myself out of one of my units. Turned the power off,...

@lekobob @kayno I just tried Kumo Cloud app again, it features programs for single zone and multiple zones. However I never saw it send anything to the kumo cloud device....

@kayno, I think @lekobob deiscovered another Programming Setter Byte We send the following when we want to set stuff fc,41,01,30,10,**01**,CB,CB (CB == ControlByte) His, when getting remote temperature setting pushed...

@lekobob, you could test your 0x05 theory by removing the comms wire from indoor to outdoor unit. It should throw 6840,6841,6844 or 6845

@lekobob, when the mhk1 sends the 0x07 + temperature, how do you get the hp to use internal temp again? You mentioned info temp packet returns all 0x00, does it...

@lekobob @kayno I just tested the 0x07 remote temperature packets. I discovered a few new things. If I set the temperature it is returned back via info 0x03 as lekebob...

@kayno @lekobob, not sure of the best way to incorporate sending Remote Temperature to the HeatPump, as it would require byte 6 to be changed from 0x01 to 0x07...And as...

@kayno @lekobob, I made a first version of setting remote Temperature via the MQTT sketch. Set remote temp sensor value mosquitto_pub -h localhost -p 1883 -t 'heatpump/set' -m '{"remoteTemp":21}' revert...