hasl-sensor / integration Goto Github PK

Api result: time data '' does not match format '%Y-%m-%dT%H:%M:%S'

Tried to fetch the data directly from API, and that is working fine.

Traffic Status is working OK.

Double and triple checked the API key but getting empty result

From dev tools in HA:

unit_of_measurement: min
api_result: Ok
scan_interval: 300
refresh_enabled: true
attribution: Stockholms Lokaltrafik
departures: []
deviations: []
last_refresh: '2022-01-04 10:06:49'
next_departure_minutes: 3
next_departure_time: '10:14:54'
deviation_count: 0
icon: mdi:train
friendly_name: SL Departure Sensor 3704

From API call in browser:
https://api.sl.se/api2/realtimedeparturesV4.xml?key=XXXX&siteid=3704

<ResponseOfDepartures xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <StatusCode>0</StatusCode> <ExecutionTime>164</ExecutionTime> <ResponseData> <LatestUpdate xmlns="http://sl.se/Departures.xsd">2022-01-04T10:09:08</LatestUpdate> <DataAge xmlns="http://sl.se/Departures.xsd">4</DataAge> <Metros xmlns="http://sl.se/Departures.xsd"/> <Buses xmlns="http://sl.se/Departures.xsd"> <Bus> <TransportMode>BUS</TransportMode> <LineNumber>157</LineNumber> <Destination>Danderyds sjukhus</Destination> <JourneyDirection>1</JourneyDirection> <StopAreaName>Herdevägen</StopAreaName> <StopAreaNumber>12125</StopAreaNumber> <StopPointNumber>12126</StopPointNumber> <TimeTabledDateTime>2022-01-04T10:14:54</TimeTabledDateTime> <ExpectedDateTime>2022-01-04T10:14:54</ExpectedDateTime> <DisplayTime>5 min</DisplayTime> <JourneyNumber>20834</JourneyNumber> </Bus> <Bus> <TransportMode>BUS</TransportMode> <LineNumber>157</LineNumber> <Destination>Spånga station</Destination> <JourneyDirection>2</JourneyDirection> <StopAreaName>Herdevägen</StopAreaName> <StopAreaNumber>12125</StopAreaNumber> <StopPointNumber>12125</StopPointNumber> <TimeTabledDateTime>2022-01-04T10:12:36</TimeTabledDateTime> <ExpectedDateTime>2022-01-04T10:16:00</ExpectedDateTime> <DisplayTime>6 min</DisplayTime> <JourneyNumber>20785</JourneyNumber> </Bus> <Bus>

Hi,

After adding an integration with HASL, options can't be modified afterwards.
If I want to change for instance time it won't work, values keeps reversing to the original one.
Only way is to delete the integration and do a new one.
Is this a "work as design" feature or is something wrong?
Running on HA version:
Home Assistant 2022.10.3
Supervisor 2022.10.0
Operating System 9.2
Frontend 20221010.0 - latest

Hi,

The HASL integration setup fails after upgrading to HA 2023.6.0. Worked fine with HA 2023.5.

Log output:

Logger: homeassistant.loader
Source: custom_components/hasl3/__init__.py:41
Integration: Svensk Kollektivtrafikssensor (HASL) ([documentation](https://hasl.sorlov.com/), [issues](https://github.com/hasl-sensor/integration/issues))
First occurred: 12:11:11 (1 occurrences)
Last logged: 12:11:11

Unexpected exception importing component custom_components.hasl3
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/loader.py", line 813, in get_component
    ComponentProtocol, importlib.import_module(self.pkg_path)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1206, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1178, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1149, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 690, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 940, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/config/custom_components/hasl3/__init__.py", line 41, in <module>
    @asyncio.coroutine
     ^^^^^^^^^^^^^^^^^
AttributeError: module 'asyncio' has no attribute 'coroutine'

Maybe related to Python 3.11?

EDIT:
Commenting out line 41 (@asyncio.coroutine) in hasl3/__init__.py makes it work just fine again.

This is outside of the scope of this project, but I was wondering if anyone managed to get Alexa or other voice assistant to return the data about the upcoming busses using this sensor. I have the sensor and voice assistant exposed to each other. I am just missing the phrase that would activate it

There is an error message in the logs saying:

Although it did work for me with a previous HA version.

Hi,

Just I'm frequently getting SLAPI_API_Error 5324: None (Departures) when polling the API. Just want to know if anyone else is having the same experience. I'm just polling aprox 150 request/day and sometimes it seems to work.

Thx!

Get api return error.

Sl departure
Plats id: 9192
Direction: don't matter
Lines: filtered and not filtred
Hämta data: 60 sec
Binary sensor: yes

No result.

Api result
time data '' does not match format '%Y-%m-%dT%H:%M:%S'

🚌

It would be nice if API error would be explained with reason:

Statuskod | Meddelande
-- | --
1001 | problem with request: Key is undefinedNyckel hare ej skickats med.
1002 | problem with request: Key is invalidNyckel är ogiltig
1003 | Invalid apiOgiltigt api
1004 | problem with request: This api is currently not available for keys with priority above 2
1005 | Nyckel finns, men ej för detta apiproblem with request: Invalid api for key
1006 | To many requests per minuteFör många anrop per minut, för den profil som används
1007 | To many requests per monthFör många anrop per månad, för den profil som används
4001 | SiteId måste gå att konvertera till heltal.
5321 | Kunde varken hämta information från TPI (tunnelbanan) eller DPS (övriga trafikslag).
5322 | Kunde inte hämta information från DPS.
5323 | Kunde inte hämta information från TPI.
5324 | Kunde varken hämta information från TPI (tunnelbanan) eller DPS (övriga trafikslag) p.g.a. inaktuell DPS-data. Detta uppstår om DPS-datan är äldre än 2 minuter vid svarstillfället.

from: https://www.trafiklab.se/node/15754/documentation

I had the response 5324. But I think it not because of the integration, but on the server side.

Hi,

I had once successfull integration but had to change locationid and now it's not working at all.
Keep getting 5324.

If I set direction to 1 or 2, it is always reset to 0 whenever I go back to the same config panel:

This means the departure card always shows both directions of my bus line, even though I am only 1 stop from the end station and will never go that direction. I always only go in the direction of the citycentre.

In addition to the problem of seeing 2 directions when I only want to display 1 direction, it is also quite confusing where the bus goes. It apparently displays the end station name, which makes no meaningful sense to me. I know I want to go in the direction of the city center, but the name of the end station far away AFTER the city center has no relevant meaning to me as I am never in that part of the city.

It would be good to have a configuration property to override the name of the direction, and force it to e.g. "Towards city centre" rather than having the name of the end station that is fairly unknown when you never go there.

The error below is appearing regularly (every 5th minute or so) in the log. The component works as it did before, and there is no registered problem with the api.

Logger: homeassistant
Source: custom_components/hasl3/sensor.py:531
Integration: SL Integration (HASL) (documentation, issues)
First occurred: 16:59:40 (12 occurrences)
Last logged: 17:05:10

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 709, in _update_entity_states
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 406, in async_update_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 453, in _async_write_ha_state
state = self._stringify_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 425, in _stringify_state
state = self.state
File "/config/custom_components/hasl3/sensor.py", line 531, in state
return len(self._sensordata["data"])
KeyError: 'data'

Worth mentioning that the trafiklab has this announcement, and they're sunsetting older APIs end 2024.03.30

https://www.trafiklab.se/api/trafiklab-apis/sl/

https://www.trafiklab.se/api/trafiklab-apis/sl/transport/

running in docker, version core-2022.3.0

home-assistant.log

ERROR (SyncWorker_3) [homeassistant.util.package] Unable to install package httpx==0.12.1: ERROR: Cannot install httpx==0.12.1 because these package versions have conflicting dependencies.
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
ERROR (MainThread) [homeassistant.setup] Setup failed for hasl3: Requirements for hasl3 not found: ['httpx==0.12.1'].

I had this up and running but now there are no bus lines available, the hasl-departure-card is just empty (though no error messages).

I don't know whether I managed to trigger this issue myself when I removed the hasl-traffic-status-card since I could not get that one to work despite my efforts. Could this have had any effect on the results in the hasl-departure card? Or could it be anything deriving from a timetable update for my local trasport company "Blekingetrafiken"?

Hi,

I've had since a long time an issue and couldn't see any data in the Lovelace Traffic Status card.
So i removed entirely the HASL Lovelace cards (i had also the Departure card) and the HASL integration. After a reboot of HA and a fresh install, i see the following error in the HA logs for the Traffic integration:
2022-03-17 18:30:07 DEBUG (MainThread) [custom_components.hasl3.slapi] Will call TL2 API
2022-03-17 18:30:09 DEBUG (MainThread) [custom_components.hasl3.slapi] SLAPI_API_Error 1007: Unknown API-response code encountered

I figured out by using directly SL TL2 API that error 1007 is "Too many requests per month".

• It would be great to catch this error in a future release since users can define their own polling rate.
• Also is the number of Traffic sensors affecting the polling #rate, meaning the more sensors user defines, the slower the polling rate shall be ?

Here is my configuration for the Traffic integration for info:

I don't know why i still got this error 1007 since it should be below the 10k requests/month but maybe the counter also includes all the API requests falling in error. Anyhow i'll wait a couple of days (or a month) and see if i get the card again.

SL Deviations is the new API regarding deviations on SLs transport network. This API replaces the older Service Alerts (Störningsinformation) and Traffic Status (Trafikläget) APIs.
The SL Deviations can not be used in HASL-sensor (still wants older APIs).

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 709, in _update_entity_states
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 355, in async_update_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 409, in _async_write_ha_state
extra_state_attributes = self.device_state_attributes
File "/config/custom_components/hasl3/sensor.py", line 458, in device_state_attributes
val['attribution'] = self._sensordata["attribution"]
KeyError: 'attribution'

Hi!
I’ve been trying to setup the new HASL version 3. I’m not able to get correct time information for booth directions. It doesent matter if I choose 1 or 2 in the direction field. The presented time is for direction 1 in booth cases. What am I wrong in the setup process?

Hi, I am getting this in my logs,

ERROR (MainThread) [custom_components.hasl3.slapi] SLAPI_API_Error 1005: Key exists but is not for requested API (Traffic Status)

I have been trying to recreate the sensors, I am using the "SL Trafikläget 2" key but also tried to use SL "Störningsinformation 2" with the same result, I updated to the latest version of hasl-sensor and still getting the same error, I have been putting quite some time into this and I am stuck now, the key works if I test with https://api.sl.se/api2/trafficsituation.json?key=

Any idea?

Hello i am using the resrobot Departure integration with the departures card, the problem that i am facing is wheneven i choose Direction 1 or 2 only the next bus shows and not all the busses, thus the card doesn't show any value

and when adding it to the card it doesn't show anything

but when choose the direction to be 0 then i get all the values, and the card shows perfectly but it shows booth direction, i am only interested in 1 direction where i need to go to Centrallen not the other way around,
so do you think this can be fixed ? or is it an error from my side
here is my card configuration:

`type: custom:hasl-departure-card
header: true
departures: true
deviations: true
timeleft: false
updated: true
name: Departures
adjust_times: false
hide_departed: false
language: en-EN
entities:
  - sensor.rr_departure_sensor_740017500_busses_test_1`

and here is when i choose the direction to be 0
this is the card:

and here is the sensor:

Thank you so much for your help.
BTW i am using the last version of the card which is : 2.6.1
and Home assistant 2023.3.1

I've had this integration up and running for a while. But now, it seems to been running into some issues...?

Upon HA start;

This error originated from a custom integration.

Logger: homeassistant.loader
Source: custom_components/hasl3/__init__.py:41
Integration: Swedish Public Transport Sensor (HASL) (documentation, issues)
First occurred: 07:11:28 (1 occurrences)
Last logged: 07:11:28

Unexpected exception importing component custom_components.hasl3
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/loader.py", line 813, in get_component
    ComponentProtocol, importlib.import_module(self.pkg_path)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1206, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1178, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1149, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 690, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 940, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/config/custom_components/hasl3/__init__.py", line 41, in <module>
    @asyncio.coroutine
     ^^^^^^^^^^^^^^^^^
AttributeError: module 'asyncio' has no attribute 'coroutine'

Logger: homeassistant.setup
Source: setup.py:215
First occurred: 07:11:28 (1 occurrences)
Last logged: 07:11:28

Setup failed for custom integration hasl3: Unable to import component: Exception importing custom_components.hasl3

Using Home Assistant Core to version 2022.3.2
slapi-v3.0.4

Error while setting up hasl3 platform for binary_sensor

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
    await asyncio.shield(task)
  File "/config/custom_components/hasl3/binary_sensor.py", line 34, in async_setup_entry
    async_add_devices(await setup_hasl_sensor(hass, config_entry))
  File "/config/custom_components/hasl3/binary_sensor.py", line 44, in setup_hasl_sensor
    if not config.options[CONF_ANALOG_SENSORS]:
KeyError: 'analog'

..Hmm. I can’t load the integration with this fix. I suck at Python and had just a few minutes.
I’ll facepalm myself and google until help from above :)

I started to get this Error about 2023-08-23 and the sensors are not updated anymore

Logger: custom_components.hasl3.slapi
Source: custom_components/hasl3/slapi/slapi.py:176
Integration: Svensk Kollektivtrafikssensor (HASL) (documentation, issues)
First occurred: 08:34:41 (229 occurrences)
Last logged: 18:18:29

SLAPI_API_Error 5322: None (Departure Board)

Home Assistant 2023.7.2
Supervisor 2023.08.1
Operating System 10.3

Hi,

Setting seconds between checks doesn't work.

The function checkminutesdiff seems to have values (d1, d2) in the wrong order.
So the result is always above threshold.

I have changed the code to:

`
def getminutesdiff(self, d1, d2):

    d1 = datetime.strptime(d1, "%Y-%m-%d %H:%M:%S")
    d2 = datetime.strptime(d2, "%Y-%m-%d %H:%M:%S")
    diff = (d1 - d2).total_seconds()
    logger.debug(f"[get_minutes_diff] diff {diff}, d1 {d1}, d2 {d2}")
    return diff

`

which seems to be working.

What are theese 3 doing? :)

And Direction settings is not working i guess?

Tack för bra integration! :)

I read on the older version that this would implement the config flow so no more yaml so I added
hasl3: to my configuration and restarted.
I then tried to hit "Options" in integrations screen but this just ticks with exceptions.

Do I need something more in the configuration such as API keys?

In some odd cases, a bus makes multiple stops during a route at the same bus stop (same site id). This is the case for me where my bus makes a first stop and then comes back a few minutes later after turning around. Both stops are on the same route (same direction and same siteid) and the stop name is the same. The siteid in my case is 7037.

In cases like this, I would only want to display the second stop the bus makes since that's the one I need to time things for.

When making a manual request to the SL API, it seems like these stops can be separated by looking at the StopPointNumber attribute in the json response. It doesn't seem like this attribute is parsed though so can't figure out how to filter on it.

Would it be possible to have an option to include additional attributes in the parsed data perhaps, so I can do some manual filtering on this? Or would it be better to use a RESTful sensor in odd cases like this one?

If I try to check the line number or directions and press update, there is no warning but if I configure again the old values are there.

Trying to filter lines and direction and it doesn't seem to work. I get all lines from site/location and all directions.

Got SLAPI_API_ERROR 5322 on my sensors and from what I understand that is an issue with the api. Curious to check what the issue was I tried the direct url to the api and got a response that was just fine.

Went to the developer tools and checked the entity and it hadn't been updated for more than an hour. Went to the integrations to the HASL integration and pressed reload on the sensors and directly got proper values for the stops.

It seems like it doesn't try to load the api again after it has gotten an error back?

Keep getting this error every other refresh:
Api result
'<' not supported between instances of 'int' and 'NoneType'

Would say it happens 50% of the time.

Using SL Departure Sensor
Sensor primary property: min
Refresh: 300
Time: 20
Direction: 1

Trying to install HASLv3 (3.0.1) via HACS but version check is wrong. My installed HA is 2021.12.0 and the required version is 2021.12 according to HASL. Should be ok but get error during install. I huess it is the ".0" that is causing the problem.

Running versions
HA: 2021.12.0
HACS: 1.19.3
HASLv3: 3.0.0, 3.0.0 or master tested

hacs.json does say "2021.12" as HA version. Maybe change that to "2021.12.0" instead?

• När angett line (54) även annan (4) upp.
• Filtret fungerar och rensar flera andra linjer som den ska. Så fungerar delvis samt direction men buss 4 som inte ska vara med.

The location ID link in the documentation redirects to a 404 page. Can't find the information anywhere on Trafiklab. Is there anywhere else I can look?

Hi!

I'm trying this out for the first time and noticed that the readme states:

First, visit https://www.trafiklab.se/api and create a free account.

They provide multiple APIs, the ones you want is

"SL Trafikinformation 4"
"SL Störningsinformation 2"

However, there's no API called "Trafikinformation 4" and the link goes to "Realtidsiformation 4"

I guess it's just a typo?

Error was opened in hasl-plattform but is in regard to hasl-sensor/integration

Details: DSorlov/hasl-platform#67

Not important, typo?

2021-06-12 21:01:44 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.signal_messages is taking over 10 seconds
/config/custom_components/hasl3/sensor.py:370: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if sensorproperty is 'min':
/config/custom_components/hasl3/sensor.py:380: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if sensorproperty is 'time':
/config/custom_components/hasl3/sensor.py:389: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if sensorproperty is 'deviations':
/config/custom_components/hasl3/sensor.py:392: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if sensorproperty is 'updated':
/config/custom_components/hasl3/sensor.py:447: SyntaxWarning: "is not" with a literal. Did you mean "!="?
  if self._unit_of_measure is not '':

I get the following warning message on my HA startup. Using Core 2022.07.1 (latest at the time of writing).

2022-07-08 09:26:03 WARNING (MainThread) [homeassistant.helpers.frame] Detected integration that uses deprecated async_get_registry to access device registry, use async_get instead. Please report issue to the custom component author for hasl3 using this method at custom_components/hasl3/init.py, line 245: device_registry = await dr.async_get_registry(hass)

No departures returned from query:

unit_of_measurement: min
api_result: Ok
scan_interval: 300
refresh_enabled: true
attribution: Stockholms Lokaltrafik
departures: []
deviations: []
last_refresh: '2022-03-08 10:29:13'
next_departure_minutes: 4
next_departure_time: '10:34:25'
deviation_count: 0
icon: mdi:train
friendly_name: SL Departure Sensor 3704

Tips denna är till resrobot och den har hållplats id nr så kanske länka den på din GitHub projekt sida? https://raw.githubusercontent.com/TekniskSupport/home-assistant-resrobot/master/stops.txt

Hi,

No matter how I try I cannot make the sensor for local bus stop timetable to show up
in HomeAssistant.

I have created an API key in Trafiklab for ResRobot 2.1.
I added Resrobot as HACS integration

I added this to configure.yaml:

sensor:

• platform: resrobot
  key: <>
  departures:
  • stop_id: 740039603
    name: Hisingstorp

Sensor is not showing up in Developer/Entity list.

So I also added this as HACS integration as well;

SL Integration (HASL)
Swedish Public Transport Sensor (HASL). Formerly named HomeAssistant SL Sensor

No matter how I try various things, the sensor showing me the timetable for a bus stop
in Jönköping (740039603) will not become visible in Home assistant.

Any ideas to help is most welcome!

According to docuymentation there should be two services for locking up a stop ID: rr_find_location and sl_find_location
but there is only one: find_location
If I try to use this service to find a stop ID I get:
SLAPI_API_Error 1002: The supplied API key is not valid (Location Lookup)

So I used a browser instead to get the stop ID, but when I create a sensors with this i get:
SLAPI_API_Error 1002: The supplied API key is not valid (Departures)

Is the ResRobot v2.1 API not implemented?

My HA won't restart anymore unless I comment out the HASL config in my sensor.yaml.

I've updated HA and HACS to latest but HASL isn't visible either through searching in HACS or via the integrations-page. Am I missing something?

The default of 300 is always applied. If I set it to e.g. 1800, it immediately resets to 300.

Does anyone else experience this?

Hi,
i was trying to do this but for skånetrafiken and i was not able to do so, since you have wrote on the description that it could be done for whole sweden,
my use case is i just need to see the departure time for a specific buss stop and the train times on the central station, and also if there is any delays that it will show the delay
i hope this is something can be done with this integration since i searched alot for a solution and i couldn't find,

many thanks
All the best!

After restart sometimes this appears in the logs and the sensors for that integration is not available..

Logger: homeassistant.config_entries
Source: config_entries.py:501
First occurred: 11:58:52 (1 occurrences)
Last logged: 11:58:52

Migration handler not found for entry Test for hasl3