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

[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

[glith]

With the latest release I have noticed that if I press on a temperature sensor I am shown the graphs for multiple my temperature sensors. This is not desired.
How do I change so the behavior is like before this new version?

[lolouk44]

I’m not experiencing this on 0.89.2 and I’ve tried on a few different sensor types
Which ones do you have?

[glith]

Some rfxtrx-sensor and zwave smoke sensors.

[lolouk44]

Don’t have that issue…

[edit] I realise I posted a picture of the humidity, not temperature, but just checked and is the same with temperatures…

[glith]

Some graphs are OK. Some sensors which have both humidity and temperature, shows both. And some sensors shows a lot of other sensors as well.
It is really strange. Maybe a corrupt database somehow?

[WeatherWitch]

Apologies in advance if this is in the wrong place.
Getting this error on startup and TP-Link bulbs not detected. TP-Link switches (HS100 and110) all ok.

Log Details (ERROR)
Thu Mar 14 2019 08:28:52 GMT+0000 (Greenwich Mean Time)
tplink: Error on device update!
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/entity_platform.py", line 248, in _async_add_entity
    await entity.async_device_update(warning=False)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/entity.py", line 348, in async_device_update
    await self.hass.async_add_executor_job(self.update)
  File "/usr/lib/python3.5/asyncio/futures.py", line 380, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.5/asyncio/tasks.py", line 304, in _wakeup
    future.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
    raise self._exception
  File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/tplink/light.py", line 170, in update
    self.get_features()
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/tplink/light.py", line 228, in get_features
    self.smartbulb.valid_temperature_range[1])
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/util/color.py", line 516, in color_temperature_kelvin_to_mired
    return math.floor(1000000 / kelvin_temperature)
ZeroDivisionError: division by zero

Thanks in Advance,

Kind regards,

Mark

[thorsten.lanting]

Am i the onlyone who can’t update?

I have tried several things but nothing worked

[nickrout]

@thorsten.lanting

I have tried several things but nothing worked

Post of the month.

[Ktnrg45 (Kt)]

Perhaps if youre careful though Id advise against it. You’ll have to edit your device registry.

[finity]

you’ll have to give way more info than that. also it might be better to start a new thread for that.

[grahamdw (Graham Walter)]

Thanks - all seems good now

[Lyukvoice]

After upgrading mqtt broker to version 4.1, nothing works anymore. Tried to completely reinstall hassio on the raspberry but the mqtt broker configurator doesn’t work!

every time I get the message “Unable to connect to the broker.”

[MarkHofmann11 (Weatherman)]

Just wondering if I’m the only one that would like to re-gain the ability to give names to TP-Link devices. HA doesn’t like apostrophes, so had given my TP-Link switches HA friendly names in the YAML. Assuming I’ll have to change the names in Google’s App now?