[miio] Binding enhancements

[marcelrv]

Placeholder / braindump for next set of features planned / wished for in the miio binding

Cloud

• Allow to send commands to devices via the cloud besides direct ([miio] Cloud Communication for devices #8981)
  Add option to binding and device config to select the communication patther
  Options 0 direct than try cloud, 1 direct, 2 cloud
  Note this also possibly allows to receive info not received directly from device e.g. powerusage for plugs, info from Bluetooth devices etc
• Cloud events subscription
  Allow support for devices like Xiaomi Mijia AI Video Doorbell, or various lumi devices like motion sensors, button as these don't have a property to query but only create events
• Support to pull some parameters from the cloud using custom cloud refresh commands [miio] Add BT Devices channel to chuangmi plug #11715

Discovery

• Add method to discover devices from cloud [miio] Add discovery from cloud feature. #9176
• Avoid upnp discovery from duplicating devices in discovery [miio] Change deviceID to Xiaomi used string #10951
• upnp discovery get token from cloud [miio] add automatic tokens to miio MDNSDiscoveryParticipant #8463

Vacuum

• Add support for dynamic channels for newer devices
• Crop the map in case blue borders are too large [miio] Map improvement cropping and customizable colors/parameters #11110
• Configurable scaling of the map [miio] Map improvement cropping and customizable colors/parameters #11110

Basic handler

• Add map of variables e.g. $smooth$ to allow for multi parameter commands to be send
  add channels (if requested) for these variables
  have global vars to substitute values-> $did$ [miio] Improve yeelight RGB with brightness, introduce substitutions #10984
• add parameter defining the QuantityType type e.g. for Celcius update with new QuantityType<>(environment.temperature, SIUnits.CELSIUS)); [miio] Allow for quantity Type #8756
• dynamically generate channels [miio] dynamically generate channelTypes #9158

Database improvements

• Per device add name (+ maybe maturity). Note: adding the name to be able to remove all basic devices from the MiIoDevices.java and drive them directly from the db
• Move from precommand & post to jsonarray of commands to allow for arbitrary amount of parameters
• Add possibility of refresh command per parameter, so not only the get_properties are done in refresh but others could be as well (allows to support viomi vacuum type devices in basic handler) [miio] Allow for custom refresh commands #8796
• Support to add the option values [miio] dynamically generate channelTypes #9158
• Write documentation for the json database format

MIOT support

• Create new handler or enhance basic handler to process commands for miot devices
• (in unsupported handler) allow to create database files based on the online miot spec [miio] Automatic create experimental support for (unsupported) miot devices #11149

Unsupported handler

• Create readable logging to file to allow to easy share device info [miio] Improved unsupported handler that build experimental support #8716
• Test all known commands to see if the device supports them [miio] Improved unsupported handler that build experimental support #8716
  Start with profile(s) that matches to the device
• Based on testing result automatically create a json database file to run it afterwards as basic device [miio] Improved unsupported handler that build experimental support #8716

Gateways support

• Support newer deviceIds the gateway subdevices are using [miio] Change deviceID to Xiaomi used string #10951
• Support substitutions for deviceId and timestamp [miio] Improve yeelight RGB with brightness, introduce substitutions #10984
• Allow more parameters to be added beside the method (needed for sending commands to subdevices) [miio] Implement lumi devices support for gateways #11688
• create a bridge handler for gateways, child devices for gateway sub devices [miio] Implement lumi devices support for gateways #11688

[micha-tum]

One more thing that might be useful: For Yeelight lamps, it is currently not possible to turn the lamp on through the RGB channel (RGB brightness > 0 should turn on the lamp, ==0 -> off). Also brightness channel changes of the item are not synced to the RGB channel brightness, only vice versa is synced. Both things are necessary to have it properly working with Google assistant, current workaround is through a dummy item and some rules, but it would be nice to have this directly in the binding. Hope this comment is in the right place here, otherwise just delete it. Thanks for your effort on the binding!

[openhab-bot]

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/xiaomi-mi-binding-config-file/115287/2

[mrumpf]

Allow the binding to be configured via a cfg file: https://community.openhab.org/t/xiaomi-mi-binding-config-file/115287/2 so that the cfg file can be added to a git repo to get all OH configuration under version control.

[marcelrv]

@mrumpf I believe that is already possible with all binding configurations
You can define the binding configuration through userdata/config/binding/miio.config

content:

:org.apache.felix.configadmin.revision:=L"9"
cloudDiscoveryMode="all"
password="superduperSecret"
service.pid="binding.miio"
username="your@email.com"

[marcelrv]

Closing the issue. Remaining on the Wishlist is Cloud events subscription.
Allow support for devices like Xiaomi Mijia AI Video Doorbell, or various lumi devices like motion sensors, button as these don't have a property to query but only create events

However, as this cloudsevents functionality involves a rather complex flow don't expect to implement this.