Seattle provider only showing one date, two weeks from now about hacs_waste_collection_schedule HOT 6 CLOSED

fixed in #51

from hacs_waste_collection_schedule.

I did and it works great, thanks so much @gabsom! So convenient having thiis as part of HA, thank you!

from hacs_waste_collection_schedule.

+1, @sguermond , we'll need your help :) I did the digging but I'm not proficient with python (or Home Assistant development) so I won't be of much help coding here, but I figured out the issue.

looking at the code, you're using API calls from https://www.seattle.gov/UTIL/WARP/CollectionCalendar, however they are actually not returning the right information. for example, I used the Carmona Court street address from your test case (1127 17TH AVE E) and the WARP API returns different info than looking at it in the collection calendar.

This is WARP:

This is the collection calendar:

I took a look at the API calls made by the collection calendar that would yield the right result and packed the fiddler file here. Essentially what happens is:

• find account ID for a given address
• get token (uses basic auth and the customerID = guest
  -- subsequent requests include this bearer token in the headrs
• get account summary
• get calendar

I wish I could help, but I think you have everything you need here.

from hacs_waste_collection_schedule.

I got the code working that pulls the right schedule - will try to clone repro and send a PR in a couple of dyas

from hacs_waste_collection_schedule.

@millercentral - did you update to the latest version? it's working great for me now, curious if it is for you as well.

from hacs_waste_collection_schedule.

@millercentral & @gabosom Thanks for catching that and fixing it so quickly! I found the API in another repo (https://github.com/mannkind/seattlewaste2mqtt) and did notice that it wasn't always returning correctly, but I was pretty stumped as to why.

I'll send in a request to the city to see what's up with the WARP API.

from hacs_waste_collection_schedule.