Integration for NissanConnect Services

Feature Requests
136

Glad its all working for you! If theres anything more you want to see or come across any bugs, I’d appreciate any help in the development :slight_smile:

137

The trip history entity code is here and then instantiated up here.

138

I can log in to the same network without problems, I use the ios application

I have a generated password, quite complex, but I don’t think it’s the problem here, I tried with a wrong password and I get another error, wrong password.

I really don’t understand what the problem is

139

that’s it, I managed to make it work, the problem in my case was with the location variable, I commented the location update and now it works.

140

Interesting - do you have car tracking in the app?

141

that icon is disabled, i think you need a separate subscription for that?

nissan
nissan722×488 160 KB

142

So I wasn’t showing the device_tracker entity unless you had the subscription but was still trying to fetch the data. Would you mind trying v0.3.3-beta.1 (guide for beta installing)? This should be fixed in that version

143

nop, i have same error

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 406, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/nissan_connect/__init__.py", line 48, in async_setup_entry
    await hass.async_add_executor_job(vehicle.refresh)
  File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/nissan_connect/kamereon.py", line 874, in refresh
    self.fetch_all()
  File "/config/custom_components/nissan_connect/kamereon.py", line 878, in fetch_all
    self.fetch_location()
  File "/config/custom_components/nissan_connect/kamereon.py", line 909, in fetch_location
    raise ValueError(body['errors'])
ValueError: [{'status': '403', 'code': 'gateway.processing', 'title': 'VNEXT', 'detail': '403 Forbidden403 FORBIDDEN'}]
144

My bad, I messed up the check. v0.3.3-beta.2?

145

to be more clear, I commented these lines and after everything was ok.
nissan2

1 Like
146

Yes, now it works!

Thank you!

1 Like
147

how did you manage to have the door control?

148

This is outstanding. Thank you for your work here.

I’m in the US with a 23 Ariya. I’m unfortunately receiving invalid credentials when I try to sign in. I’ve double checked my username and password as valid, and even did a password reset to confirm. Could it be an issue with the US API?

149

I’ll update the GitHub page to make it more clear, but currently only Europe is supported. The API integration is based on dartnissanconnect, and this is a blog from the creator explaining the problems with the US implementation:

If anyone is interested in developing/maintaining NA API support, get in touch! :slight_smile:

1 Like
150

Hi all, I’ve just started noticing today that I cannot connect to my car via Node-Red. At about 10am this morning, I had the last communication. I haven’t changed anything, so I’m wondering if something has changed on the Nissan server end. Anyone else having problems? Can see in the Node-Red debug that i get a ‘“TypeError: Cannot read properties of undefined (reading ‘vehicle’)”’ warning. The Node-Red logs also show the same…

The Nissan Connect app seems to be working

151

Looks like Nissan have changed the way auth works. I’m tracking this on GitHub, Stopped loading · Issue #23 · dan-r/HomeAssistant-NissanConnect · GitHub

2 Likes
152

To fix, the node red flows, you will need to change some config in the authentication nodes :

image
image811×137 12.4 KB

Set client-id : a-ncb-nc-android-prod
and client-secret to : 6GKIax7fGT5yPHuNmWNVOc4q5POBw1WRSW39ubRA8WPBmQ7MOxhm75EsmKMKENem

image
image742×67 5.12 KB

once done and deployed, refresh the tokens by activating the timestamp triggers.

1 Like
153

This has me authenticating again and it returns climate data but the most important values, battery % is not:

status: "Not Implemented"
code: "501"
title: "Not supported Feature"
detail: "This feature is not technically supported by this gateway"

Working for you guys?

154

@sd_dracula ado you have an Ariya or Leaf, I know they both use different endpoints, for me after I Changed the authentication, all is working.
I’m receiving all telemetry.

155

Yes I had used the new flow and that was the issue.
Once I just update the new values into my existing one it started to work again :+1: