Core: rmvtransport communication fails (rmv)

Created on 5 Aug 2019  路  11Comments  路  Source: home-assistant/core

Home Assistant release with the issue:

0.94.5

Last working Home Assistant release (if known):
sorry don't know exactly maybe V 0.91.1

Operating environment (Hass.io/Docker/Windows/etc.):

Dockervon Synology
Docker Image: https://hub.docker.com/r/homeassistant/home-assistant

Component/platform:

Description of problem:
see log below

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

 - platform: rmvtransport
    scan_interval: 120
    timeout: 10
    next_departure:
      - station: 3002398
        time_offset: 5
        destinations:
          - 'Frankfurt (Main) Dornbusch'
        products:
          - 'U-Bahn'
          - 'Bus'
        name: 'Abfahrt zum Dornbusch/S眉dbahnhof'
        max_journeys: 5
      - station: 3002398
        products: 'U-Bahn'
        destinations:
          - 'Bad Homburg v.d.H.-Ober-Eschbach (U)'
        name: 'Abfahrt nach Ober-Eschbach/Gonzenheim'
        time_offset: 6
        max_journeys: 5

Traceback (if applicable):

Additional information:

@cgtobi ask me to open here a bug: maybe a backend problem?

2019-08-02 21:21:26 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 30 seconds.
2019-08-02 21:21:57 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 60 seconds.
2019-08-02 21:22:58 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 90 seconds.
2019-08-02 21:24:29 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 120 seconds.
2019-08-02 21:26:30 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 150 seconds.
2019-08-02 21:29:01 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 180 seconds.
2019-08-02 21:32:02 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 180 seconds.
2019-08-02 21:35:03 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 180 seconds.
2019-08-02 21:38:04 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 180 seconds.
2019-08-02 21:41:05 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 180 seconds.
2019-08-02 21:44:06 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 180 seconds.
2019-08-02 21:47:07 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 180 seconds.
2019-08-02 21:50:08 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 180 seconds.
rmvtransport
Source
picture lebherz

All 11 comments

Hi @lebherz, please use the issue template as it guides you to give valuable information to help debug this issue.

cgtobi picture cgtobi on 5 Aug 2019
👍1

@lebherz The issue is related to the destination of the first journey.

        destinations:
          - 'Frankfurt (Main) Dornbusch'

I'll investigate why that causes trouble. In the meantime you can remove that as a workaround.

cgtobi picture cgtobi on 11 Aug 2019
👍1

Hi @cgtobi!

Jackpot!
in the past it worked with the name of the destination.
Now I insert the ID from here

 - platform: rmvtransport 
    scan_interval: 120
    timeout: 10
    next_departure:
      - station: 3002398
        time_offset: 5
        destinations:
          - 3001301
        products:
          - 'U-Bahn'
          - 'Bus'
        name: 'Abfahrt zum Dornbusch/S眉dbahnhof'
        max_journeys: 5
      - station: 3002398
        products: 'U-Bahn'
        destinations:
          - 3002312
        name: 'Abfahrt nach Ober-Eschbach/Gonzenheim'
        time_offset: 6
        max_journeys: 5

and it worked!
Thanks!

lebherz picture lebherz on 11 Aug 2019
👍1

Sorry @cgtobi after a third reload.. the error came back. 

2019-08-11 22:17:06 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 30 seconds.
2019-08-11 22:17:37 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 60 seconds.
2019-08-11 22:18:38 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 90 seconds.
2019-08-11 22:20:09 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 120 seconds.
2019-08-11 22:22:10 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 150 seconds.
2019-08-11 22:24:41 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 180 seconds.
lebherz picture lebherz on 12 Aug 2019

hi,

have the same problem:

Home Assistant release with the issue:

Platform **Component/platform:**not ready yet. Retrying in 150 seconds.

Please provide details about your environment.

Component/platform:

  • io.hass.arch: amd64
  • io.hass.base.image: homeassistant/{arch}-homeassistant-base
  • io.hass.base.name: python
  • io.hass.base.version: 4.0
  • io.hass.type: homeassistant
  • io.hass.version: 0.98.5

  • maintainer: Paulus Schoutsen Paulus@PaulusSchoutsen.nl

  • Full message:

2019-09-15 08:50:47 WARNING (MainThread) [homeassistant.components.sensor] Platform rmvtransport not ready yet. Retrying in 180 seconds.
  • configuration.yaml
...
sensor: !include_dir_merge_list sensor
  • sensor/bahn.yaml
- platform: rmvtransport
  scan_interval: 120
  timeout: 10
  next_departure:
    - station: 3004732
      destinations:
        - 3000525
      products:
        - 'S'
      name: 'Abfahrt Wixhausen'
    - station: 3000525
       products:
        - 'S'
      destinations:
        - 3004732
      name: 'Abfahrt Ostendstrasse'
linuxmail picture linuxmail on 15 Sep 2019

Hi @cgtobi !
any idea?

best regards
rene

lebherz picture lebherz on 15 Sep 2019

That is really curious, I don't have any issues on my system. I'll try to setup a test environment to replicate your setup as soon as possible.

cgtobi picture cgtobi on 15 Sep 2019

Great! If you need any support, let me know!

lebherz picture lebherz on 15 Sep 2019

Hi @lebherz, sorry for the very long delay. I had a look at that issue and I really wonder why destinations: - 3000525 ever worked. It should be a station name like 'Frankfurt (Main) Hauptwache'. This gave me results. But I'll have look how I can make it hand errors more gracefully. I still don't understand why it doesn't even load.

This worked fine for me:

- platform: rmvtransport
    scan_interval: 120
    timeout: 10
    next_departure:
      - station: 3004732
        destinations:
          - 'Frankfurt (Main) Hauptwache'
        products:
          - 'S'
        name: 'Abfahrt Wixhausen'
cgtobi picture cgtobi on 26 Nov 2019
👍1

Hi @cgtobi! no problem.
after changing all HAFAS_ID in "NAME_FAHRPLAN" error disappeared!!!

this now worked for me: THANKS!!!

 - platform: rmvtransport
    scan_interval: 120
    timeout: 10
    next_departure:
      - station: 'Frankfurt (Main) Nieder-Eschbach'
        time_offset: 5
        destinations:
          - 'Frankfurt (Main) Dornbusch'
        products:
          - 'U-Bahn'
          - 'Bus'
        name: 'Abfahrt zum Dornbusch S眉dbahnhof'
        max_journeys: 5
      - station: 'Frankfurt (Main) Nieder-Eschbach'
        products: 'U-Bahn'
        destinations:
          - 'Bad Homburg v.d.H.-Ober-Eschbach (U)'
        name: 'Abfahrt nach Ober-Eschbach Gonzenheim'
        time_offset: 6
        max_journeys: 5

the follow does not

  - platform: rmvtransport
    scan_interval: 120
    timeout: 10
    next_departure:
      - station: 3002398
        time_offset: 5
        destinations:
          - 3001301
        products:
          - 'U-Bahn'
          - 'Bus'
        name: 'Abfahrt zum Dornbusch S眉dbahnhof'
        max_journeys: 5
      - station: 3002398
        products: 'U-Bahn'
        destinations:
          - 3002312
        name: 'Abfahrt nach Ober-Eschbach Gonzenheim'
        time_offset: 6
        max_journeys: 5
lebherz picture lebherz on 26 Nov 2019
👍1

Hey,

i've got exactly the same problem:

configration: 

# RMV
  - platform: rmvtransport
    scan_interval: 120
    timeout: 30
    next_departure:
      - station: 'Wiesbaden-Dotzheim Nordstrander Stra脽e'
        products:
          - 'Bus'
        destinations:
          - 'Wiesbaden-Nordenstadt Daimlerring'        
        time_offset: 6
        max_journeys: 5
        name: 'Abfahrt nach Nordenstadt - Daimlerring'
      - station: 'Wiesbaden-Dotzheim Nordstrander Stra脽e'        
        destinations:
          - 'Wiesbaden Dernsches Gel盲nde'
        products:          
          - 'Bus'
        time_offset: 5
        max_journeys: 5
        name: 'Abfahrt zum Dernschen Gel盲nde'

Logs:

Platform rmvtransport not ready yet. Retrying in 180 seconds.
13:47 helpers/entity_platform.py (WARNING) - Die Nachricht ist zum ersten Mal um 13:44 aufgetreten und erscheint 2 mal
Platform rmvtransport not ready yet. Retrying in 150 seconds.
13:42 helpers/entity_platform.py (WARNING)
Platform rmvtransport not ready yet. Retrying in 120 seconds.
13:40 helpers/entity_platform.py (WARNING)
Platform rmvtransport not ready yet. Retrying in 90 seconds.
13:38 helpers/entity_platform.py (WARNING)

Regards Marc

MarcE85 picture MarcE85 on 2 Dec 2019
Was this page helpful?
0 / 5 - 0 ratings

Related issues

flsabourin picture flsabourin  路  3Comments
kirichkov picture kirichkov  路  3Comments
Elmardus picture Elmardus  路  3Comments
neonandu picture neonandu  路  3Comments
ofuangka picture ofuangka  路  3Comments