Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Problems with HA 2022.2.1 / 2022.2.2? #164

Closed
H4rl3k1n opened this issue Feb 4, 2022 · 15 comments
Closed

Problems with HA 2022.2.1 / 2022.2.2? #164

H4rl3k1n opened this issue Feb 4, 2022 · 15 comments

Comments

@H4rl3k1n
Copy link

H4rl3k1n commented Feb 4, 2022 •
edited
Loading

Hi, since HA 2022.2.1 my waste dates wont come up anymore, it worked well with 2022.2.0 and older versions. Errormessage:
fetch failed for source <waste_collection_schedule.source.ics.Source object at 0x7f89189190>: 'NoneType' object has no attribute 'upper'
I havent changed anything with the source-file, just updated HA to latest version.
Please have a look at this, thanks in advance.
@JimmyGiant
Copy link

Hey, I have the same issue. In my case since the end of december 2021 the integration keeps breaking and then suddenly working again after some time. I had no trouble whatsoever in the twelve months before and I have not changed anything besides the updates. My local waste-service is not yet integrated so I am using a link to the .ics file. Since 2022.2.1 it stopped working again. Hope it helps, thanks!

@bairnhard
Copy link

Same problem here.
My quick fix: I created a google calendar, imported the ics there, and use the google calendar iCal URL in HA. That solved it for now.

@mampfes
Copy link
Owner

mampfes commented Feb 4, 2022

Please share your config and ics file. I'm not able to reproduce it so far.

@H4rl3k1n
Copy link
Author

H4rl3k1n commented Feb 5, 2022 •
edited
Loading

Hey @mampfes , thanks for checking this issue.

Heres my config:

configuration.yaml

waste_collection_schedule:
  sources:
    - name: ics
      args:
        file: "www/abfuhrkalender/Abfuhrkalender-Forstern-2022.ics"
      customize:
        - type: Restmüll in Forstern
          show: true
          icon: mdi:trash-can
        - type: Biotonne in Forstern
          show: true
          icon: mdi:trash-can
        - type: Papiertonne in Forstern
          show: true
          icon: mdi:trash-can
        - type: Gelber Sack in Forstern
          show: true
          icon: mdi:recycle
      calendar_title: CALENDAR_TITLE
  fetch_time: "04:00"
  day_switch_time: "07:00"

sensors.yaml

- platform: waste_collection_schedule
  name: AbfallRestmuell
  details_format: upcoming
  value_template: '{{value.date}}'
  types:
    - Restmüll in Forstern

- platform: waste_collection_schedule
  name: AbfallBio
  details_format: upcoming
  value_template: '{{value.date}}'
  types:
    - Biotonne in Forstern

- platform: waste_collection_schedule
  name: AbfallPapier
  details_format: upcoming
  value_template: '{{value.date}}'
  types:
    - Papiertonne in Forstern

- platform: waste_collection_schedule
  name: AbfallgelberSack
  details_format: upcoming
  value_template: '{{value.date}}'
  types:
    - Gelber Sack in Forstern

I cant upload the ics file cause github doesnt allow it, but heres the link:
https://www.landkreis-erding.de/abfallwirtschaft/rund-um-die-entsorgung/abfuhrkalender-interaktiv/
City "Forstern", use any street you like, all the same file-format.

PS: i just updated to 2022.2.2 and used a fresh ics-file, still the same error:

Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: waste_collection_schedule.scraper
Source: custom_components/waste_collection_schedule/waste_collection_schedule/scraper.py:130
Integration: waste_collection_schedule (documentation)
First occurred: 08:31:55 (1 occurrences)
Last logged: 08:31:55

fetch failed for source <waste_collection_schedule.source.ics.Source object at 0x7f8d0c4c10>: 'NoneType' object has no attribute 'upper'

@H4rl3k1n H4rl3k1n changed the title Problems with HA 2022.2.1? Problems with HA 2022.2.1 / 2022.2.2? Feb 5, 2022
@saschaabraham
Copy link

saschaabraham commented Feb 5, 2022 •
edited
Loading

Same error here. Used an ICS file from my provider.

This is the link to the ICS- File https://awido.cubefour.de/Customer/awb-ak/KalenderICS.aspx?oid=7227d664-6b2a-484e-b786-68a5b3adf971&jahr=2022&fraktionen=&reminder=1.17:00 a direct import via url doesn't work. The conversion via google calender does.

@bairnhard
Copy link

bairnhard commented Feb 5, 2022 •
edited
Loading

Here's my config, that works.
the local file produced the same error as described above, but after uploading it to a google calendar, and reading it from there it just works. If you have a google account you can add as many calendars as you like, and you can even make them invisible so they don't interfere with whatever else you do with your Google account.


waste_collection_schedule:
  sources:
    - name: ics
      args:
        url: "https://calendar.google.com/calendar/ical/lalilu-verrat-ich-nicht%40group.calendar.google.com/private-trallala-auch-geheim/basic.ics"
        offset: 0
      customize: 
        - type: Papiertonne
          alias: papiermuell
          icon: mdi:trash-can
        - type: Restmuelltonne
          alias: restmuell
          icon: mdi:trash-can
        - type: Wertstofftonne
          alias: wertstoffmuell
          icon: mdi:recycle
  fetch_time: "04:00"
  day_switch_time: "11:00"

@H4rl3k1n
Copy link
Author

H4rl3k1n commented Feb 5, 2022

thanks @bairnhard, worked for me too. local file still not working, ics via google calendar works.

@fogowitz
Copy link

fogowitz commented Feb 9, 2022

Same Problem as H4rl3k1n same ics file "Landkreis" Erding.
Is there a solution beside the workarround with the google calendar?

mampfes added a commit that referenced this issue Feb 12, 2022
@mampfes
use icalevents instead of icalendar + recurring_ical_events
cf72f2a 
The icalevents python package is much more lightweight than icalendar +
recurring_ical_events.
recurring_ical_events also problems in some environments, see github issue:
#164
mampfes added a commit that referenced this issue Feb 12, 2022
@mampfes
use icalevents instead of icalendar + recurring_ical_events
74658e5 
The icalevents python package is much more lightweight than icalendar +
recurring_ical_events.
recurring_ical_events also problems in some environments, see github issue:
#164
@mampfes
Copy link
Owner

mampfes commented Feb 12, 2022

I create prerelease 1.16.0-pre2 which tries to address this issue. It uses a different python package to parse ICS data. Could s.o. test this please?
Note: You have to enable the switch "Show beta versions" in HACS to be able to see this pre-release.

@s--p
Copy link

s--p commented Feb 12, 2022

I create prerelease 1.16.0-pre2 which tries to address this issue. It uses a different python package to parse ICS data. Could s.o. test this please? Note: You have to enable the switch "Show beta versions" in HACS to be able to see this pre-release.

Just tried the 1.16.0-pre2 and for me it's working again.
Thanks a lot!

@H4rl3k1n
Copy link
Author

Hi, just tested your beta, it now works again with local file. Many thanks!

@tschnilo
Copy link
Contributor

I also tried the 1.16.0-pre2. And it works for me again too..
Thx!

@fogowitz
Copy link

fogowitz commented Feb 13, 2022 via email

mampfes added a commit that referenced this issue Feb 20, 2022
@mampfes
use icalevents instead of icalendar + recurring_ical_events
1f65571 
The icalevents python package is much more lightweight than icalendar +
recurring_ical_events.
recurring_ical_events also problems in some environments, see github issue:
#164
@mampfes
Copy link
Owner

mampfes commented Mar 6, 2022

Fixed in release 1.16.0

@mampfes mampfes closed this as completed Mar 6, 2022
@fogowitz
Copy link

fogowitz commented Mar 6, 2022

Works well, thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@mampfes @s--p @bairnhard @JimmyGiant @saschaabraham @H4rl3k1n @tschnilo @fogowitz