Fix local ctrl error

[topsworld]

Fixed

• Add profile devices filter, fix local control error

Added

• Add tools to update profle model file

Changed

• Improve lan control test case

It is necessary to realize the logic of profile convert specv2 later, so as to realize local control and subscribe to the Profile device

[chemwolf6922]

Suggestion: Just use the specV2 subscription result. Do not dive into the profile pitfall (again).

[chemwolf6922]

And the cloud has a field for telling if a device is "native spec V2" (for the central gateway). You should use that instead of any hard coded list.

[chemwolf6922]

And this (newly added) timeout seems suspiciously small. Please check if this is by design.

ha_xiaomi_home/custom_components/xiaomi_home/miot/miot_lan.py

Line 179 in 0af9e08

NETWORK_UNSTABLE_RESUME_TH: int = 300

[chemwolf6922]

Suggestion: Just use the specV2 subscription result. Do not dive into the profile pitfall (again).

Apparently there are device that supports the full subscription and also use the old protocol...

[topsworld]

And this (newly added) timeout seems suspiciously small. Please check if this is by design.

ha_xiaomi_home/custom_components/xiaomi_home/miot/miot_lan.py

Line 179 in 0af9e08

NETWORK_UNSTABLE_RESUME_TH: int = 300

Is a bug 🫥

[topsworld]

And the cloud has a field for telling if a device is "native spec V2" (for the central gateway). You should use that instead of any hard coded list.

The cloud interface provided does not have this field. This list contains the Profile device, and there will be no update in the future, so use HardCode