Unknown message types 0x45/0x2b

[aplund]

I get these known message type errors, but the integration generally seems to work. They tend to repeat periodically. I'm using the version tagged v0.2.6

Traceback (most recent call last):
  File "/var/lib/hass/.venv/lib/python3.11/site-packages/airtouch2/protocol/at2plus/control_status_common.py", line 74, in from_bytes
    subtype = ControlStatusSubType(subheader_bytes[0])
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/enum.py", line 712, in __call__
    return cls.__new__(cls, value)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/enum.py", line 1135, in __new__
    raise ve_exc
ValueError: 69 is not a valid ControlStatusSubType
2024-01-02 15:45:49.876 WARNING (MainThread) [airtouch2.at2plus.At2PlusClient] Unknown status message type: subtype=0, data=45:00:00:34:00:00:00:00:41:43:34:38:00:00:00:00:00:00:00:00:00:00:00:00:18:00:00:00:23:0c:00:00:00:00:00:00:00:00:00:00:41:74:63:68:32:50:4d:00:36:17:22:48:22:00:22:02:00:00:00:00
2024-01-02 15:45:51.700 WARNING (MainThread) [airtouch2.protocol.at2plus.control_status_common] Unknown message type in header (0x2b)
Traceback (most recent call last):
  File "/var/lib/hass/.venv/lib/python3.11/site-packages/airtouch2/protocol/at2plus/control_status_common.py", line 74, in from_bytes
    subtype = ControlStatusSubType(subheader_bytes[0])
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/enum.py", line 712, in __call__
    return cls.__new__(cls, value)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/enum.py", line 1135, in __new__
    raise ve_exc
ValueError: 43 is not a valid ControlStatusSubType
2024-01-02 15:45:51.708 WARNING (MainThread) [airtouch2.at2plus.At2PlusClient] Unknown status message type: subtype=0, data=2b:00:00:00:00:04:00:06:80:80:07:ff:81:81:07:ff:82:82:07:ff:83:83:07:ff:90:ff:02:f1:91:ff:07:ff```

[nathanvdh]

Yeah it's expected, you have some newer version of the protocol with messages that I don't have documentation for. I didn't want to silently ignore them. I'm not going to reverse engineer the airtouch2+ protocol / work out what they are, as I don't have a 2+ system and have no motivation. I will leave this issue open in case someone else ever wants to try and work stuff like this out.

If anyone is missing a feature they would like then I am happy to help get it working.

[aramshaw]

@nathanvdh - I'm happy to look into this. Are you able to let me know where to start to reverse engineer the airtouch2+ protocol / work out what they are. Can you point me to any online docs?

I should say I was about to provide exactly the same error message.