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

Yerun · May 1, 2020, 9:21pm

Yes it is.

BeardedConti · May 1, 2020, 9:29pm

And yes, I’ve removed it here, added with “No cast devices found” as result, enabled manual configuration (as I have them added through cast: integration) restarted, restarted, restarted,…
Oh and yes, they were working for over a year if not 2 years before that.
#34931

firstof9 · May 1, 2020, 9:29pm

And no entities inside it?

Yerun · May 1, 2020, 9:35pm

Yup they are present, and have the status ‘Recovered’ (red icons). ~~They are the only entities in the whole list with that status~~. Nope, I didn’t look right…

Mariusthvdb · May 1, 2020, 9:37pm

on 109.2 and seeing several of my cards concatenated while they in fact are separate, and where so before the update…

which is in yaml:

  - type: glance
    title: Brabant alerts
    show_header_toggle: false
    entities:
      - binary_sensor.stookalert_brabant
      - binary_sensor.meteoalarm_brabant

  - type: entities
    entities:
      - !include /config/lovelace/includes/include_aqi_woensdrecht.yaml
      - type: custom:auto-entities
        card:
          type: entities
          style: |
            ha-card {
              box-shadow: none;
              margin: 0px -15px -25px -15px;
            }
          title: Air quality
        show_empty: false
        filter:
          include:
            - entity_id: '*.luftdaten*'
            - entity_id: '*.u_s_*'
            - entity_id: '*.chinese_*'
            - entity_id: 'air_quality.*'
      - type: custom:auto-entities
        card:
          type: entities
          style: |
            ha-card {
              box-shadow: none;
              margin: 0px -15px -25px -15px;
            }

          title: Waqi
        show_empty: false
        filter:
          include:
            - entity_id: 'sensor.waqi*'

bottom of above posted view is now incorrectly attached to a following separate markdown card:

in yaml:

          title: Waqi
        show_empty: false
        filter:
          include:
            - entity_id: 'sensor.waqi*'

  - !include /config/lovelace/includes/include_weersverwachting_markdown.yaml

have a few more on that View, that are unexpectedly concatenated. Anyone else seeing that?

have another set of cards that show concatenated, while in fact there are a couple of conditional cards between them (which now are not shown because of the condition not being met)…

how strange this is.

ryanjohnson · May 1, 2020, 9:47pm

By chance are you running your Home Assistant container in a bridged network? It’s my understanding that the latest update relies on mDNS to locate Google devices. If using Docker, this means the Home Assistant container must be running with host networking and your home network must be able to handle mDNS forwarding.

firstof9 · May 1, 2020, 9:57pm

There you go, switch to host mode see if that clears it up for ya.
I confirmed in a docker container that cast isn’t working on my network using bridged network mode.

Jokerigno · May 1, 2020, 10:16pm

Hi all, I have a strange issue: I’ve set HA in italian but now entity status are in english (on off against acceso spento). This happens to door sensors too, to home zone, and to weather card.

ludeeus · May 1, 2020, 10:18pm

@Jokerigno https://github.com/home-assistant/frontend/issues/5674

Jokerigno · May 1, 2020, 10:22pm

Well he was referring to a custom component. I’m talking about home zone for example. But also weather and xiaomi sensor added via mqtt.

ludeeus · May 1, 2020, 10:24pm

sure sure, but that does not matter.
I’t breaks translations.

nakquada · May 1, 2020, 10:31pm

Hi there, my Home Assistant is now borked since upgrade. My main pages are fine, but I cant load configuration / Devices / Entity pages - I just get the same error:

Error while loading page devices.

Error while loading page automation.

etc

Jokerigno · May 1, 2020, 10:34pm

ah, ok. FIXED!

Yerun · May 1, 2020, 10:42pm

I am running it in a container yes. But the main component (I think - the container with the name homeassistant) is already on the host network. Have to admit I see a lot of other components which i am not sure about where they are all meant for. Will try to see if I can post a screenprint here.

Funny thing, port 8123 is not a published port but still working in my homeassistant url.

Jdruwe · May 1, 2020, 10:55pm

My NUC running proxmox seems to freeze when I try to update to version 0.109.2. I need to manually reboot my nuc each time. I’ve read that this can be caused by disk space so i ran the following command to check (inside my VM)

root@hassio:~# df -H
Filesystem      Size  Used Avail Use% Mounted on
udev            2.0G     0  2.0G   0% /dev
tmpfs           385M  6.2M  379M   2% /run
/dev/sda1        30G  5.4G   23G  19% /
tmpfs           2.0G     0  2.0G   0% /dev/shm
tmpfs           5.3M     0  5.3M   0% /run/lock
tmpfs           2.0G     0  2.0G   0% /sys/fs/cgroup
overlay          30G  5.4G   23G  19% /var/lib/docker/overlay2/93143758579a67b3a46d6129e01a44711a8f5e987c0f20e95da2125f26a97f0a/merged
overlay          30G  5.4G   23G  19% /var/lib/docker/overlay2/1e31b5c6a680b92a6830850cb937cad7274e6073b8568adce153910c5ea318d8/merged
overlay          30G  5.4G   23G  19% /var/lib/docker/overlay2/3ae6ff96f2d8141d4d378ae8a9ba338fc531644b90f3f34d479d0da001b724c4/merged
overlay          30G  5.4G   23G  19% /var/lib/docker/overlay2/a17c5cdf960dc9b3371d40fb0e5c3fdcb0b2fcb822c33675b977e7878d776cba/merged
overlay          30G  5.4G   23G  19% /var/lib/docker/overlay2/8bfcb783866ea60bd18c3c76ceee9e87992bff931cf1d8aeaa49b7118faf3033/merged
overlay          30G  5.4G   23G  19% /var/lib/docker/overlay2/f1396d2dc1d85dc46cd2d203d80b7ed8c97e69d9ee585d0242799aa70f0c7e55/merged
overlay          30G  5.4G   23G  19% /var/lib/docker/overlay2/e6edd431de2efe0652a9daa912cf3677f78564168902ee27cc001a41097d78b9/merged
overlay          30G  5.4G   23G  19% /var/lib/docker/overlay2/1b9284aacc5a7d19eb93549e1f51319da6bfd5a96476e421d8e997440c795953/merged
overlay          30G  5.4G   23G  19% /var/lib/docker/overlay2/d2ad0d49c6fab8eac8abfd851fef1b0e36353bb8e25337512fd4dfff9e89c4fd/merged
overlay          30G  5.4G   23G  19% /var/lib/docker/overlay2/1bddb7df4a3c697bcea41dd20092d5e578b41164537be1d59b453ed26684baec/merged
overlay          30G  5.4G   23G  19% /var/lib/docker/overlay2/6b4f2e77aa46a23185a5749e59347b02a65e1a6c96e8ed1c2ea3b05ee15e94ca/merged
tmpfs           385M     0  385M   0% /run/user/0

There seems to be space enough, someone an idea?

aidbish · May 1, 2020, 11:23pm

restart googles home, i believe google sent out an update in last couple of days( well for me anyway) and i had to restart them. The google update borked on a couple of nest hubs and i had to reset them.

so maybe worth a try

Malaga82 · May 2, 2020, 12:23am

Same, addons won’t start anymore and can’t access supervisor fronted


2020-05-02 02:20:56 ERROR (MainThread) [homeassistant.components.hassio.http] Client error on api addons/a0d7b954_nginxproxymanager/info request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)],
2020-05-02 02:20:59 ERROR (MainThread) [homeassistant.components.hassio.http] Client error on api addons/a0d7b954_pi-hole/info request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)],
2020-05-02 02:21:02 ERROR (MainThread) [homeassistant.components.hassio.http] Client error on api addons/a0d7b954_nodered/info request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)],
2020-05-02 02:21:05 ERROR (MainThread) [homeassistant.components.hassio.http] Client error on api addons/core_mariadb/info request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]

Strange thing, it auto updates to .2 version and now I can’t enable addons

Ok, for some reasons hassio_supervisor get screwed and couldn’t start anymore. With luck I recreated it and now addons are back online.
Had to remove and readd to sidebar and several start and stop of Nginxproxymanager.
I don’t know what happened but something get updated and failed hard.
If can help, port 443 was not allocated, since NPM use it


20-05-02 00:30:34 ERROR (SyncWorker_0) [supervisor.docker] Can't start addon_a0d7b954_nginxproxymanager: 500 Server Error: Internal Server Error ("driver failed programming external connectivity on endpoint addon_a0d7b954_nginxproxymanager (66e9059643484b1bd101fa53fa7111be32c24a89f8304e9e6b042c31195efb80): Bind for 0.0.0.0:443 failed: port is already allocated"),
future: <Task finished coro=<Addon.start() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:472> exception=AddonsError()>,
20-05-02 00:30:34 ERROR (MainThread) [asyncio] Task exception was never retrieved,
Traceback (most recent call last):,
  File "/usr/src/supervisor/supervisor/addons/addon.py", line 493, in start,
    raise AddonsError() from None,
supervisor.exceptions.AddonsError

Kanishkaz · May 2, 2020, 7:20am

Hi All,

Anyone tried adding their vacuum cleaner as a HomeKit accessory after this update?
I can see a switch to control my vacuum now. It also shows the battery level and charging status in the details.

However, the charging status doesn’t look like it’s updating correctlly. Anyone else seeing the same behaviour?

Cheers.

mirekmal · May 2, 2020, 7:53am

Where did you get this information from? Info about Synology integration changes for 0.109 states only:

Also in the documentation there is nothing about only one device being supported?

bouwew · May 2, 2020, 7:54am

I had a similar error as yours. Supervisor not working.
I manage to fix it by restarting the host operating system (running on a VM in Proxmox).