SCAN_INTERVAL is being used and MIN_TIME_BETWEEN_UPDATES limits the amount of updates.
So what actually happens is afvalwijzer only updating once per hour. When you put debug logging on, you’ll see what is actually happening. Maybe something else is slowing down your system. I removed these values before, but due to reponsive issues I re-added those values again.
If I remove SCAN_INTERVAL, and restart HASS, then HASS will only update afvalwijzer after an hour, not sooner.
yes, I noticed that too…and even now it doesn’t always initiate at startup, will test some more to see if an error is thrown or something else is amiss.
as you can see, the component creates 4 sensors, which I have displayed in the Glance Next pickups. Only thing is, the first one is todays pickup…
It would be wonderful if the Component would create these sensors, taking into account it should skip today. Just as it does now for the count_today option (which I have not set to use the default value false), in the understanding that’s what’s needed to have it skip today in the counting of the next days. Which works perfectly now indeed.
So, could you please have a look if this is alright?
update @xirixiz did you have a chance to look at this please? What could I do to assist in realizing the component to skips todays pickup for the next pickup dates?
Where can I find the bigger icons?
I have a pick up day which is combined both the GFT and Plastic. I got this working, but the icon on mijnafvalwijzer itself is very small.
I am looking for this one, but then the bigger variant:
As I had some time over I decided to create some icons in vector format. Not the best I ever created, but it should solve your need (and maybe the need of someone else)
which is the default for count_today: false which makes the sensors
{{states('sensor.saver_trash_first_next_in_days')}}, {{states('sensor.saver_trash_first_next_date')|capitalize}} and {{states('sensor.saver_trash_first_next_item')|capitalize}}
correct, as displayed in my screenshot above.
the listing below that is not correct though, because it also shows todays pickup.
@xirixiz
there’s a typo in line 134 of the python library not sure if that was already picked up. Doesn’t seem to hurt anything though, I’ve never seen an error…
if you’re looking at it, semantics might be improved on that same first_next_in_days. Either trash_first_in_days, or maybe even better make it trash_next_in_days.
which would give the opportunity to also improve the naming of the other 2 sensors using first, into trash_next_date and trash_next_item.