Do you need to disable the integration, or just change the update interval?
I’m not sure about the mqtt variant of this, but using the integration that works directly in HA, the documentation includes information on how to request an adhoc update. Perhaps you could set the update interval to be very infrequent and then write an automation in HA which does more frequent polling for updates. You could either switch that automation off through the UI (perhaps remotely using Nabu Casa), or implement a variable/helper that tells the whole system when you are on vacation.
When I stayed in due to COVID self isolation, I think after something like 14 days, the car automatically stop responding to Nissan server polling. The integration will only throw up an error in the logs so not noticeable during vacation, but very noticeable when I’m restarting HA to tweak settings.
So I wouldn’t worry about it.
But don’t let the 12v run flat. The car electronics require the 12v to “jump start” the main traction battery. You can buy the cheapest power-bank car jump start kit. It only needs 12v and doesn’t require normal ICE car level of jump start current, so if it does go flat, just connect this up and it will start. Once the main battery is powered up, it will recharge the 12v.
Hi
I have managed to install Leaf2mqtt and install mosquitto. The logs show it is logging in and I have added the integration of the battery received, battery updated and battery level. But they are all showing as unavailable.
I will have missed something but wondered if someone could help. I ahve been using HA for about 1 month so all new!
I gave up on the Nissan Leaf integration with haos for a while and I decided to give another try recently (mostly with node red) but service refresh work very really, I don’t think anything is wrong with my flow ?
just running a manual refresh now and the last refresh date in HA it’s still from yesterday (before 4 refresh automation)
Hey,
i’m the the UK and just taken delivery of the new Nissan Leaf 2022 model. is there any versions on this that will work with my car.
I run Home Assistant Operating System
Yup, that sounds normal for the Nissan Servers! But to be more helpful, I found that I was able to debug the Nissan login issues using a third party app called Quickleaf (android only I think). Using that I quickly found that the login credentials used by the Nissan app are slightly different to those used by HA but the same as those used by Quickleaf. There’s no rocket science involved, but the app allows you to test the logins and be certain you’ve got it right far faster than restarting HA.
You timed your installation poorly: Nissan have just changed their endpoint and authentication. Tobias Westergaard Kjeldsen is the author of dartnissanconnect, the library that underlies these and his own MyLEAF phone app — he has just published updates to the library to align to these changes.
For your add-on to work, you’ll need the add-on to be re-built to pull in the new library. I’ve done this for my OG leaf2mqtt Docker container, which is successfully pulling in data this morning, but I expect there’s work for at least one of @Sriracha and @EtienneMD to do here to get the add-on working again. You might want to try simply removing and re-adding it: that might force a rebuild which would make it work.
(No changes needed to the code chaps — just need to rebuild with the updated library included.)
Again as per @Troon 's post it seems the work to make the login work correctly has been done. But for people without docker/linux skills (like myself), we need to humbly and patiently wait for somebody in the community with the skills to update the Leaf2MQTT Add-on …