Open d4icon opened 4 months ago
Hey there @epenet, mind taking a look at this issue as it has been labeled with an integration (renault
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
renault documentation renault source (message by IssueLinks)
One detail. The A/C call does work.
It is the other two that return the same error. (I tried with the car plugged in, of course).
I would love to be able to make it work for some automations.
Thanks
PD: car is new: Renault Scenic etech
Same issue with a new Megane Etech.
any news?
charge_start and charge_stop are not compatible with all vehicles, and there is no official documentation to know which vehicles work and which don't work.
It seems that the best workaround is to use instead the schedule mode (instant/calendar)
charge_start and charge_stop are not compatible with all vehicles, and there is no official documentation to know which vehicles work and which don't work.
It seems that the best workaround is to use instead the schedule mode (instant/calendar)
Mmm... But something doesn't add up for me.
There are colleagues with the Megane Etech, that it works for them and others that it doesn't (like the one above).
Something doesn't add up. And I find it strange that in my case (the new Scenic, which is practically a Megane Etech) it doesn't work either... or some do and some don't.
Could you give me more information or where to look? Any test that can be done?
Maybe they have updated the API or something new is required?
Using the programming does not work for me, as I want to use it to automate the charging, depending on the time and the price of kWh. The car falls asleep once you stop charging, and the charger does not wake it up. The only way is the car key, or from the official application, using the button to ‘start charging’ or ‘stop charging’.
I would really appreciate some help.
Translated with DeepL.com (free version)
I had a BMS update on my Megane my25, but I had to go back to the dealer to fix it.
The car no longer goes to sleep when charging stops.
Potentially the same fix for the Scenic is available?
I had a BMS update on my Megane my25, but I had to go back to the dealer to fix it.
The car no longer goes to sleep when charging stops.
Potentially the same fix for the Scenic is available?
How long ago was this? Well, I don't know if there is something similar in the Scenic.
Why did the car fall asleep if the charger stopped for some reason (lack of power at home for X minutes)?
Tell me more about it. Thanks
Had the update at the end of August, I don't know why the car stopped charging.
Worth booking it in.
charge_start and charge_stop are not compatible with all vehicles, and there is no official documentation to know which vehicles work and which don't work. It seems that the best workaround is to use instead the schedule mode (instant/calendar)
Mmm... But something doesn't add up for me.
There are colleagues with the Megane Etech, that it works for them and others that it doesn't (like the one above).
Something doesn't add up. And I find it strange that in my case (the new Scenic, which is practically a Megane Etech) it doesn't work either... or some do and some don't.
Could you give me more information or where to look? Any test that can be done?
Maybe they have updated the API or something new is required?
Using the programming does not work for me, as I want to use it to automate the charging, depending on the time and the price of kWh. The car falls asleep once you stop charging, and the charger does not wake it up. The only way is the car key, or from the official application, using the button to ‘start charging’ or ‘stop charging’.
I would really appreciate some help.
Translated with DeepL.com (free version)
@epenet any help? On the other hand... If the ‘start charging’ and ‘stop charging’ buttons work in the official Renault application, I find it strange that I can't use it from here.
Same problem here with the Scenic . Starting charge works fine from the MyRenault app, so the feature exist. I would be glad to help tracking the problem if someone can point me in the right direction
Same problem here with the Scenic . Starting charge works fine from the MyRenault app, so the feature exist. I would be glad to help tracking the problem if someone can point me in the right direction
exactly. This is what I meant, @epenet
The option is there and it works in the app. It should be able to be implemented here as well.
The Renault API is fully undocumented. The first step is to ensure it is working in renault-api: https://github.com/hacf-fr/renault-api
It is not working either. I have opened an issue here, but I have not idea if this is still maintained ... https://github.com/hacf-fr/renault-api/issues/1348
It is not working either. I have opened an issue here, but I have not idea if this is still maintained ... hacf-fr/renault-api#1348
Thanks - the library is still maintained but it relies on "discoveries" by users. So until a user discovers how to do start charge, then we're rather stuck
The Renault API is fully undocumented. The first step is to ensure it is working in renault-api: https://github.com/hacf-fr/renault-api
* If it is working there, it can be easily used in Home Assistant. * If it is not working there, then it needs to be added there before it can be used in Home Assistant.
OK, I'll give you some information, and some questions I have. I'll do it in the other repo as you indicated, which seems a more appropriate place.
The problem
Registrador: homeassistant.components.websocket_api.http.connection Fuente: components/websocket_api/commands.py:241 integración: Home Assistant WebSocket API (documentación, problemas) Ocurrió por primera vez: 11:55:18 (1 ocurrencias) Último inicio de sesión: 11:55:18
[140716478846368] Unexpected exception Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/renault/renault_vehicle.py", line 40, in wrapper return await func(self, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/renault/renault_vehicle.py", line 151, in set_charge_start return await self._vehicle.set_charge_start() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/renault_api/renault_vehicle.py", line 504, in set_charge_start response = await self.session.set_vehicle_action( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/renault_api/renault_session.py", line 261, in set_vehicle_action return await kamereon.set_vehicle_action( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/renault_api/kamereon/init.py", line 364, in set_vehicle_action await request( File "/usr/local/lib/python3.12/site-packages/renault_api/kamereon/init.py", line 157, in request kamereon_response.raise_for_error_code() File "/usr/local/lib/python3.12/site-packages/renault_api/kamereon/models.py", line 136, in raise_for_error_code error.raise_for_error_code() File "/usr/local/lib/python3.12/site-packages/renault_api/kamereon/models.py", line 98, in raise_for_error_code raise exceptions.KamereonResponseException( renault_api.kamereon.exceptions.KamereonResponseException: ('err.func.wired.forbidden', 'The access is forbidden')
The above exception was the direct cause of the following exception:
Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service response = await hass.services.async_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 2731, in async_call response_data = await coro ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 2774, in _execute_service return await target(service_call) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 999, in entity_service_call single_response = await _handle_entity_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1071, in _handle_entity_call result = await task ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/button/init.py", line 132, in _async_press_action await self.async_press() File "/usr/src/homeassistant/homeassistant/components/renault/button.py", line 47, in async_press await self.entity_description.async_press(self) File "/usr/src/homeassistant/homeassistant/components/renault/renault_vehicle.py", line 42, in wrapper raise HomeAssistantError(err) from err homeassistant.exceptions.HomeAssistantError: ('err.func.wired.forbidden', 'The access is forbidden')
What version of Home Assistant Core has the issue?
core-2024.7.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
renault
Link to integration documentation on our website
https://www.home-assistant.io/integrations/renault/
Diagnostics information
Registrador: homeassistant.components.websocket_api.http.connection Fuente: components/websocket_api/commands.py:241 integración: Home Assistant WebSocket API (documentación, problemas) Ocurrió por primera vez: 11:55:18 (1 ocurrencias) Último inicio de sesión: 11:55:18
[140716478846368] Unexpected exception Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/renault/renault_vehicle.py", line 40, in wrapper return await func(self, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/renault/renault_vehicle.py", line 151, in set_charge_start return await self._vehicle.set_charge_start() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/renault_api/renault_vehicle.py", line 504, in set_charge_start response = await self.session.set_vehicle_action( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/renault_api/renault_session.py", line 261, in set_vehicle_action return await kamereon.set_vehicle_action( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/renault_api/kamereon/init.py", line 364, in set_vehicle_action await request( File "/usr/local/lib/python3.12/site-packages/renault_api/kamereon/init.py", line 157, in request kamereon_response.raise_for_error_code() File "/usr/local/lib/python3.12/site-packages/renault_api/kamereon/models.py", line 136, in raise_for_error_code error.raise_for_error_code() File "/usr/local/lib/python3.12/site-packages/renault_api/kamereon/models.py", line 98, in raise_for_error_code raise exceptions.KamereonResponseException( renault_api.kamereon.exceptions.KamereonResponseException: ('err.func.wired.forbidden', 'The access is forbidden')
The above exception was the direct cause of the following exception:
Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service response = await hass.services.async_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 2731, in async_call response_data = await coro ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 2774, in _execute_service return await target(service_call) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 999, in entity_service_call single_response = await _handle_entity_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1071, in _handle_entity_call result = await task ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/button/init.py", line 132, in _async_press_action await self.async_press() File "/usr/src/homeassistant/homeassistant/components/renault/button.py", line 47, in async_press await self.entity_description.async_press(self) File "/usr/src/homeassistant/homeassistant/components/renault/renault_vehicle.py", line 42, in wrapper raise HomeAssistantError(err) from err homeassistant.exceptions.HomeAssistantError: ('err.func.wired.forbidden', 'The access is forbidden')
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response