Add known limitations to eheimdigital #40015
Conversation
|
It seems that this PR is targeted against an incorrect branch since it has a parent PR on one of our codebases. Documentation that needs to be updated for an upcoming release should target the |
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| @@ -151,6 +149,10 @@ actions: | |||
|
|
|||
| {% enddetails %} | |||
|
|
|||
| ## Known limitations | |||
|
|
|||
| - The integration does not support other EHEIM Digital devices than those listed above. More devices will be added in future updates. It is, however, supported to have an unsupported device as the main device and supported devices as sub-devices, even though the unsupported device will not have any entities shown in Home Assistant. | |||
There was a problem hiding this comment.
I find this a bit confusing. Could give an example, maybe?
There was a problem hiding this comment.
Ah, sorry. With EHEIM Digital, all devices can take the role of main/master or sub/slave. It just depends on which was set up at first, which becomes the main device, and the others are the subs.
If you have for example three devices, from which one is unsupported but set up as the main device, the integration works and communicates with all devices via the main device (the devices have a "meshing" so you talk to the main device and the messages get forwarded and vice versa) but the unsupported main device has no entities.
There was a problem hiding this comment.
Ok, thank you. That makes it a bit clearer. But I still don't understand.. why would I want add a device if I cannot see its entities?
Proposed change
Add known limitations to eheimdigital based on home-assistant/core#148263 (comment)
Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.