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

Blog
103 
ha core update --version=0.108.9

EDIT, dang. Too slow.

2 Likes
104

yes it did, depending on your weather integration.
I’ve long ago tried to start a discussion about that, but it was never picked up. Installed another weather integration to be sure it wasn’t sunny at night :wink:

105

I posted earlier this. seems that only me have this problem?
can you check it somehow?

106

Synology integration cannot be configured for multiple devices.
I have 2 devices, one physical and one virtual. Both properly recognized after installation of 0.109. I started with configuration of physical one and it went smoothly (well, again all sensors I used changed names). Then I tried to configure second one, virtual and it hangs indefinitely on configuration screen with spinning wheel… I tried few times, even restarted HA in meantime, but always with the same result. Same if trying secure or insecure connection or different users. It seems to go through authentication though, since if I enter wrong user/password combination I instantly get error message.

107

Why me?. I don’t have any covers and I’m not on 0.109 yet.

109

That’s ok no worries. You are always so helpful to everyone that’s why I asked from you.
Eventually someone we resolve it. I downgraded to 0.108.9 and I am ok for the time being.
I just liked so much the 0.109 because it was very fast. I will upgrade in a later version I guess
Thanks!

110

After updating to 0.109.0 the postgesql sensor failed:

Couldn't connect using postgresql://username:[email protected]:5433/database DB_URL: (psycopg2.errors.UndefinedObject) unrecognized configuration parameter "wait_timeout" (Background on this error at: http://sqlalche.me/e/f405)

Anyone seen this before?
(this is the sensor: https://www.home-assistant.io/integrations/sql/#database-size-in-postgres)

issue: https://github.com/home-assistant/core/issues/34928

111

So if you’ve changed a bunch of the entities names you loose them? :stuck_out_tongue:

112

yes.

I didn’t say it made sense. :wink:

It’s happened to me several times using the Unifi integration. I eventually got smart and made sure I named the devices in the controller the same as I wanted them in HA so I wouldn’t need to keep renaming them every time I needed to clear out all of the unwanted entities by deleting then re-adding the integration because we aren’t allowed to delete them thru the UI. But that’s another story…

113

With the latest release unifi integration will try to clean up all registries when changing options that will remove entities e.g. Don’t track wired clients will remove all affected entities and their references in entity and device registry

1 Like
114

Ditto. Do you know what they are talking about with this purge option?

115

Couple of issues for me;

  • saying there is a new integration but doesn’t show the name; just a blank entry with Ignore and Configure
  • add integration dialog does not show any field prompts
116

I can’t delete the integration from the UI.

I currently have in my config. Do I need this?

isy994:
  host: !secret isy_host
  username: !secret isy_username
  password: !secret isy_password
117

If you have this line in your configuration.yaml file (under recorder:):

purge_interval: 1 # or any other number of days

Delete it.

Purging will occur every night by default.

118

You only posted your 1st message 2 hours ago, sit back, relax & wait.

1 Like
119

FYI - https://github.com/home-assistant/core/issues/34932
- https://github.com/home-assistant/core/issues/34939

Thanks for your hard work BTW

120

Does broadlink.send works for anyone on 0.109 with RM4C mini

121

It should have an icon. Without that it could for example be Netatmo.

122

Problem with new FritzBox 7530 auto-descovery:
lost states:
states.sensor.fritzbox.attributes.transmission_rate_down
states.sensor.fritzbox.attributes.transmission_rate_up

in yaml mode this appears.

Moreover, Fritz Repeater 1750E (mesh) have been found but after login there is no integration possible, with message:
Aborted:
“Connected to AVM FRITZ!Box but it’s unable to control Smart Home devices.”

I have reverted fritz in yaml mode for now.

123

Hi Makis, I’m having the same issue here with a tuya curtain switch (used for my sunscreen). For some reason it never showed the correct state (open/close) in previous releases as well, however in those I was able to press all buttons whereas now you can only press stop which doesn’t do anything.

Capture

Edit: btw also running hassio in a NUC though don’t think that is related?