0.109: New integrations page and weather card, frontend lost weight

kostak · April 30, 2020, 11:51am

Same Issue here with all Tuya Covers on 0.109.0 and 0.109.1. Only Stop Button is available but not functional. Up and Down Buttons are gayed.
In Version 0.108.9 i was able to use all buttons.

MatthewFlamm · April 30, 2020, 11:53am

Also to @nickrout. It was decided that nighttime conditions be completely removed from all weather platforms, but no dev has implemented it yet.

github.com/home-assistant/architecture

Add support for partlycloudy-night in weather component

opened 06:30PM - 10 Dec 19 UTC

closed 10:02AM - 20 Dec 19 UTC

MatthewFlamm

## Context Currently the weather component only supports `partlycloudy`. The… icon `mdi:weather-partly-cloudy` displays a sun covered partially with clouds whether it is day or night. `clear-night` and `sunny` already distinguish a similar weather condition between day and night. `sunny` is clearly incorrect at night, while `partlycloudy` condition itself is still accurate. However, the icon support at night is incorrect, showing a sun. None of the other conditions involve a sun or moon besides `partlycloudy`, `sunny`, and `clear-night`. ## Proposal I propose adding `partlycloudy-night` as a supported condition with associated icon `mdi:weather-night-partly-cloudy`. I suggest `partlycloudy-night` over `night-partlycloudy` to align with `clear-night`. This would allow for icon support for nighttime for partly cloudy conditions. I have not checked all integrations with weather platforms yet, and some have unclear weather code mappings without documentation. By my interpretation, at least darksky, nws, envrionment canada, and meteo_france could utilize the new condition. ## Consequences * Current integrations with weather platforms that support a day/night distinction will need to include `partlycloudy-night` support. However, this is not required immediately, as it will continue to work with the current state. * Some platforms may not support a day/night distinction, and the icon will continue to be incorrect at night. This is no difference to the current state but may create confusion if some platforms support and some do not. This confusion can already exist with platforms that do not support `clear-night` and only use `sunny`, e.g. metoffice. * See also #321 for renaming `partlycloudy`. If that is accepted, then this proposal would change to using `partly-cloudy-night`. If it is preferred to follow the mdi naming according to #321, this proposal would change to `night-partly-cloudy`.

sose5000 · April 30, 2020, 12:08pm

It took me removing that form the config, then deleting the HACS ISY plugin, then i was able to remove the integration. Neither the build in ISY nor the HACS plugin work any longer though. Very frustrating.

BlackChart · April 30, 2020, 12:08pm

Sorry - forgot that page existed.
It desn’t give anything useful - I tried every single thing in there and averything still executes in MainThread.

I was more thinking of some useful examples to get us going.

sose5000 · April 30, 2020, 12:09pm

Other people manage their deployment differently.

carloscae · April 30, 2020, 1:19pm

All my sensors are now unresponsive on Homekit. Only lights and switches working.
tried restarting HASS, Router and Homekit bridge (ATV).

hads514 · April 30, 2020, 1:20pm

I created an issue re ISY Custom Component in GitHub. As I no longer have the error available, additional input to this may be helpful.

Reverting to 0.108.9 was the simplest solution for me for the moment.

shbatm · April 30, 2020, 1:28pm

For the ISY994 custom component, enable ‘Show Beta’ on the ISY994 integration page in HACS and install 1.3.7 for compatibility with 0.109.0. Later today I’ll finish testing and mark it as a regular release.

mmatesic01 · April 30, 2020, 1:31pm

From 0.109.0, native HA thermostat integration does not show set temperature for zwave thermostat valve (danfoss,devolo) anymore. Other HACS thermostat intergations do.

ericpignet · April 30, 2020, 1:32pm

For me with 0.109.1, broadlink switches worked fine, however broadlink sensor was broken.
There were many changes in this sensor so I was afraid it was a bug, but I realized the name of the detected sensor entity had changed. New name was sensor.broadlink_temperature, I had to adjust the name where it was used.
Note that they also added a type attribute for broadlink sensor, but for me it is not necessary.
So all good for me with Broadlink RM Pro.

fofonta · April 30, 2020, 1:34pm

Hi, I have the same result

G8YTZ · April 30, 2020, 1:39pm

Synology DSM, broken in .109, I did do the rename, still broken.

Burningstone · April 30, 2020, 1:53pm

I know.
I just don’t think it’s a good idea to deploy my home automation system from my phone, but that’s just my opinion, to each his own.

rockyrhode · April 30, 2020, 1:54pm

Same here. No sensors or locks available in HomeKit since 109.

rockyrhode · April 30, 2020, 1:56pm

Just updated to 109.1. When I click any of the pages (Automations, Scripts, Scenes, etc) it says “Error while loading page automation.”. I have rebooted several times and cleared cache.

carloscae · April 30, 2020, 1:56pm

I just tested removing one sensor from homekit.yaml, restarting, re-adding, restarting.

sensor shows up again.
so, basically you need to remove and re-add all sensors and lose all configuration on homekit side. not particularly excited about this when I have over 20 sensors and some shortcut automations…

carloscae · April 30, 2020, 2:03pm

template sensors are unaffected.

Makis · April 30, 2020, 2:26pm

I roll back on 0.108.9 until it is fixed.
I think it has to do with entities card not with tuya.

prepi na perimenoume

Canedje · April 30, 2020, 2:40pm

I just installed 0.109.1
Broadlink for my broadlink M3 mini is working again

tuncaya · April 30, 2020, 2:46pm

show_forecast: False