-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
[Architecture] Allow multiple entities per device #223
Comments
So you want to convert some Somfy attribute to hass entity_id? |
@tetienne not sure yet how to do it technically. Opened this issue for tracking, since I faced it a few times in my last work on the integration. But in the end, it would be good to understand if for example battery state and other states should be in their own entity. Good one to discuss on Discord. Open for any technical architectures. |
'There hasn't been any activity on this issue recently. Is this issue still present? |
I started on this one, however there is a lot of work to be done. And we need to rethink how we currently init the sensor / binary sensor platform.
|
@Hankey71 the version below should add a sensor for the expected number of showers. Could you give https://github.com/iMicknl/ha-tahoma/archive/refs/heads/feature/add_secondary_sensors.zip a try? Extract this file and place |
Hi @iMicknl |
Great to hear, @Hankey71! And the screenshot is from a long time ago, but I guess I took it while developing via your account. 😄 |
Is your feature request related to a problem? Please describe.
Currently, we only have one entity per discovered Somfy TaHoma device. However, looking at some of the devices, there are more interesting states and/or actions to take, which we put now in attributes.
Looking at PR's to core, I get the feeling that the attributes part is used less and less and should not be used to store everything.
For example, looking at some sensors, there are multiple power states and the same for some security devices.
Describe the solution you'd like
Rewrite part of the integration to dynamically allow the creation of multiple entities per device.
Additional context
Example of a Z-Wave device, with multiple entities. Some less frequent used entities are hidden by default.
The text was updated successfully, but these errors were encountered: