0.113: Automations & Scripts, and even more performance!

ousi78 · July 22, 2020, 10:26pm

Hi,
I lost my cover just after update my HA. My dashboard show me entity unavailable. You can see below my config code? Thx for support.

rfxtrx:
device: /dev/serial/by-id/usb-RFXCOM_RFXtrx433XL_DO332IY6-if00-port0
cover:

platform: rfxtrx
automatic_add: true
devices:
“071a0000010A0202”: # RFY
name: Séjour

“071a0000020A0404”: # RFY
name: SàM

“071a00030A0909”: # RFY
name: Cuisine

kanga_who · July 22, 2020, 10:42pm

Smooth update and no problems to report so far, well done

Geoff571 · July 22, 2020, 10:58pm

This looks like such an awesome release. I’ve spent a inordinate amount of time coding around some of the nuances in scripts and automation to handle multiple recurring trigger, I can’t wait to try so some of the improved features.

Many thanks guys, you just keep going from strength to strength.

BradAU · July 22, 2020, 11:16pm

An issue has been raised on the browser_mod github page.

madrian · July 22, 2020, 11:30pm

@lisegra same problem here. Yeelight auto discovery is broken for me too.

I added them manually as a workaround to the config.

nickrout · July 22, 2020, 11:34pm

Updated from the Android app 300 Miles from home. Well done team

crookedview · July 22, 2020, 11:35pm

Same here. I had the Bond custom component installed through HACS, so I uninstalled it from there and restarted Home Assistant. I was then able to utilize the new built-in integrations setup method.

duceduc · July 22, 2020, 11:38pm

There is conflicting snippets at this link

One shows queued and another queue

pnbruckner · July 22, 2020, 11:45pm

That’s a typo in the release announcement, probably because originally it was going to be queue but was changed to queued before being released. I believe the docs are correct.

@frenck, sorry about that!

frenck · July 22, 2020, 11:47pm

Don’t worry about it @pnbruckner… I thought I had them all

cpuram · July 22, 2020, 11:49pm

@frenck image size considerably reduced to ~330mb in 0.113 from ~420mb in 0.112. wondering what changed. thanks.

Gimlichael · July 23, 2020, 12:13am

This build breaks all my Hue integrations; the log is filled with something like “light does not exists” and if i click it on it in HA, it asks if i want to remove the node.

So far i had to roll-back to 0.112.4.

schoenof · July 23, 2020, 1:00am

I disabled the tensorflow stuff and the upgrade to 0.113 finished now…re-enabling tensorflow after 113.0 upgrade results in some errors and hangs the HA startup again…seems there is some issue with 113 and tensorflow

konnectedvn · July 23, 2020, 2:00am

What will happen when we overreach max? Latest one will be ignored or newest one will be finished?

Zoriontsu · July 23, 2020, 2:14am

Hmmm, I am not using Tensorflow but Amazon Rekognition. Will try disabling.

Coolie1101 · July 23, 2020, 2:19am

0.113: AUTOMATIONS & SCRIPTS: RUNNING MODES, REPEATS, CHOOSER, BONUS! COOL DOWN

tenor !

HUGE! shout outs to @frenck and @pnbruckner, I always admire and appreciate your work.

.
Big thanks to @bdraco , @pvizeli, and @yosilevy

Congratulations??? to @ludeeus, I think

nickrout · July 23, 2020, 4:00am

Whenever I see "node red’ I run a mile. Not saying either you or I am right. It’s horses for courses.

kanga_who · July 23, 2020, 4:13am

I’ve never had the need in 3 years of using HA to even try Node-Red, let alone consider it the new default for automations.

jspanitz · July 23, 2020, 4:27am

Upgrade completed but just sits at “Home Assistant is starting, not everything will be available yet.”

Tried a restart and forcing the upgrade again. Made sure HACS is updated to latest version as well. Have ConBee II removed from PI for other reasons, so safe to ignore those errors.

Logs: https://pastebin.com/nh2LDPJB

owiebaclay · July 23, 2020, 4:28am

Thanks for the info sir.