tofuschnitzel / home-assistant-wienerlinien Goto Github PK

Version of the custom_component
1.2.1

Describe the bug
I integrated Wienerlinien on my hassio through HACS and took the example in my configuration.yaml
But, when i try to use it as an entity in my lovelace i get only wienerlinien update, which does not response me the expected stops

Could someone help me with this?

When using this integration with a station id, that has multiple lines, it is completely being ignored which line is the first and next.

I think it's because this integration isn't actually looking into the data, but always takes the first line.

As an example:

• 10A: in 7 min, in 37min
• 11A: in 2 min, in 12min

I'd assume, that the first is 11A in 2min, and next is 10A in 7min.

What the integration does is: 10A (because first in the list) in 7min as first, and 10A in 37min as next.

Can you fix this please? :)

Thanks

Version of the custom_component

1.3.0 beta
Describe the bug
A clear and concise description of what the bug is.
If there is no data at the time of HA restart (during the night) - the sensors will never update once the morning comes
If the HA is restarted during the day, the sensors survive the night and show data once again the next morning
log

Can be provided if you tell me how...

I'd like to set up a stop for S3 at Jedlersdorf but the linked website does not seem to find any stops for that line (even though the line is listed in the drop-down menu)

The stops don't show up as entitys and I get the following Error message in the HA logs.

2022-06-21 18:39:55 WARNING (MainThread) [homeassistant.components.sensor] Platform wienerlinien not ready yet: None; Retrying in background in 30 seconds
2022-06-21 18:39:55 WARNING (MainThread) [homeassistant.components.sensor] Platform wienerlinien not ready yet: None; Retrying in background in 30 seconds

Version of the custom_component
Version 1.2.1

• platform: oebb
  evaId: 691662
  dirInput: 1360161
  showJourneys: 5

Describe the bug
Updating Entities.

Is there possibility to automatically Refresh Data?

Es sind zwar die letzten 2 Entities gewählt beide fahren aber Komischerweise an der selben uhrzeit weg. Gibts eine möglichkeit die Einträge automatisch zu Refreshen?

log

Add your logs here.

1.3

Not having countdown available any more severly limits the usage in a number of visualisations - bar cards with severity (like: red color if I can't make it from my behind to the station anyways, green if I can make it), placing the value in a custom map based on a picture,... all that does not seem to work (at least not for me) without a countdown-attribute.

prettyplease? ;-)

ahja: danke, tofuschnitzel, dass es dich gibt ;-))

log

Add your logs here.

Hey,

I have two stops with both directions added to the integration.
One of them has only one line, the other one two lines running from the stop.

I set up one "next" and one "first" sensor supplying all four IDs to each of the sensors. Now it sometimes happens that the generated sensors seem to change the platform / direction.

sensor.XXX_first_departure => platform 1
sensor.XXX_first_departure_2 => platform 2

and then it switches:

sensor.XXX_first_departure => platform 2
sensor.XXX_first_departure_2 => platform 1

I think it happens during restarting HA, but not always. However, I'm not 100% sure about that.

Thanks!

Christoph

Hi! I'm using the 2022.12.x (currently 2022.12.8) version of HA (OS) and I can't get the sensor to show up. The configuration is:

sensor:
# https://till.mabe.at/rbl/?line=170&station=32615
- platform: wienerlinien
  firstnext: first
  stops:
    - '303'

There is nothing in the logs either. I'm on 1.3.0-beta.

Adding two stops with the same name (Reglergasse, 97A) I would like to add a friendly name including the direction.

Describe the solution you'd like
either add support for friendly_name or an ID generation in the YAML so that a friendly name can be set in hte UI

• platform: wienerlinien
  stops:
  • "8641"
  • "8633"

I am using the integration succesfully for over 2 months now and everything seems to work fine for the most part. I've added the 3 closest stops to me in YAML and... well, only 2 work well. These two work actually very well, with accuracy in seconds!

The third stop gives always bogus info, and is 100% unreliable (not even once it gave a good estimate about when the tram was coming). I tried adding it multiple times and still nothing.

Furthermore it does not match the readings from Wien Mobil App which tells me there is something else involved here potentially.

Please let me know what type of info you need, and I will make sure to post it here!

Thank you tofuSchnitzel!

Allow to get both: first and next.

• platform: wienerlinien
  firstnext: both
  stops:
  • "8641"
  • "8633"

If i add more then 4-6 Sensors to the configuration file, the sensors wont show up and partially disappear after restarting HA.
I am using HA in docker and the Beta 1.3.0 version of this integration.

here is my configuration as an example

sensor:
  - platform: wienerlinien
    firstnext: first
    stops:
      - "852"
      - "724"
      - "901"
      - "4926"
      - "4118"
      - "4416"
      - "1448"
      - "1474"
      - "4109"
      - "4906"
      - "4411"
      - "4925"
      - "4920"
      - "4921"
      - "4619"
      - "4610"
      - "1449"
      - "1473"
      - "1449"
      - "2618"
      - "4426"
      - "4409"
  - platform: wienerlinien
    firstnext: next
    stops:
      - "852"
      - "724"
      - "901"
      - "4926"
      - "4118"
      - "4416"
      - "1448"
      - "1474"
      - "4109"
      - "4906"
      - "4411"
      - "4925"
      - "4920"
      - "4921"
      - "4619"
      - "4610"
      - "1449"
      - "1473"
      - "1449"
      - "2618"
      - "4426"
      - "4409"
      - "1462"
      - "1461"

log
2023-09-09 14:08:47.456 WARNING (MainThread) [custom_components.wienerlinien.sensor] Skipping already existing monitor
This is the only thing popping up in the logges repeatedly

It seems, that the problem is starting after adding more then 12 sensors (2 times 6 for "next" and "first").

Is there anything i am doing wrong, or is there a way to get this running with like 20-30 stops?

thanks in advance

EDIT:
It seems to be an API Limit problem.
if i am checking my IDs on the official page
https://www.wienerlinien.at/ogd_realtime/monitor?stopid=724

And do it for a lot of lines, i am getting after a while
"Abfrage Limit erreicht"

but it is working again after several seconds.
So it would be best to have a sleep of 5-10 seconds between each API call to avoid this behavior.

And maybe it would be possible to get the times for the first, next and so on in 1 API call.
The Times for the next upcoming 7 stops are delivered in 1 API call (key 0 till 6)

But as far as i can see i cant get both timings for first and next in one call, so i need to add 2 sensors for first and next, right?

Version of the custom_component
1.2.0

Describe the bug
The sensors work for the 4 stops that I am tracking but stop working about 40 minutes later and they just dissapear

Not sure what logs to post or where to find them, they just simply disappear...

Version of the custom_component
1.2.0

Describe the bug
After configuration the parameters as described I get an error. Sensors for the stations (stops) are not available.

log
2022-06-10 01:08:23 ERROR (MainThread) [homeassistant.components.hassio.handler] /store return code 500
2022-06-10 01:08:23 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /store