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
Widgets don't stay saved to new location (1.4.0-beta.20) #459
Comments
While attempting to recreate this bug on my Samsung galaxy OS it seemed to work untill my 4th move then HG said everything wasn't configured and sent me to the initial setup screen again :( . |
Strangely after several hours HG appeared setup again on my android, however widgets were still not in the moved position. Tried the Edge browser on the Android with same results. (Widgets move to new location but don't get saved to that location)😖😖😖 |
Let me know if this happen again with latest release. |
With latest release beta 24 this still happens on my windows 10 pc using the Edge browser. HG is running on a raspi 3b+. This happens with both the 32 and 64 bit versions. |
So, is this problem occurring only on Edge browser? |
Yes only with the Edge browser on Windows pc |
- Fix issue #459 (widget sorting order not saved) - UPnP: fix HomeGenie Server not discovered in Windows OS - ZigBee: removed "Flow Control" option from settings page, still available in *systemconfig.xml* file.
Version
latest version 1.4.0-beta.20 both 32 and 64 bit versions tested on my pi 3b+
Describe the bug
unable to move (re-arrange widgets) and them stay saved to that location.
Code to Reproduce
Write a small snippet to isolate your bug and could be possible to our team test. (REQUIRED)
Expected behavior
once widgets have been moved they stay there for next load of HG
Screenshots/Stacktrace
If applicable, add screenshots/stacktrace
Additional context
widgets do move to new location however if you refresh the screen or restart HG they are not where they should be but back in there previously moved position.
this happens for both newly added widgets as well as old added widget.
this may be Browser specific but happens in the Edge browser.
The text was updated successfully, but these errors were encountered: