Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roadmap: UI config and devices with multiples entities #138

Open
Kirmas opened this issue Jan 21, 2021 · 3 comments
Open

Roadmap: UI config and devices with multiples entities #138

Kirmas opened this issue Jan 21, 2021 · 3 comments

Comments

@Kirmas
Copy link

Kirmas commented Jan 21, 2021

This is more questions than Issue.

As I understand current vision of the deviсes in home assistant is a deviсe object with multiply entity(switches, sensors, fans, etc.). But in current component, as I understand, deviсe implemented as fans entity with addition values, without any sensors.

To more understanding about what I say pictures from yeelight integration:
image

I think about changing this. As I understand for this I must:

  • Implement config from UI.
  • Add device_info function implementation to any entity.
  • And In the end move "addition values" to separate sensors.

Amount off how many device this integration support I think its big amount of job. And I will spend a lot of time to implementation and bug fixing.

What do you think about this? Maybe its a bad idea, why? Maybe you already have a plans about this?

Best regard.

@syssi
Copy link
Owner

syssi commented Jan 21, 2021

This is the way to go! This (custom) component was born at a time there didn't exist devices in Home Assistant. The architecture of Home Assistant has changed and evolved. This is the roadmap which should be tacked (but my time is the limiting factor here at moment):

  1. Provide a platform called xiaomi_miio or xiaomi_miio at the lowest level of the configuration.yaml (xiaomi_miio/__init__.py).
  2. Refactor the speed property. Only official supportes values are allowed here to be alexa/google home compatible. We have to move the speed / operation mode of the xiaomi device to a new service.
  3. Use this platform to configure all supported devices. Expose devices and spawn multiple entities (fan, sensor, climate etc) as needed. Don't provide sensor values as attributes anymore.
  4. Dispatch state updates received by __init__.py to all related entities (sensors, switches, etc.).
  5. Implement a config_flow to setup the platform via the UI. Tests are required.

Do you like to join? ;-)

@syssi syssi changed the title UI config and devises with multi entity. UI config and devices with multiples entities Jan 21, 2021
@syssi syssi changed the title UI config and devices with multiples entities Roadmap: UI config and devices with multiples entities Jan 21, 2021
@syssi syssi pinned this issue Jan 21, 2021
@Kirmas
Copy link
Author

Kirmas commented Jan 21, 2021

You 100% true about time factor. All of us have main job, and family.

Maybe you have better place for communicate about this project than issue. Im very new with home assistant thats why, I can ask some question, but not a lot, I don't trying to find mentor (Home Assistant development docs sometimes don't enough) :).

I haven't understand clearly what "lowest level of the configuration.yaml" means.

But I have some devices that this component support, and I want to help improve integration.

If you OK with this. What can I help with first?

@spacecakes
Copy link

This would be great. I didn't manage to get the official Miio integration working (seems broken at the moment, judging from the people replying to issues) and found this one. Still works!

Are there still plans to make this a device platform or merge it with the official integration?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants