New custom integration: polleninformation (30+ European countries are supported)

[krissen (Kristian Niemi)]

Home Assistant: Pollen Information EU

Hello, dear fellow pollen sufferers!

Tired of sneezing your way through spring? Now you can track Europe’s pollen levels without turning your sofa into a tissue graveyard:

• 14 European countries supported (Austria → United Kingdom)
• Per-allergen sensors (birch, grass, ragweed…)*
• Air-quality metrics: ozone (O₃), PM₂.₅/PM₁₀, NO₂, SO₂, temperature & more*
• Multi-day forecast to plan your antihistamine doses
• Auto-updates every 8 hours—because pollen never sleeps

(Sensor availability varies by country.)

Pair it with the pollenprognos-card for a sneeze-proof Lovelace UI:
https://github.com/krissen/pollenprognos-card

Note, you need v2.2.0 of the card for compatibility with the integration! This version is still in pre-release. Still testing to make sure I’m not interrupting the current users, of other integrations, before I release this one. So try it out and let me know!

Installation (via HACS)

1. In HACS → Custom Repositories, add: https://github.com/krissen/polleninformation
2. Install Pollen Information EU
3. Restart Home Assistant
4. Go to Settings → Devices & Services → Add Integration, search for Pollen Information EU and enter your region & GPS coordinates

Come join the sniffle squad!

[krissen (Kristian Niemi)]

Apologies. After more thorough testing, v0.2.3 now has a pruned list of countries supported by polleninformation.eu. Current list is: Austria, Switzerland, Germany, Spain, France, United Kingdom, Italy, Lithuania, Latvia, Poland, Sweden, Türkiye, Ukraine, Holy See (Vatican City State).

[PhilO20 (Phil Olson)]

stopped working for me !

[krissen (Kristian Niemi)]

Hi,

Could you elaborate? What used to work, and what has stopped working in what manner?

The integration, entities, or the card and visualizations of it?

Kind regards,
Kristian

EDIT: I see no changes in my own testing; both card and integration are working. Let me know more details and I’ll look into it!

[NavNav]

that’s a nice integration! no chance for North America eh? especially Canada?

[krissen (Kristian Niemi)]

Hi,

So this particular integration is for the service polleninformation.eu which, I’m sure, won’t ever collect data from North America. So no chance for Canada, no.

That said, I’ve already added support for three integrations to the card. Adding support for additional integrations is not a problem. In other words, if you can get information about pollen levels for Canada into home assistant, let me know what integration you use, and I can look into adding support to the card.

For instance, I know there’s a Kleenex pollen radar integration in HACS. I think it supports USA but not Canada. There is a google pollen integration, but seems somewhat of a hassle to set up. There might well be others, in addition.

[sanji_japan (J)]

Hello, I installed both polleninformation (0.4.4) and pollenprognos-card (2.5.1). I requested and got an API key for the service.

However, I always get the message “Loading forecast…” and nothing else on the dashboard.

any suggestion on what to do ?

thanks !

[krissen (Kristian Niemi)]

Hi,

Have you successfully added a location? Are there entities provided by the polleninformation integration?

If that is the case, could you provide a screenshot or some such of said entities; it would look something like the below:

Let’s start there!

[sanji_japan (J)]

Thanks for the reply.

Yes I have defined the location

But I have no entities created

[krissen (Kristian Niemi)]

So the reason why the card shows loading forecast, but is unable to present results, is that the integration has not created entities. There is nothing to show.

The question is why entities aren’t created for you. I trust you have restarted HA after installation of the integration?

I tried adding the integration, using parts of your location (if that is your home location, you might want to remove the screenshot?), and I get the expected entities.

(Screenshot redacted)

(Screenshot redacted)

Could you enable debug logging in HA for this integration, example-code for configuration.yaml:

logger:
  default: warning
  logs:
    custom_components.polleninformation: debug

Adapt default to your current default, and add the last line to your possibly already existing logs: -list, or copy-paste the above into your configuration.yaml.

If you could provide the relevant log-lines you find for the polleninformation -integration? So we can see what is happening. Please obfuscate your API-key and possibly your location (truncate to two decimals or some such, and/or replacing them with a random number). You can also DM me the log-lines, if you don’t want to obfuscate. It might already be obvious from what you see in the logs as-is (having enabled debugging); it might be even more clear if you remove the location that you have, and add it again.

[krissen (Kristian Niemi)]

If you prefer UI rather than console, another way of getting debug info (should work), is

• enable debug logging in integration settings
  

  

• restart HA

• go back to integration settings; turn off debug logging

• HA should now offer a log file for download. It should contain what we want.

(I’m using a lot of “should” because I don’t normally do it like this, but just tested and seems to work.)

[sanji_japan (J)]

Thanks for following up, I removed my picture - but I can’t remove it from your answer

First question, your screenshop shows “PollenInfo.org”, while mine shows “Polleninformation EU”. Is that normal ? The rest seems identical !

[krissen (Kristian Niemi)]

I’ve redacted the images.

First question, your screenshop shows “PollenInfo.org”, while mine shows “Polleninformation EU”. Is that normal ? The rest seems identical !

Not sure why it is different. Don’t think it matters.

Did you manage to get some logs?

[sanji_japan (J)]

Yes indeed,
It seems that the problem is the API key. It is not sent at all

2025-08-22 16:30:23.354 DEBUG (MainThread) [custom_components.polleninformation] INIT: Setup entry with lat=46.0000, lon=7.0000, country=CH, lang=de, apikey=
2025-08-22 16:30:23.356 DEBUG (MainThread) [custom_components.polleninformation] COORDINATOR: Update data with lat=46.0000, lon=7.00000, country=CH, lang=de, apikey=
2025-08-22 16:30:23.356 DEBUG (MainThread) [custom_components.polleninformation.api] Calling polleninformation.at: https://www.polleninformation.at/api/forecast/public?country=CH&lang=de&latitude=46.0000&longitude=7.0000&apikey=
2025-08-22 16:30:23.546 DEBUG (MainThread) [custom_components.polleninformation] COORDINATOR: API result: {'error': 'missing api key'}
2025-08-22 16:30:23.546 DEBUG (MainThread) [custom_components.polleninformation] Finished fetching polleninformation data in 0.190 seconds (success: True)
2025-08-22 16:30:23.572 WARNING (MainThread) [custom_components.swissweather.coordinator] Pollen code not set, not loading current state.

[sanji_japan (J)]

However the key is defined correctly in the options in HA…

[krissen (Kristian Niemi)]

At least we know the reason for failure!

Could you send me a PM with a screenshot of your full config for the polleninformation location entry? Including both coordinates and API key? (Wouldn’t ask otherwise, but not sure how I can troubleshoot further without it.)

[sanji_japan (J)]

So I deleted everything, restarted HA and reinstalled everything. This time it worked, and got the entities created normally !

The only thing I see being done different is that at the first installation, I did not have the API key ready so I added it later.
This time I introduced directly the API key at installation.

Not sure if this is the reason, but in all cases thanks for looking and happy it works now !

Thanks again

[sanji_japan (J)]

And by the way, if you put the threshold too low (like 2 if nothing is above 1…) then you still get the message “Loading forecast…”, but this could be a card issue.

[krissen (Kristian Niemi)]

Happy to hear it got sorted!

if you put the threshold too low (like 2 if nothing is above 1…) then you still get the message “Loading forecast…”, but this could be a card issue.

That is indeed a card issue. It currently doesn’t differentiate well enough between different reasons for allergens not being shown, but shows the same message regardless — even though the text might not be apt for the situation. I haven’t found it to be too big of a deal to do something about it. Thank you for reminding me about the issue.

[krissen (Kristian Niemi)]

Hopefully, the latest release(s) of the card might have amended this issue somewhat.