home-assistant / frontend

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

Automation entity/device picker selects incorrect choice #23934

Open boojew opened 1 month ago

boojew commented 1 month ago

Model Name: Apple iPhone 16 pro max Software Version: 18.3 App version: 2025.1.1

Home Assistant Core Version

2025.1.4 Describe the bug When using the automation editor, if I try and select a device of entity, it will always select the wrong entity. Usually the one at the top of the list, but I am sure I have seen it pick devices not even in the list.

Does NOT happen on mobile safari.

To Reproduce Create or edit automation, in action pane, select an action like switch turn on or device and then try and pick a device. Happens both when trying to filter by typing a name or just picking from the list.

Expected behavior

Screenshots

Additional context

bgoncal commented 1 month ago

Can you share a screen recording comparing how it behaves in iOS Safari and the App? Just so I evaluate if this can be fixed in the App or with the frontend team.

boojew commented 1 month ago

Sure thing. This is the app

https://github.com/user-attachments/assets/213e8c95-1108-491d-a91e-f1a4e776f15a

This is safari (video was too big to embed)

https://drive.google.com/file/d/1gb4q337bQka5kkzbZueqXuBuX00mVNMS/view?usp=drivesdk

I just did it for entity.. I couldn’t get it to happen for devices this time around, but it was happening yesterday.

bgoncal commented 1 month ago

I requested access to the safari video

boojew commented 1 month ago

Oops. Thought I made it public. Sorry. Done.

bgoncal commented 1 month ago

If you do it repeatedly in the app and in safari, does safari shows the bug at least once? Same for the App, if you try several times, does the app select it correctly sometimes?

bgoncal commented 1 month ago

I am checking with the frontend team if they know what could cause this, I'll be back when I have more information

bgoncal commented 1 month ago

I checked with frontend and even though the issue is not happening in Safari to you, it's Safari-related according to them. I will be transferring this issue to frontend repo