I was seeing people on Reddit have similar issues
1 Like
Saw the same thing for a Jasco dimmer switch. Rolling back to 2021.12 brought it back just fine.
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.
Does Tuya now have the power consumption working?
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
I’m holding off, too.
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/"}'
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…
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
I’ve found my two amcrest cameras have timed out a few times (but not every time) during a restart. When they timeout, the only option is to restart again and hope they connect.
Welcome to new streamlining experience, thanks to all developers who made it happen, worried and scared to update 
As a genuine question, why remove the default_config: directive at all? Seems like everything can be overridden even with it?
how to fix error for device_tracker:
2022-02-03 09:13:59 ERROR (MainThread) [homeassistant.setup] Error during setup of component device_tracker
?
Hey, does anyone know if this is caused by something from HACS or from HA? I don’t know how to fix it to update to the new version…
[Errno 2] No such file or directory:
*/usr/local/11b/python3.9/site-packages/multidict 6.0.2.dist-info/METADATA'
1 Like
Means I have to wait when this will be core in HACS and then update my HA…
Hi @rsachoc
It is not a light entity. It is a sensor entity. I saw the reference to state_value_template in the notes that you reference. I tried changing my config to use the state_value_template instead of value_template but when i ran the check configuration button it gave an error. So i don’t think this is it.
I am seeing the similar results as @nikito7 has posted. If i check states in developer tools. The state on the MQTT topic jumps from the correct value if the topic msg has my value_template var in its json. If it doesn’t, the entire json string of the topic msg is show in the state (see @nikito7 post for an example)
An example of the config i am using can be seen on the OMG documentarian OMG (Mijia Thermometer BLE)
1 Like
Is remote_rpi_gpio integration also going away in near future?
1 Like