Betatest - Renault ZE Services Binding

sihui · July 29, 2023, 5:55am

No, sorry, I am using Sitemaps with BasicUI and Android App.

Doug_Culnane · July 30, 2023, 3:05pm

I do not have a widget but I have a basic openHAB 4 page. Let me know if you need this but it is quite easy to make your own.

Doug_Culnane · July 30, 2023, 3:07pm

Sorry for the slow reply. How about the error to debug but the “lock status disabled message” to stay at warn? (The log is the only location I have to display things that are not working and why.)

sihui · July 30, 2023, 3:25pm

Not a problem at all.
I know you would have answered faster if I had reported a binding malfunction

That is perfectly fine. It just would show a cleaner openHAB startup, and if someone does not like it one can set the binding to error anyway.

Pinocchio · July 31, 2023, 7:09am

Odometer and Estimated Range is showing meters and not kilometers?
Have played with gain and also unit metric change, but I didn’t get it.
How can I transform the value from meters to kilometers?

sihui · July 31, 2023, 7:59am

Assuming you are on openHAB4:

this config

Number:Length ZOE_km "Kilometerstand [%.0f km]" {unit="km", channel="renault:car:zoe:odometer"}
Number:Length ZOE_distance "Reichweite [%.0f km]" {unit="km", channel="renault:car:zoe:estimatedrange"}

shows

odo

range

Doug_Culnane · August 4, 2023, 9:03am

PR for your logging request here:

sihui · April 19, 2024, 7:25am

Since around three days there are reports of missing data from several sources (other home automation forums, stand alone php scripts) for the Renault servers.

I am seeing the same, neither the Renault app nor this bindings shows all previous available data for our Renault ZOE PhII. All Remote Services were renewed in February 2024 and are valid three years.

debug.log

2024-04-19 09:06:18.042 [DEBUG] [lt.internal.api.MyRenaultHttpSession] - Kamereon Request: https://api-wired-prod-1-euw1.wrd-aws.com/commerce/v1/accounts/18029234-4f00-479e-89e4-c376aecc3085/kamereon/kca/car-adapter/v1/cars/VF1XXXXXXXXXX/lock-status?country=DE Response: [404] Not Found
{"type":"FUNCTIONAL","messages":[{"code":"err.func.wired.notFound","message":"{\"errors\":[{\"errorCode\":404,\"errorMessage\":\"There is no data for this vin and uid\",\"errorLevel\":\"error\",\"errorType\":\"functional\"}],\"error_reference\":\"rrt-071990d735b57f7a5-c-eu-18017-5913616-95\"}"}],"errors":[{"errorCode":"err.func.wired.notFound","errorMessage":"{\"errors\":[{\"errorCode\":404,\"errorMessage\":\"There is no data for this vin and uid\",\"errorLevel\":\"error\",\"errorType\":\"functional\"}],\"error_reference\":\"rrt-071990d735b57f7a5-c-eu-18017-5913616-95\"}"}],"error_reference":"FUNCTIONAL"}
2024-04-19 09:06:18.063 [WARN ] [ault.internal.handler.RenaultHandler] - Disabling unsupported lock status update.

trace.log

2024-04-19 09:08:25.460 [TRACE] [lt.internal.api.MyRenaultHttpSession] - GigyaApi Request: https://accounts.eu1.gigya.com/accounts.getAccountInfo Response: [200] OK
{
  "callId": "038757474631484bbfd52795c39ae372",
  "errorCode": 0,
  "apiVersion": 2,
  "statusCode": 200,
  "statusReason": "OK",
  "time": "2024-04-19T07:08:25.441Z",
  "registeredTimestamp": 1596643887000,
  "UID": "0797a2bf93b7446c950dfaabxxxxxxxxxxxxxxx",
  "UIDSignature": "a1kQuIqgfwCjqKwFxxxxxxxxxxxxx",
  "signatureTimestamp": "1713510505",
  "created": "2020-08-05T16:11:27.855Z",
  "createdTimestamp": 1596643887000,
  "data": {
    "personId": "44bcc109-6162-4703-818e-xxxxxxxxxxxxxxxxx",
    "gigyaDataCenter": "eu1.gigya.com"
  },
  "preferences": {},
  "emails": {
    "verified": [
      "xxxxxxx@xxx.de"
    ],
    "unverified": []
  },
  "isActive": true,
  "isRegistered": true,
  "isVerified": true,
  "lastLogin": "2024-04-19T07:08:25.287Z",
  "lastLoginTimestamp": 1713510505000,
  "lastUpdated": "2020-08-05T16:11:54.340Z",
  "lastUpdatedTimestamp": 1596643914340,
  "loginProvider": "site",
  "oldestDataUpdated": "2020-08-05T16:11:27.855Z",
  "oldestDataUpdatedTimestamp": 1596643887855,
  "password": {
    "created": "2022-03-21T23:00:51.909Z"
  },
  "profile": {
    "email": "xxxxxxxx@xxx.de"
  },
  "registered": "2020-08-05T16:11:27.954Z",
  "socialProviders": "site",
  "verified": "2020-08-05T16:11:54.340Z",
  "verifiedTimestamp": 1596643914340
}
2024-04-19 09:08:25.481 [DEBUG] [lt.internal.api.MyRenaultHttpSession] - personId ID: 44bcc109-6162-4703-818e-xxxxxxxxxxxxxxxxxxxxxx gigyaDataCenter: eu1.gigya.com
2024-04-19 09:08:25.562 [TRACE] [lt.internal.api.MyRenaultHttpSession] - GigyaApi Request: https://accounts.eu1.gigya.com/accounts.getJWT Response: [200] OK
{
  "callId": "a2cd8769bf8642a8bb2b8e77efbe0294",
  "errorCode": 0,
  "apiVersion": 2,
  "statusCode": 200,
  "statusReason": "OK",
  "time": "2024-04-19T07:08:25.541Z",
  "ignoredParams": [
    {
      "paramName": "personId",
      "warningCode": 403007,
      "message": "This parameter was not recognized as valid for this API method with your security credentials nor was it recognized as a standard Gigya control parameter."
    },
    {
      "paramName": "gigyaDataCenter",
      "warningCode": 403007,
      "message": "This parameter was not recognized as valid for this API method with your security credentials nor was it recognized as a standard Gigya control parameter."
    }
  ],
  "id_token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsImtpZCI6IlJFUTBNVVE1TjBOQ1JUSkVNemszTTBVMVJrTkRRMFUwUTBNMVJFRkJSamhETWpkRU5VRkJRZyJ9.eyJpc3MiOiJodHRwczovL2ZpZG0uZ2lneWEuY29tL2p3dC8zXzdQTGtzT3lCUmtIdjEyNng1V2hIYi01cHFDMXFGUjhwUWp4U2VMQjZuaEFuUEVSVFVsd25Zb3puSFN4d1g2NjgvIiwiYXBpS2V5IjoiM183UExrc095QlJrSHYxMjZ4NVdoSGItNXBxQzFxRlI4cFFqeFNlTEI2bmhBblBFUlRVbHduWW96bkhTeHdYNjY4IiwiaWF0IjoxNzEzNTEwNTA1LCJleHAiOjE3MTM1MTA4MDUsInJpc2tTY29yZSI6MC4wLCJzdWIiOiIwNzk3YTJiZjkzYjc0NDZjOTUwZGZhYWI5YTMxZjRlMCIsImRhdGEucGVyc29uSWQiOiI0NGJjYzEwOS02MTYyLTQ3MDMtODE4ZS1iOTk5N2I3Nzg1YWUiLCJkYXRhLmdpZ3lhRGF0YUNlbnRlciI6ImV1MS5naWd5YS5jb20ifQ.DUmjXY8KetLSGKgEUYovGQz8_PYBSnltkRN5l179le-lyLMTPGr73BV_6aOMZ6pryWjfekZIMX2pYL6-KYAIb78rcRerPSQrxDUyMcFml7GfdAWZPyfboRSvO3alm5oIKn2oQeNV5eTIrHMB-wbU-W-o5MsnjziqCKbKhdKWle7X01nbvF5DmIGEHLg4CE9b3pkKtK-C9V26mssGzaNb5p4jtjOmjU27RKHBg8vWRsZXsgXc8Bnlt_bBax-zjBrB1PsV6QqqH1RiM0fgcQ9uGDt-a2-4gdofYn3YhZbK6d6YAYZ4Vy2KcwSCznzwYt0iEol4JqnNy_yoLQjsUE8JBw"
}

sihui · April 19, 2024, 10:30am

Since a couple of hours everything seems to be working again

StefanSiarzewski · April 19, 2024, 2:59pm

For 3 days now, the odometer (mileage) has stopped displaying correctly - the MyRenault application has the correct value (the same as in the car)
via renault-api I also receive the correct value, but with Renault openhab binding the mileage value stopped 3 days ago

by the way,
checking renault-api, I see that the item has appeared
“Charge rate” - I don’t know if it was also available before, but maybe it’s worth adding to the binding?

My car is Zoe ZE50
I’ve been using the binding for less than a year and so far everything has worked perfectly.

sihui · April 19, 2024, 3:52pm

Unfortunately I did not look close enough to my own data, you are correct, the odometer Channel does not get the correct mileage of the car.

I found in another forum, that there are two different datapoints for that reading (/cockpit) in the Renault api, version 1 and version 2. Version 1 has the correct odometer reading, version two does not have the correct reading anmyore.

@Doug_Culnane, could you please have a look if you got some spare time? Maybe you should wait a couple of days for a fix, because three days ago version 2 of the mentioned datapoint was still working

Edit: I read in another home automation forum, that they even have the option to switch between the two different cockpit datapoints, because Renault seems to change that from time to time …

Doug_Culnane · April 19, 2024, 5:19pm

Thanks for the info. Lets see what the stable fix (if needed) is likely to be, then I can modify the binding.

StefanSiarzewski · April 21, 2024, 11:30am

github.com/openhab/openhab-addons

[Renault] Cockpit/odometer information no longer retrieved

opened 05:53PM - 20 Apr 24 UTC

maxonthegit

bug

## Expected Behavior One of the channels exposed by things created with the [Re…nault binding](https://www.openhab.org/addons/bindings/renault/) is `odometer`, which is supposed to indicate the total distance traveled so far. Linking a _Number_ type item to this channel is expected to provide a reading of the car odometer. ## Current Behavior Up to a few days ago, the odometer reading was regularly available. Then, suddenly, the linked item just ceased to be updated: the car odometer in the _My Renault_ mobile app continued to increase, confirming that such information is available in the My Renault cloud, but the item was just frozen at the last available reading. None of the following attempts restored the expected odometer reading: * pausing and resuming the thing created with the Renault binding * creating a new Renault car thing from scratch and linking the existing item to its `odometer` channel * forcedly setting the existing item to a different value from the Karaf console and waiting for it to be updated * creating a new item and linking it to the `odometer` channel No relevant errors appear in the Karaf console using `log:tail` when either of the aforementioned actions is undertaken (just some warnings about known unsupported features of this car model, like lock status update, HVAC and battery status; these have always been there anyway). ## Possible Solution Developers of the [renault-api project](https://github.com/hacf-fr/renault-api), the openHAB Renault binding is based upon, have already spotted a change in the Renault API that causes cockpit reading to fail being retrieved: this is documented in their [issue #1135](https://github.com/hacf-fr/renault-api/issues/1135). As a fallback, the API call for the cockpit data should be reverted to using version 1 of the API. As of version 4.1.2 of openHAB and of the `org.openhab.binding.renault` binding, this corresponds to updating [line 238](https://github.com/openhab/openhab-addons/blob/f466c88406c506baf75ddccd9df597cf4aa3d964/bundles/org.openhab.binding.renault/src/main/java/org/openhab/binding/renault/internal/api/MyRenaultHttpSession.java#L238) of file `/bundles/org.openhab.binding.renault/src/main/java/org/openhab/binding/renault/internal/api//MyRenaultHttpSession.java` from: ``` + "/kamereon/kca/car-adapter/v2/cars/" + config.vin + "/cockpit?country=" + getCountry(config)); ``` to: ``` + "/kamereon/kca/car-adapter/v1/cars/" + config.vin + "/cockpit?country=" + getCountry(config)); ``` To verify this suggestion, I have attempted to rebuild the addon using Maven after applying this change, and the `odometer` reading became available again in the usual expected way. ## Steps to Reproduce (for Bugs) 1. Install the [Renault binding](https://www.openhab.org/addons/bindings/renault/) in an openHAB 4.1.2 instance. 2. Create a thing using the Renault binding. 3. Create a _Number:Length_ item pointing to the `odometer` channel of the freshly created thing. 4. Check that the item is never updated. ## Context N/A ## Your Environment I am using the latest stable (4.1.2, release build) version of openHAB, packaged in a Docker container created from its [stock `openhab/openhab` image](https://hub.docker.com/r/openhab/openhab/). Although this is of limited relevance, Docker is executed on a Raspberry Pi OS/Raspbian installation which is at release 11 (bullseye).

looks like a path to solving the problem

Doug_Culnane · April 22, 2024, 6:03am

Thanks for the excellent bug report and fix suggestion. I have opened a pull request.

github.com/openhab/openhab-addons

[Renault] Cockpit/odometer information no longer retrieved #16669

openhab:main ← dougculnane:BUG-16669

opened 06:01AM - 22 Apr 24 UTC

dougculnane

+1 -1

# [Renault] Cockpit/odometer information no longer retrieved #16669 As per th…e excellent Bug report this apply the suggested fix. # Description The odometer information no longer works in version 2 of the API so switching to V1 restores this channel. This is a problem on the Renault API but the suggested fix repairs the binding. # Testing This was built and tested on my installation and the odometer value is updated again. Also the Bug report suggest this fix worked on their test installation.

JensA · May 1, 2024, 5:40am

Is there a chance to get this fix for OH 3.4.x?