2021.6: A little bit of everything

[Nath]

Hi, guys, just to make sure, does somebody noticed any issues with LIFX after update? (I went from 2021.5.3 and haven’t been using LIFX Legacy btw). For some reason my lights gone offline, I’m not able to re-add them because they are supposedly not present in my network but sometimes I get “Discovered LIFX” which after configuration is empty anyway. Official LIFX app works without issues.

[maxgiordan (max)]

Hi friends, I also have problems in the frontend.
Custom cards: change status regularly but are blocked when pressed … unless you refresh your browser.
Even after cleaning the cache, after a few seconds freeze again but continue to change status regularly (icon changes color when turned on).
This happens on all browsers, but what’s the problem?

[apross (André Pross)]

Also by me, this release broke my ecowitt (hacs) integration. Had to roll back.

[Prodigyplace]

@apross

broke my ecowitt (hacs) integration

Did you report it to the developer? That is not a direct part of HA and is therefore off-topic here. HACS are community developed plugins.

[0101binary0101]

I’m ok with the energy consumption missing, as I wrote my own container with the tuyaapi to collect the data.

[fedesat]

Hi guys,
When I have installed last version 2021.6.2 the Wundergroundpws not working ( no entity) could you help me?
Regards

[roberto59 (roberto)]

Could you share more details?
Are you using the tuya integration?

[KennethLavrsen]

Update to those of you that do not read all the bug reports on Github but come here to read about latest release.

The issue with the Logbook loading slowly ended up not having anything to do with which database you have. In fact the root cause is also why my camera streams did not work.

The reason is the TOD integration (time of day). Under certain conditions (depending on when during the day vs the TOD settings) the integration goes into a loop that takes 99% of the CPU. This made any CPU demanding features to perform slowly.

There is already a fix made and should be in one of the next releases. In the meantime you can just comment out any binary sensors based on TOD integration. The TOD has some still open bugs so you can also just replace it by a template sensor.

Here are the two I use. One define by time and one defined by sun state

template:
  binary_sensor:
    - name: Night Time
      unique_id: night_time
      state: >
        {{ not '06:30' <= as_timestamp(now()) | timestamp_custom('%H:%M') <= '23:00' }}
   
    - name: "Darkness"
      unique_id: darkness_template_sensor
      state: >
        {{ is_state('sun.sun', 'below_horizon') }}

There could be other new issues that have the root cause in lack of CPU power caused by TOD.

In my case the TOD caused a CPU loop only when the time was not after midnight but before darkness. My problem suddenly stopped at midnight. That is how we figured out the root cause. The TOD bug had already been opened at that time. Hope this post can help those that do not read github bugs all the time

[Bergerie]

Upgrade to core 2021.6.0 caused loss of google calendar card initial view setting. This has been experienced on multiple machines following the upgrade. Anyone else experiencing the same and/or found remedial action.

[Prodigyplace]

@Bergerie

2021.6.0

Is it fixed in the latest patch, 2021.6.2 ? I see the frontend version changed in 2021.6.1.

[rct]

Maybe it is just me, but I was hoping to see some updates on the Zwave-JS status in this release.
The initial release/blog with all the excitement it was 2021.2.

Is the Zwave-JS integration still beta/WIP? Is migration recommended yet?

Edit: I should note that I don’t need a fully automated migration, but I need things like locks (Schlage deadbolts) to be stable.

[Prodigyplace]

zwavejs and zwavejs2mqtt are updated separate from HA.I currently anm testing zwavejs2mqtt as a control panel connected to the zwavejs integration using w the websocket interface,

The zwavejs2mqtt control panel give better information & control over the devioces, including a basic network map.

[rct]

Thanks for the info @Prodigyplace. I was hoping the release blog would have some updates on status given the previous coverage. I get the impression Zwave-JS is still somewhat of a WIP.

Does running Zwavejs2MQTT to give you the control panel change the topology?

Is it ZwaveJs → Zwavejs2MQTT → Hass or

ZwaveJS → Hass
ZwaveJS → Zwavejs2MQTT

[Prodigyplace]

Here is my current version.

[arganto]

@arganto

Collapsed attributes: Previously, all themes automatically used our light theme as the base to build on. As of today, themes can be based on our default dark theme as well!

But there is still no selectable default theme, isn’t it? Why?

E.g. to assign this theme to a special view, if main theme is another one. In cards, I can set each theme, but not the build in HA ones.[Or what is the common work-arround to pick and assign the default in these cases]

Disable polling updates on any integration

Is there a service for this as well, to switch off and on for a given integration? [I checked and didn’t find a kind of homeassistant.auto_update_entity = on/off for data:<integrationname> and only homeassistant.update_entity instead].

Am I invisible or are these question too stupid or unclear?

[Wellut (Tiainen Veli)]

Same here.

[Vahaldor]

Entities card (multiple) dismantled on iOS app and OSX app.

[Bergerie]

Unfortunately not yet fixed in release 2021.6.2

[petro]

@finity

When was the last time you (not you specifically, kanga…) checked any logs on your Windows or Linux PC without something breaking forcing you to look there? And now that I think about it I’m not even sure how to check the logs on a Windows PC so I doubt I’ve EVER actually checked them

I check them every day. It’s called event viewer. There’s no way you haven’t had a software crash to desktop. You must be only using software with millions of users that have 100s of devs.

[petro]

I personally don’t think it’s beta anymore. I run the nightly alpha build and upgrade pretty much every day and I haven’t ran into an issue in 2 months. Last issue was due to a custom integration.

At this point, stand alone HA is very stable.