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

NMBS API failed #91204

Closed
Mariusthvdb opened this issue Apr 11, 2023 · 5 comments
Closed

NMBS API failed #91204

Mariusthvdb opened this issue Apr 11, 2023 · 5 comments

Comments

@Mariusthvdb
Copy link
Contributor

Mariusthvdb commented Apr 11, 2023

The problem

seeing below errors for the first time in HA logs

seems rather nasty, because the API error prevents the HA startup, and makes it take about 3 minutes

What version of Home Assistant Core has the issue?

2023.4.2

What was the last working version of Home Assistant Core?

2023.3.x

What type of installation are you running?

Home Assistant OS

Integration causing the issue

NMBS

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.nmbs.sensor
Source: components/nmbs/sensor.py:299 
Integration: nmbs (documentation, issues) 
First occurred: 08:09:35 (1 occurrences) 
Last logged: 08:09:35

API failed in NMBSSensor


Logger: homeassistant.bootstrap
Source: bootstrap.py:499 
First occurred: 08:09:10 (2 occurrences) 
Last logged: 08:10:10

Waiting on integrations to complete setup: sensor.nmbs_3


Logger: homeassistant.components.nmbs.sensor
Source: components/nmbs/sensor.py:168 
Integration: nmbs (documentation, issues) 
First occurred: 08:11:25 (3 occurrences) 
Last logged: 08:12:20

API failed in NMBSLiveBoard

Additional information

No response

@Mariusthvdb Mariusthvdb changed the title NMBS API error NMBS API failed Apr 11, 2023
@home-assistant
Copy link

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

Code owner commands

Code owners of nmbs 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 nmbs Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


nmbs documentation
nmbs source
(message by IssueLinks)

@Mariusthvdb
Copy link
Contributor Author

Mariusthvdb commented Jun 17, 2023

just keeping this alive:

Logger: homeassistant.components.nmbs.sensor
Source: components/nmbs/sensor.py:303 
Integration: nmbs (documentation, issues) 
First occurred: 16 juni 2023 om 20:16:28 (3022 occurrences) 
Last logged: 11:26:55

API returned invalid connection: {'error': 500, 'message': 'Could not get data: This request failed due to internal errors.. Please report this issue at https://github.com/irail/irail/issues/new'}
API returned invalid connection: {'error': 404, 'message': 'No results found'}
API returned invalid connection: {'error': 504, 'message': 'Could not get data: An upstream server experienced a timeout while obtaining this data. Please report this issue at https://github.com/irail/irail/issues/new'}
API returned invalid connection: {'error': 504, 'message': 'Could not get data: No response from NMBS/SNCB. Please report this issue at https://github.com/irail/irail/issues/new'}

its reported upstream: iRail/iRail#478

why the thumbs down @thibmaek ?

@thibmaek
Copy link
Contributor

I no longer want to maintain this component, hence the 'no' reaction.

Read somewhere that NMBS would start blocking access to scraping/api by third parties, perhaps that's what's happening here. I would check the irail repo for any open issues.

@Mariusthvdb
Copy link
Contributor Author

right, for a moment I figured you didnt like me reporting this. understood.
Ill try and filter the errors, they are infuriating.
making this integration truly unreliable.

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 22, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Oct 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants