You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue tracks the progress of adding descriptors to existing integrations.
Call for help
If you possess any devices besides the 1st gen Roborock vacuum and a zhimi powerstrip which I have, please consider creating a pull request to add the @sensor, @setting and @action descriptor decorators so that homeassistant (and other potential downstreams) can create entities for your device automatically in the future. https://python-miio.readthedocs.io/en/latest/contributing.html#status-containers contains some documentation on the topic, and the issues linked below in the checklist show an example of how they look like in homeassistant.
For development and testing, you can either use miiocli's commands status, settings, set, actions, call, etc. or a homeassistant custom component.
When we get feature parity (or close to it) with the existing homeassistant support, the plan is to create smaller PRs (per platform, most likely) based on the fork to first enable the additional entities, and sunset the hard-coded ones afterward.
When adding the descriptors to the status classes, you can provide the following extra kwargs that are currently used by the fork:
device_class would be great to have besides the name and the unit
icon for defining custom icons when no device_class is set
state_class is not a priority at the moment, the default value should be chosen inside homeassistant and overridden only when needed
This issue tracks the progress of adding descriptors to existing integrations.
Call for help
If you possess any devices besides the 1st gen Roborock vacuum and a zhimi powerstrip which I have, please consider creating a pull request to add the
@sensor
,@setting
and@action
descriptor decorators so that homeassistant (and other potential downstreams) can create entities for your device automatically in the future. https://python-miio.readthedocs.io/en/latest/contributing.html#status-containers contains some documentation on the topic, and the issues linked below in the checklist show an example of how they look like in homeassistant.For development and testing, you can either use
miiocli
's commandsstatus
,settings
,set
,actions
,call
, etc. or a homeassistant custom component.When we get feature parity (or close to it) with the existing homeassistant support, the plan is to create smaller PRs (per platform, most likely) based on the fork to first enable the additional entities, and sunset the hard-coded ones afterward.
When adding the descriptors to the status classes, you can provide the following extra kwargs that are currently used by the fork:
device_class
would be great to have besides the name and the uniticon
for defining custom icons when nodevice_class
is setstate_class
is not a priority at the moment, the default value should be chosen inside homeassistant and overridden only when neededIntegrations
The text was updated successfully, but these errors were encountered: