2022.2: Let's start streamlining!

Blog
120

The legacy integration?

121

same thing for me. zwave works. but zwave lights dont work. going back to the last release fixed it.

122

It’s just the MQTT sensor integration reading messages from rtl_433. I have an RPI3 running rtl_433, using rtl_433 cli option to publish MQTT – something like this:

rtl_433  -F "mqtt://localhost:1883,user=$mqttuser,pass=$mqttpwd,retain=0,events=rtl_433[/id]" ...

I’ll see if I can learn more and identify what changed.

Thanks!

124

Hello, I just passed the configuration check and I get this error and therefore I can’t update:

Testing configuration at /tmp/config

INFO: homeassistant.helpers.storage:Migrating core.device_registry storage from 1.2 to 1.3

INFO: homeassistant.helpers.storage:Migrating

core.entity_registry storage from 1.4 to 1.5

Fatal error while loading config: [Errno 2] No such file or directory: /usr/local/lib/python3.9/site

packages/multidict-6.0.2.dist-info/METADATA

Failed config General Errors:

[Errno 2] No such file or directory:

*/usr/local/11b/python3.9/site-packages/multidict 6.0.2.dist-info/METADATA'

I don’t know what I have to change to be able to update, I need help. I have the last updated, so this is the next one. Thanks in advance

4 Likes
125

Like this:

template:
  button:
    - name: "Start my script"
      press:
        - service: script.my_script
1 Like
130

Thanks Tom!

Hard to tell from the docs what the difference is between button and input_button? Or when we would use one or the other?

131

yes correct. legacy.
as mentioned. all other zwave works. just not lights. previous stable version works.
also (and I realize you are not a github bug report, but wanted to mention it for anyone else searching)
restart server from the UI doesn’t work.
I have to manually stop/start or restart from the cli

133

I’d like to say that this update is awesome, and my gui seems way faster - although that is by no means scientific, just an impression.

Also restarts seem faster.

135

The template button has service(s) associated with it. The input_button does not. You have to monitor the input_button yourself, like with an automation trigger.

Use an input_button when you want to trigger an automation.

Use a template button when you want a service or services started with the button. Scripts are services.

2 Likes
136

I was seeing people on Reddit have similar issues

1 Like
145

Saw the same thing for a Jasco dimmer switch. Rolling back to 2021.12 brought it back just fine.

146

I also rolled back. I probably need to bite the bullet and convert to ZwaveJS, but I hadn’t gotten around to it. I wasn’t sure how much manual reconfiguration I’d have to do after running the migration script.

148

Does Tuya now have the power consumption working?

149

I have to agree with the others concerning removal of the Works With Nest API integration. This will lead to loss of functionality with a lot of popular home automation products. In my case, it will break all automations related to my Nest Protects which improve my familie’s safety.

I would also like for someone on the inside to come explain why a working API with no satisfactory replacement is being removed from HA.

4 Likes
150

see this post: Legacy Nest - #7 by allenporter

4 Likes
152

I’m holding off, too.

153

I did not upgrade Tasmota on my devices, I changed the autodiscovery messages with a script. A lot less work.

The old one I had in case I had to recover them (only the first shown)

  scripttasmotalights:
    sequence:
      - service: mqtt.publish
        data:
          retain: true
          topic: homeassistant/light/689626_LI_1/config
          payload: '{"name":"lichtbovenkleineslaapkamer","cmd_t":"~cmnd/POWER","stat_t":"~tele/STATE","val_tpl":"{{value_json.POWER}}","pl_off":"OFF","pl_on":"ON","avty_t":"~tele/LWT","pl_avail":"Online","pl_not_avail":"Offline","uniq_id":"689626_LI_1","device":{"identifiers":["689626"]},"~":"lichtbovenkleineslaapkamer/"}'

The new one:

  scripttasmotalights:
    sequence:
      - service: mqtt.publish
        data:
          retain: true
          topic: homeassistant/light/689626_LI_1/config
          payload: '{"name":"lichtbovenkleineslaapkamer","cmd_t":"~cmnd/POWER","stat_t":"~tele/STATE",stat_val_tpl":"{% raw %}{{value_json.POWER}}{% endraw %}","pl_off":"OFF","pl_on":"ON","avty_t":"~tele/LWT","pl_avail":"Online","pl_not_avail":"Offline","uniq_id":"689626_LI_1","device":{"identifiers":["689626"]},"~":"lichtbovenkleineslaapkamer/"}'
154

Thanks, hadn’t seen that one. Hopefully someone takes over maintenance (I certainly don’t have the required skills). I might try to copy the code to my custom component folder and hope for the best…

158

Hi all,

Why is the old NEST deprecated???
Smoke sensors are not supported in the new intergration… It doesn’t make sense to stop the old intergration then?

3 Likes
159

See Legacy Nest - #7 by allenporter

2 Likes