yes climate stopping is possible. I will try to edit the files and check the response.
edit:
I cannot find the file in the custom component folder:
yes climate stopping is possible. I will try to edit the files and check the response.
edit:
I cannot find the file in the custom component folder:
Thatās because itās in the skodaconnect Python library and not the integration.
Can you try latest release? I changed a few things related that might solve it. I have no way of testing for Enyaq though.
I havenāt looked into the departure schedule switches yet though.
thanks for the new update, but its still not working. Here are the error messages:
Error handling message: Unknown error
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 26, in _handle_async_response
await func(hass, connection, msg)
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 525, in handle_execute_script
await script_obj.async_run(msg.get("variables"), context=context)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1219, in async_run
await asyncio.shield(run.async_run())
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 353, in async_run
await self._async_step(log_exceptions=False)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 371, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 571, in _async_call_service_step
await service_task
File "/usr/src/homeassistant/homeassistant/core.py", line 1491, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1526, in _execute_service
await handler.job.target(service_call)
File "/config/custom_components/skodaconnect/__init__.py", line 406, in set_climater
if await car.set_climatisation(action, temp, hvpower, spin) is True:
File "/usr/local/lib/python3.9/site-packages/skodaconnect/vehicle.py", line 798, in set_climatisation
data['airConditioningSettings']['targetTemperatureInKelvin'] = temp + 273.15
KeyError: 'airConditioningSettings'
'airConditioningSettings'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 185, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1491, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1526, in _execute_service
await handler.job.target(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service
await self.hass.helpers.service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 658, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 830, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 695, in _handle_entity_call
await result
File "/config/custom_components/skodaconnect/switch.py", line 57, in async_turn_on
await self.instrument.turn_on()
File "/usr/local/lib/python3.9/site-packages/skodaconnect/dashboard.py", line 478, in turn_on
await self.vehicle.set_climatisation(mode = 'electric')
File "/usr/local/lib/python3.9/site-packages/skodaconnect/vehicle.py", line 798, in set_climatisation
data['airConditioningSettings']['targetTemperatureInKelvin'] = temp + 273.15
KeyError: 'airConditioningSettings'
Thanks, can you provide the debug logs leading up to this as well? Something isnāt quite right, the aircon settings data might have changed.
Some progress today. Got some help with debugging Enyaq specific requests and a new version is published which should solve a few issues such as start climatisation not working.
Latest versions also have support for large and small model image url sensors which might be useful for some.
Thanks for the new version. I can confirm that the Enyaq clima is working now
Ive updated HoneOS and Core to the latest Added the Integration from HACS but who Iām trying to add it to Homeassistant intagaren im getting this error āConfig flow could not be loadedā any suggestions how to solve it?
Update:
It just started to work by itself for some reason
Hi all,
I have 2 skodas, a karoq and a electric citigo iv.
The integration is working perfect with the karoq, but when i add the citigo iv i only get 8 entities (41 for the karoq) - and nothing useful. I canāt call any services.
I have read back in this thread, and see that other users have had succes with the citigo-e. This was all before the gui setup.
I have the skoda connect app running without problems, so both the car and credentials should be working.
Any ideas where it goes wrong?
Thanks,
update:
After enabling full logging and restarting HA, a lot of entities were registered. 54 to be precise - but all of them are unavailable. I installed the integration for my citigo 18 hours ago - do i just need to be more patient?
With the Karoq it worked instantly.
Another update:
After several restarts everything seems to be reachable. Learn to be patient Jakob
That type of issues can also be related to privacy settings in car.
Just received my Enyaq and conveniently came across this thread. Installed, and working immediately. So cool - thanks @Farfar!
If anyone with multiple vehicles would like to try it, thereās a github branch Iām working on that should work better. It might not migrate settings correctly though so test in a dev environment or similar.
Itās named multi-vehicle-account and is only available through manual install.
Hello,
I have been using the Skoda integration for a few weeks now. Thank you for the work you have done.
Basically it all works great. But what I canāt get to work yet is a warning when the trunk is open for more than 10 minutes or the car is not locked. Here I often get false alarms that report the trunk would still be open, although it has long been closed. If I go to the Skoda app, it looks the same there. Only when I do a regresh there, I get the correct values.
I guess that can only be solved with the forced refresh, right? Does it make sense to call this in an automation every āxā minutes? Which values make sense from practice? How did you configure this?
A function āAlert me when the door is opened at nightā will not work because of the delay, right?
Keep in mind that to save car battery life Skoda Cloud allows you only 19 refreshes of data. Then you need to start again the engine. So it is impossible to refresh status every x minutes.
These things are solved with automations within Home Assistant. Basically you could trigger a forced refresh if a certain condition exist for more than x minutes, unlocked car, open trunk etc.
ItĀ“s a bad idea to periodically force refresh status since thereās a limit to the number of requests that can be made before the car needs to be started. This exist to conserve the 12V battery.
For all cars on ālegacyā API (all but Enyaq) the limit is 15 requests and then you need to start the car, ignition on is sufficient to reset the limit.
Enyaq does not have this limit at all.
I have now tried to solve this via nesting:
I regularly query the status of the vehicle and if, for example, a door is reported open for more than 30 minutes, I set a forced refresh and make the query again five minutes later. Only then is a message sent.
What do you think about this?
alias: WARNING Car Door
description: ''
trigger:
- platform: state
entity_id: binary_sensor.kodiaq_door_closed_left_front
to: 'on'
for:
hours: 0
minutes: 30
seconds: 0
condition:
- condition: state
entity_id: binary_sensor.kodiaq_sty_ts110_1_5a7f_vehicle_moving
state: 'off'
for:
hours: 1
minutes: 0
seconds: 0
action:
- service: switch.turn_on
data: {}
target:
entity_id: switch.kodiaq_sty_ts110_1_5a7f_force_data_refresh
- delay:
hours: 0
minutes: 5
seconds: 0
milliseconds: 0
- choose:
- conditions:
- condition: state
entity_id: binary_sensor.kodiaq_sty_ts110_1_5a7f_door_closed_left_back
state: 'on'
sequence:
- device_id: 6de96b872e39d1adfcd02cd4c701a3c2
domain: mobile_app
type: notify
message: WARNING Car
title: >-
Door is open
default: []
mode: single
At a glance it looks good, I canāt test it myself at the moment. Does it work as you intended?
On my car? Not sure.
If you need a image thereās a sensor created with the url for your car.
Ow nice, missed that in the list! Great to know!