You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tl;dr is that I was asking if we could add some way to track the number of books read. @cdubz mentioned I can use tags and they've thought about graphing before; and he thinks this should be possible via the API. I think I could keep track of the number of books read (and probably read over time via a sensor) in HA if we could have sensors added or some way to add a custom sensor. The sensor(s) would just be a 'count' of the number of tags within a specified amount of time. Perhaps 7, 30, 365 days, and all time would be sufficient.
What do you think? This seems to align with some other feature requests as well that are accomplished via notes+tags in BabyBuddy. If you point me in the right direction I could try and look at the code as well.
Thank you!
The text was updated successfully, but these errors were encountered:
Ahh yea I see you mention the same / a similar concept in this: #77 (comment)
Would this existing PR accomplish what I'm thinking? #78 (if so I can try to take a look; I'm not a python dev in the least but I could give it a shot.)
Background commentary: https://github.com/orgs/babybuddy/discussions/666
Tl;dr is that I was asking if we could add some way to track the number of books read. @cdubz mentioned I can use tags and they've thought about graphing before; and he thinks this should be possible via the API. I think I could keep track of the number of books read (and probably read over time via a sensor) in HA if we could have sensors added or some way to add a custom sensor. The sensor(s) would just be a 'count' of the number of tags within a specified amount of time. Perhaps 7, 30, 365 days, and all time would be sufficient.
What do you think? This seems to align with some other feature requests as well that are accomplished via notes+tags in BabyBuddy. If you point me in the right direction I could try and look at the code as well.
Thank you!
The text was updated successfully, but these errors were encountered: