2021.5: Stability, performance, triggers, color modes!

[Skeletorjus]

I think it fails on the SSL-sertificate.
To make it work you have to have ssl: false in your motionEye addon config.
You also have to set a port to your web-interface in the same place.
Then use http://ip:port in the integration configuration. You can also use the hostname (a0d7b954-motioneye) here.
I found that it gives an error if you have blank passwords, so you should probably make them.

[petro]

I never told you to remove it. I wasn’t even talking to you. I was talking to the people who use Fritz box. You you and Others decided to bring me into a deprecation argument. Do whatever you wanna do, I don’t care.

[spacegaier (Philip Allgaier)]

@ben1410 Switching to the template function approach does indeed “resolve” the issue and is the preferred syntax anyway, see warning here: Templating - Home Assistant

[TazUk]

@123

A special note of thanks for the re-invented Template integration . It took several minutes of busy work to convert all my Template Sensors and Template Binary Sensors from ‘legacy’ format to ‘modern’ format but the end-result was worth it. Now all of them are neatly organized in one place, containing trigger-based and non-trigger-based Template Sensors and Template Binary Sensors.

Since I’m looking to do something similar, can I ask what may be a dumb question?

Can I translate a legacy template:

wan:
   friendly_name: "Internet Connection"
   value_template: "{% if is_state('binary_sensor.WAN_Check_BBC', 'off') and is_state('binary_sensor.WAN_Check_OpenDNS', 'off') %}Offline{% else %}Online{% endif %}"

to modern:

- name: wan 
  friendly_name: "Internet Connection"
  state: "{% if is_state('binary_sensor.WAN_Check_BBC', 'off') and is_state('binary_sensor.WAN_Check_OpenDNS', 'off') %}Offline{% else %}Online{% endif %}"

retaining the friendly name for display use? or do I need to factor display name choices into migrating?

[pergola.fabio]

Is this needed, legacy not supported anymore?

[TazUk]

No I believe it’s still supported - I just like the idea of centralising my template sensors as I have a lot of them.
However I cannot see friendly_name detailed under the ‘modern configuration’ section of the integration documents - which will add a multiplier to the time required to shift my configuration around.

[thecobra666]

To have it decoupled from HA. Like a ZHA docker container instead.

[nickrout]

You mean like using zigbee2mqtt?

[parautenbach (Pieter Rautenbach)]

@nickrout

No, deprecated means “still supported for the moment, but will be removed in future”.

Exactly. Not sure why anybody is confused. I think some are confusing deprecating something with decommissioning something.

[thecobra666]

Yes but zha is not zigbee2mqtt. I like the way it works with the zwavejsmqtt container which has the option to enable a websocket link to ha instead of mqtt.

[thermseekr (Tales Maschio)]

I have not, will do. I have an AVR-X3000.

[pergola.fabio]

Ah , i have 4000, it’s the same… Ok, gonna wait then for update… Can you report?

[jaalperin (Jeff Alperin)]

Integration setup times in info panel are very useful. How about sorting by them?

[thermseekr (Tales Maschio)]

I’m not sure where to report, and I won’t be able to do it before getting home tonight (it’s 8:37 AM now here). Would you mind doing it?
Thanks a lot.
Tales

[TripleJ (Johnni Jakobsen)]

yes this is really cool. But how to actually achieve this is there a guide on this I have missed.?

[pergola.fabio]

On GitHub, create an issue there… i havent updated yet, so I cant

[kslb (KSLBe)]

Do not update if you have MS SQL database or else you will get in trouble…

[arganto]

@arganto

If I have such cases, as before for fritzbox_callmonitor, iRobot, etc. etc. Where and how to change the settings then afterwards if they change?

Before I opened the config.yaml changed e.g. user, pw, token or whatever other options. After migration to UI, most of the times, there is no chance to change them in UI? What are the thoughts behind this?

• Remove and re-add every time I want to change any option
• Change this in hidden .storage yaml files

Both are the opposite of UI setup - in my point of view.

Any ideas for me?

E.g. (no changes with this release, done in one of the last releases, but just as an example) callmonitor, before: a lot of options in config.yaml. Now since some time in UI. Changes in documentations here:

Add config flow to fritzbox callmonitor (#14651)

If there are now changes in host, port, id, user, pw, options, … everything could be adjusted in yaml. And How to do it now? There are no options in this integration. And there are no options in most of the ofter integrations I use, which were moved from yamlt to UI. Perhaps the setup is moved now, but how to adjust if needed?

[strawwmann]

I have the same issue with the Lovelace control cards for Tasmota lights being broken (both for lights configured with MQTT integration and those configured with the Tasmota integration).

The issue was logged in detail as a bug during development:

Tasmota Lights no longer change color when using the Color Wheel

but then it looks like it was just closed and ignored without being fixed in the PR:

Add color_mode support to tasmota light

Further, the reason given for implementing the breaking change:

Tasmota lights no longer supports deprecated white_value, use rgbw_color instead.

does not seem to be mentioned anywhere in the Tasmota changelogs:

arendst/Tasmota/blob/c8de5437a355d502ee0c50e4e9dbb0a03394da6f/CHANGELOG.md

(and I have tested that setting a value for ‘white’ still works fine for Tasmota lights, whether from the Tasmota console or MQTT, including for the latest 9.4.0.3 Tasmota release.)

So there certainly seems to be something odd going on here.

@emontnemery could you please take a look at this, including the bug report issue #50095 (linked above).