images/ha_xiaomi_home
2
0
Fork 0
mirror of https://github.com/XiaoMi/ha_xiaomi_home.git synced 2025-12-17 02:42:11 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updated Features that will not be implemented (markdown)

Li Shuzhen
2025-11-28 08:58:42 +08:00
parent dba6fa3fcf
commit c79a8a4b7a
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
Features-that-will-not-be-implemented.md

@@ -2,6 +2,12 @@
Home Assistant entities generated by xiaomi_home are strictly bound to device IDs. At present, there is no feasible or reliable way to make one entity display data coming from two or more different physical devices.
## Bridging entities from Home Assistant into MiHome APP
xiaomi_home is designed to import Xiaomi IoT devices into Home Assistant. Importing Home Assistant entities into MiHome APP should be handled by another integration, just like HomeKit Bridge integration for Apple Home APP. Here we call this integration "MiHome Bridge".
However, developing MiHome Bridge to bridge entities which are generated by other IoT platform devices would expose Xiaomi to significant legal risk. Controlling devices from other IoT platforms within MiHome APP without authorization from the device and the platform brand significantly increases the risk of infringement. Therefore, we have no plan to develop this integration.
## Camera video stream
The camera video stream is encrypted using P2P encryption, with the encryption key negotiated between the Mi Home APP and the camera device. xiaomi_home is an untrusted client and cannot negotiate the video encryption key with the device, so it cannot fetch the camera video stream.
@@ -17,7 +23,7 @@ MIoT-Spec-V2 protocol allows setting multiple properties in one command message.
{"id":1234,"method":"set_properties","params":[{"did":"2262","piid":1,"siid":2,"value":true},{"did":"2262","piid":2,"siid":2,"value":50},{"did":"2262","piid":4,"siid":2,"value":3000}]}
```
However, not all IoT devices support processing this type of message. Even if a device is capable of handling messages that contain multiple property settings, the number of property values it can process at one time varies from device to device. If the number of property values to be set in a single command message exceeds the device’s capability, the device may crash or exhibit other anomalies.
However, not all IoT devices support processing this type of message. Even if a device is capable of handling messages that contain multiple property settings, the number of property values it can process at one time varies from device to device. If the number of property values to be set in a single command message exceeds the device's capability, the device may crash or exhibit other anomalies.
The only certainty is that all devices can handle the command message that sets only one property value. It is extremely rare for a device to function only when multiple property values are set in one command message. If the device fails to operate properly when command messages are sent one by one, with each command setting only one property, then the device does not comply with the MIoT-Spec-V2 protocol standard.