Unexpected ConBee devices in deCONZ device list and unexpected response from cmd command GCFFlasher -l

[DRichards995]

Describe the bug

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

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

deCONZ and GCFFlasher see just the Conbee II and don't report Conbee devices where there aren't any

Screenshots

Attaching screenshot of deCONZ screen. Notice the IDs of the unexpected Combee devices match those listed by GCFFlasher

Environment

• 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

Not applicable

Additional context

Nothing to add

[github-actions[bot]]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[github-actions[bot]]

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.