[michaelarnauts]

Summary

On a ComfoConnect Pro, list-nodes crashes on the node of the Pro itself (product 222), seen by two users in discussion #55:

File ".../aiocomfoconnect/comfoconnect.py", line 490, in get_node_info
    return NodeInfo(*await self.get_properties(props, node_id))
File ".../aiocomfoconnect/comfoconnect.py", line 476, in get_properties
    raise ValueError(f"The response is too short for the value of property {prop.property_id}")

get_node_info asked for all properties in one request, and read them one by one when that failed with an RMI error (a node fails it as a whole when it lacks one, like the model of a bridge). The Pro answers the combined request with fewer values than we asked for, so get_properties raised a ValueError, which list-nodes doesn't catch.

get_node_info now simply reads the properties one by one. That works for every node, without depending on how a node answers the combined request; a property the node doesn't have is None, and when none can be read the ComfoConnectRmiError is raised, as before. It's 7 small requests per node instead of 1: list-nodes with a unit and a LAN C still takes under 3 seconds, of which 2 are waiting for the nodes to be announced.

get_properties stays as it was; nothing else in the library uses it.

Home Assistant will read the node info of every node (michaelarnauts/home-assistant-comfoconnect#236), so without this its setup would fail on a Pro.

Testing

• test_get_node_info reads every property with its own request; test_get_node_info_with_missing_properties and test_get_node_info_of_unknown_node as before.
• pytest, pylint (10/10) and black pass.
• list-nodes against a LAN C with a ComfoAir Q450 shows the same info for both nodes as before.
• Not tested on a Pro; asked for its debug output in ComfoConnect LAN C end of sale. Compatibility with successor ComfoConnect Pro? #55.

🤖 Generated with Claude Code