Problems with HA 2022.2.1 / 2022.2.2?
See original GitHub issueHi, 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.
Issue Analytics
- State:
- Created 2 years ago
- Comments:15 (4 by maintainers)
Top Results From Across the Web
Upgrade core to 2022.2.2 fails - Home Assistant OS
When updating core 2021.12. 10 → 2022.2. 2 afterwards de webgui is not reachable anymore and doesn't work. Command line is still active....
Read more >Energy Dashboard showing only 0 values since 2022.2.1 ...
The problem Energy Dashboard stopped reading values after 2022.2.1 update. Sensors are showing correct values in developer menu, ...
Read more >Problems with Core Upgrade Past 2022.6.6 : r/homeassistant
I tried running an “ha core update” in terminal and it gave the same error. There's connectivity to the device, I've done full...
Read more >What's new in first release of 2022(.2) for Home Assistant
This video has been recorded on BETA 3 version of HA 2022.2, but most of the things should be present or stay same...
Read more >IntelliJ IDEA 2022.2 crashes silently when loading any project
PluginManager - Problems found loading plugins: The Design Tools ... IntelliJ IDEA 2022.2.2 (Ultimate Edition) Build #IU-222.4167.29, built on September 13, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fixed in release 1.16.0
Works well, thank you