Hi,
If you followed the steps for a clean basic OH 5.0.2 and only added the Zigbee binding and nothing else then OH should not be using any other com ports at this point except what you configured for the dongle.
This test effectively removes OpenHAB from being the issue.
Which points it back to either a hardware issue (dongle or PC) or a software issue with OS.
If you want to further validate that you have a few options.
The behavior you are seeing reminds me of how the P version of the dongle acts with OH
Are you 100% sure you have a E version and are you 100% sure the firmware version flashed correctly?
with OpenHAB stopped again make sure the openhab service is also stopped and disabled! (windows 11 likes to try and fix services that are set to automatic and just stopped and not disabled)
and you run from command line with elevated permission
mode
what does it return?
when you run
mode COM3
assuming from your earlier posts you said dongle was assigned to COM3 what does it return?
now after running that review the results what does the comm port report as the baud and flow control settings?
something like this ?
PS C:\WINDOWS\system32> mode COM3
Status for device COM3:
-----------------------
Baud: 115200
Parity: None
Data Bits: 8
Stop Bits: 1
Timeout: ON
XON/XOFF: OFF
CTS handshaking: OFF
DSR handshaking: OFF
DSR sensitivity: OFF
DTR circuit: ON
RTS circuit: OFF
next start OpenHAB version 5.0.2 from bat file.
Now run the mode command again does the COMM Port the dongle is on disappear?
If yes then OH bound to the comm port and took control.
If no then the OS is not releasing it to OpenHAB to allow it to connect too. This would indicate some other process outside of OpenHAB has the comm port locked.
If you truly want to check all of your hardware and OS without the OpenHAB influence, then go to the Zigbee2MQTT site and follow all the steps to install Zigbee2MQTT on windows and see if it works with your dongle.
if you want to see what OpenHAB is using then you can (with OpenHAB running) from the karaf cli
run
openhab> serial identifiers
[name: COM1, current owner: null]
[name: COM2, current owner: null]
[name: COM6, current owner: org.openhab.binding.zwave]
[name: COM3, current owner: org.openhab.binding.zigbee]
[name: COM4, current owner: null]
openhab>
and that will show you from OpenHAB point of view what it has attached
you may also run serial creators to see exactly what all comm ports are being used by OpenHAB and who owns them
openhab> serial creators
class org.openhab.core.io.transport.serial.rxtx.rfc2217.internal.RFC2217PortProvider, accepted protocols: [ProtocolType [pathType=NET, scheme=rfc2217]], port identifiers: []
class org.openhab.core.io.transport.serial.internal.RxTxPortProvider, accepted protocols: [ProtocolType [pathType=LOCAL, scheme=rxtx]], port identifiers: [[name: COM1, current owner: null], [name: COM2, current owner: null], [name: COM6, current owner: org.openhab.binding.zwave], [name: COM3, current owner: org.openhab.binding.zigbee], [name: COM4, current owner: null]]
openhab>
hope this helps.
even if you did not buy it from them directly.
