core
core copied to clipboard
EnTur (Norwegian public transport) fails to load
The problem
Since updating to HA 2022.7.2, the "entur" integration fails to load. There has been no changes to my configuration (packages)
What version of Home Assistant Core has the issue?
core-2022.7.2
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
EnTur
Link to integration documentation on our website
https://www.home-assistant.io/integrations/entur_public_transport/
Diagnostics information
No response
Example YAML snippet
##########################################################################
# EnTur
#
# Note:
# "EnTur" is a standard integration already present in HomeAssistant
# https://www.home-assistant.io/integrations/entur_public_transport/
# It is "dormant", i.e. is not loaded by HA unless called for by the
# "- platform: entur_public_transport" statement in configuration file
# Note: The description in this link also explains how to find the ID for
# YOUR particular "StopPlace". Note also that a StopPlace can have several
# PlatformId. This may be important if you wish to have e.g. only one
# direction.
#
# To properly display the data retrieved, use the "Entur Card" in HACS
# authored by https://github.com/jonkristian
#
# EXPLANATION FOR CODE/SETUP BELOW:
#
# There are two bus lines of main interest to me/my family, even though
# there are several other bus lines.
# Also, I wish to have the NEXT bus from both bus lines displayed on the
# main screen on the tablet main controller, and a sub-page with many more
# departures for the same bus lines.
# As the EnTur card can only display the entire array of data retrieved, I
# needed to have two "sensors" for each bus line of interest; one with
# the next two departures, and another with many more depatures.
#
# Changes:
# 2022-04-03 Moved from configuration.yaml to packages/entur.yaml
# 2022-04-04 Added comments, added EnturCard code in comments for clarity
#
##########################################################################
sensor:
#
- platform: entur_public_transport
name: Transport130
expand_platforms: true
show_on_map: true
number_of_departures: 6
stop_ids:
- "NSR:StopPlace:3771" # Clausenbakken
line_whitelist:
- "RUT:Line:130"
#
#
- platform: entur_public_transport
name: Transport130_small
expand_platforms: true
show_on_map: true
number_of_departures: 2
stop_ids:
- "NSR:StopPlace:3771" # Clausenbakken
line_whitelist:
- "RUT:Line:130"
#
#
- platform: entur_public_transport
name: Transport150
expand_platforms: true
show_on_map: true
number_of_departures: 6
stop_ids:
- "NSR:StopPlace:3776" # Stabekk Kino
line_whitelist:
- "RUT:Line:150"
#
#
- platform: entur_public_transport
name: Transport150_small
expand_platforms: true
show_on_map: true
number_of_departures: 2
stop_ids:
- "NSR:StopPlace:3776" # Stabekk Kino
line_whitelist:
- "RUT:Line:150"
#
#################################################################
#
# EnTur Card used in MainScreen
#
# - type: custom:entur-card
# name: []
# show_clock: false
# show_next: true
# show_human: true
# show_extra_departures: true
# entities:
# - entity: sensor.transport130_small_clausenbakken_platform_6747
# name: Clausenbakken
# - type: custom:entur-card
# name: []
# show_clock: false
# show_next: true
# show_human: true
# show_extra_departures: true
# entities:
# - entity: sensor.transport150_small_stabekk_kino_platform_6756
# name: Stabekk Kino
#
##################################################################
#
# EnTur Card used in SubScreen
#
#type: horizontal-stack
#cards:
# - type: vertical-stack
# cards: []
# - type: custom:entur-card
# name: Rutetider
# show_clock: true
# show_next: false
# show_human: true
# show_extra_departures: true
# entities:
# - entity: sensor.transport130_clausenbakken_platform_6747
# name: Clausenbakken
# destination: Skøyen
# - type: vertical-stack
# cards:
# - type: custom:entur-card
# name: Rutetider
# show_clock: true
# show_next: false
# show_human: true
# show_extra_departures: true
# entities:
# - entity: sensor.transport150_stabekk_kino_platform_6756
# name: Stabekk Kino (Vest)
# destination: Oslo Bussterminal
# - type: vertical-stack
# cards: []
Anything in the logs that might be useful for us?
2022-07-10 22:37:10 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform entur_public_transport is taking over 10 seconds.
2022-07-10 22:37:10 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform entur_public_transport is taking over 10 seconds.
2022-07-10 22:37:10 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform entur_public_transport is taking over 10 seconds.
2022-07-10 22:37:10 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform entur_public_transport is taking over 10 seconds.
2022-07-10 22:37:10 ERROR (MainThread) [homeassistant.components.sensor] Setup of platform entur_public_transport is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2022-07-10 22:37:10 ERROR (MainThread) [homeassistant.components.sensor] Setup of platform entur_public_transport is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2022-07-10 22:37:10 ERROR (MainThread) [homeassistant.components.sensor] Setup of platform entur_public_transport is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2022-07-10 22:37:10 ERROR (MainThread) [homeassistant.components.sensor] Setup of platform entur_public_transport is taking longer than 60 seconds. Startup will proceed without waiting any longer.
Additional information
No response
entur_public_transport documentation entur_public_transport source (message by IssueLinks)
Hey there @hfurubotten, mind taking a look at this issue as it has been labeled with an integration (entur_public_transport
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
Are there any plans for fixing this integration, or do we just give up and remove our sensors? This issue is still present in 2022.7.6.
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.