Betatest - Renault ZE Services Binding

I am seeing this since a couple of weeks, but only temporary for one or two hours. After that updates are coming in again.

I saw this yesterday or the day before yesterday, but at the moment log is clean and updates are coming in.

1 Like

Thanks for the feedback. That is 3 installations I know of with this problem, so I guess all have this issue.

It would be interesting to know if the App works when the binding does not? There might be an issue between the car and the Renault server which I can not fix. However if the logs show an distinct error and the app works then i can try to fix with a catch and re-login or something


IIRC the app did not work either, but I will pay more attention to that if the issue occurs again and report here.

1 Like

Several times in the last weeks I got

2025-11-17 09:01:50.677 [WARN ] [nding.renault.internal.handler.RenaultHandler] - Error My Renault Http Session.
org.openhab.binding.renault.internal.api.exceptions.RenaultUpdateException: java.util.concurrent.ExecutionException: org.eclipse.jetty.client.HttpResponseException: HTTP protocol violation: Authentication challenge without WWW-Authenticate header
	at org.openhab.binding.renault.internal.api.MyRenaultHttpSession.getKamereonResponse(MyRenaultHttpSession.java:325) ~[?:?]
	at org.openhab.binding.renault.internal.api.MyRenaultHttpSession.getAccountID(MyRenaultHttpSession.java:192) ~[?:?]
	at org.openhab.binding.renault.internal.api.MyRenaultHttpSession.initSesssion(MyRenaultHttpSession.java:81) ~[?:?]
	at org.openhab.binding.renault.internal.handler.RenaultHandler.getStatus(RenaultHandler.java:252) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) ~[?:?]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:358) ~[?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
	at java.lang.Thread.run(Thread.java:1583) [?:?]
2025-11-17 09:01:56.006 [WARN ] [nding.renault.internal.handler.RenaultHandler] - Error updating HVAC status.
org.openhab.binding.renault.internal.api.exceptions.RenaultUpdateException: java.util.concurrent.ExecutionException: org.eclipse.jetty.client.HttpResponseException: HTTP protocol violation: Authentication challenge without WWW-Authenticate header
	at org.openhab.binding.renault.internal.api.MyRenaultHttpSession.getKamereonResponse(MyRenaultHttpSession.java:325) ~[?:?]
	at org.openhab.binding.renault.internal.api.MyRenaultHttpSession.getHvacStatus(MyRenaultHttpSession.java:228) ~[?:?]
	at org.openhab.binding.renault.internal.handler.RenaultHandler.updateHvacStatus(RenaultHandler.java:275) ~[?:?]
	at org.openhab.binding.renault.internal.handler.RenaultHandler.getStatus(RenaultHandler.java:265) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) ~[?:?]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:358) ~[?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
	at java.lang.Thread.run(Thread.java:1583) [?:?]

but it always recovered by itself.
So I am not worried about this, just for information :innocent:

1 Like

I just got an email from Renault saying they will shortly using 2FA (extra code via email) on accounts and web services.
Let’s see what happens to the function of the binding, then :innocent:

1 Like

Me too :melting_face:

and me too


Will be upgrade for new model cars ?? ( Renault 5 E-Tech in my example) . Everything is working, beside HVAC. Debug:

[DEBUG] Kamereon Request: https://api-wired-prod-1-euw1.wrd-aws.com/.../actions/hvac-start
Response: [400] Bad Request
{“type”:“FUNCTIONAL”,“messages”:[{“code”:“err.func.wired.invalid-body-format”,“message”:“Body has at least one wrongly formatted value”}],“errors”:[{“errorCode”:“err.func.wired.invalid-body-format”,“errorMessage”:“Body has at least one wrongly formatted value”}],“error_reference”:“FUNCTIONAL”}

1 Like

Hey all.

I have conntected my Zoe successful with the renault binding.

All is working fine, except “battery available engergy”. It shows “NULL”.

Does anybody have the same problem?

BTW. In the past I remember having es well external and internal temperatures. Is this not supported anymore?

Good morning everyone, I noticed that since 24th of March the values of my Zoe are no longer updated (especially SoC). As the MyRenault App also shows outdated values, I assume that this is not a problem of the binding, but one of the Renault backend. Just for curiosity: Does anyone here see similar problems?

I will contact Renault support now.

You are correct that if the App and the binding are both not working then it is the Renault Backend.

From my observations the Renault Backend can fail temporarily, but if it goes on longer than a few days or some “services” do not work then the My Renault account might be the issue.

Check the My Renault website to see if your account need to be renued.

Hi @Doug_Culnane , just checked my account and it says that I have booked all available services. I now opened a support case at Renault, let’s wait for the response. I keep you updated.

1 Like

Not sure why the battery available energy is not working. You would have to set logging to debug and inspect the messages from the backend so we can see if and what values are delivered.

External temperatures never worked on my car/account.. The internal temperature is a setting for the HVAC thermostat but I am not sure if this has any affect.

In my case, since March 22nd, the binding can’t connect and the app says I need to re-enable “data sharing” from the car


Not sure if it is similar to your problem?

That’s what I am seeing, too. (ZOE 10/2020)
But I had never outages for more than a couple of hours.

Unfortunately I never could make the hvac channel working, but that is another story :person_shrugging:

HVAC stopped working on our car too but I think this is because of the account and the services available on it. However I am not sure.

For me it still works with the Renault App on Android and also with an external php script (GitHub - db-EV/ZoePHP: Unofficial PHP client for Renault Zoe · GitHub) as a workaround.
It is called from openHAB through executeCommandLine and cURL. In the php code the url is

echo '<TR><TD COLSPAN="2"><A HREF="'.$requesturi.'?acnow">'.$lng['Start preconditioning'].'</A></TD></TR>'."\n";

If you have some spare time you maybe could take a look at the Renault binding debug log :innocent: :

events.log:

2026-03-27 14:07:05.969 [INFO ] [openhab.event.ItemCommandEvent               ] - Item 'ZOE_ac' received command ON (source: org.openhab.ui.basic$wss3:030801=>org.openhab.core.io.rest)
2026-03-27 14:07:05.994 [INFO ] [openhab.event.ItemStatePredictedEvent        ] - Item 'ZOE_ac' predicted to become ON
2026-03-27 14:07:06.016 [INFO ] [openhab.event.ItemStateChangedEvent          ] - Item 'ZOE_ac' changed from OFF to ON (source: org.openhab.core.autoupdate.optimistic)
2026-03-27 14:07:06.039 [INFO ] [openhab.event.ItemStateChangedEvent          ] - Item 'ZOE_ac' changed from ON to PENDING (source: org.openhab.core.thing$renault:car:zoe:hvacstatus)
2026-03-27 14:07:38.169 [INFO ] [openhab.event.ItemStateChangedEvent          ] - Item 'ZOE_ac' changed from PENDING to OFF (source: org.openhab.core.thing$renault:car:zoe:hvacstatus)

debug log:

2026-03-27 14:07:07.246 [DEBUG] [ing.renault.internal.api.MyRenaultHttpSession] - Kamereon Request: https://api-wired-prod-1-euw1.wrd-aws.com/commerce/v1/accounts/1234-1234-1234-1234/kamereon/kca/car-adapter/v1/cars/YXZYXZYXZYXZYXZ/actions/hvac-start?country=DE Response: [400] Bad Request
{"type":"FUNCTIONAL","messages":[{"code":"err.func.wired.invalid-body-format","message":"Body has at least one wrongly formatted value"}],"errors":[{"errorCode":"err.func.wired.invalid-body-format","errorMessage":"Body has at least one wrongly formatted value"}],"error_reference":"FUNCTIONAL"}

If you need the full debug log with “GigyaApi jwt” and “personId ID” I could send that via PM.

I am on openHAB 5.2.0.M2.

Found at least one reason: Zoe system info showed no network connection, did not even show IMEI info. This led me to the assumption that the TCU needs a reset; this can be done by pulling fuse F31 (there is a youtube video showing where it is placed; it is a 10A fuse, 2nd row from the left, 2nd position from the bottom). After pulling it for 1 min and putting it back in network connectivity came back and IMEI is also shown. Now I wait for the SoC to be updated in the backend, which might take a couple of minutes.

1 Like

Backend is updated now also :slight_smile:

Thank you @sihui for this bug report. I finally debugged this properly and have created a PR. The start HVAC works with this fix.

Sorry it took me a long time to get round to this.

1 Like