I logged a bug/defect in REST API GitHub a fortnight ago
opened 05:04PM - 22 Oct 22 UTC
stale
Bug report
<!--
- Use this issue template to report a bug in the deCONZ REST-API.
- A… nything that is not clearly a bug can implicate manual closure. For support we recommend the forum: https://forum.phoscon.de
- If you want to report a bug for the Phoscon App, please head over to: https://forum.phoscon.de
- Make sure not to remove any headers and fill the template completely. If you remove the headers, the issue will be auto-closed.
- If you're unsure if the bug fits into this issue tracker, please ask for advise in our Discord chat: https://discord.gg/QFhTxqN
- Please make sure sure you're running the latest version of deCONZ: https://github.com/dresden-elektronik/deconz-rest-plugin/releases
-->
[ This is a report of a bug in deCONZ GUI rather than in the REST API (but the deCONZ page https://forum.phoscon.de/c/deconz/6 directed me here, so hope that's ok ]
## Describe the bug
<!--
Describe the issue you are experiencing here to communicate to the
maintainers. Tell us what you were trying to do and what happened.
Help us understand the issue by providing valuable context.
-->
Using Windows 10 with the deCONZ GUI open and connected to my Combee II network, I find that dragging the GUI window around the screen frequently causes the GUI to disconnect from the device. This is the only circumstance that unexpected disconnects are occurring.
When the issue occurs, the GUI doesn't actually crash it just disconnects from the device, and the user is able to directly connect to the device again without issue. Working with the GUI without moving the GUI window (ie normal work open/closing of panels, moving the nodes around within the network chart) is perfectly fine - there are no disconnects under normal & extended operations). There are no issues moving windows from other applications around on the same Windows computer
Occurrence was fairly frequent to begin with, but I've gradually 'trained' myself to avoid the window manipulation which seemingly leads to the issue, but I'm still hit by the issue from time to time.
## Steps to reproduce the behavior
<!--
If the problem is reproducable, list the steps here:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. Observed error
If the problem can't be reproduced and is sporadic, please provide some details
on how often and when the issue happens.
-->
1. Open deCONZ on Windows 10 computer
2. Connect to Device (in my case the device is a Conbee II and it autojoins when I first start)
3. With the chart of the discovered network showing,
grab the top bar of the window and begin dragging the window around the screen.
[ The issue doesn't normally present itself with a just short single-action drag. Drags of just 1s duration don't cause the issue
Sometimes it requires dragging the screen first one direction and then another
(it may take 3-5s for the issue to occur sometimes up to 10s. Eventually it does.
Sometimes it appeared that moving the window so its top or left edge of the window went beyond screen extent
caused the problem but I don't think this is a clear critical factor. I think it's just time moving/jiggling the window
around which results in the disconnect, maybe some form of Paint/refresh window issue ?)
5. At some point the GUI disconnects from the device, and the GUI returns to the initial window requesting the Device to Connect
## Expected behavior
<!--
If applicable, describe what you expected to happen.
-->
The GUI window should never disconnect from the device because the window is being dragged around the screen.
## Screenshots
<!--
If applicable, add screenshots to help explain the problem.
-->
Not applicable. Above description is sufficient.
## Environment
<!--
The deCONZ and firmware versions are found in the Phoscon App: Menu -> Settings -> Gateway,
as well as in the deCONZ GUI: Menu > Help > About deCONZ.
-->
- Host system: PC with Windows 10
- Running method: Windows
- Firmware version: 0x26580700 (this is what appears in 'About deCONZ'
- deCONZ version: v2.18.2
- Device: ConBee II
- Do you use an USB extension cable: Yes ( a 30cm cable connected between Conbee II and USB hub + 40 cm from USB Hub to laptop)
- Is there any other USB or serial devices connected to the host system? Yes, multiple (telescope, 2 cameras, focuser, USB Hubs,
- observatory dome)
## deCONZ Logs
<!--
Debug logs can help to investigate certain problems like device pairing and communication issues.
Logging can be enabled on the command line as described in:
https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/deCONZ-debug-flags
Secondly, for versions above 2.05.87: In the deCONZ GUI: click Help > debug view. Output of APS,ZDP, ZCL and INFO can be handy.
-->
Not applicable
## Additional context
<!--
If relevant, add any other context about the problem here, like network size, number of routers and end-devices
and what kind of devices/brands are in the network.
-->
Nothing to add
but I didn’t post a message to the forum at the time (this might explain why the issue is about to go stale in Github if nobody knows about it. Perhaps I should be posting to both places ? I’m not yet sure how the forum/gitbub exactly work together)
The bug/defect is to do with deCONZ GUI rather than its REST API, but the bug logging process led me to the REST API GitHub. Description of the issue follows:
Using Windows 10 with the deCONZ GUI open and connected to my Combee II network, I find that dragging the GUI window around the screen frequently causes the GUI to disconnect from the device. This is the only circumstance that unexpected disconnects are occurring.
When the issue occurs, the GUI doesn’t actually crash it just disconnects from the device, and the user is able to directly connect to the device again without issue. Working with the GUI without moving the GUI window (ie normal work open/closing of panels, moving the nodes around within the network chart) is perfectly fine - there are no disconnects under normal & extended operations). There are no issues moving windows from other applications around on the same Windows computer
Occurrence was fairly frequent to begin with, but I’ve gradually ‘trained’ myself to avoid the window manipulation which seemingly leads to the issue, but I’m still hit by the issue from time to time.
David
Mimiix
November 13, 2022, 9:04am
2
Hi, just bump the GitHub issue. The bot makes sure it’s not forgotten about by auto closing. When this happens , all devs get an email from GitHub. However , if there is not a lot of interest on fixing ut,. It can take a while.
No need to post here , as GitHub is enough.