You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not using Home Assistant. Or: a developer has told me to come here.
I have checked the troubleshooting section and my problem is not described there.
I have read the changelog and my problem is not mentioned there.
Deploy method
Home Assistant Add-on
Z-Wave JS UI version
9.20.0
ZwaveJS version
13.3.1
Describe the bug
Changing UI settings (dark mode, navigation tabs, streamer mode) does not activate the Save button anymore. The new settings are applied immediately but don't survive reloading the page. The only way to save these settings is to change some other setting as well to enable the Save button.
To Reproduce
Change a UI setting - new setting is applied
Refresh the page - old setting is used
Change a UI setting and some other setting, click Save
Refresh the page - new setting is used
Expected behavior
UI setting changes should activate the Save button, or be saved without needing to click the button and survive page reloads.
Additional context
Full disclosure, a HA developer didn't tell me to come here 😉 I confirmed that the bug can be reproduced in both the HA addon and the docker version.
The text was updated successfully, but these errors were encountered:
Checklist
Deploy method
Home Assistant Add-on
Z-Wave JS UI version
9.20.0
ZwaveJS version
13.3.1
Describe the bug
Changing UI settings (dark mode, navigation tabs, streamer mode) does not activate the Save button anymore. The new settings are applied immediately but don't survive reloading the page. The only way to save these settings is to change some other setting as well to enable the Save button.
To Reproduce
Expected behavior
UI setting changes should activate the Save button, or be saved without needing to click the button and survive page reloads.
Additional context
Full disclosure, a HA developer didn't tell me to come here 😉 I confirmed that the bug can be reproduced in both the HA addon and the docker version.
The text was updated successfully, but these errors were encountered: