2021.6: A little bit of everything

[aidbish (Adrian)]

@ttobias

update becoming more frequently

its become less frequent. Used to be every 3 weeks, now every 4 weeks

[aidbish (Adrian)]

After managing a fleet of a couple hundred IOS devices the last few years, i can tell you we had less dramas from user running chrome than we did safari. regardless of the underlying code

[wheindl (Walter H.)]

I am getting the same issue, and reported it (and see the reports) in the Jandy iAqualink pages of the HA community. It worked perfectly before the upgrade to 2021.6. What is dismaying is that I restored a snapshot of 2021.5.4 and still it is broken. I tried removing then reinstalling the integration, but it won’t let me do that.

[aidbish (Adrian)]

you need to create a github issue if its an official integration, posting on a community thread isnt the same. Issues · home-assistant/core (github.com)

In fact an issue has already been done, and seems it has nothing to do with this release as it was happening before, hence why you rolling back to previous version still presents the issue… iAqualink integration no longer works. · Issue #51389 · home-assistant/core (github.com)

Jandy iAqualink Pool Integration - Share your Projects! / Custom Components - Home Assistant Community (home-assistant.io)

[123 (Taras)]

@ttobias

it would be nice if timers would get some love and get restored after a restart.

I offered a way of doing that here:

Restore active/paused timers after a restart

Notice of Deprecation Thanks to the contribution of raman325, starting from Home Assistant version 2022.4, an active or paused timer entity can be restored after a restart. Therefore the restoration technique described in this topic is no longer needed. This topic remains for historical purposes, in case someone is curious to learn more about the scripting techniques it used to restore active/paused timers. However no further support for it will be provided now that timer restoration is a nat…

An active timer, interrupted during its countdown by restarting Home Assistant, is restored when Home Assistant starts. It is restored with a new duration representing the remaining time left of its original duration minus however long Home Assistant was offline. If the timer’s duration expired while Home Assistant was offline, the timer is not restored on startup.

---

NOTE

Timers, and restoring them, should be used judiciously. I agree with frenck that they’re not a panacea, especially not for long intervals when better techniques are available. FWIW, I don’t use any long-duration timers.

[finity]

@nibblerrick

I had an answer

But the answer was incomplete (it’s better to use maintained software than to patch your own non-maintained local version…unless you want to of course) and I didn’t know if you knew there was an alternative. So I pointed it out.

[Squishbutt]

Yeah, turns out Jandy changed the URL, so this is not a version issue. Fortunately, the dev is already aware and working on a fix.

[cboehnke (Bunk)]

Hmm, remote console working here, and no such errors. With nabucasa on 2021.6.1

[cboehnke (Bunk)]

Love the update, system is snappy!

Does anybody when and how the “illuminance” disappeared?
I had this:

- platform: illuminance
  name: Estimated Illuminance
  entity_id: weather.home

But [check configuration] says
“Platform error sensor.illuminance - Integration ‘illuminance’ not found.”

And weather.home doesn’t show this as a state attribute (anymore).

[DavidFW1960 (David)]

Illuminance is a custom_component and it’s working fine for me.

[cboehnke (Bunk)]

Thanks @DavidFW1960 - forgot that was a custom component, I just needed an update from GitHub - pnbruckner/ha-illuminance: Home Assistant Illuminance Sensor
Back in business.

[tom_l]

Updating to 2021.6.1 causes my CPU to run one core flat out. I grabbed a profiler capture but am having no luck seeing what is going wrong.

[roberto59 (roberto)]

I have same smartplugs, under localtuya I can see energy consumption.
Now it’s gone and Tuya integration allow me only to switch on/off

[jmiheve]

I stand corrected.

I did try adding a version number with no luck and had to roll back HA, but looking back I realized that I may have missed a comma. I’ll give it another try this weekend when I have some free time.

[maxym]

you mean major versions. minor versions/patches are more often then in the past (subjective feeling)

I’m this kind of guy who likes to keep sw up to date. But since Jan, I’m really struggling to chose reasonably stable version I would jump for. May’s version advertised as “stability…” seemed to be full of issues causing update less stable/reliable. This release obviously contain “a little bit of bugs” too.
I mean serious issues like one reported by Kenneth. I saw also serious issue with NodeRed.

Also I read there are magnitude of issues with custom integrations in case of which core development doesn’t care. You guys haven’t figured out yet that most of HA functionality and popularity comes from 3rd party add ons? Thus those should be taken into consideration when releasing new ver. Saying to the user “we disabled part of your home automation, go find original author to fix this” doesn’t sound friendly.

I admit that bugs are integral part of development. But their number exposed to regular users should be far far lower. I’m just wondering if there is someone up there who does evaluation of HA development quality and leads developers somehow. Or it’s just wild uncontrolled approach.

BTW it’s not a domain of free open source projects to be buggy. A lot of such projects are led in the way to be rock stable. Are we heading there or nobody cares?

[aidbish (Adrian)]

It would help though if there were more beta testers during the beta cycle, its the same people every month, and only a handful. Hard to catch everything with limited resources

Regarding custom integrations, the changes in this release were put out in January in a blog post on the developers blog, with warnings in the users system that it would be a requirement in a future release for the last 3 months and to let the custom developers know

[maxym]

Maybe third party addons should be incl to internal testing then marked as not working for new HA version? I know it’s again more work for core dev, but it would help users to not break their installations unconsciously.

I would ask another question. In the past (before new versioning pattern), most recent patch version could have been treated as most stable. Does the same apply to todays development? I mean does most recent May’s version contain all issues brought by this ver fixed?

[aidbish (Adrian)]

Problem with that is that most integrations require hardware and people beta testing won’t know unless they have that hardware. I am not sure how it can be accomplished correctly with so many integration/hardware combinations
though some responsibility also falls to custom integration Devs to maintain them and for the users of them. If you see a warnings in your logs, telling you to let the custom integration dev know, dont ignore it

[dimadusk]

Why Mikrotik, Synology and Speedtest are being depreciated?

[tiimsvk]

Hello.
Local tuya stopped working after update

Setup failed for localtuya: Integration not found.

How do I fix it?