No module named 'google.transit'

[zelial]

Describe the bug
Can't add the integration to HA. This error message is displayed in the UI:

Config flow could not be loaded: {"message":"Invalid handler specified"}

And this appears in the container's log:
2024-02-29 21:25:03.830 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading flow for integration gtfs2: No module named 'google.transit'

Release used
gtfs2 v0.3.8
HA 2024.2.5 container

[vingerha]

I cannot reproduce this. Did a complete fresh install of the container and the app and used my reference source for static and realtime data....all fine
What is your source and where (!) in the process/screen does it crash?

[zelial]

I ... cant reproduce it now either. I don't remember it exactly but it occurred before the config wizard asks about data source addition/deletion. Anyway, sorry for the confusion, I"m closing this issue.

[vingerha]

If it is the first install, it was possibly still loading the required python modules....no clue though as not reproducable ...and it works now :)

[ppoloskov]

I'm facing this problem right now.
HA in container under Kubernetes -- Core 2024.11.2 Frontend 20241106.2
HACS installed. I added GTFS2 (tried version 0.5.4 and last beta).

When I try to add integration from Settings, I get error "Config flow could not be loaded: {"message":"Invalid handler specified"}" and I see in the logs
'''
2024-11-29 11:23:50.500 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading flow for integration gtfs2: No module named 'google.transit'
'''
What information can I provide for debug?

[ppoloskov]

I also tried a few different gtfs integrations and all of them failing to find 'google.transit' module. Should I add some component to the core HA?

[vingerha]

Weird situation again, this comes via gtfs-realtime-bindings which is part of the requirememts for this integration, installed via manifest.json. Can you do a pip list | grep gtfs on cli of your container/HA and find out if it is installed? I have never installed this manually so wonder why there is this issue now a second time (reported twice with this ticket)

[github-actions]

This issue is stale because it has been open for 20 days with no activity.