# Node Red access to USB port for rfxcom (running in iobroker)

**URL:** https://discourse.nodered.org/t/node-red-access-to-usb-port-for-rfxcom-running-in-iobroker/77626
**Category:** General
**Tags:** windows, iobroker
**Created:** [16 April 2023 11:20 UTC](https://discourse.nodered.org/t/node-red-access-to-usb-port-for-rfxcom-running-in-iobroker/77626 "2023-04-16T11:20:17Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![Mikee1234K](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mikee1234k/32/70283_2.png) [@Mikee1234K](https://discourse.nodered.org/u/Mikee1234K)
#### Post date: [16 April 2023 11:20 UTC](https://discourse.nodered.org/t/node-red-access-to-usb-port-for-rfxcom-running-in-iobroker/77626/1 "2023-04-16T11:20:17Z")

</div>

My Node Red runs in iobroker, on Windows10 Pro. I want to give Node Red access to one (or all) of my USB ports, to access my Rfxtrx 433 device (it is on USB4)  
I am trying to use the Rfxcom nodes, but trying to configure the device it does not look as if I have access to the USB ports on my machine. I guess I need to configure that in iobroker, but dont know how  
I have a rfx sensor node, and configured the serial port as /dev/ttyUSB4, but it just says disconnected under the rfx sensor node (I have tried anything from USB0 to 4). I have attached a debug to the sensor node (show complete message) but nothing is showing in the debug window

---

<div class="post-metadata">

### Author: ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [16 April 2023 12:18 UTC](https://discourse.nodered.org/t/node-red-access-to-usb-port-for-rfxcom-running-in-iobroker/77626/2 "2023-04-16T12:18:29Z")

</div>

> [@Mikee1234K](#):
>
> /dev/ttyUSB4

That is not a Windows USB port. They are things like `COM3:`.

To see available COM ports, open "device manager", turn on "show hidden" and they should show up as "Ports (COM & LPT)"

---

<div class="post-metadata">

### Author: ![Mikee1234K](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mikee1234k/32/70283_2.png) [@Mikee1234K](https://discourse.nodered.org/u/Mikee1234K)
#### Post date: [16 April 2023 12:29 UTC](https://discourse.nodered.org/t/node-red-access-to-usb-port-for-rfxcom-running-in-iobroker/77626/3 "2023-04-16T12:29:40Z")

</div>

It is on USB4. I checked in the device manager on the events, which shows

Device FTDIBUS\VID\_0403+PID\_6001+A1Y17NPPA\0000 was configured.

Driver Name: oem19.inf  
Class Guid: {4d36e978-e325-11ce-bfc1-08002be10318}  
Driver Date: 08/16/2017  
Driver Version: 2.12.28.0  
Driver Provider: FTDI  
Driver Section: FtdiPort.NTamd64  
Driver Rank: 0xFF0000  
Matching Device Id: FTDIBUS\COMPORT&VID\_0403&PID\_6001  
Outranked Drivers:  
Device Updated: false  
Parent Device: USB\VID\_0403&PID\_6001\A1Y17NPP  
 ![Com port](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/2/c219367c38a8f11928c37096b5acaf232e6188b1.png)

---

<div class="post-metadata">

### Author: ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [16 April 2023 12:31 UTC](https://discourse.nodered.org/t/node-red-access-to-usb-port-for-rfxcom-running-in-iobroker/77626/4 "2023-04-16T12:31:10Z")

</div>

So the serial port you need to use in Windows is `COM4:`

---

<div class="post-metadata">

### Author: ![Mikee1234K](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mikee1234k/32/70283_2.png) [@Mikee1234K](https://discourse.nodered.org/u/Mikee1234K)
#### Post date: [16 April 2023 12:34 UTC](https://discourse.nodered.org/t/node-red-access-to-usb-port-for-rfxcom-running-in-iobroker/77626/5 "2023-04-16T12:34:07Z")

</div>

Yes I tried that, its not connecting

 ![Screenshot 2023-04-16 133325](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/e/6e0b0ceda04796b030a56098b226c47fd50e5761.png)

---

<div class="post-metadata">

### Author: ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [16 April 2023 12:38 UTC](https://discourse.nodered.org/t/node-red-access-to-usb-port-for-rfxcom-running-in-iobroker/77626/6 "2023-04-16T12:38:41Z")

</div>

Possibly the port needs a specific configuration - you would need to check the devices documentation for that. Or possibly ioBroker is getting in the way, I don't use it so I can't help there.

I would usually stop node-red and use a command line tool to connect to the serial port to make sure it is talking and that I know what settings to use.

Also check and make sure nothing else has grabbed the port. Typically only one app/service can connect to a serial port at one time.

You could also delete the rfx node and use a standard serial node to see if you can get any data out.

---

<div class="post-metadata">

### Author: ![Mikee1234K](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mikee1234k/32/70283_2.png) [@Mikee1234K](https://discourse.nodered.org/u/Mikee1234K)
#### Post date: [16 April 2023 12:42 UTC](https://discourse.nodered.org/t/node-red-access-to-usb-port-for-rfxcom-running-in-iobroker/77626/7 "2023-04-16T12:42:33Z")

</div>

That was it. My Homeseer system was still using the USB port to read data from the Rfxtrx. After I turned it off, data started flowing !

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)
#### Post date: [30 April 2023 12:43 UTC](https://discourse.nodered.org/t/node-red-access-to-usb-port-for-rfxcom-running-in-iobroker/77626/8 "2023-04-30T12:43:29Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
