To enter your cloud details go to the bindings page, click the Xiaomi Mi IO binding and than configure. The list of the known countries and related severs is here.Īfter successful Xiaomi cloud login, the binding will use the connection to retrieve the required device tokens from the cloud.įor Xiaomi vacuums the map can be visualized in openHAB using the cloud connection. However to enable cloud functionality enter your Xiaomi username, password and server(s). Hence if you get your token after reset and than include it with the Mi Home app, the token will change. The Xiaomi devices change the token when inclusion is done. Then search in "RAW, ," for "USERID_mihome.sqlite" and look for the 32-digit-token or 96 digit encrypted token. When finished, use Google Play to get the most recent version back.įor iPhone, use an un-encrypted iTunes-Backup and unpack it and use a sqlite tool to view the files in it: It seems that version was released with debug messages turned on by mistake.Īn APK file with the old version can be easily found using one of the popular web search engines.Īfter downgrading use a file browser to navigate to directory SmartHome/logs/plug_DeviceManager, then open the most recent file and search for the token. The easiest way to obtain tokens is to browse through log files of the Mi Home app version 5.4.49 for Android. If the device does not discover your token, it needs to be retrieved from the Mi Home app. This may depends on the firmware version. Some devices provide the token upon discovery. See binding configuration for more details about the binding config. Multiple servers can be separated with comma, or leave blank to test all known servers. Use the one of the regional servers: cn,de,i2,tw,ru,sg,us. The server(s) to which your devices are connected need to be entered as well. Go to the binding config page and enter your cloud username and password. The binding can retrieve the needed tokens from the Xiaomi cloud. The binding needs a token from the Xiaomi Mi Device in order to be able to control it. The basic discovery will not discovery the type, but will discover a token for models that support it.Īccept only one of the 2 discovery results, the alternate one can further be ignored. The mDNS discovery method will discover your device type, but will not discover a (required) token. If both methods discover your device, 2 discovery results may be in your inbox for the same device. Depending on your network setup and the device model, your device may be discovered by one or both methods. The binding has 2 methods for discovering devices. Note, these devices require a defined gateway to functionįor experimenting with other devices which use the Mi IO protocol or to build experimental support Thing type for subdevices connected to the gateway. Similar to basic, but with the Bridge feature, it can support to forward commands for connected devices Channels and commands are determined by database configuration Once the token is available and the device model is determined, this ThingType will automatically change to the appropriate ThingTypeįor Xiaomi/RoboRock Robot Vacuum productsįor most other devices like yeelights, airpurifiers. The following things types are available: ThingType If your Xiaomi wifi device is controlled by the mihome app, most likely it communicates using the Mi IO protocol and can communicate with openHAB using this binding. This protocol is used for most of Xiaomi Mi Ecosystem wifi devices which is branded as MiJia. This binding is used to control Xiaomi products implementing the Mi IO protocol.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |