ta2k/iobroker.nissan

ioBroker Adapter for Nissan Connect

ioBroker.nissan

Tests:

This adapter uses Sentry libraries to automatically report exceptions and code errors to the developers.
For more details and for information how to disable the error reporting see Sentry-Plugin Documentation!
Sentry reporting is used starting with js-controller 3.0.

Nissan adapter for ioBroker

With the Nissan adapter you can ask your nissan vehicle for the latest data, display the current battery and charging status, the current state of the climate control, start or stop climate control and and start charging remotely.

Nissan Connect/App information

Forum

Feel free to follow the discussions in the german iobroker forum

Changelog

WORK IN PROGRESS

• (bolliy) Requirements from ioBroker Check and Service Bot

0.1.4 (2024-07-07)

• (bolliy) dependency and configuration updates
• (bolliy) breaking change: added Admin 5 configuration
• (bolliy) ConnectEV: update status before reading cachedeStatus
• (bolliy) improve State roles and types
• (bolliy) ConnectEV: update Blowfish v4.1

0.1.2 (2024-05-31)

• Refresh Token fix

0.1.1 (2024-05-20)

• Login fixed.

0.1.0 (2024-05-18)

• login fixed

0.0.2

• (TA2k) initial release

License

MIT License

Copyright (c) 2021-2024 TA2k [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

iobroker.nissan's Issues

Werte werden nicht aktualisiert

Describe the bug
Die Werte in ioBroker werden nicht automatisch aktualisiert. Erst wenn der Adapter pausiert und würden aktiviert wird, werden die aktuellen Daten angezeigt. Das Abfrageintervall steht auf 5Minuten.
Im Log habe ich einige Fehler bekommen.

Screenshots & Logfiles
Daten, die bis ca. 5.30 stimmten.

Daten, nach Restart des Adapter

Logfile:

Versions:

• Adapter version: 0.0.6
• JS-Controller version: 4.0.21
• Node version: 14.19.1
• Operating system: Linux

Update stable version in repo from 0.0.12 to 0.0.15

Think about update stable version to 0.0.15

Version: stable=0.0.12 (208 days old) => latest=0.0.15 (42 days old)
Installs: stable=80 (79.21%), latest=10 (9.9%), total=101
Click to edit

Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot

Dear adapter developer,

I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter nissan for common errors and appropiate suggestions to keep this adapter up to date.

Please see the result of the check below.

ioBroker.nissan

-

👍 No errors found

👍 No warnings found

Please review issues reported and consider fixing them as soon as appropiate.

Feel free to contact me (@ioBroker-Bot) if you have any questions or feel that an issue is incorrectly flagged.

And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.

your
ioBroker Check and Service Bot

Note: This issue replaces issue #36

@mcm1957 for evidence

Update stable version in repo from 0.1.2 to 0.1.4

Think about update stable version to 0.1.4

Version: stable=0.1.2 (52 days old) => latest=0.1.4 (15 days old)
Installs: stable=46 (38.02%), latest=8 (6.61%), total=121

Click to use developer portal
Click to edit

Do not close this issue manually as a new issue will be created if condition for update still exists.

Please drop a comment if any reason exists which blocks updating to version 0.1.4 at this time.

Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

Update stable version in repo from 0.0.12 to 0.1.2

Think about update stable version to 0.1.2

Version: stable=0.0.12 (565 days old) => latest=0.1.2 (15 days old)
Installs: stable=90 (70.31%), latest=18 (14.06%), total=128

Click to use developer portal
Click to edit

Do not close this issue manually as a new issue will be created if condition for update still exists.

Please drop a comment if any reason exists which blocks updating to version 0.1.2 at this time.

Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

Failing to get lock-status

I want to update a datapoint (nissan.0.SJNFAAZXXXXX.remote.charging-start) and I get the following message in the log:

nissan.0 | 2022-04-03 22:05:13.868 | error | Failing to get lock-status

I have a Nissan Leaf built in 2020.

Any idea, what is going wrong?

AxiosError: Request failed with status code 400

Version 0.0.15 (non-npm: TA2k/ioBroker.nissan) in /opt/iobroker/node_modules/iobroker.nissan, node: v18.16.1, js-controller: 4.0.24

Get Log:

AxiosError: Request failed with status code 400

"\n\n<html lang="en">\n\n <meta charset="utf-8">\n <meta http-equiv="X-UA-Compatible" content="IE=edge">\n <meta name="viewport" content="width=device-width, initial-scale=1">\n <meta name="description" content="OAuth2 Error">\n <title>OAuth2 Error Page</title>\n\n\n<body style="display:none">\n <div id="wrapper">Loading...\n <footer id="footer" class="footer">\n <script type="text/javascript">\n pageData = {\n realm : "\/a-ncb-prod",\n baseUrl: "https://prod.eu2.auth.kamereon.org:443/kauth/XUI/\",\n error: {\n description: "Client authentication failed",\n message: "invalid_client"\n }\n }\n </script>\n <script src="https://prod.eu2.auth.kamereon.org:443/kauth/XUI/main-authorize.js\"></script>\n\n\n"

No code received

"\n\n\n\n \n \n \n \n \n\n\n\n
Loading...
\n
\n \n \n\n\n"

Adapter will nicht mehr: Cloud not connect to https://gdcportalgw.its-mo.com/...

Hallo zusammen,

leider funktioniert mein Nissan Adapter seit Tagen nicht mehr.
Die Fehlermeldung lautet:

Error: Cloud not connect to https://gdcportalgw.its-mo.com/api_v210707_NE/gdc/: Request failed with status code 404.

Einloggen in der App geht und zeigt auch korrekte Daten.

Hat jemand eine Idee?
Vielen Dank schon mal!

Update stable version in repo from 0.0.2 to 0.0.3

Think about update stable version to 0.0.3

Version: stable=0.0.2 (126 days old) => latest=0.0.3 (73 days old)
Installs: stable=5 (45.45%), latest=2 (18.18%), total=11
Click to edit

AxiosError: Request failed with status code 400

Hab leider mit der aktuellsten Github Version wieder ein Problem:

Nissan Iobroker Installierte Version: 0.1.1

2024-05-30 19:01:08.723 error AxiosError: Request failed with status code 400
2024-05-30 19:01:08.723 error Refresh token failed
2024-05-30 19:01:08.602 error {"errors":[{"status":"Unauthorized","code":"401","title":"authentication","detail":"authentication failed","meta":[{}]}]}
2024-05-30 19:01:08.602 error AxiosError: Request failed with status code 401
2024-05-30 19:01:08.602 error Failing to get battery-status for SJNFAAxxxxxxx code: 401
2024-05-30 19:01:08.589 warn Authentication error, trying to refresh token

Auch bei allen Anderen Objekten

Tritt erst nach gewisser Zeit auf

Plattform: linux
Node.js: v18.16.1(18.20.3)
NPM: 9.5.1(10.7.0)

Keine Verbindung mehr möglich

Describe the bug
Seit dem letzten Nissan Update bekomme ich keine Verbindung mehr über den iob Adapter.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots & Logfiles

nissan.0	2022-10-22 18:01:27.766	Fehler	{"error_description":"Fehlender Parameter, 'Code'","Fehler":"invalid_request"}
nissan.0	2022-10-22 18:01:27.764	Fehler	AxiosError: Anforderung mit Statuscode 400 fehlgeschlagen
nissan.0	2022-10-22 18:01:27.761	Fehler	Zugriffstoken

Versions:

• Adapter version: 0.0.9
• JS-Controller version: 4.0.23
• Node version: v16.17.1
• Operating system: Ubuntu 18.04.6 LTS

typo in command to lock/unlock doors?

https://github.com/TA2k/ioBroker.nissan/blob/efe24f55144b005a9217eb624424b6044f4272bd/main.js#L708C13-L708C17

Shouldn't this be "action" : "lock" rather than "lock" : "lock" ?
I don't have a Nissan I have a Renault, but if I use "lock" : "lock" I get error 400, "Http message is not readable", while with "action": "lock" I get "403", "Access is denied for this resource"

Additionally, I think target is missing:

"target": "driver_s_door",

or

'doorType': 'driver_s_door'

, it's not clear...

I offer my help as a maintainer

Hey @TA2k,
I see that this adapter is having trouble keeping up with its releases. (#18)
I have also already submitted some pull requests, which you have kindly merged.

Do you happen to need help with this? Since I need the adapter for my leaf ze0, I would like to offer my help with maintenance.

Ich würde mich sehr freuen ;)

Stephan

Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot

Dear adapter developer,

I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter nissan for common errors and appropiate suggestions to keep this adapter up to date.

Please see the result of the check below.

ioBroker.nissan

-

ERRORS:

• ❗ [E204] Version "0.1.3" listed at common.news at io-package.json does not exist at NPM. Please remove from news section.

WARNINGS:

• 👀 [E851] .npmignore found but "files" is used at package.json. Please remove .npmignore.
• 👀 [W040] "keywords" within package.json should contain "ioBroker"
• 👀 [W162] js-controller 5.0.0 listed as dependency but 5.0.19 is recommended. Please consider updating dependency at io-package.json.

Please review issues reported and consider fixing them as soon as appropiate.

Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.

Warnings reported by repository checker should be reviewed. While some warnings can be considered as a suggestion and be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.

Feel free to contact me (@ioBroker-Bot) if you have any questions or feel that an issue is incorrectly flagged.

And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.

your
ioBroker Check and Service Bot

@mcm1957 for evidence

{"code":401,"reason":"Unauthorized","message":"Authentication Failed"}

Does not work anymore:

nissan.0	2021-09-19 21:30:28.819	error	{"error_description":"Invalid Token ID","error":"invalid_grant"}
nissan.0	2021-09-19 21:30:28.818	error	Error: Request failed with status code 400
nissan.0	2021-09-19 21:30:28.812	error	Access token
nissan.0	2021-09-19 21:30:28.295	error	{"code":401,"reason":"Unauthorized","message":"Authentication Failed"}
nissan.0	2021-09-19 21:30:28.294	error	Error: Request failed with status code 401
nissan.0	2021-09-19 21:30:28.293	error	Post JWT

Einloggen nicht möglich

Hallo zusammen,

wir haben seit 2 Tagen einen gebrauchten Leaf und ich benötige den SOC im ioBroker um die Ladung zu steuern.
Da das Fahrzeug Baujahr 2018 ist und die "alten" Registrierwege von Nissan gekappt wurden, hat der Nissan Kundendienst die Registrierung übernommen.
Die App auf dem Mobiltelefon funktioniert also.
Leider kann ich mich aber nicht über den Adapter einloggen.
Mit den Zugangsdaten, die ich in der App verwende kommt folgender Fehler:

nissan.0	2023-05-10 15:49:28.914	error	Error: error:0308010C:digital envelope routines::unsupported
nissan.0	2023-05-10 15:49:28.144	warn	Nissan EV not connected. Start Relogin
nissan.0	2023-05-10 15:49:28.141	error	TypeError: Cannot read properties of undefined (reading 'sessionInfo')
nissan.0	2023-05-10 15:49:28.139	info	Connected to Nissan EV
nissan.0	2023-05-10 15:49:28.136	error	Error: error:0308010C:digital envelope routines::unsupported
nissan.0	2023-05-10 15:49:26.695	info	Start Connecting to Nissan EV
nissan.0	2023-05-10 15:49:26.629	info	starting. Version 0.0.12 (non-npm: TA2k/ioBroker.nissan) in /opt/iobroker/node_modules/iobroker.nissan, node: v18.16.0, js-controller: 4.0.24

In der App habe ich den Haken bei "Old Nissan App" gesetzt da ich ja die "EV-App" nutze.
Wenn ich den Haken bei "Old Nissan App" entfernen klappt der Login, aber es wird kein Fahrzeug gefunden.
Auch das Handy habe ich vorher abgemeldet.

Hat hier jemand eine Idee?

Vielen Dank schonmal!

test and release

would you check the current status on github and create a minor release and push it to npm. With my rights I can't release a new version - I think. I will announce the beta version in the forum.

Thank you very much

Stephan

Invalid or missing token

Beschreibung des Bugs
Am Anfang wurde nur aktuallisiert, wenn ich vorher die Nissan Connect App geöffnet habe. Dann ein Update von 0.0.2 auf 0.0.4 durchgeführt, was aber keine Änderung brachte und jetzt seit ein paar Tagen (29.03) bekomme ich folgende Meldung im Log und keine Leaf-Änderungen mehr geladen. Nissan scheint dort etwas geändert zu haben.

Screenshots & Logfiles
Log-Info (xxx= waren andere Zahlen die ich für das Posting geändert habe):

nissan.0	2022-04-02 10:37:29.452	error	{"errors":{"status":"Unauthorized","code":"401000","title":"Unauthorized","detail":"Invalid or missing token","meta":[{"spanId":"xxx","traceId":"xxx","parentSpanId":"xxx","component":"alliance-platform-usersadapter-prod"}]}}
nissan.0	2022-04-02 10:37:29.448	error	Error: Request failed with status code 401
nissan.0	2022-04-02 10:37:28.668	info	Login successful

Versions:

• Adapter version: 0.0.4
• JS-Controller version: 4.0.21
• Node version: 14.19.1

Additional context
Dort ist überall ein grüner Haken:
Verbunden mit Host
Lebenszeichen
Verbunden mit Gerät oder Dienst

Request failed with status code 404

Error: Cloud not connect to https://gdcportalgw.its-mo.com/api_v210707_NE/gdc/: Request failed with status code 404
mit Old Nissan EV App for models before 2019
seit 17.5. und auch mit Version 0.1.0

Compatibility check to js-controller 4.0

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

If something is not correct this is logged as 'warning' or 'info' log.

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn or info log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1749

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!