[NextBus] SFMTA not supported

[drozycki]

The problem

I'm trying to use the NextBus integration to show SFMTA arrival times near my home. NextBus (now UmoIQ) supports the SFMTA (link), but the SFMTA does not show up in the agency dropdown when configuring the integration! This is probably because the agencyList API call omits this (and many other) agencies. There used to be a workaround (specify agency tag sfmta-cis in configuration.yml) but support for that was dropped by this PR three months ago!

What version of Home Assistant Core has the issue?

core-2024.7.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

NextBus

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

sensor:
  - platform: nextbus
    name: "Outbound K"
    agency: sfmta-cis
    route: K
    stop: "6991"

Anything in the logs that might be useful for us?

No response

Additional information

I have raised this issue at info@cubicsystems.com (NextBus/UmoIQ parent company) but frankly I am not confident that they will fix their API anytime soon. I also reached out to the SFMTA.

[home-assistant]

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

Code owner commands

Code owners of nextbus 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 nextbus 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)}}

---

nextbus documentation
nextbus source
_{^{(message by IssueLinks)}}

[drozycki]

CC'ing the author and reviewer of the PR which broke the workaround @jpbede @joostlek

Why was configuration.yaml support removed? Can we revert that change?

I suppose we could hardcode SFMTA in config_flow.py: _get_agency_tags if you prefer.

I'd be happy to whip up a PR whatever is decided.

[joostlek]

Apparently APIs changed and a PR is open to recruit the whole thing

[drozycki]

#121133

[drozycki]

Thanks for merging the fix to dev last week. I noticed the commit was not included in 2024.7.4. Do you expect it to release in 2024.8.0 next week?

[drozycki]

I confirmed that the issue is resolved in today's 2024.8.0 release. Thanks all for getting this out so quickly!