Preset Modes not reported correctly

[pearson]

Devices:

• Two portable air conditioners
  • A Midea MP12SVWBA3RCM
  • A Danby DPA100B9IWDB-6

Problem:

• Midea Smart AC does not seem to receive Preset Mode state information from my air conditioners. For example:
  • If "Boost" has been turned on directly or through the NetHome app, the Preset Mode in the Home Assistant UI will not update to show this
  • If the Preset Mode is changed in the Home Assistant UI from "None" to "Boost", the air conditioner will go into Boost mode, but the Home Assistant Preset Mode display will switch back to the "Eco" leaf after ~2 minutes
    • If a Home Assistant UI page is opened as soon as the NetHome app shows the air conditioner is in Boost mode, that Home Assistant UI page will show the "Eco" leaf as the Preset Mode
  • If the entity data is read through Node-RED, "preset_mode" will always be set to "none". This seems to fit with how a new Home Assistant UI page will show the Eco leaf immediately after Boost mode was turned on.

Notes:

• The two portable air conditioners are very similar, with styling features being the main difference
• Through msmart-ng discover, neither air conditioner reports back AC. Instead, they report back <DeviceType.AIR_CONDITIONER: 172>, and 172 is (of course) decimal for a hex AC.
  • I'm not certain if these air conditioners are officially supported. AC is clearly listed as required, yet mine are returning the equivalent of a hex AC in decimal.
  • Besides this problem with preset modes, Midea Smart AC is working very well with these air conditioners
• Assuming that "TURBO" is the same as "Boost Mode", the it appears that Midea Smart AC has the device's features correct in the diagnostics download:

      "additional_capabilities": [
        {
          "__type": "<flag 'Capability'>",
          "repr": "<Capability.CUSTOM_FAN_SPEED: 1>"
        },
        {
          "__type": "<flag 'Capability'>",
          "repr": "<Capability.TURBO: 16>"
        },
        {
          "__type": "<flag 'Capability'>",
          "repr": "<Capability.DISPLAY_CONTROL: 32>"
        },
        {
          "__type": "<flag 'Capability'>",
          "repr": "<Capability.FILTER_REMINDER: 128>"
        },
        {
          "__type": "<flag 'Capability'>",
          "repr": "<Capability.SWING_VERTICAL_ANGLE: 2048>"
        }
      ],

Conclusion:

• To me this appears to be a bug, but perhaps some tweaks are required for these two air conditioners?
• I do really appreciate your integration, as it has made many air conditioner-related tasks significantly easier. Once I get Boost mode working properly, I'll have everything I need running. Thank you! 😃