Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
11.2k stars 1.6k forks source link

Doesn't work function to change friendly name in mobile app and mobile browser #22385

Open zvezdochet2004 opened 2 weeks ago

zvezdochet2004 commented 2 weeks ago

Screenshot_2024-05-02-02-17-07-547_io homeassistant companion android-edit Screenshot_2024-05-02-02-09-18-038_io homeassistant companion android-edit

What happened?

The button to change friendly name has disappeared in the mobile app and mobile version browser Chrome (OS Android)

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

Open the device panel or device card

Zigbee2MQTT version

1.37.0

Adapter firmware version

20210813

Adapter

zStack3x0

Setup

Addon in home assistant supervised

Debug log

No response

tsloms commented 2 weeks ago

Same problem here

Milinator commented 2 weeks ago

Same here

timwnl commented 2 weeks ago

Same issue here in iOS safari browsers, running in docker. Works fine in desktop browsers

Koenkk commented 2 weeks ago

@nurikk could you check this?

serlinGi commented 2 weeks ago

with android phone this feature rewards you by placing the phone horizontally

TheRealWaldo commented 2 weeks ago

The same is occurring in the Home Assistant application.

Milinator commented 2 weeks ago

The same is occurring in the Home Assistant application.

Just found out: If you put your phone into horizontal mode the edit button appears. Strange because that wasn't the case before this update and I don't understand why that'd be a better approach. It worked like this.

TheRealWaldo commented 2 weeks ago

Also note: the 'also rename home assistant' switch is gone on both mobile AND web.

The devices entites named by their ID (0xaf00fe etc.) and there doesn't seem to be a way to update them anymore.

Koenkk commented 1 week ago

Also note: the 'also rename home assistant' switch is gone on both mobile AND web.

This has already been fixed in the dev branch