-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
Confused re new version #342
Comments
The error is just a reminder that it removed the parameters, that were previously obsolete and now are removed.
So my conclusion is, that your configuration is fine and simple as you say. Previously, you had it over-complicated, proabably becase it was so complicated and confusing (which was the reasn for the change). Ok? |
HI
So in March when the green bin starts its 3 week cycle how should i implement it correctly ? |
Ok, so you need to have 2 entities, both with 14 days period, but one with a starting date a week later than the other. For the 3rd one, just configure the first month and last month - that's a standard config on the second screen. I think you have that configured. And you need to configure it either every 21 days (3 weeks) starting from a chosen date. The challenge here is, that it will repeat evey 21 days starting from the initial date, and it will just cut out the two months. So when you configure it to start on March 7 2022, for next year it will start in a multiply of 21 days from March 7, 2022 - that will be March 20 I am afraid. This is how it always worked, I did not change a thing in this. So you'd have to adjust the config next year to start on March 6 next year. Or, you can now configure it for a weekly schedule, configure it for a manual update and then make an automation to drop the collections in the two weeks in between. So technically, it is now possible (was not before). But if this is not your thing, I'd leave it there. |
HI The configuration via configuration.yaml has been deprecated. If you have previously configured the integration there, it will be imported to ConfigFlow, and you should remove it. |
After you submit. But it looks like you found a bug. Let me check.... |
#342 - Fix configuration for every-n-days
That's interesting, I had this out for quite some time, but nobody found this. Anyhow, i just made a release fixing the first issue. I cannot replicate the other one, that one works fine for me. |
Well at least it was found early :) |
I have the new version but i think the day calcs are out.
|
Feb 9 2021 was Tuesday. Today is Tuesday. So the collection should today, not tomorrow. |
Sorry I didn't see the year default back to 2021 |
Now it is working pure genius very easy to use well done |
Write your question here
HI
I have just updated and read your well explained latest version, but i didn’t fully understand it sorry.
My is an extremely basic setup Brown & Black Bin every two weeks but my Green waste is every 3 weeks but stops for several months over Xmas.
I had it running correctly but now i am getting a log error, but on the frontend, it still looks correct.
I don’t understand what i am supposed to do you mention 2 stages and 10 different blueprints seems more complicated than before :)
This error originated from a custom integration.
Logger: custom_components.garbage_collection
Source: custom_components/garbage_collection/init.py:324
Integration: Garbage Collection (documentation, issues)
First occurred: 16:48:34 (3 occurrences)
Last logged: 16:48:34
Removed data config {'offset': 21, 'holiday_in_week_move': False, 'holiday_move_offset': 1, 'observed': True, 'include_dates': ['2022-03-07']}. Please check the documentation how to configure the functionality.
Removed data config {'offset': 14, 'holiday_in_week_move': False, 'holiday_move_offset': -2, 'observed': True}. Please check the documentation how to configure the functionality.
Removed data config {'offset': 14, 'holiday_in_week_move': False, 'holiday_move_offset': 1, 'observed': True}. Please check the documentation how to configure the functionality.
Diagnotics see here
The text was updated successfully, but these errors were encountered: