Skip to content
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

Graphical update-state box position within OTA menu #22806

Closed
Grandma-Betty opened this issue May 28, 2024 · 3 comments
Closed

Graphical update-state box position within OTA menu #22806

Grandma-Betty opened this issue May 28, 2024 · 3 comments
Labels
problem Something isn't working

Comments

@Grandma-Betty
Copy link

Grandma-Betty commented May 28, 2024

What happened?

Within the Z2M OTA menu in Home Assistant, it is very annoying that on a certain point, while updating multiple devices simultaneously, device update state boxes unfortunately are popping up on a position where it is not possbile to start updates for other devices because they get in the way, please have a look on the attached screenshot, where you can see the problem. The red device update buttons are "hidden" behind the blue update state boxes.
Screenshot 2024-05-28 092530

What did you expect to happen?

The position of the popping up blue update states should get re-arranged in a way they will not get in an unfortunate way. Edit: Or even give the possibility to deactive popups completely.

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

1.37.1

Adapter firmware version

20221226

Adapter

zStack3x0

Setup

HAOS 2024.5.4 x86-64 (Virtual machine)

Debug log

No response

@Grandma-Betty Grandma-Betty added the problem Something isn't working label May 28, 2024
@LaurentChardin
Copy link
Contributor

Hi,

May i suggest you create/move a ticket to the following github repo : https://github.com/nurikk/zigbee2mqtt-frontend ?
The issue you are describing is linked on how the react app is reacting to events in the websocket, and probably it should start to behave differently during the OTA process.

Seems more like frontend topic to be analysed (and see if we can manage it in React before trying to change the middleware)

@LaurentChardin
Copy link
Contributor

By the way, the culprit is the react-notifications-component which seems to have an issue clearing out the DOM under frequent load of notifications: teodosii/react-notifications-component#157

Issue to reference here : https://github.com/nurikk/zigbee2mqtt-frontend

@LaurentChardin
Copy link
Contributor

@Koenkk Issue created here : nurikk/zigbee2mqtt-frontend#2033. we could close this one..

@Koenkk Koenkk closed this as completed Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants