-
Notifications
You must be signed in to change notification settings - Fork 111
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
Comments
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):
Do you like to join? ;-) |
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. I 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? |
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? |
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:
I think about changing this. As I understand for this I must:
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.
The text was updated successfully, but these errors were encountered: