Nissanleaf

[filcole]

Description:

Follow-up to pull request #19786 for Nissan Leaf integration to try to fix issues identified by @MartinHjelmare.

Improvements remaining to be made (at least!):

• how to implement start charging. Switch (status quo), scene + sensor, or service + sensor.
• icons
• remove time.sleep(x)

**Pull request for home-assistant.io with documentation has already been merged: home-assistant/home-assistant.io#8073 but needs to be updated to include new service.

Example entry for configuration.yaml:

nissan_leaf:
  username: "username"
  password: "password"
  region: 'NE'     # Indicates Europe, must be changed for other regions
  nissan_connect: true  # Set to false for early Leafs 24kWh that don't report location
  update_interval: 
    hours: 1
  update_interval_charging: 
    minutes: 15
  update_interval_climate: 
    minutes: 5
  force_miles: true

Two new services exposed:

- service: nissan_leaf.update
  data:
    vin: XXXXXXXXXX

- service: nissan_leaf.start_charge
  data:
    vin: XXXXXXXXXX

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
• New dependencies are only imported inside functions that use them ([example][ex-import]).
• New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
• New files were added to .coveragerc.

If the code does not interact with devices:

• Tests have been added to verify that the new code works.

[MartinHjelmare]

Please rebase the branch on latest dev, so only the new commits after the last PR was merged are in this branch.

[MartinHjelmare]

For charging I think a custom service in the component + a sensor or binary sensor entity that exposes charging status sounds good.

[MartinHjelmare]

Yes! Service + sensor is a good idea! 👍

The service should be registered in the nissan_leaf component.

[filcole]

Converted to a service and sensor in commit 9fa7369

[MartinHjelmare]

Great!

[MartinHjelmare]

Please link a docs PR with the update for the new service.

[filcole]

Here's the PR for the updated docs that include the new service, home-assistant/home-assistant.io#8630

[DevSecNinja]

Thanks for this great new component! I'm testing it now with my Nissan Leaf 2018 TEKNA. Everything seems to work fine and fast! I'm confident that this works much better than the Nissan app, as I've been using the other non-official component as well. 👍

[filcole]

Please link a docs PR with the update for the new service.

@MartinHjelmare apologies for the delay - I've linked the new docs PR to this PR.

[BenWoodford]

Slight correction in the docs: 2015s have CarWings too. The cut-off was the 16 plate 24kwh and the 65 plate 30kwh I believe.

The easiest way to identify is that Nissan Connect's T&C buttons are orange and blue, CarWings they're both blue. Or just look for anything saying "CarWings" in Settings.

[MartinHjelmare]

Please open an issue in or make a PR to the docs repo.