RFXcom problems

Configuration
22

I have done that but it dosen’t help.
Still the same fault :slightly_frowning_face:

23

So you have verified that Nodered no longer connects?
What do you get if you type “lsusb -v” ?
e.g with me it shows this connection as part of a much(!) longer output

Bus 001 Device 003: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x0403 Future Technology Devices International, Ltd
  idProduct          0x6015 Bridge(I2C/SPI/UART/FIFO)
  bcdDevice           10.00
  iManufacturer           1 RFXCOM
  iProduct                2 RFXtrx433XL
  iSerial                 3 DO5P0DW0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0020
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower               90mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              2
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
24

Yes and no, I have stopped Node-RED addon in HA
Don’t know how to verify that Node-RED isn’t connect?
Do you write “lsusb -v” in Putty that are connected to HAOS or can you do that in any other way?

25

I tried to run the “lsusb -v” command in the command terminal in the HAOS and I got this output.
image

Not the same as you?

26

So probably a different OS, I am on ubuntu
On Nodered, I am not sure what deactivating means for HAOS, if the container (it is also a container in HAOS) still runs then this could still connect. Did you try to go to your nodered url / webpage and verify it is really ‘out’?

27

I’m running HAOS, I guess that is different to ubuntu!
“lsusb -v” is maybe not working?

When I have stopped Node-RED and try open Node-RED I get following:
image

Guess that it means that Node-RED is disconnected

28

Seems OK but cannot tell for sure as not known to HAOS in that detail.
When you start Nodered, can you then still use the rfxcom from there?

29

No, the problem is that I couldn’t get the RFXtrx to work from Node-RED.
That’s why I try to go back to HA
But now the RFXtrx is not working at all!
Neither from HA or Node-RED

30

darn, well… I ran out of options as I donot know HAOS as well.
I suggest to also try to post this in the ‘integrations’ area of discord

31

I see, thank you any way :grinning:

32

Another idea (possibly last one :slight_smile: )… can you put it in another usb slot and try to set the whole thing up from scratch in HA again?

33

On discord, ‘integrations’ … user henkjanvries looks to have the same issue as you have (post 12/10/2022)…no response to his issue…
Also check the HA core issues, e.g. this one
2022.12.7 Integration RFXTRX malfunction · Issue #84177 · home-assistant/core (github.com)

34

Have put a question on Discord but no replay unfortunately :slightly_frowning_face:

35

I noticed… did you check the link above? Else open a ticket too…it also speaks of HAOS 12.7 as release. Else try to downgrade/upgrade. I would also try to not just deactivate nodered but fully remove it at the same time as rfx integration and reboot once or twice before reinstalling, it sounds a bit odd but once in a while rebooting does not pick up everything immediately (no explanation)

36

I’m running HAOS
image

I don’t really want to remove Node-RED, because I have all my automations in Node-RED.
Wrote in the HA core issue, see if I get any help there

37

Right… I though it was completely down but it is not … so then I return on the topic of node-red possibly (still?) blocking it. Is there a way that you can remove it and re-load ?
How did you get node-red to connect to the rfxtrx…I have NR too but never tried this…are there plugins of sorts?

38

I added the node-red-contrib-rfxcom library in “Manage palettes” to get the RFXtrx nodes.
I could try to remove that library

39

yep… remove

40

No I have remove the RFXcom library from Node-RED.
Removed the RFXtrx from the HA integration, reboot the system.
Added the RFXtrx integration again.
But unfortunately the result is the same, still can not connect.
Question:
Should I select the same protocols in the RFXtrx option as I have done in the RFXmngr SW or should it be unselected?
image

41

I only use auto-add when I really want to add … there is a risk that you will connect to hundreds of neighbourly smoke detectors/etc. and mass removing does not exist.
So, did you make sure that the rfx itself is accepting things? I had to go in with rfxmgr and select the options to send/receive, then save…only then it works