[Bug]: Issue with Roman Numerals in Date Names Leading to Incorrect Calendar Matches

[Bleialf]

I Have A Problem With:

A specific source

What's Your Problem

Here's your GitHub issue formulation:

Title: Issue with Roman Numerals in Date Names Leading to Incorrect Calendar Matches

Hi,
First off, I want to say this is an awesome repository—thanks for all the hard work!

I recently set it up and encountered a minor issue related to the Roman numbering scheme in my source.

Source: umweltverbaende_at (Baden)
Source URL: https://baden.umweltverbaende.at/?gem_nr=30605&jahr=2025&kat=32&vb=bn

The names of the dates in the source follow this pattern:

"Abfuhrbereich II: Restmüll"
"Abfuhrbereich III: Restmüll"
My specific Rayon is "Abfuhrbereich II: Restmüll." However, when I add this to my calendar, events for "Abfuhrbereich III: Restmüll" are also added.

I suspect this might be due to a regex match issue, where "Abfuhrbereich III" is mistakenly included. Unfortunately, I haven’t had the chance to dive into the code to verify this yet.

For now, I’ve worked around the issue by setting the calendar to "Abfuhrbereich II:" which seems to resolve it.

Quick heads-up:
If there’s a specific setting or configuration I missed that could fix this, please let me know.

Thanks again for this great tool!

Best regards,
Kevin

Source (if relevant)

umweltverbaende_at

Logs

Relevant Configuration

Checklist Source Error

• Use the example parameters for your source (often available in the documentation) (don't forget to restart Home Assistant after changing the configuration)
• Checked that the website of your service provider is still working
• Tested my attributes on the service provider website (if possible)
• I have tested with the latest version of the integration (master) (for HACS in the 3 dot menu of the integration click on "Redownload" and choose master as version)

Checklist Sensor Error

• Checked in the Home Assistant Calendar tab if the event names match the types names (if types argument is used)

Required

• I have searched past (closed AND opened) issues to see if this bug has already been reported, and it hasn't been.
• I understand that people give their precious time for free, and thus I've done my very best to make this problem as easy as possible to investigate.