I logged a defect/bug in deCONZ and in GCFFlasher a fortnight ago
opened 05:41PM - 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
-->
## 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.
-->
The Devices List shown when deCONZ starts contains 4 entries on my Windows 10 machine. One of the these is my Conbee II and is thus expected, but the other 3 are unexpected Conbee devices. I've never had Conbee devices on my computer or system ever.
deCONZ autojoins to my Conbee II device so this is not a significant issue.
I didn't think anything of it until today when I had need to check the Com port that my ConBee II is connected to, ahead of flashing Firmware (after mistakenly using ZShark - never again). I knew it was COM7 but I checked it with GCFFlasher -l and go the following table
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Path | Vendor | Product | Serial | Type
-----------------+--------+---------+------------+-------
\\.\COM4 | 0x0403 | 0x6015 | PA2U9D23A | ConBee
\\.\COM6 | 0x0403 | 0x6015 | US2RETFYA | ConBee
\\.\COM3 | 0x0403 | 0x6015 | DN033EKNA | ConBee
\\.\COM5 | 0x0403 | 0x6001 | AK08TPBAA | Generic FTDI
\\.\COM7 | 0x1CF1 | 0x0030 | DE2456287 | ConBee II
It contains my ConBee II as expected on COM7, but it shows ConBee on 3 of the other COM Ports that I use. None of these have a ConBee. Code used by GCFFlasher and deCONZ is clearly being mistaken by these ports.
Ports 3, 4 and 6 contain FTDI USB-Serial Convertors (all 0x0403 / 0x6015 in the table) attached to Observatory Dome, a Powerbox Hub and a Telescope respectively), all totally different equipment and using different make of USB-Serial convertor but possibly the same FTDI chipset.
Port 5 also contains an FTDI USB-Serial Convertor ( 0x0403 / 0x6001 in table) connected to a Focuser
## 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.
-->
Issue is repeatable on my system. But may not necessarily appear on other people systems.
1. With a WIndow Computers, attach ConBee II device
2. Attach one or more USB-Serial Convertors of type 0x0403 / 0x6015
3. Open deCONZ and look at list of devices for unexpected ConBee devices
4. Alternatively run GCFFlasher and look at list of COM Ports for unexpected ConBee devices
5. Unexpected Conbee devices seen
## Expected behavior
<!--
If applicable, describe what you expected to happen.
-->
deCONZ and GCFFlasher see just the Conbee II and don't report Conbee devices where there aren't any
## Screenshots
<!--
If applicable, add screenshots to help explain the problem.
-->
Attaching screenshot of deCONZ screen. Notice the IDs of the unexpected Combee devices match those listed by GCFFlasher
## 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 (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 and other)
## 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 didn’t post a note to the forum at the time, which might explain why it is about to go stale, if nobody knows about. Should I be automatically post to this forum if I add something to GitHub issues?
Description of the logged issue follows
The Devices List shown when deCONZ starts contains 4 entries on my Windows 10 machine. One of these is my Conbee II and is thus expected, but the other 3 are unexpected Conbee devices. I’ve never had Conbee devices on my computer or system ever. deCONZ autojoins to my Conbee II device so this is not a significant issue.
I didn’t think anything of it until today when I had need to check the Com port that my ConBee II is connected to, ahead of flashing Firmware. I knew it was COM7 but I checked it with GCFFlasher -l and got the following table
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh*
Path | Vendor | Product | Serial | Type*
-----------------±-------±--------±-----------±------*
.\COM4 | 0x0403 | 0x6015 | PA2U9D23A | ConBee*
.\COM6 | 0x0403 | 0x6015 | US2RETFYA | ConBee*
.\COM3 | 0x0403 | 0x6015 | DN033EKNA | ConBee*
.\COM5 | 0x0403 | 0x6001 | AK08TPBAA | Generic FTDI*
.\COM7 | 0x1CF1 | 0x0030 | DE2456287 | ConBee II*
It contains my ConBee II as expected on COM7, but it shows ConBee on 3 of the other COM Ports that I use. None of these have a ConBee. Code used by GCFFlasher and deCONZ is clearly being mistaken by these ports.
Ports 3, 4 and 6 contain FTDI USB-Serial Convertors (all 0x0403 / 0x6015 in the table) attached to Observatory Dome, a Powerbox Hub and a Telescope respectively), all totally different equipment and using different make of USB-Serial convertor but possibly the same FTDI chipset. Port 5 also contains an FTDI USB-Serial Convertor ( 0x0403 / 0x6001 in table) connected to a Focuser
Mimiix
November 13, 2022, 9:03am
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.