-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After upgrade to 1.37.0. Option to rename the devices don’t show to add to home assistant #22415
Comments
Same issue here on home assistant green. The blue rename button is gone. |
same here.. |
Yep seems it's been removed. A lot of randomly generated entity names for new devices in HOAS MQTT now. I miss this option! |
Same here. Hope this very useful option will come back in next release ... |
I did a rollback in proxmox, and is working fine in proviois 1.36 version. |
I hope this is a bug, and not "a feature". I didn't see mention about this in the release notes, unless I'm missing something. Anybody got a workaround for this issue? |
Rollback to previous version till owner solve the problem |
The buttons were accidentally hidden on mobile browser width. Sorry about that. A fix has been applied to the front end project. |
Thnaks a lot. Do yopu means we will, have a new release in a few days? |
Already fixed in the dev branch |
Thanks, Will you promote to a new release soon? I m not using Dev. |
I will publish a hotfix release in the coming days. |
Thanks a lot |
So glad, thank you for the incredible work! |
exact the same here .. |
After upgrade to 1.37. A can rename existing and new devices because option to rename in home assistant disappears. Rollback to previous version solve the problem
What did you expect to happen?
Add and change devices in home assistant
How to reproduce it (minimal and precise)
After upgrade to 1.37 in lxc promox server
Zigbee2MQTT version
1.37.0
Adapter firmware version
20221226
Adapter
Slz06
Setup
Lxc proxmox
Debug log
No response
### What happened?The text was updated successfully, but these errors were encountered: