English please
Yes! I made a whole post about this but it only fails when i upgrade node red to 6.12. I kept getting api errors when I used both. So many errors it actually bogged the system down to the point of crashing constantly
Edit: went back to earlier with my snapshot - after new try with 0.106.2 problem disappeared.
After upgrading to 0.106.2 everything seem to work just OK but for some reason in DEVTOOL INFO page the ācondition of the systemā does not seem to work. It never finishes the job ā¦ RPI3B+/HassIO
Disable content blockers for HA. That will fix memory usage for Safari. You can contibue using content blockers for other sites.
Disabling content blockers for HA webpage will fix the high memory usage issue.
Same problems for me, after adding the Melcloud integration the window closes without any configuration and canāt find the X-MitsContextKey key.
Did you solve it?
EDIT: here you can find the key: Mitsubishi MELCLOUD integration with Home Assistant
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ā¦)
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
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.
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.
Thatās a bit of a whingey post. What pull requests have you started to improve these areas?