home-assistant / frontend

:lollipop: Frontend for Home Assistant
https://demo.home-assistant.io
Other
3.94k stars 2.66k forks source link

Companion app extremely slow on Iphone #20728

Open Solarflor opened 4 months ago

Solarflor commented 4 months ago

Checklist

Describe the issue you are experiencing

My wife have Iphone 13 and I have iPhone 15. Both phone’s companion app works extremely slow. It takes 15-20 seconds to register button clicks on dashboards or just moving through it . Tried clearing front end cache. Tried reset. Tried reinstall. Same result If I open HA with Safari I have the same problem. No proplem with Chrome.

Describe the behavior you expected

The problem started with previous version of HA version but now it is impossible to use it. Also other users are complaining the same problem with Iphone

Steps to reproduce the issue

1.The probelm appear in the main menu, Panoramic and other Dashboards 2. 3. ...

What version of Home Assistant Core has the issue?

2024.5.1

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

No response

Which operating system are you using to run this browser?

No response

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

beasthouse-au commented 2 months ago

There should be something wrong in my lovelace setting How your have set it in your configuration file?

This is my setting

lovelace:
  mode: storage

same as this but what i meant was doing this.

CleanShot 2024-07-02 at 00 06 12@2x

CleanShot 2024-07-02 at 00 06 54@2x

CleanShot 2024-07-02 at 00 07 24@2x

themistymay commented 2 months ago

I'll reiterate the issue not being dashboard specific. I have two matching phones, one is impacted and one is not so it is not a dashboard/lovelace issue. It would have to be something underneath that is instantiating either non-deterministically or impacted by something local to the phone that is outside the front end and app cache.

On Mon, Jul 1, 2024 at 10:08 AM beasthouse-au @.***> wrote:

There should be something wrong in my lovelace setting How your have set it in your configuration file?

This is my setting

lovelace: mode: storage

same as this but what i meant was doing this.

@.*** (view on web) https://github.com/home-assistant/frontend/assets/78465928/fb07d424-f931-421c-bc15-f3e047a41791

@.*** (view on web) https://github.com/home-assistant/frontend/assets/78465928/a499a307-6718-4c87-a67f-5cde085fff5e

@.*** (view on web) https://github.com/home-assistant/frontend/assets/78465928/e95e4d19-b22f-4d6a-8199-c91e02b94deb

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/frontend/issues/20728#issuecomment-2200253833, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABB72YBCJAJJLBOQLYHLJ3ZKFPGJAVCNFSM6AAAAABHGZ5GX6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBQGI2TGOBTGM . You are receiving this because you commented.Message ID: @.***>

Solarflor commented 2 months ago

same as this but what i meant was doing this.

I don't have it and I don't know why.

Solarflor commented 2 months ago

Solved!

I followed @loopy321 and @beasthouse-au way and I have creating a new default dashboard with nothing on it.

bramkragten commented 1 month ago

After a lot of debugging, this seems to be a regression in Safari/iOS. Newer versions of Safari are showing these performance issues while older versions are not. We will file a bug at Apple.

thoduh commented 1 month ago

Since I activated Homeassistant Cloud (Test month) today, the app has been working without any delay.

beasthouse-au commented 1 month ago

Since I activated Homeassistant Cloud (Test month) today, the app has been working without any delay.

Yeah it's been fairly stable lately

thoduh commented 3 weeks ago

Only lasted a short time, problems are back... :-(

rodrigofragadf commented 3 weeks ago

It had improved for a while but the problem came back.

le-clu commented 3 weeks ago

For me, the latest iOS update solved it. So either it is a coincidence or the bug with Safari mentioned above was indeed fixed by Apple.