Here's the local Met Office weather station recorded outdoor temp vs byte_09 for the last 48 hours:

I think that pretty much confirms byte_09 is the Midea ambient temp value.

@cathoderay

Hi CathodeRay,

I delved a little deeper into the Python code last night and may have some possible code modifications to try. Could you send a text copy of any routines that you have modified so that we are both looking at the same song sheet.

Posted by: @derek-m

↑

Could you send a text copy of any routines that you have modified so that we are both looking at the same song sheet.

Done!

Posted by: @cathoderay

↑

Posted by: @derek-m

↑

Could you send a text copy of any routines that you have modified so that we are both looking at the same song sheet.

Done!

I cannot open the files as they are not in a text format. Could you copy the code then put it into a Word documents please.

@derek-m - they are text files, just open them in any text editor. If you use one of the better ones (I use Notepad++), it will do some basic code highlighting and auto-completion for you.

Posted by: @cathoderay

↑

@derek-m - they are text files, just open them in any text editor. If you use one of the better ones (I use Notepad++), it will do some basic code highlighting and auto-completion for you.

I had not noticed that they had come through as .py files. Now corrected and opened.

@cathoderay

Have you obtained any Type 01 messages recently, and if so did they show any additional data?

Looking at the Type 04 group of messages, the byte, Hex ec to fa, in position 155 gives decimal values of 236 to 250, which would appear to indicate a changing variable. It could not be a temperature, unless it requires decoding with some form of equation, but I wondered if it could be something like 'fan speed'. Is there anything in the controller data that could give some form of indication?

Posted by: @derek-m

↑

Have you obtained any Type 01 messages recently, and if so did they show any additional data?

They (the 03/01messages) are the ones that arrive every minute, so lots of them, but most of the values are static, and I think all the available bytes in the message are already decoded/extracted. Here's recent pair, first the 'Received' message, then the decoded 'Status update':

2023-02-24 19:52:56.182 DEBUG (Heat Pump Wi-Fi Controller) [custom_components.midea_ac_lan.midea.devices.c3.device] [device_id] Received: {'header': 'aa23c300000000000003', 'body': '010975910303281e323041231905371919053c223c14290080', 'message type': '03', 'body type': '01'}
2023-02-24 19:52:56.184 DEBUG (Heat Pump Wi-Fi Controller) [custom_components.midea_ac_lan.midea.core.device] [device_id] Status update: {'zone1_power': True, 'zone2_power': False, 'dhw_power': False, 'disinfect': False, 'fast_dhw': False, 'zone_temp_type': [True, True], 'mode': 3, 'mode_auto': 3, 'zone_target_temp': [40, 30], 'dhw_target_temp': 50, 'room_target_temp': 24.0, 'zone_heating_temp_max': [65, 55], 'zone_heating_temp_min': [35, 25], 'zone_cooling_temp_max': [25, 25], 'zone_cooling_temp_min': [5, 5], 'room_temp_max': 30.0, 'room_temp_min': 17.0, 'dhw_temp_max': 60, 'dhw_temp_min': 20, 'tank_actual_temperature': 41, 'outdoor_temperature': 0, 'zone1_water_temp_mode': True, 'zone2_water_temp_mode': False, 'zone1_room_temp_mode': False, 'zone2_room_temp_mode': False}

Posted by: @derek-m

↑

Is there anything in the controller data that could give some form of indication?

Here's a list of all the Operational Paramater pages available in the wired controller. Note that in some cases my wired controller is blank (shows '--') for the value eg on page 3 both T1 LEAVING WATER TEMP and Ta ROOM TEMP are both blank (but the LWT/RWT do show up on page 4 as TW_O PLATE WATER OUTLET TEMP and TW_I PLATE WATER INLET TEMP, TW_O(ut) is LWT, TW_I(n) is RWT and also note the image is wrong, my controller has TW_I PLATE WATER INLET not OUTLET TEMP):

@cathoderay My Lenovo M710q arrived this morning and is all setup for Remote Desktop. When doing nothing it consumes about 8W! 

I’m going to get it setup to run my telescope which it will be mounted to. Quite a task. It will then go in the Observatory on the motorised mount.

I’ll then install HA again and set it up to run in the background.

Phil

@cathoderay

I have some thoughts as to what additional code may be required to obtain additional data, though I still don't fully understand how the different parameters are being included in the desired list, or the 'available' list.

If you are agreeable, I would suggest changing the 'indoor_temperature' and 'outdoor_temperature' to 'current_temperature' and 'target_temperature', both of which have been used as parameter names elsewhere. Then see if there are any changes to the data collected.

Posted by: @derek-m

↑

If you are agreeable, I would suggest changing the 'indoor_temperature' and 'outdoor_temperature' to 'current_temperature' and 'target_temperature', both of which have been used as parameter names elsewhere. Then see if there are any changes to the data collected.

Have done so, but only for indoor/current_temperature, target_temperature causes a fatal error ("TypeError: Attempted to reuse key: 'target_temperature'"). The results may also throw some light on whether the parameter names have an inherent meaning inside the code, or are arbitrary labels attached by us to particular data in a specific location. As you know, I think it is the latter, that's why labelling the data at position xx as 'byte_xx' works, as would labelling it 'any_name_xx'.

Will report back when I have some results.

PS target_temperature was used twice, but only in one place, may be able to add it after all

@cathoderay

I have been delving ever deeper into the Python code, with a few interesting results, details of which I will provide shortly.

Have you made any progress at your end?