Closed robinostlund closed 9 months ago
@oliverrahner No Problem, without you and the other guy's effort I wouldn't have any information inside HA. :-) So better do a bunch of try-and-error and we'll get it reliable again.
Do you want me after midnight to keep the 4.4.68 running or should it be disabled until you had the time to make changes.?
@gohakn It's really up to you, if you do not mind potentially being locked out of the app until the next day, just keep using it. The next days, I won't have much time. I hope to get the control stuff done today, but won't be able to work on the request reduction until probably next Monday.
@sebking1971 Any log entries?
I also tested version 4.4.68 and it seems to work for my Tiguan E-Hybrid. There is one thing I am missing, but this was also not available in the old version: I would like to be able to set the maximum charging current from Homeassistant. Currently this is just a readonly value. The reason why I would like to have this feature: I want to control the charging current dependent on the status of my photovoltaic installation via an automation in Homeassistant. Is it possible to enable this value as read/write?
@squonk11 I can check this next week, if it is settable via the app, I should be able to include it in the lib.
@enoch85 @shift-del1 @florie1706 This all seems to be related to the apparently too high amount of requests we are sending. Reducing the poll interval as mentioned above should remove this issue until we found a better way.
@enoch85 @shift-del1 @florie1706 This all seems to be related to the apparently too high amount of requests we are sending. Reducing the poll interval as mentioned above should remove this issue until we found a better way.
Indeed it is working again today morning, just changed the poll interval form 5 minutes to 10 minutes. Let's see how it works now ;)
@squonk11 I can check this next week, if it is settable via the app, I should be able to include it in the lib.
@oliverrahner Just check that the service is working, like in the picture I've posted above.
I also tested version 4.4.68 and it seems to work for my Tiguan E-Hybrid. There is one thing I am missing, but this was also not available in the old version: I would like to be able to set the maximum charging current from Homeassistant. Currently this is just a readonly value. The reason why I would like to have this feature: I want to control the charging current dependent on the status of my photovoltaic installation via an automation in Homeassistant. Is it possible to enable this value as read/write?
@squonk11 I can check this next week, if it is settable via the app, I should be able to include it in the lib.
@oliverrahner : It was settable with the previous version of the app (Volkswagen WeConnect) but with the new app (Volkswagen App) it is not settable any more - they removed this important feature from the app.
@squonk11 In your automation, use the action Call a service and set it up like below.
Using hybrid vehicles you can only set it to max or reduced.
@virtualdj : Thank you, I will try this during the next days.
@squonk11 I can check this next week, if it is settable via the app, I should be able to include it in the lib.
@oliverrahner Just check that the service is working, like in the picture I've posted above.
@virtualdj But if it isn't possible to set anymore in the app, I can't make that service work again... The backend has been completely reworked by VW, so we can't even check (easily) if they only removed it from the frontend, but it's still there as a feature on their servers.
Thanks so much for your work! Very much appreciate it.
The following sensors are missing now. Is it known/expected? I really use only the first one, though. The rest won't be missed.
Another thing is that there are now buttons for things that my Passat GTE 2018 doesn't support, such as locking doors/trunk. But I'd assume that as this part isn't fully finished yet, they'll lose their ability to change the state at a later point. Not a big deal anyway.
Nevertheless, thanks again for bringing the integration back to life!
First of all I would like to thank @robinostlund and @oliverrahner for their great work. Version 4.4.68 is running so far. However, all of my entity IDs have now changed, which is causing problems with automations.
e.g. before: tiguan_carid_battery_level now: tiguan_longname_carid_battery_level
Where can I change this entity name?
First of all I would like to thank @robinostlund and @oliverrahner for their great work. Version 4.4.68 is running so far. However, all of my entity IDs have now changed, which is causing problems with automations.
e.g. before: tiguan_carid_battery_level now: tiguan_longname_carid_battery_level
Where can I change this entity name?
That would be the "name" when you add the integration (defaults to VIN)
It might be possible to rename it to fix the entities, but if not, then remove the integration and add it back
@oliverrahner Today at midnight ( when the counter at VW was reset) and the Integration started working again I changed the Update interval from 5 to 10 Minutes but now at 11:50 I'm locked out again.
Is possible that it is not an Intervall Problem? I have an Iobroker Adapter for VW, that has an Intervall with 8min. And It was no Problem. In the Konfig can Set an Force Request and much more. I try it without them
But if it isn't possible to set anymore in the app, I can't make that service work again...
@oliverrahner @squonk11 It is available on the new Volkswagen app and has been there since the beginning. It's under Settings > Reduced AC current and it's a switch.
This feature is also working in the other backend library if you need to get the URL.
What was missing initially in the Volkswagen app was the windshield heather, but it has been added now.
Hi all,
First of all, thanks for the great work getting this to work again. 👍🏼
I got the Beta (v4.4.68) to work for a while, but after some time all sensors where unavailable i HomeAssistent. I then checked The Volkswagen app, and all sensors has disappeared from there also? Same, when I check the WeConnect website.
Is this the API thats been blocked? if so how do I get it unblocked again?
Thanks
Hi all,
First of all, thanks for the great work getting this to work again. 👍🏼
I got the Beta (v4.4.68) to work for a while, but after some time all sensors where unavailable i HomeAssistent. I then checked The Volkswagen app, and all sensors has disappeared from there also? Same, when I check the WeConnect website.
Is this the API thats been blocked? if so how do I get it unblocked again?
Thanks
Ah, it could be the same as this: https://github.com/robinostlund/homeassistant-volkswagencarnet/issues/507#issuecomment-1832792232
I will try to remove it from Homeassistsnt and wait until tomorrow 🤔
To begin, I really appreciate all work on this integration. I've been using it for over a year now and preferred using this over the Native Volkswagen app. Since they moved API to this new app, it has been a pain to keep track with my car. I'm very glad this new version brings it back to life!
For now my main issue is the missing features to control my parking heater (especially in the cold days now). Below the information on all sensors that my car (Arteon 2017 Diesel with Auxilary heater) had before, and which were recovered with the latest update:
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns="http://www.w3.org/TR/REC-html40">
Home Assisstant entity | Support | Current state -- | -- | -- binary_sensor.arteon_door_closed_left_back | Supported | off binary_sensor.arteon_door_closed_left_front | Supported | off binary_sensor.arteon_door_closed_right_back | Supported | off binary_sensor.arteon_door_closed_right_front | Supported | off binary_sensor.arteon_doors_locked | Supported | off binary_sensor.arteon_hood_closed | Supported | off binary_sensor.arteon_parking_light | Supported | off binary_sensor.arteon_request_in_progress | Supported | off binary_sensor.arteon_trunk_closed | Supported | off binary_sensor.arteon_trunk_locked | Supported | off binary_sensor.arteon_vehicle_moving | Supported | off binary_sensor.arteon_window_closed_left_back | Supported | off binary_sensor.arteon_window_closed_left_front | Supported | off binary_sensor.arteon_window_closed_right_back | Supported | off binary_sensor.arteon_window_closed_right_front | Supported | off binary_sensor.arteon_windows_closed | Supported | off device_tracker.arteon_position | Supported | home sensor.arteon_adblue_level | Supported | 10500 sensor.arteon_combustion_range | Supported | 540 sensor.arteon_fuel_level | Supported | 60 sensor.arteon_last_connected | Unavailable | unavailable sensor.arteon_last_trip_average_fuel_consumption | Supported | 6.5 sensor.arteon_last_trip_average_speed | Supported | 53 sensor.arteon_last_trip_duration | Supported | 73 sensor.arteon_last_trip_length | Supported | 65 sensor.arteon_odometer | Supported | 190805 sensor.arteon_oil_inspection_days | Supported | 610 sensor.arteon_oil_inspection_distance | Supported | 14100 sensor.arteon_parking_heater_heating_ventilation_duration | Unavailable | unavailable sensor.arteon_parking_heater_heating_ventilation_status | Unavailable | unavailable sensor.arteon_parking_time | Unavailable | unavailable sensor.arteon_request_results | Unknown | Unknown sensor.arteon_requests_remaining | Unknown | -1 sensor.arteon_service_inspection_days | Supported | 245 sensor.arteon_service_inspection_distance | Supported | 14100 switch.arteon_force_data_refresh | Supported | off switch.arteon_parking_heater_heating | Unavailable | unavailable switch.arteon_parking_heater_ventilation | Unavailable | unavailable
Only report issues here with the latest beta release and do not start any discussion here!
Thanks