0.106: Light brightness stepping, better Safe Mode and person dialog

I take it you read my post? I’ve already disabled content blockers both in their own config settings as in the global Safari settings

No, haven’t bothered because I think the custom component is much better resolved (and it works…)

1 Like

Has anyone else had TotalConnect fail on them with the upgrade to 0.106.2?

Has anyone else noticed that the iOS app /presense is now reported much more often. I’ve been home all day, it reports that I’ve been home all day, but I have logbook entries every 5-10 minutes saying i’m home. I cannot see a state change

2 Likes

Some automatons seem to have stopped working and entities now take a long time to come up on android, almost to the point it’s unusable.

You’re going to have to come up with more than that if you are seeking help.

Log scrolling issue was reported a while back. It only scrolls one line at a time. It’s marked as fixed but problem still remains on iPads, even on 0.106.2

Since this was reported before and marked fixed how do we report that since its is not a new issue…?

Here’s the merged report, but it’s been closed and no way to comment that it’s still broken:

Jeff

did you ever get this sorted? I have several blank pages.

If the issue was closed recently, you comment on it stating its not fixed and they can reopen it. If some time has passed, then create a new issue. Never comment on a merged PR even if things are broken.

1 Like

I suppose in my case its the custom mini graph causing the issues.

anyone facing bluetooth issues ? bluetooth is dead since 0.105.

At 106.2 I still have the logbook scrolling issues to. iOS Companion App 2.0.0 (69). Are you opening a new issue?

Overall the performance has become annoying with this release:

  • The splash screen at start up takes way too much time
  • A lot of white screens that show for a couple of seconds without anything happening for instance when you open items in the menu
  • Entities page is sooooo slow…why are all entities loaded at start? Incremental lazy load is the general pattern for this kind of long lists. And why can’t I search while the data is loading. Enabling the search from start would make it much more usable.
  • File editor takes ages to open
  • Supervisor same issues
  • Frequent timeouts in logs
  • Automations that worked instantly have delays now for instance lights turning on when movement is detected

All signals that serieus time should be spent on performance testing and tuning before you release.

4 Likes

That’s a bit of a whingey post. What pull requests have you started to improve these areas?

1 Like

have you tried a bottom-up troubleshooting approach? Are you sure it’s no I/O issue or other kind of hardware/network issue going on?

What is it hosted on? You can imagine the software getting more features to make it better and user friendlier. Sometimes you just need more calculating power, if you want to keep up with the new things coming along.

Imagine where DOS started with just a few KB/megs of hardware where we now need more and more :slight_smile:

Hi, Same issue for me , downgrade to 0.105.5 fixed it

Here I was working on my automations while upgrading to .106 and they seemed to slow down or not work at all. Very frustrating when I can’t see if the automation is receiving the triggers or I just coded it wrong. Trying to mode to Node Red now.

I was able to get it to load. I had to remove the Monster Card custom and replace it with auto entitites. Also some of my other cards won’t load now until they get updated which i am just waiting on now.

  • Suggestion:

light.increase should be called with transition enabled if transition is enabled on the light, otherwise the light will not “dim” but simply blink toward desired brightness while rotating a dimmer. Or at least it should support the proper option.

I have recently upgraded to Home Assistant 0.106.2 and now my Tado heating/hot-water devices are listed as unavailable.
I presume that this is due to the breaking change that says:
“Adding support of multiple Tado accounts has changed the unique ID generation of sensor and climate devices, and now includes the ID of the home.”

My pre-existing devices have ids like …
sensor.heating_temperature
and I see in the “unused” section of the UI entities like this
sensor.heating_temperature_2

Is that a result of the update?
Does this mean that I will lose history details if I switch to the new id?
If yes, is there a way to retain the history?