Hi all,
my issue is solved with current version 2.2.0 of waste-collection-schedule. Thanks all for your help!
Cheers,
Stefan
Hello All,
maybe someone could help me here or has some advise.
In general the Waste Collection Schedule works more or less but its not possible to change any config via yaml files for me.
Neighter I see the location settings nor the created sensor settings. Just to validate, both should be findable in the configuration.yaml?
Currently I use this setting:
- Core2024.9.1
- Supervisor2024.09.1
- Operating System13.1
- Frontend20240906.0
Cheers
Marcus
The API returns concrete days and some kind of rhythm information, which is then turned into this long term calendar with some JavaScript magic, I looked into this a while back, and I think it wasn’t that straight forward. The WCS source only takes the concrete dates returned by the API (same endpoint used by the website). The concrete days may be further in the future or only show the next collection. Do you really need to know the collection further in the future? I may have another look at the JavaScript of the website on how to “predict” the following collections.
There are 2 ways to configure WCS:
- Throug the GUI: you configure everything from the GUI, You can only change setting in the GUI: sensor and other settings with the Configrue butten next to your source. And Source arguments using the reconfigure option (see image below)
- Through configuration.yaml: You configure everything in your configuration.yaml, You cannot change any setting with in the GUI
settings → Devices & Service → Waste Collection Schedule:
So no you should not see your GUI configured source in your confiugration.yaml. You need to change the configuration using the GUI
1 Like
I really just need to know the next week, maybe 2 so I would know when Yard waste is going to be in Spring and Fall. That way I know I need to do a clean up the weekend prior to the pickup. If I find out on Sunday that the pickup is that upcoming week I only have a day or 2 to accomplish it. I figured where it was picking up the recycling correctly it may just be reading the other 2 incorrectly as their site shows all 3 well into the future.
Great work on this custom component!
I had been manually adding collections to a calendar before this, so this should help a lot.
I was wondering though, my calendar has only populated two weeks into the future. Is this normal? It would be useful if it populated the whole year really.
It depends on the source you’re using, some (especially a lot of UK sources) only return a few collection dates. If you tell me the source you’re using, I can take a look
1 Like
Sure - it’s the Amber Valley, Derbyshire, UK source.
It’d be great if you could take a look. Thanks
I added a predict option to the ambervalley_gov_uk source, if set to True (ticked in GUI), the source tries to predict more dates in the future in ambervalley_gov_uk add predict argument, which tries to predict collections further in the future by 5ila5 · Pull Request #2707 · mampfes/hacs_waste_collection_schedule · GitHub
This will be part of the next release or is available now as master (git) version
install master/git: Developer tools → actions → select update: Install update → click Coose entity and select WCS → select version and type master in the input field → run the action → restart HA
install master with HACS version < 2.0: (3-dot menu → redownload → change version to master → fully restart HA (this will increase update cycle by a lot)
I take it that Amber Valley only has a couple of weeks data then? Seems odd why they wouldn’t just have a years worth. They send this info out (printed) so it’s not like they decide things on the fly as such. Anyhow - your new option sounds good!
I can’t see a ‘master’ option when I try to download through HACS though?
This is all I have:
We get the data from the server endpoint used to display the information you can finde here: Bin collection dates
So the data looks like this: https://info.ambervalley.gov.uk/WebServices/AVBCFeeds/WasteCollectionJSON.asmx/GetCollectionDetailsByUPRN?uprn=100030041980
HACS Removed the option to directly select the git branch if there are releases you need to use the first methods for HACS version 2.0 and higher:
install master/git: Developer tools → actions → select
update: Install update→ clickCoose entityand select WCS → selectversionand typemasterin the input field → run the action → restart HA
1 Like
Awesome - thanks for the instructions!
I’ve added the predict option to a new test calendar. It has indeed populated more items.
How does the prediction handle dates that are different to the norm? So as an example, at Christmas time the council have moved the bin day from the 26th to the 27th.
Will this get ‘corrected’ a couple of weeks before as the data is pulled in?
is it at all possible to have a look at “Dunedin District Council” around the same time this was starting to get updated so did they change by adding two new bin although only two of the four show up
cheers
It should always show the next collection (like the website) and add days to this for the predicted dates. I don’t know if the website properly shows the changed collection dates on holidays, but if so the prediction is probably Wrong around this time
I moved the source to the API used by the DCC Kerbside Collection APP, which is a lot easier to handle:
So same as above this will be part of the next update or can be used now using the master/development version
1 Like
I know it’s an old post but did you find any solution for this? Or is here a better integration that works for SOT?
Can you provide your error log?
The error you replied to was fixed here: fix stoke_gov_uk as some addresses my provide different date format by 5ila5 · Pull Request #1368 · mampfes/hacs_waste_collection_schedule · GitHub
So there is no way the exact same error shows up for you as well