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.

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

"The Feedreader YAML configuration import failed" when migrating to ConfigFlow configuration #121404

Closed
jeremysherriff opened this issue Jul 6, 2024 · 2 comments · Fixed by #121421

Comments

@jeremysherriff
Copy link

The problem

I have an RSS feed which, it appears, is not always available or does not comply with standards which then prevents the the YAML configuration from being imported.

When attempting to set up the feed manually I receive the error The URL seems not to serve any feed entries and I cannot proceed. I believe this should be a warning and allow continuation, rather than a terminating error.

Although the URL does return XML data, I suspect it does not return a required element.

This feed provides new data very infrequently, however when it does it is for matters of public safety.

What version of Home Assistant Core has the issue?

core-2024.7.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Feedreeder

Link to integration documentation on our website

https://www.home-assistant.io/integrations/feedreader

Diagnostics information

No response

Example YAML snippet

This is my original YAML configuration.  The problem feed is the last one (Civil Defense):

feedreader:
  urls:
    - https://alerts.home-assistant.io/feed.xml
    - https://www.health.govt.nz/feeds/media-atom.xml
    - https://www.civildefence.govt.nz/resources/rss

Anything in the logs that might be useful for us?

Enabling Debug logging for the Feedreeder integration does not appear to capture creation events.

Additional information

I have not previously noticed any errors in the log files regarding the feed not providing data, but without downgrading and checking I am unable to be 100% certain.

@home-assistant
Copy link

home-assistant bot commented Jul 6, 2024

Hey there @mib1185, mind taking a look at this issue as it has been labeled with an integration (feedreader) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of feedreader can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign feedreader Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


feedreader documentation
feedreader source
(message by IssueLinks)

@martin3000
Copy link
Contributor

I have the same problem with the URL https://warnung.bund.de/api31/mowas/rss/082260000000.rss
Normally there are 0 entries.
Changing async_step_user in config_flow.py fixes that:

        if not feed.entries:
            if self.context["source"] == SOURCE_IMPORT:
                return self.abort_on_import_error(
                    user_input[CONF_URL], "no_feed_entries"
                )
            feed_title = "-empty-"
        else:
            feed_title = feed["feed"]["title"]

@github-actions github-actions bot locked and limited conversation to collaborators Aug 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants