-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Don't use that many State Attributes #71
Comments
That's a good hint, will dig into this. Thank you! |
@mawoka-myblock I thought about this but the
But we should keep that in mind when someone have this issue. I gonna pin that issue for further references. |
maybe create a "device" per spool? |
Oh, I'd also suggest removing the good first issue label, as I'd say that this isn't one. |
That could be indeed a reasonable alternative. I will consider this! |
Currently I'm evaluating the possibility to create "Hubs" für every storage location and within that a device per spool and for every attribute an own entity. Something like Meross Integration is doing here: But at the moment we're pretty busy with renovating our kitchen so that need some time. But with that refactoring I gonna address this problem #103 as well. |
tbh, I don't even use your integration, just stumbled upon it, so take your time. If you should still need help, feel free to ask |
Checklist
Is your feature request related to a problem? Please describe.
The usage of state attributes could make the database size increase quickly.
Describe the solution you'd like
Create dedicated sensors, especially for remaining and used weight, since that is update pretty frequently
Describe alternatives you've considered
Maybe not that important?
Additional context
https://developers.home-assistant.io/docs/core/entity/#generic-properties
The text was updated successfully, but these errors were encountered: