Bad Gateway / Forbidden error

Hi!
I was trying to setup this integration but I can't get it to work. I keep getting Bad Gateway / Forbidden errors.
When I log in to the Skoda Connect portal everything works, so my credentials are correct. This is my config:
I'm running Home Assistant version: 2020.12.0
SkodaConnect integration version: 1.0.27
skodaconnect:
  username: !secret skoda_username
  password: !secret skoda_password
  scandinavian_miles: false
  imperial_units: false
  scan_interval:
    minutes: 5

And this is the errorlog:
Could not fetch tripstatistics, error: 403, message='Forbidden', url=URL('https://msg.volkswagen.de/fs-car/bs/tripstatistics/v1/skoda/CZ/vehicles/TMBAP9NE6xxxxxx/tripdata/shortTerm?newest')

Could not fetch StoredVehicleDataResponse, error: 502, message='Bad Gateway', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMBAP9NE6xxxxxx/status')

Could not fetch position (ClientResponseError), error: 502, message='Bad Gateway', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMBAP9NE6xxxxxx/position')

I tried with and without the S-PIN and also resetted the S-PIN as well as the password for my account.
What am I missing?
Thank you in advance!
Jeffrey

Hello, is Skoda App on your mobile phone fully working? Do you see trip statistics, car status (kilometres, if it is locked, windows closed, fuel level) and car position in the app on mobile phone?

Thank you for reaching out so quickly.
Yes the Skoda app is fully functioning. All statistics are displayed.

And what country are you in?

The Netherlands

Hmm I am missing VIN number in your config posted above. Do you have it there (lowercase)? It is really strange, because there are some guys in NL using it fine...

Is that the part of name: vwv12345678='name' ?

I now have this:
skodaconnect:
  username<EMAIL_ADDRESS>  password: !secret skoda_password
  scandinavian_miles: false
  imperial_units: false
  scan_interval:
    minutes: 5
  name:
    tmbap9ne6jxxxxxxx: "Octavia"

Still same error

I now have this:
skodaconnect:
  username: "!secret skoda_username"
  password: !secret skoda_password
  scandinavian_miles: false
  imperial_units: false
  scan_interval:
    minutes: 5
  name:
    tmbap9ne6jxxxxxxx: "Octavia"

Still same error

This looks correct (assuming xxxxx you replaced only here for privacy). Try to restart HA and you should be good

I'm getting the same error. One thing I noticed is that the Skoda Connect portal (web version) doesn't display my statistics, while the app does. Maybe that's the problem?

I think this might be related to wrong homeregion set in the integration.
I see that your homeregion (base url for api requests) gets set to msg.volkswagen.de, this might be the reason why it's not working.
I don't remember though if there's any debugging information available that might tell us what's wrong. I will have to take a look in the code.

I think this might be related to wrong homeregion set in the integration.
I see that your homeregion (base url for api requests) gets set to msg.volkswagen.de, this might be the reason why it's not working.
I don't remember though if there's any debugging information available that might tell us what's wrong. I will have to take a look in the code.

I'm getting the same error. One thing I noticed is that the Skoda Connect portal (web version) doesn't display my statistics, while the app does. Maybe that's the problem?

Could you enable debugging for the library with:
logger:   logs:     skodaconnect.api: debug
Look for lines like theese in the log:
2021-01-01 11:05:04 DEBUG (MainThread) [skodaconnect.api] Getting homeregion for TMBXXXXXXXXX 2021-01-01 11:05:04 DEBUG (MainThread) [skodaconnect.api] Request for https://mal-1a.prd.ece.vwg-connect.com/api/cs/vds/v1/vehicles/TMBXXXXXXXXX/homeRegion 2021-01-01 11:05:06 DEBUG (MainThread) [skodaconnect.api] Received [200] response: {'homeRegion': {'baseUri': {'systemId': 'ICTO-25343', 'content': 'https://mal-3a.prd.eu.dp.vwg-connect.com/api'}}} 2

I'm getting the same error. One thing I noticed is that the Skoda Connect portal (web version) doesn't display my statistics, while the app does. Maybe that's the problem?

Could you enable debugging for the library with:
logger:   logs:     skodaconnect.api: debug
Look for lines like theese in the log:
2021-01-01 11:05:04 DEBUG (MainThread) [skodaconnect.api] Getting homeregion for TMBXXXXXXXXX 2021-01-01 11:05:04 DEBUG (MainThread) [skodaconnect.api] Request for https://mal-1a.prd.ece.vwg-connect.com/api/cs/vds/v1/vehicles/TMBXXXXXXXXX/homeRegion 2021-01-01 11:05:06 DEBUG (MainThread) [skodaconnect.api] Received [200] response: {'homeRegion': {'baseUri': {'systemId': 'ICTO-25343', 'content': 'https://mal-3a.prd.eu.dp.vwg-connect.com/api'}}} 2

@Farfar I have also homeregion msg.volkswagen.de, most probably it’s related to car model... You have very “new” model and have different capabilities so maybe different servers. But let’s see what debug from @JeffreySnijders will show...

@Farfar I have also homeregion msg.volkswagen.de, most probably it’s related to car model... You have very “new” model and have different capabilities so maybe different servers. But let’s see what debug from @JeffreySnijders will show...

I'm getting the same error. One thing I noticed is that the Skoda Connect portal (web version) doesn't display my statistics, while the app does. Maybe that's the problem?

Could you enable debugging for the library with:
logger: logs: skodaconnect.api: debug
Look for lines like theese in the log:
2021-01-01 11:05:04 DEBUG (MainThread) [skodaconnect.api] Getting homeregion for TMBXXXXXXXXX 2021-01-01 11:05:04 DEBUG (MainThread) [skodaconnect.api] Request for https://mal-1a.prd.ece.vwg-connect.com/api/cs/vds/v1/vehicles/TMBXXXXXXXXX/homeRegion 2021-01-01 11:05:06 DEBUG (MainThread) [skodaconnect.api] Received [200] response: {'homeRegion': {'baseUri': {'systemId': 'ICTO-25343', 'content': 'https://mal-3a.prd.eu.dp.vwg-connect.com/api'}}} 2

Thank for reaching out. I'm not quite sure where I have to put this line of code (not a developer, sorry...).

I'm getting the same error. One thing I noticed is that the Skoda Connect portal (web version) doesn't display my statistics, while the app does. Maybe that's the problem?

Could you enable debugging for the library with:
logger: logs: skodaconnect.api: debug
Look for lines like theese in the log:
2021-01-01 11:05:04 DEBUG (MainThread) [skodaconnect.api] Getting homeregion for TMBXXXXXXXXX 2021-01-01 11:05:04 DEBUG (MainThread) [skodaconnect.api] Request for https://mal-1a.prd.ece.vwg-connect.com/api/cs/vds/v1/vehicles/TMBXXXXXXXXX/homeRegion 2021-01-01 11:05:06 DEBUG (MainThread) [skodaconnect.api] Received [200] response: {'homeRegion': {'baseUri': {'systemId': 'ICTO-25343', 'content': 'https://mal-3a.prd.eu.dp.vwg-connect.com/api'}}} 2

Thank for reaching out. I'm not quite sure where I have to put this line of code (not a developer, sorry...).

@JeffreySnijders you need to put the code in your configuration.yaml (where you put the config for the integration) and then look for the log lines in home-assistant.log in the same directory.
I see though that the code got messed up here, should be newline after every ':' and proper indentation for every new sub clause

@JeffreySnijders you need to put the code in your configuration.yaml (where you put the config for the integration) and then look for the log lines in home-assistant.log in the same directory.
I see though that the code got messed up here, should be newline after every ':' and proper indentation for every new sub clause

Right! So it would become like this:
skodaconnect:
  username: "!secret skoda_username"
  password: !secret skoda_password
  scandinavian_miles: false
  imperial_units: false
  scan_interval:
    minutes: 5
  name:
    tmbap9ne6xxxxxxxx: "Octavia"
  logger:
    logs:
      skodaconnect.api: debug

Trying that out now. Thank you.

Right! So it would become like this:
skodaconnect:
  username: "!secret skoda_username"
  password: !secret skoda_password
  scandinavian_miles: false
  imperial_units: false
  scan_interval:
    minutes: 5
  name:
    tmbap9ne6xxxxxxxx: "Octavia"
  logger:
    logs:
      skodaconnect.api: debug

Trying that out now. Thank you.

Hmm not quite:
Invalid config for [skodaconnect]: [logger] is an invalid option for [skodaconnect]. Check: skodaconnect->skodaconnect->logger. (See /config/configuration.yaml, line 168).

Hmm not quite:
Invalid config for [skodaconnect]: [logger] is an invalid option for [skodaconnect]. Check: skodaconnect->skodaconnect->logger. (See /config/configuration.yaml, line 168).

O wait. You said in my configuration.yml, period. Not in the Skoda Connect integration config. Sorry...

O wait. You said in my configuration.yml, period. Not in the Skoda Connect integration config. Sorry...

Alright, so I have the lines you requested (I think):
2021-01-03 17:26:02 DEBUG (MainThread) [skodaconnect.api] Tokens OK
2021-01-03 17:26:02 DEBUG (MainThread) [skodaconnect.api] Fetching vehicles
2021-01-03 17:26:02 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/usermanagement/users/v1/skoda/CZ/vehicles
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Response headers: <CIMultiDictProxy('X-FS-Tracking-ID': '81932e63-ceda-4428-8044-371e7112843f', 'Content-Encoding': 'gzip', 'Content-Type': 'application/json;charset=UTF-8', 'Content-Length': '66', 'Date': 'Sun, 03 Jan 2021 16:26:03 GMT', 'Server': 'www')>
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Received [200] response: {'userVehicles': {'vehicle': ['TMBAP9NXXXXXXXXX']}}
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] URL loaded
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Vehicle JSON string exists
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Vehicle_URL TMBAP9NXXXXXXXXX
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Going to call vehicle updates
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Updating vehicle status TMBAP9NXXXXXXXXX
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Getting homeregion for TMBAP9NXXXXXXXXX
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Request for https://mal-1a.prd.ece.vwg-connect.com/api/cs/vds/v1/vehicles/TMBAP9NXXXXXXXXX/homeRegion
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Response headers: <CIMultiDictProxy('X-FS-Tracking-ID': '5ab1beae-efb9-4c76-a049-4ae37a071ff6', 'Content-Encoding': 'gzip', 'Content-Type': 'application/json;charset=utf-8', 'Content-Length': '120', 'Date': 'Sun, 03 Jan 2021 16:26:03 GMT', 'Server': 'www')>
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Received [200] response: {'homeRegion': {'baseUri': {'systemId': 'ICTO-10487', 'content': 'https://mal-1a.prd.ece.vwg-connect.com/api'}}}
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/promoter/portfolio/v1/skoda/CZ/vehicle/TMBAP9NXXXXXXXXX/carportdata
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Response headers: <CIMultiDictProxy('X-FS-Tracking-ID': '0f273df3-2134-484f-9f66-cffb1f01b995', 'Content-Encoding': 'gzip', 'Content-Type': 'application/json;charset=UTF-8', 'Content-Length': '249', 'Date': 'Sun, 03 Jan 2021 16:26:04 GMT', 'Server': 'www')>
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Received [200] response: {'carportData': {'systemId': 'msg', 'requestId': 'MSG-ivwb2196-1609691163607-02733-SCZ', 'brand': 'skoda', 'country': 'CZ', 'vin': 'TMBAP9NXXXXXXXXX', 'modelCode': '5E33BD', 'modelName': 'OCTAVIA AMB TS85/1.0 A7F', 'modelYear': 2018, 'color': 'LF7Y', 'countryCode': 'NL', 'engine': 'CHZ', 'mmi': '7UF', 'transmission': 'SML'}}
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/position
2021-01-03 17:26:04 WARNING (MainThread) [skodaconnect.api] Could not fetch position (ClientResponseError), error: 502, message='Bad Gateway', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/position')
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/status
2021-01-03 17:26:04 WARNING (MainThread) [skodaconnect.api] Could not fetch StoredVehicleDataResponse, error: 502, message='Bad Gateway', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/status')
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/tripstatistics/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/tripdata/shortTerm?newest
2021-01-03 17:26:04 WARNING (MainThread) [skodaconnect.api] Could not fetch tripstatistics, error: 403, message='Forbidden', url=URL('https://msg.volkswagen.de/fs-car/bs/tripstatistics/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/tripdata/shortTerm?newest')
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/climatisation/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/climater
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Could not fetch climatisation, error 403 (not supported on car?), error: 403, message='Forbidden', url=URL('https://msg.volkswagen.de/fs-car/bs/climatisation/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/climater')
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/batterycharge/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/charger
2021-01-03 17:26:05 DEBUG (MainThread) [skodaconnect.api] Could not fetch charger, error 403 (not supported on car?), error: 403, message='Forbidden', url=URL('https://msg.volkswagen.de/fs-car/bs/batterycharge/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/charger')
2021-01-03 17:26:05 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/rs/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/status
2021-01-03 17:26:05 DEBUG (MainThread) [skodaconnect.api] Could not fetch pre-heating, error 403/502 (not supported on car?), error: 502, message='Bad Gateway', url=URL('https://msg.volkswagen.de/fs-car/bs/rs/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/status')

Alright, so I have the lines you requested (I think):
2021-01-03 17:26:02 DEBUG (MainThread) [skodaconnect.api] Tokens OK
2021-01-03 17:26:02 DEBUG (MainThread) [skodaconnect.api] Fetching vehicles
2021-01-03 17:26:02 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/usermanagement/users/v1/skoda/CZ/vehicles
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Response headers: <CIMultiDictProxy('X-FS-Tracking-ID': '81932e63-ceda-4428-8044-371e7112843f', 'Content-Encoding': 'gzip', 'Content-Type': 'application/json;charset=UTF-8', 'Content-Length': '66', 'Date': 'Sun, 03 Jan 2021 16:26:03 GMT', 'Server': 'www')>
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Received [200] response: {'userVehicles': {'vehicle': ['TMBAP9NXXXXXXXXX']}}
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] URL loaded
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Vehicle JSON string exists
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Vehicle_URL TMBAP9NXXXXXXXXX
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Going to call vehicle updates
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Updating vehicle status TMBAP9NXXXXXXXXX
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Getting homeregion for TMBAP9NXXXXXXXXX
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Request for https://mal-1a.prd.ece.vwg-connect.com/api/cs/vds/v1/vehicles/TMBAP9NXXXXXXXXX/homeRegion
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Response headers: <CIMultiDictProxy('X-FS-Tracking-ID': '5ab1beae-efb9-4c76-a049-4ae37a071ff6', 'Content-Encoding': 'gzip', 'Content-Type': 'application/json;charset=utf-8', 'Content-Length': '120', 'Date': 'Sun, 03 Jan 2021 16:26:03 GMT', 'Server': 'www')>
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Received [200] response: {'homeRegion': {'baseUri': {'systemId': 'ICTO-10487', 'content': 'https://mal-1a.prd.ece.vwg-connect.com/api'}}}
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/promoter/portfolio/v1/skoda/CZ/vehicle/TMBAP9NXXXXXXXXX/carportdata
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Response headers: <CIMultiDictProxy('X-FS-Tracking-ID': '0f273df3-2134-484f-9f66-cffb1f01b995', 'Content-Encoding': 'gzip', 'Content-Type': 'application/json;charset=UTF-8', 'Content-Length': '249', 'Date': 'Sun, 03 Jan 2021 16:26:04 GMT', 'Server': 'www')>
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Received [200] response: {'carportData': {'systemId': 'msg', 'requestId': 'MSG-ivwb2196-1609691163607-02733-SCZ', 'brand': 'skoda', 'country': 'CZ', 'vin': 'TMBAP9NXXXXXXXXX', 'modelCode': '5E33BD', 'modelName': 'OCTAVIA AMB TS85/1.0 A7F', 'modelYear': 2018, 'color': 'LF7Y', 'countryCode': 'NL', 'engine': 'CHZ', 'mmi': '7UF', 'transmission': 'SML'}}
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/position
2021-01-03 17:26:04 WARNING (MainThread) [skodaconnect.api] Could not fetch position (ClientResponseError), error: 502, message='Bad Gateway', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/position')
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/status
2021-01-03 17:26:04 WARNING (MainThread) [skodaconnect.api] Could not fetch StoredVehicleDataResponse, error: 502, message='Bad Gateway', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/status')
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/tripstatistics/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/tripdata/shortTerm?newest
2021-01-03 17:26:04 WARNING (MainThread) [skodaconnect.api] Could not fetch tripstatistics, error: 403, message='Forbidden', url=URL('https://msg.volkswagen.de/fs-car/bs/tripstatistics/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/tripdata/shortTerm?newest')
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/climatisation/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/climater
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Could not fetch climatisation, error 403 (not supported on car?), error: 403, message='Forbidden', url=URL('https://msg.volkswagen.de/fs-car/bs/climatisation/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/climater')
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/batterycharge/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/charger
2021-01-03 17:26:05 DEBUG (MainThread) [skodaconnect.api] Could not fetch charger, error 403 (not supported on car?), error: 403, message='Forbidden', url=URL('https://msg.volkswagen.de/fs-car/bs/batterycharge/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/charger')
2021-01-03 17:26:05 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/rs/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/status
2021-01-03 17:26:05 DEBUG (MainThread) [skodaconnect.api] Could not fetch pre-heating, error 403/502 (not supported on car?), error: 502, message='Bad Gateway', url=URL('https://msg.volkswagen.de/fs-car/bs/rs/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/status')

Many thanks for this integration. I was was waiting for something like this.
This is my configuration entry:
skodaconnect:
  username<EMAIL_ADDRESS>  password: **********
  scandinavian_miles: false
  imperial_units: false
  scan_interval:
      minutes: 10
  name:
      tmbjj7**********: 'Octavia'
  resources:
      - distance
      - position
      - service_inspection
      - oil_inspection
      - door_locked
      - trunk_locked
      - fuel_level
      - windows_closed
      - last_connected
      - combustion_range
      - trip_last_average_speed
      - trip_last_average_fuel_consumption
      - trip_last_duration
      - trip_last_length
      - parking_light
      - door_closed_left_front
      - door_closed_left_back
      - door_closed_right_front
      - door_closed_right_back
      - trunk_closed
      - window_closed_left_front
      - window_closed_left_back
      - window_closed_right_front
      - window_closed_right_back
      - service_inspection_km
      - oil_inspection_km
      - outside_temperature
      - window_heater
      - battery_level
      - requests_remaining

The App shows everything correct and the state in HA gets updated too according to the actual state of the car.

Many thanks for this integration. I was was waiting for something like this.
This is my configuration entry:
skodaconnect:
  username<EMAIL_ADDRESS>  password: **********
  scandinavian_miles: false
  imperial_units: false
  scan_interval:
      minutes: 10
  name:
      tmbjj7**********: 'Octavia'
  resources:
      - distance
      - position
      - service_inspection
      - oil_inspection
      - door_locked
      - trunk_locked
      - fuel_level
      - windows_closed
      - last_connected
      - combustion_range
      - trip_last_average_speed
      - trip_last_average_fuel_consumption
      - trip_last_duration
      - trip_last_length
      - parking_light
      - door_closed_left_front
      - door_closed_left_back
      - door_closed_right_front
      - door_closed_right_back
      - trunk_closed
      - window_closed_left_front
      - window_closed_left_back
      - window_closed_right_front
      - window_closed_right_back
      - service_inspection_km
      - oil_inspection_km
      - outside_temperature
      - window_heater
      - battery_level
      - requests_remaining

The App shows everything correct and the state in HA gets updated too according to the actual state of the car.

@Kaibob2
That's odd. I'm not seeing any sign of the skoda integration in my HA entities. So you're saying that the integration works, despite the error messages?

@Kaibob2
That's odd. I'm not seeing any sign of the skoda integration in my HA entities. So you're saying that the integration works, despite the error messages?

All specified entites are there and populated with correct values.

Doors unlocked, Trunk unlocked, left front door open:

The two screenshots don't correspond with one another as they are taken at different car states.

All specified entites are there and populated with correct values.

Doors unlocked, Trunk unlocked, left front door open:

The two screenshots don't correspond with one another as they are taken at different car states.

Alright, so I have the lines you requested (I think):
2021-01-03 17:26:02 DEBUG (MainThread) [skodaconnect.api] Tokens OK
2021-01-03 17:26:02 DEBUG (MainThread) [skodaconnect.api] Fetching vehicles
2021-01-03 17:26:02 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/usermanagement/users/v1/skoda/CZ/vehicles
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Response headers: <CIMultiDictProxy('X-FS-Tracking-ID': '81932e63-ceda-4428-8044-371e7112843f', 'Content-Encoding': 'gzip', 'Content-Type': 'application/json;charset=UTF-8', 'Content-Length': '66', 'Date': 'Sun, 03 Jan 2021 16:26:03 GMT', 'Server': 'www')>
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Received [200] response: {'userVehicles': {'vehicle': ['TMBAP9NXXXXXXXXX']}}
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] URL loaded
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Vehicle JSON string exists
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Vehicle_URL TMBAP9NXXXXXXXXX
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Going to call vehicle updates
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Updating vehicle status TMBAP9NXXXXXXXXX
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Getting homeregion for TMBAP9NXXXXXXXXX
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Request for https://mal-1a.prd.ece.vwg-connect.com/api/cs/vds/v1/vehicles/TMBAP9NXXXXXXXXX/homeRegion
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Response headers: <CIMultiDictProxy('X-FS-Tracking-ID': '5ab1beae-efb9-4c76-a049-4ae37a071ff6', 'Content-Encoding': 'gzip', 'Content-Type': 'application/json;charset=utf-8', 'Content-Length': '120', 'Date': 'Sun, 03 Jan 2021 16:26:03 GMT', 'Server': 'www')>
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Received [200] response: {'homeRegion': {'baseUri': {'systemId': 'ICTO-10487', 'content': 'https://mal-1a.prd.ece.vwg-connect.com/api'}}}
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/promoter/portfolio/v1/skoda/CZ/vehicle/TMBAP9NXXXXXXXXX/carportdata
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Response headers: <CIMultiDictProxy('X-FS-Tracking-ID': '0f273df3-2134-484f-9f66-cffb1f01b995', 'Content-Encoding': 'gzip', 'Content-Type': 'application/json;charset=UTF-8', 'Content-Length': '249', 'Date': 'Sun, 03 Jan 2021 16:26:04 GMT', 'Server': 'www')>
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Received [200] response: {'carportData': {'systemId': 'msg', 'requestId': 'MSG-ivwb2196-1609691163607-02733-SCZ', 'brand': 'skoda', 'country': 'CZ', 'vin': 'TMBAP9NXXXXXXXXX', 'modelCode': '5E33BD', 'modelName': 'OCTAVIA AMB TS85/1.0 A7F', 'modelYear': 2018, 'color': 'LF7Y', 'countryCode': 'NL', 'engine': 'CHZ', 'mmi': '7UF', 'transmission': 'SML'}}
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/position
2021-01-03 17:26:04 WARNING (MainThread) [skodaconnect.api] Could not fetch position (ClientResponseError), error: 502, message='Bad Gateway', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/position')
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/status
2021-01-03 17:26:04 WARNING (MainThread) [skodaconnect.api] Could not fetch StoredVehicleDataResponse, error: 502, message='Bad Gateway', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/status')
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/tripstatistics/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/tripdata/shortTerm?newest
2021-01-03 17:26:04 WARNING (MainThread) [skodaconnect.api] Could not fetch tripstatistics, error: 403, message='Forbidden', url=URL('https://msg.volkswagen.de/fs-car/bs/tripstatistics/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/tripdata/shortTerm?newest')
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/climatisation/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/climater
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Could not fetch climatisation, error 403 (not supported on car?), error: 403, message='Forbidden', url=URL('https://msg.volkswagen.de/fs-car/bs/climatisation/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/climater')
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/batterycharge/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/charger
2021-01-03 17:26:05 DEBUG (MainThread) [skodaconnect.api] Could not fetch charger, error 403 (not supported on car?), error: 403, message='Forbidden', url=URL('https://msg.volkswagen.de/fs-car/bs/batterycharge/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/charger')
2021-01-03 17:26:05 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/rs/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/status
2021-01-03 17:26:05 DEBUG (MainThread) [skodaconnect.api] Could not fetch pre-heating, error 403/502 (not supported on car?), error: 502, message='Bad Gateway', url=URL('https://msg.volkswagen.de/fs-car/bs/rs/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/status')

Something is strange, the integration shouldn't request data every second and won't retry if one endpoint fails. In your case it looks as if it tries to poll every second, strange indeed.
Could you try uninstalling everything, restart home assistant, reinstall and then restart again?

Alright, so I have the lines you requested (I think):
2021-01-03 17:26:02 DEBUG (MainThread) [skodaconnect.api] Tokens OK
2021-01-03 17:26:02 DEBUG (MainThread) [skodaconnect.api] Fetching vehicles
2021-01-03 17:26:02 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/usermanagement/users/v1/skoda/CZ/vehicles
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Response headers: <CIMultiDictProxy('X-FS-Tracking-ID': '81932e63-ceda-4428-8044-371e7112843f', 'Content-Encoding': 'gzip', 'Content-Type': 'application/json;charset=UTF-8', 'Content-Length': '66', 'Date': 'Sun, 03 Jan 2021 16:26:03 GMT', 'Server': 'www')>
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Received [200] response: {'userVehicles': {'vehicle': ['TMBAP9NXXXXXXXXX']}}
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] URL loaded
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Vehicle JSON string exists
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Vehicle_URL TMBAP9NXXXXXXXXX
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Going to call vehicle updates
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Updating vehicle status TMBAP9NXXXXXXXXX
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Getting homeregion for TMBAP9NXXXXXXXXX
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Request for https://mal-1a.prd.ece.vwg-connect.com/api/cs/vds/v1/vehicles/TMBAP9NXXXXXXXXX/homeRegion
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Response headers: <CIMultiDictProxy('X-FS-Tracking-ID': '5ab1beae-efb9-4c76-a049-4ae37a071ff6', 'Content-Encoding': 'gzip', 'Content-Type': 'application/json;charset=utf-8', 'Content-Length': '120', 'Date': 'Sun, 03 Jan 2021 16:26:03 GMT', 'Server': 'www')>
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Received [200] response: {'homeRegion': {'baseUri': {'systemId': 'ICTO-10487', 'content': 'https://mal-1a.prd.ece.vwg-connect.com/api'}}}
2021-01-03 17:26:03 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/promoter/portfolio/v1/skoda/CZ/vehicle/TMBAP9NXXXXXXXXX/carportdata
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Response headers: <CIMultiDictProxy('X-FS-Tracking-ID': '0f273df3-2134-484f-9f66-cffb1f01b995', 'Content-Encoding': 'gzip', 'Content-Type': 'application/json;charset=UTF-8', 'Content-Length': '249', 'Date': 'Sun, 03 Jan 2021 16:26:04 GMT', 'Server': 'www')>
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Received [200] response: {'carportData': {'systemId': 'msg', 'requestId': 'MSG-ivwb2196-1609691163607-02733-SCZ', 'brand': 'skoda', 'country': 'CZ', 'vin': 'TMBAP9NXXXXXXXXX', 'modelCode': '5E33BD', 'modelName': 'OCTAVIA AMB TS85/1.0 A7F', 'modelYear': 2018, 'color': 'LF7Y', 'countryCode': 'NL', 'engine': 'CHZ', 'mmi': '7UF', 'transmission': 'SML'}}
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/position
2021-01-03 17:26:04 WARNING (MainThread) [skodaconnect.api] Could not fetch position (ClientResponseError), error: 502, message='Bad Gateway', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/position')
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/status
2021-01-03 17:26:04 WARNING (MainThread) [skodaconnect.api] Could not fetch StoredVehicleDataResponse, error: 502, message='Bad Gateway', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/status')
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/tripstatistics/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/tripdata/shortTerm?newest
2021-01-03 17:26:04 WARNING (MainThread) [skodaconnect.api] Could not fetch tripstatistics, error: 403, message='Forbidden', url=URL('https://msg.volkswagen.de/fs-car/bs/tripstatistics/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/tripdata/shortTerm?newest')
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/climatisation/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/climater
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Could not fetch climatisation, error 403 (not supported on car?), error: 403, message='Forbidden', url=URL('https://msg.volkswagen.de/fs-car/bs/climatisation/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/climater')
2021-01-03 17:26:04 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/batterycharge/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/charger
2021-01-03 17:26:05 DEBUG (MainThread) [skodaconnect.api] Could not fetch charger, error 403 (not supported on car?), error: 403, message='Forbidden', url=URL('https://msg.volkswagen.de/fs-car/bs/batterycharge/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/charger')
2021-01-03 17:26:05 DEBUG (MainThread) [skodaconnect.api] Request for https://msg.volkswagen.de/fs-car/bs/rs/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/status
2021-01-03 17:26:05 DEBUG (MainThread) [skodaconnect.api] Could not fetch pre-heating, error 403/502 (not supported on car?), error: 502, message='Bad Gateway', url=URL('https://msg.volkswagen.de/fs-car/bs/rs/v1/skoda/CZ/vehicles/TMBAP9NXXXXXXXXX/status')

Something is strange, the integration shouldn't request data every second and won't retry if one endpoint fails. In your case it looks as if it tries to poll every second, strange indeed.
Could you try uninstalling everything, restart home assistant, reinstall and then restart again?

@Farfar In fact i didn't touch anything beside the necessary config. With scan_interval: minutes: 10 i thought this would be a good polling interval, but i suppose this is not the polling interval you mean. I left the resources part out at first installation and only added it after seeing the errors in the log. I hoped to eliminate the errors by leaving the respective entrys out. For example everything with charger and climatisation it not in resources but appears in the errors.

@Farfar In fact i didn't touch anything beside the necessary config. With scan_interval: minutes: 10 i thought this would be a good polling interval, but i suppose this is not the polling interval you mean. I left the resources part out at first installation and only added it after seeing the errors in the log. I hoped to eliminate the errors by leaving the respective entrys out. For example everything with charger and climatisation it not in resources but appears in the errors.

@Farfar In fact i didn't touch anything beside the necessary config. With scan_interval: minutes: 10 i thought this would be a good polling interval, but i suppose this is not the polling interval you mean. I left the resources part out at first installation and only added it after seeing the errors in the log. I hoped to eliminate the errors by leaving the respective entrys out. For example everything with charger and climatisation it not in resources but appears in the errors.

Most probably there's some mismatch in refresh interval and when the integration will refresh tokens. It will refresh tokens if they expire within 1 minute of the update, but tokens should be validated and refreshed if expired on every update.
I use 1 minute update interval in the configuration and it's working fine. States will update a little faster then.
I will try 10 minute interval and see if I can reproduce.

@Farfar In fact i didn't touch anything beside the necessary config. With scan_interval: minutes: 10 i thought this would be a good polling interval, but i suppose this is not the polling interval you mean. I left the resources part out at first installation and only added it after seeing the errors in the log. I hoped to eliminate the errors by leaving the respective entrys out. For example everything with charger and climatisation it not in resources but appears in the errors.

Most probably there's some mismatch in refresh interval and when the integration will refresh tokens. It will refresh tokens if they expire within 1 minute of the update, but tokens should be validated and refreshed if expired on every update.
I use 1 minute update interval in the configuration and it's working fine. States will update a little faster then.
I will try 10 minute interval and see if I can reproduce.

@Farfar
I have tried uninstalling and reinstalling the integration, but without success. Same errors keep showing up.

@Farfar
I have tried uninstalling and reinstalling the integration, but without success. Same errors keep showing up.

@Farfar
I have tried uninstalling and reinstalling the integration, but without success. Same errors keep showing up.

Ok. What model year is your car? Do you have multiple users, it isn't the guest user you are trying to login with?
I will try to find the time to release next version soon with quite a lot of fixes and will also try to implement a check on startup for which services/endpoints are available. That might help pinpoint this issue.

@Farfar
I have tried uninstalling and reinstalling the integration, but without success. Same errors keep showing up.

Ok. What model year is your car? Do you have multiple users, it isn't the guest user you are trying to login with?
I will try to find the time to release next version soon with quite a lot of fixes and will also try to implement a check on startup for which services/endpoints are available. That might help pinpoint this issue.

Model year is 2018. I'm the only user, no guest user.
Tomorrow I'll be getting te new Octavia 2021 model, so I'm not able to continue testing this (unless I get the same errors with the new model). Though I found it useful for other people that might have the same errors to create this issue.
I will of course test it with the new car and report back if that works fine or not.

Model year is 2018. I'm the only user, no guest user.
Tomorrow I'll be getting te new Octavia 2021 model, so I'm not able to continue testing this (unless I get the same errors with the new model). Though I found it useful for other people that might have the same errors to create this issue.
I will of course test it with the new car and report back if that works fine or not.

Model year is 2018. I'm the only user, no guest user.
Tomorrow I'll be getting te new Octavia 2021 model, so I'm not able to continue testing this (unless I get the same errors with the new model). Though I found it useful for other people that might have the same errors to create this issue.
I will of course test it with the new car and report back if that works fine or not.

Have you had a chance to test the integration with your new car?
I am having a hard time trying to reproduce this and if you have no trouble with the new car I will close this issue.
There's a new release in the works and it will make it easier to debug what API endpoints are available for the car so we can easier debug issues like this.

Model year is 2018. I'm the only user, no guest user.
Tomorrow I'll be getting te new Octavia 2021 model, so I'm not able to continue testing this (unless I get the same errors with the new model). Though I found it useful for other people that might have the same errors to create this issue.
I will of course test it with the new car and report back if that works fine or not.

Have you had a chance to test the integration with your new car?
I am having a hard time trying to reproduce this and if you have no trouble with the new car I will close this issue.
There's a new release in the works and it will make it easier to debug what API endpoints are available for the car so we can easier debug issues like this.

I have tested it just now and can confirm it works with my new car.
Thank you very much for your help.

I have tested it just now and can confirm it works with my new car.
Thank you very much for your help.

In my case nothing has changed until now.

In my case nothing has changed until now.

OK

OK

Nope. Changing to minutes: 1 doesn't change anything.

Nope. Changing to minutes: 1 doesn't change anything.

Nope. Changing to minutes: 1 doesn't change anything.

OK. I suspect there's some issue when tokens expire but I haven't been able to reproduce it myself.
The upcoming release will hopefully take care of this issue for you. I will release it ASAP.

Nope. Changing to minutes: 1 doesn't change anything.

OK. I suspect there's some issue when tokens expire but I haven't been able to reproduce it myself.
The upcoming release will hopefully take care of this issue for you. I will release it ASAP.

That would be great

That would be great

Any progress here?

Any progress here?

Works for me, but hade not tester so much

Works for me, but hade not tester so much

I still see this in the logs:
Could not fetch StoredVehicleDataResponse, error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMB*******/status')
19:07:57 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:12 aufgetreten und erscheint 79 mal
Could not fetch position (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMB*******/position')
19:07:47 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:27 aufgetreten und erscheint 71 mal
Could not fetch pre-heating (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/rs/v1/skoda/CZ/vehicles/TMB*******/status')
17:46:26 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:28 aufgetreten und erscheint 69 mal
Could not fetch charger (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/batterycharge/v1/skoda/CZ/vehicles/TMB*******/charger')
17:46:26 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:26 aufgetreten und erscheint 70 mal
Could not fetch climatisation (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/climatisation/v1/skoda/CZ/vehicles/TMB*******/climater')
17:46:26 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:28 aufgetreten und erscheint 72 mal
Could not fetch tripstatistics, error: 502, message='Bad Gateway', url=URL('https://msg.volkswagen.de/fs-car/bs/tripstatistics/v1/skoda/CZ/vehicles/TMB*******/tripdata/shortTerm?newest')
17:46:26 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:24 aufgetreten und erscheint 71 mal
Could not fetch carportData, error: 500, message='Internal Server Error', url=URL('https://msg.volkswagen.de/fs-car/promoter/portfolio/v1/skoda/CZ/vehicle/TMB*******/carportdata')
17:46:25 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:24 aufgetreten und erscheint 69 mal

Clicking on a log entry ends in:
Logger: skodaconnect.api
Source: /usr/local/lib/python3.8/site-packages/skodaconnect/api.py:423
First occurred: 16:25:12 (79 occurrences)
Last logged: 19:07:57

    Could not fetch StoredVehicleDataResponse, error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMB*******/status')
    Could not fetch StoredVehicleDataResponse, error: 401, message='Unauthorized', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMB*******/status')
    Could not fetch StoredVehicleDataResponse, error: 500, message='Internal Server Error', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMB*******/status')

or
Logger: skodaconnect.api
Source: /usr/local/lib/python3.8/site-packages/skodaconnect/api.py:405
First occurred: 16:25:27 (71 occurrences)
Last logged: 19:07:47

    Could not fetch position (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMB*******/position')
    Could not fetch position (ClientResponseError), error: 401, message='Unauthorized', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMB*******/position')
    Could not fetch position (ClientResponseError), error: 500, message='Internal Server Error', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMB*******/position')

I only have these resources in my configuration.yaml:
  resources:
      - distance
      - position
      - service_inspection
      - oil_inspection
      - door_locked
      - trunk_locked
      - fuel_level
      - windows_closed
      - combustion_range
      - parking_light
      - door_closed_left_front
      - door_closed_left_back
      - door_closed_right_front
      - door_closed_right_back
      - trunk_closed
      - window_closed_left_front
      - window_closed_left_back
      - window_closed_right_front
      - window_closed_right_back
      - outside_temperature
      - battery_level

Entries like charger or climatisation shouldn't come up in the error log, or am i missing something.
Even with the reduced resources i get the following entities created and they are most likely working as far as i can tell:

I still see this in the logs:
Could not fetch StoredVehicleDataResponse, error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMB*******/status')
19:07:57 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:12 aufgetreten und erscheint 79 mal
Could not fetch position (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMB*******/position')
19:07:47 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:27 aufgetreten und erscheint 71 mal
Could not fetch pre-heating (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/rs/v1/skoda/CZ/vehicles/TMB*******/status')
17:46:26 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:28 aufgetreten und erscheint 69 mal
Could not fetch charger (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/batterycharge/v1/skoda/CZ/vehicles/TMB*******/charger')
17:46:26 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:26 aufgetreten und erscheint 70 mal
Could not fetch climatisation (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/climatisation/v1/skoda/CZ/vehicles/TMB*******/climater')
17:46:26 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:28 aufgetreten und erscheint 72 mal
Could not fetch tripstatistics, error: 502, message='Bad Gateway', url=URL('https://msg.volkswagen.de/fs-car/bs/tripstatistics/v1/skoda/CZ/vehicles/TMB*******/tripdata/shortTerm?newest')
17:46:26 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:24 aufgetreten und erscheint 71 mal
Could not fetch carportData, error: 500, message='Internal Server Error', url=URL('https://msg.volkswagen.de/fs-car/promoter/portfolio/v1/skoda/CZ/vehicle/TMB*******/carportdata')
17:46:25 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:24 aufgetreten und erscheint 69 mal

Clicking on a log entry ends in:
Logger: skodaconnect.api
Source: /usr/local/lib/python3.8/site-packages/skodaconnect/api.py:423
First occurred: 16:25:12 (79 occurrences)
Last logged: 19:07:57

    Could not fetch StoredVehicleDataResponse, error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMB*******/status')
    Could not fetch StoredVehicleDataResponse, error: 401, message='Unauthorized', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMB*******/status')
    Could not fetch StoredVehicleDataResponse, error: 500, message='Internal Server Error', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMB*******/status')

or
Logger: skodaconnect.api
Source: /usr/local/lib/python3.8/site-packages/skodaconnect/api.py:405
First occurred: 16:25:27 (71 occurrences)
Last logged: 19:07:47

    Could not fetch position (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMB*******/position')
    Could not fetch position (ClientResponseError), error: 401, message='Unauthorized', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMB*******/position')
    Could not fetch position (ClientResponseError), error: 500, message='Internal Server Error', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMB*******/position')

I only have these resources in my configuration.yaml:
  resources:
      - distance
      - position
      - service_inspection
      - oil_inspection
      - door_locked
      - trunk_locked
      - fuel_level
      - windows_closed
      - combustion_range
      - parking_light
      - door_closed_left_front
      - door_closed_left_back
      - door_closed_right_front
      - door_closed_right_back
      - trunk_closed
      - window_closed_left_front
      - window_closed_left_back
      - window_closed_right_front
      - window_closed_right_back
      - outside_temperature
      - battery_level

Entries like charger or climatisation shouldn't come up in the error log, or am i missing something.
Even with the reduced resources i get the following entities created and they are most likely working as far as i can tell:

I still see this in the logs:
Could not fetch StoredVehicleDataResponse, error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMB*******/status')
19:07:57 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:12 aufgetreten und erscheint 79 mal
Could not fetch position (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMB*******/position')
19:07:47 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:27 aufgetreten und erscheint 71 mal
Could not fetch pre-heating (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/rs/v1/skoda/CZ/vehicles/TMB*******/status')
17:46:26 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:28 aufgetreten und erscheint 69 mal
Could not fetch charger (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/batterycharge/v1/skoda/CZ/vehicles/TMB*******/charger')
17:46:26 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:26 aufgetreten und erscheint 70 mal
Could not fetch climatisation (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/climatisation/v1/skoda/CZ/vehicles/TMB*******/climater')
17:46:26 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:28 aufgetreten und erscheint 72 mal
Could not fetch tripstatistics, error: 502, message='Bad Gateway', url=URL('https://msg.volkswagen.de/fs-car/bs/tripstatistics/v1/skoda/CZ/vehicles/TMB*******/tripdata/shortTerm?newest')
17:46:26 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:24 aufgetreten und erscheint 71 mal
Could not fetch carportData, error: 500, message='Internal Server Error', url=URL('https://msg.volkswagen.de/fs-car/promoter/portfolio/v1/skoda/CZ/vehicle/TMB*******/carportdata')
17:46:25 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:24 aufgetreten und erscheint 69 mal

Clicking on a log entry ends in:
Logger: skodaconnect.api
Source: /usr/local/lib/python3.8/site-packages/skodaconnect/api.py:423
First occurred: 16:25:12 (79 occurrences)
Last logged: 19:07:57

    Could not fetch StoredVehicleDataResponse, error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMB*******/status')
    Could not fetch StoredVehicleDataResponse, error: 401, message='Unauthorized', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMB*******/status')
    Could not fetch StoredVehicleDataResponse, error: 500, message='Internal Server Error', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMB*******/status')

or
Logger: skodaconnect.api
Source: /usr/local/lib/python3.8/site-packages/skodaconnect/api.py:405
First occurred: 16:25:27 (71 occurrences)
Last logged: 19:07:47

    Could not fetch position (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMB*******/position')
    Could not fetch position (ClientResponseError), error: 401, message='Unauthorized', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMB*******/position')
    Could not fetch position (ClientResponseError), error: 500, message='Internal Server Error', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMB*******/position')

I only have these resources in my configuration.yaml:
  resources:
      - distance
      - position
      - service_inspection
      - oil_inspection
      - door_locked
      - trunk_locked
      - fuel_level
      - windows_closed
      - combustion_range
      - parking_light
      - door_closed_left_front
      - door_closed_left_back
      - door_closed_right_front
      - door_closed_right_back
      - trunk_closed
      - window_closed_left_front
      - window_closed_left_back
      - window_closed_right_front
      - window_closed_right_back
      - outside_temperature
      - battery_level

Entries like charger or climatisation shouldn't come up in the error log, or am i missing something.
Even with the reduced resources i get the following entities created and they are most likely working as far as i can tell:

Is this the latest code on github or the latest release? If it is the latest release then it is the same status as last time, 13 days ago, upcoming release should fix it.
As the code is written in last release it will try to fetch data for all API endpoints regardless of enabled resources.

I still see this in the logs:
Could not fetch StoredVehicleDataResponse, error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMB*******/status')
19:07:57 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:12 aufgetreten und erscheint 79 mal
Could not fetch position (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMB*******/position')
19:07:47 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:27 aufgetreten und erscheint 71 mal
Could not fetch pre-heating (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/rs/v1/skoda/CZ/vehicles/TMB*******/status')
17:46:26 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:28 aufgetreten und erscheint 69 mal
Could not fetch charger (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/batterycharge/v1/skoda/CZ/vehicles/TMB*******/charger')
17:46:26 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:26 aufgetreten und erscheint 70 mal
Could not fetch climatisation (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/climatisation/v1/skoda/CZ/vehicles/TMB*******/climater')
17:46:26 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:28 aufgetreten und erscheint 72 mal
Could not fetch tripstatistics, error: 502, message='Bad Gateway', url=URL('https://msg.volkswagen.de/fs-car/bs/tripstatistics/v1/skoda/CZ/vehicles/TMB*******/tripdata/shortTerm?newest')
17:46:26 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:24 aufgetreten und erscheint 71 mal
Could not fetch carportData, error: 500, message='Internal Server Error', url=URL('https://msg.volkswagen.de/fs-car/promoter/portfolio/v1/skoda/CZ/vehicle/TMB*******/carportdata')
17:46:25 – /usr/local/lib/python3.8/site-packages/skodaconnect/api.py (WARNING) - Die Nachricht ist zum ersten Mal um 16:25:24 aufgetreten und erscheint 69 mal

Clicking on a log entry ends in:
Logger: skodaconnect.api
Source: /usr/local/lib/python3.8/site-packages/skodaconnect/api.py:423
First occurred: 16:25:12 (79 occurrences)
Last logged: 19:07:57

    Could not fetch StoredVehicleDataResponse, error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMB*******/status')
    Could not fetch StoredVehicleDataResponse, error: 401, message='Unauthorized', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMB*******/status')
    Could not fetch StoredVehicleDataResponse, error: 500, message='Internal Server Error', url=URL('https://msg.volkswagen.de/fs-car/bs/vsr/v1/skoda/CZ/vehicles/TMB*******/status')

or
Logger: skodaconnect.api
Source: /usr/local/lib/python3.8/site-packages/skodaconnect/api.py:405
First occurred: 16:25:27 (71 occurrences)
Last logged: 19:07:47

    Could not fetch position (ClientResponseError), error: 504, message='Gateway Timeout', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMB*******/position')
    Could not fetch position (ClientResponseError), error: 401, message='Unauthorized', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMB*******/position')
    Could not fetch position (ClientResponseError), error: 500, message='Internal Server Error', url=URL('https://msg.volkswagen.de/fs-car/bs/cf/v1/skoda/CZ/vehicles/TMB*******/position')

I only have these resources in my configuration.yaml:
  resources:
      - distance
      - position
      - service_inspection
      - oil_inspection
      - door_locked
      - trunk_locked
      - fuel_level
      - windows_closed
      - combustion_range
      - parking_light
      - door_closed_left_front
      - door_closed_left_back
      - door_closed_right_front
      - door_closed_right_back
      - trunk_closed
      - window_closed_left_front
      - window_closed_left_back
      - window_closed_right_front
      - window_closed_right_back
      - outside_temperature
      - battery_level

Entries like charger or climatisation shouldn't come up in the error log, or am i missing something.
Even with the reduced resources i get the following entities created and they are most likely working as far as i can tell:

Is this the latest code on github or the latest release? If it is the latest release then it is the same status as last time, 13 days ago, upcoming release should fix it.
As the code is written in last release it will try to fetch data for all API endpoints regardless of enabled resources.

It's the latest release 1.0.27 as provided in HACS. I hoped i could provide more Info with my last post. If not, sorry, just ignore it :)

It's the latest release 1.0.27 as provided in HACS. I hoped i could provide more Info with my last post. If not, sorry, just ignore it :)

It's the latest release 1.0.27 as provided in HACS. I hoped i could provide more Info with my last post. If not, sorry, just ignore it :)

No problem, I think I know where the problem lies. I could be wrong though but the new code is so different that all problems that might persist should be as good as new ;)
Just feeling a bit stressed to get next version released as it should fix many issues and help troubleshoot others. It's Stanley enough that I think I'll release it tomorrow.

It's the latest release 1.0.27 as provided in HACS. I hoped i could provide more Info with my last post. If not, sorry, just ignore it :)

No problem, I think I know where the problem lies. I could be wrong though but the new code is so different that all problems that might persist should be as good as new ;)
Just feeling a bit stressed to get next version released as it should fix many issues and help troubleshoot others. It's Stanley enough that I think I'll release it tomorrow.

It's the latest release 1.0.27 as provided in HACS. I hoped i could provide more Info with my last post. If not, sorry, just ignore it :)

I have released 1.0.30 as a beta (v1.0.30-rc) that can be installed from HACS with beta releases enabled (press reinstall on repo and enable beta to get access).
When enough people have tested this I will release as a stable version.
The critical part would be legacy pre-heater on non-PHEV cars, the code have changed quite a bit and I can't test it since my car only got the newer style climater with auxiliary heater.

It's the latest release 1.0.27 as provided in HACS. I hoped i could provide more Info with my last post. If not, sorry, just ignore it :)

I have released 1.0.30 as a beta (v1.0.30-rc) that can be installed from HACS with beta releases enabled (press reinstall on repo and enable beta to get access).
When enough people have tested this I will release as a stable version.
The critical part would be legacy pre-heater on non-PHEV cars, the code have changed quite a bit and I can't test it since my car only got the newer style climater with auxiliary heater.

Hi. Just installed RC3. The only error in the log is:
Logger: skodaconnect.connection
Source: /usr/local/lib/python3.8/site-packages/skodaconnect/connection.py:598
First occurred: 13:22:32 (1 occurrences)
Last logged: 13:22:32
Could not fetch pre-heating, error: name 'err' is not defined

and all entities appear as restored:true in the entity list. None gets updated. All are unavailable. Only the following seem to work:
binary_sensor.octavia_request_in_progress
device_tracker.octavia
sensor.octavia_requests_remaining
switch.octavia_force_data_refresh

switch.octavia_force_data_refresh is not supported here, by the way

Hi. Just installed RC3. The only error in the log is:
Logger: skodaconnect.connection
Source: /usr/local/lib/python3.8/site-packages/skodaconnect/connection.py:598
First occurred: 13:22:32 (1 occurrences)
Last logged: 13:22:32
Could not fetch pre-heating, error: name 'err' is not defined

and all entities appear as restored:true in the entity list. None gets updated. All are unavailable. Only the following seem to work:
binary_sensor.octavia_request_in_progress
device_tracker.octavia
sensor.octavia_requests_remaining
switch.octavia_force_data_refresh

switch.octavia_force_data_refresh is not supported here, by the way

Hi, i am also on RC3 and no sensors gets updated any longer.
2018 Superb L&K 190hp TDI 4x4, living in Sweden.
When trying to activate the parking heater the error log is the following:
`Logger: homeassistant.components.websocket_api.http.connection
Source: custom_components/skodaconnect/switch.py:32
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 1:48:06 PM (1 occurrences)
Last logged: 1:48:06 PM
[140018450977408] 'Vehicle' object has no attribute 'is_combustion_climatisation_supported'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 135, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1445, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1480, in _execute_service
await handler.job.target(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 204, in handle_service
await self.hass.helpers.service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 593, in entity_service_call
future.result()  # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 664, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 630, in _handle_entity_call
await result
File "/config/custom_components/skodaconnect/switch.py", line 32, in async_turn_on
await self.instrument.turn_on()
File "/usr/local/lib/python3.8/site-packages/skodaconnect/dashboard.py", line 528, in turn_on
await self.vehicle.set_pheater(mode='heating', spin=self.spin)
File "/usr/local/lib/python3.8/site-packages/skodaconnect/vehicle.py", line 352, in set_pheater
if not self.is_combustion_climatisation_supported:
AttributeError: 'Vehicle' object has no attribute 'is_combustion_climatisation_supported'`

Hi, i am also on RC3 and no sensors gets updated any longer.
2018 Superb L&K 190hp TDI 4x4, living in Sweden.
When trying to activate the parking heater the error log is the following:
`Logger: homeassistant.components.websocket_api.http.connection
Source: custom_components/skodaconnect/switch.py:32
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 1:48:06 PM (1 occurrences)
Last logged: 1:48:06 PM
[140018450977408] 'Vehicle' object has no attribute 'is_combustion_climatisation_supported'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 135, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1445, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1480, in _execute_service
await handler.job.target(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 204, in handle_service
await self.hass.helpers.service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 593, in entity_service_call
future.result()  # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 664, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 630, in _handle_entity_call
await result
File "/config/custom_components/skodaconnect/switch.py", line 32, in async_turn_on
await self.instrument.turn_on()
File "/usr/local/lib/python3.8/site-packages/skodaconnect/dashboard.py", line 528, in turn_on
await self.vehicle.set_pheater(mode='heating', spin=self.spin)
File "/usr/local/lib/python3.8/site-packages/skodaconnect/vehicle.py", line 352, in set_pheater
if not self.is_combustion_climatisation_supported:
AttributeError: 'Vehicle' object has no attribute 'is_combustion_climatisation_supported'`

I edited my above post. I installed RC2 there. Now with RC3 the log error is gone, but the entities are still in the state as described above

I edited my above post. I installed RC2 there. Now with RC3 the log error is gone, but the entities are still in the state as described above

Please restart home assistant completeley, looks as if the library isn't updated since there's no variable named "err" anymore.
Check library version from shell with "pip show skodaconnect" logged in with correct user and in venv if applicable.
Can you supply the start of home-assistant.log please? The logs from within home assistant is rather useless unless something acutally throws an error.
What I am interested in is the lines with:
INFO (MainThread) [skodaconnect.vehicle] Vehicle XYZWXYZWXYZW added from Skoda Connect. Homeregion is "https://mal-3a.prd.eu.dp.vwg-connect.com/api"
DEBUG (MainThread) [skodaconnect.vehicle] Enabled API endpoints: dict_keys(['preheater', 'realcar', 'carport', 'mobiledevicemgmt_v1', 'rolesrights_secondaryuser_v2', 'rolesrights_securitypin_v1', 'rclima_v1', 'statusreport_v1', 'timerprogramming_v1', 'cc_breakdown_v2', 'speedalert_v1', 'rolesrights_secondaryuser_v1', 'rolesrights_primaryuser_v2', 'dwap', 'rbatterycharge_v1', 'rlu_v1', 'dealerappoint_v1', 'rolesrights_securitypin_v2', 'rolesrights_authorization_v2', 'rhonk_v1', 'geofence_v1', 'usermanagement_users_v1', 'carfinder_v1', 'rolesrights_primaryuser_v1', 'trip_statistic_v1', 'pso_v1', 'rolesrights_permissions_v1', 'hotspotwlan_v1'])

Please restart home assistant completeley, looks as if the library isn't updated since there's no variable named "err" anymore.
Check library version from shell with "pip show skodaconnect" logged in with correct user and in venv if applicable.
Can you supply the start of home-assistant.log please? The logs from within home assistant is rather useless unless something acutally throws an error.
What I am interested in is the lines with:
INFO (MainThread) [skodaconnect.vehicle] Vehicle XYZWXYZWXYZW added from Skoda Connect. Homeregion is "https://mal-3a.prd.eu.dp.vwg-connect.com/api"
DEBUG (MainThread) [skodaconnect.vehicle] Enabled API endpoints: dict_keys(['preheater', 'realcar', 'carport', 'mobiledevicemgmt_v1', 'rolesrights_secondaryuser_v2', 'rolesrights_securitypin_v1', 'rclima_v1', 'statusreport_v1', 'timerprogramming_v1', 'cc_breakdown_v2', 'speedalert_v1', 'rolesrights_secondaryuser_v1', 'rolesrights_primaryuser_v2', 'dwap', 'rbatterycharge_v1', 'rlu_v1', 'dealerappoint_v1', 'rolesrights_securitypin_v2', 'rolesrights_authorization_v2', 'rhonk_v1', 'geofence_v1', 'usermanagement_users_v1', 'carfinder_v1', 'rolesrights_primaryuser_v1', 'trip_statistic_v1', 'pso_v1', 'rolesrights_permissions_v1', 'hotspotwlan_v1'])

Easiest might be to send me the complete log file. Please redact all sensitive data before doing so.

Easiest might be to send me the complete log file. Please redact all sensitive data before doing so.

@Farfar Attached is anything related to skodaconnect
Ps. I´ve installed rc3 through hacs, but manifest.json still says rc2 and so does the log. 😀
skodaconnect.log
from the log file.

@Farfar Attached is anything related to skodaconnect
Ps. I´ve installed rc3 through hacs, but manifest.json still says rc2 and so does the log. 😀
skodaconnect.log
from the log file.

@Farfar Attached is anything related to skodaconnect from the log file.
Ps. I´ve installed rc3 through hacs, but manifest.json still says rc2 and so does the log.
skodaconnect.log

Thanks I already see what I think is the culprit. Something errs when the integration tries to auto discover what API endpoints are enabled so most are disabled. I will work on a fix right away.

@Farfar Attached is anything related to skodaconnect from the log file.
Ps. I´ve installed rc3 through hacs, but manifest.json still says rc2 and so does the log.
skodaconnect.log

Thanks I already see what I think is the culprit. Something errs when the integration tries to auto discover what API endpoints are enabled so most are disabled. I will work on a fix right away.

and

RC4 is available now. I have reworked the API service discovery since it seems to fail for most cars for some reason. If it keeps mucking up at least I have added some more debugging so I might catch exactly what goes wrong.

and

RC4 is available now. I have reworked the API service discovery since it seems to fail for most cars for some reason. If it keeps mucking up at least I have added some more debugging so I might catch exactly what goes wrong.

GREAT JOB!! As far as i can tell for the moment everything works perfect. Especially the switch.octavia_force_data_refresh entity is huge improvement and works as intended. Thank you for this integration. I will keep testing in the next days and build some automations around it.

GREAT JOB!! As far as i can tell for the moment everything works perfect. Especially the switch.octavia_force_data_refresh entity is huge improvement and works as intended. Thank you for this integration. I will keep testing in the next days and build some automations around it.

GREAT JOB!! As far as i can tell for the moment everything works perfect. Especially the switch.octavia_force_data_refresh entity is huge improvement and works as intended. Thank you for this integration. I will keep testing in the next days and build some automations around it.

Please do and report back. Especially the pre-heater if you have it on your car.

GREAT JOB!! As far as i can tell for the moment everything works perfect. Especially the switch.octavia_force_data_refresh entity is huge improvement and works as intended. Thank you for this integration. I will keep testing in the next days and build some automations around it.

Please do and report back. Especially the pre-heater if you have it on your car.

I would love to have one, but don't.
Would it be an option to invert the sensors for the doors. For example binary_sensor.octavia_door_closed_left_back is off when the window is closed. I would say it's more logical if it's on when closed because it says window closed = on (true)

I would love to have one, but don't.
Would it be an option to invert the sensors for the doors. For example binary_sensor.octavia_door_closed_left_back is off when the window is closed. I would say it's more logical if it's on when closed because it says window closed = on (true)

Would it be an option to invert the sensors for the doors. For example binary_sensor.octavia_door_closed_left_back is off when the window is closed. I would say it's more logical if it's on when closed because it says window closed = on (true)

I agree. But the way that the binary sensor door device class works we can't invert the state.
I might rename the sensors though so they make more sense.

Would it be an option to invert the sensors for the doors. For example binary_sensor.octavia_door_closed_left_back is off when the window is closed. I would say it's more logical if it's on when closed because it says window closed = on (true)

I agree. But the way that the binary sensor door device class works we can't invert the state.
I might rename the sensors though so they make more sense.

I see. Renaming the sensors would have been my Plan B :)

I see. Renaming the sensors would have been my Plan B :)

Nice job getting the sensors working again! The parking heater switches, both heat/vent,  still doesn´t work though.
I´m getting this error message and some additional traceback.
DEBUG (MainThread) [custom_components.skodaconnect.switch] Turning ON pheater_heating.
ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139712086054944] 'Vehicle' object has no attribute 'is_combustion_climatisation_supported'

Do you need any additional info?

Nice job getting the sensors working again! The parking heater switches, both heat/vent,  still doesn´t work though.
I´m getting this error message and some additional traceback.
DEBUG (MainThread) [custom_components.skodaconnect.switch] Turning ON pheater_heating.
ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139712086054944] 'Vehicle' object has no attribute 'is_combustion_climatisation_supported'

Do you need any additional info?

Nice job getting the sensors working again! The parking heater switches, both heat/vent, still doesn´t work though.
I´m getting this error message and some additional traceback.
DEBUG (MainThread) [custom_components.skodaconnect.switch] Turning ON pheater_heating.
ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139712086054944] 'Vehicle' object has no attribute 'is_combustion_climatisation_supported'

Do you need any additional info?

No I think I have what I need to find the misbehaving code. It's probably the library changes that I haven't changed correctly in the integration code. Will take a look tomorrow.

Nice job getting the sensors working again! The parking heater switches, both heat/vent, still doesn´t work though.
I´m getting this error message and some additional traceback.
DEBUG (MainThread) [custom_components.skodaconnect.switch] Turning ON pheater_heating.
ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139712086054944] 'Vehicle' object has no attribute 'is_combustion_climatisation_supported'

Do you need any additional info?

No I think I have what I need to find the misbehaving code. It's probably the library changes that I haven't changed correctly in the integration code. Will take a look tomorrow.

I´m getting this error message and some additional traceback.

Could you test if changing if not self.is_combustion_climatisation_supported: to if not self.is_pheater_heating_supported: on row 359 in skodaconnect/vehicle.py ?
Exact location of the file depends on where and how you installed home assistant. sudo find / -name vehicle.py should get you the path.

I´m getting this error message and some additional traceback.

Could you test if changing if not self.is_combustion_climatisation_supported: to if not self.is_pheater_heating_supported: on row 359 in skodaconnect/vehicle.py ?
Exact location of the file depends on where and how you installed home assistant. sudo find / -name vehicle.py should get you the path.

So, finally managed to access the homeassistant container through ssh in hassio and i edited the file and that seems to solve the check, but then it fails further down on row 383 in set_pheater
2021-01-28 11:21:22 ERROR (MainThread) [skodaconnect.vehicle] Failed to set parking heater to heating
2021-01-28 11:21:22 WARNING (MainThread) [skodaconnect.vehicle] Failed to set parking heater mode to heating - Failed to set parking heater to heating
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/skodaconnect/vehicle.py", line 383, in set_pheater

Ventilation fails in a similar manner 'Vehicle' object has no attribute 'pheater_climatisation'
Thanks!

So, finally managed to access the homeassistant container through ssh in hassio and i edited the file and that seems to solve the check, but then it fails further down on row 383 in set_pheater
2021-01-28 11:21:22 ERROR (MainThread) [skodaconnect.vehicle] Failed to set parking heater to heating
2021-01-28 11:21:22 WARNING (MainThread) [skodaconnect.vehicle] Failed to set parking heater mode to heating - Failed to set parking heater to heating
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/skodaconnect/vehicle.py", line 383, in set_pheater

Ventilation fails in a similar manner 'Vehicle' object has no attribute 'pheater_climatisation'
Thanks!

Ventilation fails in a similar manner 'Vehicle' object has no attribute 'pheater_climatisation'

New release: RC5. Hopefully this will at least make it one step further. I reworked the code some so if it still fails I might know more as to why.

Ventilation fails in a similar manner 'Vehicle' object has no attribute 'pheater_climatisation'

New release: RC5. Hopefully this will at least make it one step further. I reworked the code some so if it still fails I might know more as to why.

Ventilation and heating works like a charm now, both turning on and off.
All such requests output the following in the log, but still functioning.
DEBUG (MainThread) [skodaconnect.connection] Request for parking heater returned with state "unknown",
Great job fixing this. Tack!

Ventilation and heating works like a charm now, both turning on and off.
All such requests output the following in the log, but still functioning.
DEBUG (MainThread) [skodaconnect.connection] Request for parking heater returned with state "unknown",
Great job fixing this. Tack!

DEBUG (MainThread) [skodaconnect.connection] Request for parking heater returned with state "unknown",

That's because it can't determine the state from the returned data. Does that line end with a valid request ID and remaining requests?

DEBUG (MainThread) [skodaconnect.connection] Request for parking heater returned with state "unknown",

That's because it can't determine the state from the returned data. Does that line end with a valid request ID and remaining requests?

Yes, request id and remaining requests are both there, sorry.
DEBUG (MainThread) [skodaconnect.connection] Request for parking heater returned with state "unknown", request id: 18534028, remaining requests: 11
Once these requests finished the icon and the toggle both became yellow/active.
DEBUG (MainThread) [custom_components.skodaconnect.sensor] Getting state of pheater_status
DEBUG (MainThread) [custom_components.skodaconnect.sensor] Getting state of pheater_duration

Is there anything else i should test?

Yes, request id and remaining requests are both there, sorry.
DEBUG (MainThread) [skodaconnect.connection] Request for parking heater returned with state "unknown", request id: 18534028, remaining requests: 11
Once these requests finished the icon and the toggle both became yellow/active.
DEBUG (MainThread) [custom_components.skodaconnect.sensor] Getting state of pheater_status
DEBUG (MainThread) [custom_components.skodaconnect.sensor] Getting state of pheater_duration

Is there anything else i should test?

Once these requests finished the icon and the toggle both became yellow/active.

Excellent! Then it's only the pre heater function that doesn't return a state along with request id.
The important thing is that the request id is there so it can check for status and refresh after request is finished.
I now feel confident that it will work when stable version is released. Thank you for testing!
Only missing thing now is service to be able to change duration for parking heater.

Once these requests finished the icon and the toggle both became yellow/active.

Excellent! Then it's only the pre heater function that doesn't return a state along with request id.
The important thing is that the request id is there so it can check for status and refresh after request is finished.
I now feel confident that it will work when stable version is released. Thank you for testing!
Only missing thing now is service to be able to change duration for parking heater.

Do you know if it's possible to get the remaining fuel range as seen in this screenshot from the app, in addition to the fuel level percentage? Days and distance are negative in HA, but positive in the app. I could of course use a value_template to flip them, but i'm guessing more users get a bit annoyed by it too. 😀

Do you know if it's possible to get the remaining fuel range as seen in this screenshot from the app, in addition to the fuel level percentage? Days and distance are negative in HA, but positive in the app. I could of course use a value_template to flip them, but i'm guessing more users get a bit annoyed by it too. 😀

Do you know if it's possible to get the remaining fuel range as seen in this screenshot from the app, in addition to the fuel level percentage?

Yes it's there already: sensor.xyzw_combustion_range.
And the service intervals might change as well, the negative value makes more sense for service overdue.

Do you know if it's possible to get the remaining fuel range as seen in this screenshot from the app, in addition to the fuel level percentage?

Yes it's there already: sensor.xyzw_combustion_range.
And the service intervals might change as well, the negative value makes more sense for service overdue.

Doh, was looking for something fuel related.. Thanks! 😆

Doh, was looking for something fuel related.. Thanks! 😆

Closing this issue as it should be solved in current code.

Closing this issue as it should be solved in current code.


rubocop issues: tree_builder_automate_simulation_results.rb

== app/presenters/tree_builder_automate_simulation_results.rb ==
C: 31: 24: Optional arguments should appear at the end of the argument
list.
R: 40:  3: Assignment Branch Condition size for get_root_elements is too
high. [29.43/15]
C: 59: 44: Space between { and | missing.
C: 59: 50: Space missing inside }.
C: 70: 19: Redundant curly braces around a hash parameter.
R: 70:121: Line is too long. [149/120]

/cc @chriskacerguis

@cynepco3hahue Can you please take a look at the build failure?

Hi guys, if no one has any objections, do we can start to merge PR's connect to rubocop issues?

@dclarizio can you take a look and merge when you get a minute?


Use the cache whenever something bad happens when refreshing the Pillar.

When working on bsc#1093123 I've seen that the orchestration fails becasue 1) haproxy was temporarily down 2) the pillar cannot be accessed 3) velum.py crashes with an exception. We can avoid this failure for this kind of transient errors by using the Pillar cache (when present).
Related to bsc#1093123.

I think we want to backport this one.


New translation - messages_hu.yml

Welcome!
I want to give you a new language. Language name: messages_hu.yml (Hungarian).
I'm sorry to write here, but I did not know about Pull Request.
File Required: "UTF-8 Encoding Without BOM" - Required for Minecrafter, because if it is not configured, it will send meaningless messages (for example: é). The file was verified but not tested.
What I've Changed: I put a ('') sign before and end of each text.
Here is the file: https://pastebin.com/c7h0Vt0Z
Or download: http://www.mediafire.com/file/k7w637lbwnoe2nk/messages_hu.yml

Will add, thanks.


"flush" wal_pos reported in keepalive unless we have pending transactions

The server may generate WAL that doesn't correspond to a transaction commit, e.g.:

automatic checkpoints driven by checkpoint_timeout
transactions that roll back

Currently we only update our "flush lsn" when we see a COMMIT, so if enough of this non-committed-transaction activity occurs before we see a COMMIT, the server may run out of WAL space and crash.  I believe this is the root cause of #68.
The server's regular keepalive messages are already informing us of the updated wal_pos resulting from this activity.  So this commit makes us acknowledge it as "flushed" (even though we didn't actually do anything about it), provided that we aren't currently waiting for Kafka to acknowledge a transaction in flight (in which case acknowledging the subsequent activity would could result in us losing the transaction in flight, in case of a restart).
I've also tested the case where Bottled Water restarts before the transaction is committed, and it does pick up from the right point and capture the whole transaction.
In the process of debugging this I ran into a bug in the client's logic for keeping track of transactions in flight, where the client would acknowledge each commit twice (each time it processed a new COMMIT, it would first reprocess the COMMIT of the previous transaction).  I think the bug was harmless, but it made the logic hard to reason about, since effectively it was processing records since "removed" from the circular buffer abstraction.  Since this change allows keepalives during that interval to update the fsync_lsn, it would also trigger the "Commits not in WAL order!" warning each time a transaction came in.
To work around that, I also refactored the circular buffer of transactions to remove some special cases in the handling of the initial snapshot transaction and distinguish more clearly between the buffer being empty and full.
I initially planned to write automated tests for this behaviour by querying pg_replication_slots.restart_lsn; however, the very async nature of the communication made it difficult to make the tests pass without large (20 second) sleeps - Bottled Water only checkpoints every 10 seconds, Postgres only issues keepalives once per checkpoint_timeout, etc.  So right now there is no additional test coverage.  It passes the existing tests, though :)

I'm going to merge this to make progress, since it fixes a known and serious bug and has no observed deleterious effects.  Still interested in any feedback (/ping @ept if you get a spare minute :)).


Add project_id to data_project

All Submissions:

[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] My code follows the code style of this project.
[x] I ran lint checks locally prior to submission.
[x] Have you checked to ensure there aren't other open PRs for the same update/change?

What about the current behavior has changed?

Issue Number: closes  #162
Does this introduce a change to go.mod, go.sum or vendor/?

[ ] No

Does this introduce a breaking change?

[ ] No

Any relevant logs, error output, etc?
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
Other information

It might be worth removing the project_name field and just having the project_id field accept both. Didn't do that atm because of breaking changes, but it's an easy change

LGTM


SceneViewer .glb model loading fails with latest Google app installed

Hi devs,
Our team is experiencing an error when launching SceneViewer AR via an intent string on the web as shown in the documentation.

The glb we're testing is here.
The error we're seeing is...

This error happens on Android phones with the latest Google app installed (May 24, 2021) [<IP_ADDRESS>.arm64].
Bug experienced across multiple phones...
Samsung Galaxy M31
Redmi Note 9
One Plus 8T
Xaomi A3
Redmi Note 8 Pro
Samsung Galaxy S8
Samsung Galaxy S9
Samsung Galaxy S10 Plus
Samsung Galaxy S20 Plus
If you have older versions of the Google app, the bug does not occur (we haven't figured out exactly what version number the bug started in)

Hi we are facing with same issue.. this issue comes from permission access, if you managed to press give access button this issue will never appear again. I think this code let the error remove

Can you try? This code from

I had the same problem. Realised I was running version 1.4.1 and upgrading to 1.7.1 fixed the issue for me.
Now it pops up the same screen, but without the "Couldn't load the object" error.
After giving it access, it works as it should.

@elalish : FYI this proposed workaround does not help us, as we are loading SceneViewer via an intent string via button press on our website. We do not intend to integrate Model Viewer, and based on the documentation this shouldn't be a problem to load directly into SceneViewer and skip Model Viewer.

@DerrickBarra I believe you can work around this by using ar_preferred instead of ar_only.


Upgrade github.com/alecthomas/units, which implement encoding.TextMarshaler

As https://github.com/alecthomas/units/pull/12 .
It also make http://<IP_ADDRESS>:9090/config page display units.Base2Bytes consist with config file.
before:
body_size_limit: 5242880

after (human-readable):
body_size_limit: 5MB

Signed-off-by: hanjm<EMAIL_ADDRESS>

Thanks!


Kino.Input.read ignores updates

Example
# Kino bug: `Input.read()` doesn't return updated values

```elixir
Mix.install([
  {:kino, "~> 0.13.1"}
])
```

## Section

```elixir
text = Kino.Input.text("Type something")
button = Kino.Control.button("Reveal the bug")

Kino.listen(button, fn
  %{type: :click} ->
    text |> Kino.Input.read() |> IO.inspect(label: "current input value")

  _ ->
    nil
end)

Kino.Layout.grid([
  text,
  button
])
```

Demo:
https://github.com/livebook-dev/kino/assets/43530070/a14d9067-76d7-4c3b-be64-7b57fb785763
Expected behaviour
Expected on each button click to get the latest input value of the text field.
Actual behaviour
The first read value is returned repeatedly on consecutive reads.
Livebook version

Livebook
Elixir

v0.13.2
v1.17.1

This is expected, Kino.Input.read should be used to read the input value in the executing cell, not in a background process. We make sure that Kino.Input.read returns the value from the time the cell started executing. In a background process the return value is basically undefined; for example if you change the input and evaluate another cell, then the background process would get the latest value on next read. The reason we do this is because we track dependency between inputs and cells, so when a cell calls Kino.Input.read, and the input value changes later, we mark that cell as stale.
For accessing the input value asynchronously you can either use Kino.Control.form with input and submit button (so that all form inputs are sent together). Or, you can subscribe to both the input and the button, and keep track of the current value in the state as it changes:
text = Kino.Input.text("Type something")
button = Kino.Control.button("Click")

Kino.Control.tagged_stream(button: button, text: text)
|> Kino.listen(%{text: ""}, fn
  {:text, event}, state ->
    {:cont, %{state | text: event.value}}

  {:button, _event}, state ->
    IO.inspect(state.text, label: "current input value")
    {:cont, state}
end)

Kino.Layout.grid([text, button])

We should add a note about this in the docs. @josevalim or perhaps we should change it such that Kino.Input.read raises when called from any process other than the cell? There could be a false positive, for example if you try to read inside Task.async_stream, but a simple workaround is to read the input into a variable upfront, which is guaranteed to be the same value anyway. wdyt?

@jonatanklosko raising an error works for me!


Conhost crash when using accessibility tools

Environment
Windows build number: Version 10.0.18362.295
Conhost build: commit df26c677efcb815a3b66a974345c9d3483cab678
Any other software? Inspect from the 10.0.18362.0 SDK
Steps to reproduce

Start a conhost session.
Start the Inspect utility.
Click on the top level window in the UI Automation tree that matches the conhost session.

Expected behavior
You should see details about the window in the right hand pane.
Actual behavior
I get an access violation in WindowUiaProviderBase::get_ProviderOptions because pOptions has a value of 0x13, which isn't a valid pointer. The crash can also happen in other places depending on what accessibility call is triggered first.
I believe this is a regression thatwas introduced in commit cdfbf8f1064db75c23f417c20c20567c3054f0ad.
It's been a while since I've worked with COM, but I'm fairly certain you can't return an interface without a cast the way it is now being done in those QueryInterface methods. Otherwise the returned interface pointer won't be pointing to the correct vtable. And I suspect that's resulting in the wrong method being called by the code that is using the returned interface, hence the bogus parameter value (the parameter was likely intended for a completely different method).

Yeah ☹ this'll be fixed by #3051, but we should get something in a bit quicker.


Return cursor to inside span

Just a small change to keep consistent with Obsidian's behavior on bolding and italics. Figured it would be better on a usability standpoint.
Keen to hear your thoughts and love the work on this extension :slightly_smiling_face:

It seems logical to stay consistent with Obsidian's behavior. I may, however, add a setting to change between behaviors in the future because I personally don't really like Obsidian's original behavior 😄.
Thanks for the contribution!


Rename 'Atari - 8-bit Family' to 'Atari - 8-bit'

This change removes the "Family" from Atari - 8-bit. "Family" in the playlist title isn't really translatable, and we don't adopt the "Family" naming scheme to other similar console sets.

I agree with that, we should have unified system names in libretro project.


Extending administrators modules

Can you expand the administrator modules? For example, can you add a new field called "brief description" in the Blog module? Thank you.

You can by doing a migration then add the field to the quarx.forms config - otherwise you could disable the default and add in your own module.


Fix for working with cudf 0.15

Cudf 0.15 recently disabled iterating over the values of an index, which broke
a number of ops in nvtabular. (change https://github.com/rapidsai/cudf/pull/5340)
Fix by using values_host.

rerun tests

rerun tests

rerun tests

rerun tests

rerun tests

rerun tests

rerun tests


mkdef

To implement a library a common practice is to mark public symbols using XXXX_EXPORT, and use macros to conditionally compile the related code:
#ifndef XXXX_STATIC
  #ifdef _WIN32
    // works on both MSVC and MinGW
    #ifdef BUILDING_XXXX
      #define XXXX_EXPORT __declspec(dllexport)
    #else
      #define XXXX_EXPORT __declspec(dllimport)
    #endif
  #else
    #ifdef BUILDING_XXXX
      // compile using GCC or Clang with -fvisibility=hidden
      #define XXXX_EXPORT __attribute__((visibility("default")))
    #endif
  #endif
#endif
#ifndef XXXX_EXPORT
  #define XXXX_EXPORT
#endif

This is just common practice but OpenSSL does not use it.
So all of the symbols from OpenSSL are not exported by default on Windows.
On other platforms it is exported provided -fvisibility=hidden is not set (I am not doing this).
For resolving this problem OpenSSL team chooses to maintain a list (util/libeay.num / util/ssleay.num on 1.0.2, util/libcrypto.num / util/libssl.num on 1.1.1 onwards), from which it generates a .def file using mkdef.pl.
To link the DLL using this .def file makes the symbols listed in it are exported.
I just feel this extremely complicated so I use following to export all symbols by default on Windows:
set(CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS YES)

However on OpenSSL 3.0 onwards the source code of libcrypto is splitted into crypto and provider, the provider is built as static library then link to libcrypto.
According to the documentation WINDOWS_EXPORT_ALL_SYMBOLS does not affect static library, so the link error occurs on Windows.
Currently I switched the providers to object library to workaround this issue but I don't think it is a perfect workaround since the static library is gone. ( 4a0fc04da0a87e310e4aa23d76088fbf016b48f4 )
So I think it is needed for mkdef.pl alternative.
Since mkdef.pl reads data output from Configure I don't think using it directly is a solution.
Probably generating a cmake script during configure and run it during build will be the final solution.

mkdef is also used for generating version script for Linux.
I have no knowledge about version script before, I think it may be a kind of assembly code or linker script.

OpenSSL 1.1.1 and before use a more complicated version than 3.0.0 and later of mkdef.pl.
It seems like that the mkdef.pl on 1.1.1 and before is a combination of mkdef.pl and mknum.pl.