Pollen sensors show "Unknown" with upgrade to 0.67.0

[bachya]

Home Assistant release with the issue:

Last working Home Assistant release (if known):
0.66.1

Operating environment (Hass.io/Docker/Windows/etc.):
Raspberry Pi, Docker

Component/platform:
sensor/pollen

Description of problem:
As of 0.67.0, a number of the Pollen sensors show "Unknown":

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

sensor:
  - platform: pollen
    zip_code: "76231"
    monitored_conditions:
      - allergy_average_forecasted
      - allergy_average_historical
      - allergy_index_today
      - allergy_index_tomorrow
      - allergy_index_yesterday
      - disease_average_forecasted

Traceback (if applicable):

2018-04-14 21:12:23 ERROR (SyncWorker_1) [homeassistant.components.sensor.pollen] Pollen.com API didn't return any data
2018-04-14 21:12:23 ERROR (SyncWorker_12) [homeassistant.components.sensor.pollen] Pollen.com API didn't return any data
2018-04-14 21:12:24 ERROR (SyncWorker_10) [homeassistant.components.sensor.pollen] Pollen.com API didn't return any data
2018-04-14 21:12:24 ERROR (SyncWorker_8) [homeassistant.components.sensor.pollen] Pollen.com API didn't return any data
2018-04-14 21:12:24 ERROR (SyncWorker_5) [homeassistant.components.sensor.pollen] Pollen.com API didn't return any data
2018-04-14 21:12:54 ERROR (SyncWorker_15) [homeassistant.components.sensor.pollen] Pollen.com API didn't return any data
2018-04-14 21:12:54 ERROR (SyncWorker_18) [homeassistant.components.sensor.pollen] Pollen.com API didn't return any data
2018-04-14 21:12:54 ERROR (SyncWorker_16) [homeassistant.components.sensor.pollen] Pollen.com API didn't return any data
2018-04-14 21:12:54 ERROR (SyncWorker_14) [homeassistant.components.sensor.pollen] Pollen.com API didn't return any data

Additional information:

[bachya]

Looks like this has to do with the actual pollen.com website; will continue monitoring:

[grantalewis]

Seeing the same ~20 hours later.

[nordicblue]

pollen.com must be having some major difficulties with their service, as it is still down multiple days later. Going to disable it for now.....

[nordicblue]

I wanted to see if I am correct. The module uses pypollen 1.1.1, which is a Python website parses that then creates an API from the data is parses from the pollen.com website? Meaning, if Pollen.com changes their layout of how the data is presented, it will break the API as the data is no longer where it should be? And this is what happened?

[bachya]

@nordicblue: Close. pypollencom is a Python package that queries an unpublished API via pollen.com. The package is pretty resistant against changes to the data structure; in this case, however, the entire API went down, which is why the package isn’t receiving any responses at all.

It looks like the website is back up. I will look into this today and see if I can make any progress.

[dmwyatt]

@bachya pollen.com is throwing a 403 when using pypollencom. They've likely changed whatever auth mechanism...

[nordicblue]

@bachya, thanks for the response, explanation and also your hard work on this package:)

Noticed the site was back up, and the component was still having issues, so figured it had something to do with pollen.com changing something within their site.

I'll leave it to the experts, however, as I am definitely not a Python expert:)

[bachya]

Did some digging – looks like the API now requires:

• a non-empty User-Agent header
• a different Referrer header (consistent with the URL of the request)

Will obviously require a new version of pypollencom; I'll get working on that, then will submit a HASS PR to fix.

[bachya]

Version 1.1.2 of pypollencom published and local testing looks good – will submit the PR shortly:

[nordicblue]

Thanks, @bachya.

I attempted to upgrade to 1.1.2 with pip, but I assume that since HASS is calling version 1.1.1, upgrading just the pypollencom is not going to suffice, correct? No biggie, if so, I can hang tight until the next release of HASS to see the allergy reports on my dashboard. Just glad that there are people like yourself contributing to this great software. YOU ROCK! 👍

[arsaboo]

@nordicblue You can always add the fix to custom_components/sensor

[bachya]

@nordicblue Thanks for the kind words! Glad to help. @arsaboo is right on the money: if you want this right now, you can apply his instructions. I'm doing that – can't stand looking at Unknowns. 😆