Nissan Leaf Component(s)/Platform

Development
405

@andbad Running 0.117.6 fine here, sorry :confused:

406

You’re right. From yesterday, the error has returned. :frowning:
Today, I upgraded again to 0.117.6 and the error go away. It’s very strange.
Is there any kind of cache in the code?

EDIT: Nothing to do. After some restarts of HA, it has returned again. I don’t know what to do.

By(t)e

407

That seems to be the way it is, it’s usually the Nissan servers that are at fault (but not always)

408

It’s not Nissan servers.

  • All works ok.
  • Restart HA
  • Got the error.
  • Downgrade to 0.117.5
  • Upgrade to 0.117.6
  • Restart HA
  • All works ok

I make this steps in about 5 minutes. Meanwhile, the Nissan app and website works normally.
So, I think that something break when I restart HA.

By(t)e

409

It’s hit and miss depending on when you restart HASS and whether the Nissan servers are responding at that very moment, hence the inconsistency. Even when they seem relatively stable they can still do a bad reply

I doubt they changed anything, as they’re trying to phase this API out

410

I think that somethig break inside HA, when I restart it.
The API and the integration seems to work fine.

411

I wonder if upgrade did break the component? I get the same CarwingsError. After 0.118.0 upgrade all leaf enties gone. Usally when there is server problem the entites do not go away.

It is working on hassio 0.116.4

412

I confirm that the entities gone.
Post your details here: https://github.com/home-assistant/core/issues/43194

By(t)e

413

The integration broke between 0.118.0b2 and 0.118.0b3.
See this issue: https://github.com/home-assistant/core/issues/43312

414

Yeah, 0.118.0 has broken it a little. :slight_smile:

415

Has anyone updated to 0.118.2? Has it been repaired in that version?

416

Yes I’m running on 0.118.2 and problem remains.

417

Thanks, in that case I wouldnt update until fixed.

418

Has anyone updated to 0.118.4? Is it working now?

419

Nope. Its still missing

420

Same problem here. 0.118.4 still has the problem.

421

And 0.118.5 still has the issue as well. The integration is dead.

422

Going off the findings in that issue, it seems an update to the requests library broke it as there’s now a default user agent, which the Nissan API doesn’t like.

423

Does anyone know how to work around this?

424

Only fix atm is to downgrade to version 0.117.6