0.89: Nissan Leaf, PlayStation 4, Point alarm control, Owlet baby monitor

[hulkhaugen]

Prevent partial custom component overlays (@balloob - #21070) (breaking change)

So does this mean that a custom device_tracker will stop working, or is that a domain and not a component? I’m using a custom asuswrt device-tracker as the original haven’t been working since 0.81.6, and i’m quite dependent on this for my automations.

[finity]

@hulkhaugen

as the original haven’t been working since 0.81.6

I’m on v88.1 right now and my asuswrt device trackers are working fine.

[nickrout]

They are very asus firmware dependent from the many threads I have observed. So works for you is not works for someone else.

[smile]

The nissan_leaf component offers integration with the NissanConnect EV cloud service. NissanConnect EV was previously known as Nissan Carwings. It offers:

• sensors for the battery status, range and charging status
• a switch to start and stop the climate control
• a device tracker to locate the car (only on later Leaf models)
• services to request updates from the car and to request the car starts charging.

I couldn’t found services to request updates from the car and to request the car starts charging

.

[nelbs]

Thanks, I did not know about the wait_template

[nelbs]

Did you read the “Granting Port Access” part of the docs?

If you are experience problems with it please read the following discussion.

Native PlayStation 4 Component Discussion

Ran through the setup again with WSL Debian, the port bind seems to work but the config always fails: [image] Busted out an old Pi and completed a venv install using python 3.5 instead. The integration “works” after setcap command run but again the component fails to register: [image] [image]

[grahamdw (Graham Walter)]

I’m struggling with trusted_networks. Previously I had

trusted_networks:
  - 127.0.0.1
  - 192.168.11.0/24

in the http: section, and everything worked fine. I substituted

auth_providers:
  - type: trusted_networks
    trusted_networks:
      - 127.0.0.1
      - 192.168.11.0/24

in the homeassistant: section and just get 401: Unauthorized errors. Is there some obvious gotcha? I’m accessing via http rather than https as this instance is only accessible on my internal network, if that makes any difference.

[anon34565116]

I remember reading that for 0.89.1 you need the trusted networks in both http & auth_providers until 0.89.2 is released.

[BullFrog]

I have the same problem.

[inutilis (Irakli)]

404 Client Error: Not Found is usually sign of insufficient space on sdcard.

Try deleting some logs, snapshots or history db to solve it temporary. And then you should think of getting bigger sdcard.

[nickrout]

Look under the services page.

[Steven_Rollason]

I’ve been getting a lot of errors the last couple of days which appear to relate to TrackR (I have a few TrackR tags and had been tracking these in Home Assistant):

2019-03-11 15:26:10 ERROR (Thread-18) [pytrackr.api] API error not updating state. 500

2019-03-11 15:31:40 ERROR (Thread-9) [pytrackr.api] API error not updating state. 500

2019-03-11 15:42:40 ERROR (Thread-19) [pytrackr.api] API error not updating state. 500

2019-03-11 15:53:40 ERROR (Thread-4) [pytrackr.api] API error not updating state. 500

2019-03-11 16:04:40 ERROR (Thread-2) [pytrackr.api] API error not updating state. 500

I can’t say for certain that these are due to 0.89, but I hadn’t noticed them before updating.

[TravelinMax (Max)]

A question about the new TP-Link component, can the enable_led not be set on switches? Does the old tplink integration still work in 0.89.0+?

[TravelinMax (Max)]

Found the answers to both of my questions

1. Disable TP-Link LEDs with the new configuration
2. No

[dhaker]

Just a opinion . My Honewell Lylic Thermostat has been working great in HA with the help of [Bram_Kragten] programming abilities. Since I upgraded to 0.89.0 I have not been able to make my Thermostat connect. I have tried everything proposed by https://github.com/teunehv/ha-custom-components/tree/master/custom_components/lyric .
Nothing worked. Thanks for breaking my working system!!

[nickrout]

You need to ask the developer of that custom component to use the new custom component file structure. Clearly they haven’t been paying attention

The Great Migration | Home Assistant Developer Documentation

[lolouk44]

I have the same issue. I have 2 sensors:

• Home to work, based on UK postcodes. Shows 0 all the time regardless of where I am located
• person to home (based on UK postcode). Shows a crazy time. I’m currently at home (Gatwick area) and I get this:
  

Would love some support on this issue as 0.89 defo broke that sensor.
Will try and get some debug data…

@petro since you made a change to add person, would you have any idea how to troubleshoot this?
I’ve added homeassistant.components.sensor.waze_travel_time: debug to my logger: config but I get no logs from Waze…

[lolouk44]

This has just been fixed in 0.89.2

[Klagio]

Waze travel time update

Thanks for your time in resolving this issue. What about inserting the GPS coordinates instead of the address, would that work (I can try later today) ? In my case is a one time operation, no big deal. EDIT, YES, it works, just go to maps.google.com enter the address you need, point it on the map, copy/paste the GPS coordinates in your waze_travel_time in origin/destination, and voila’ … problem solved

[lolouk44]

Thanks, changed and now use a zone which contains coordinates