RFXCOM in home Assistant

Dear,
Until today I’m trying to convert all my iobroker working domotic to Home Assistant.
I’ve RFXcom working on iobroker and try to place it on home assistant.
I’d connect the rfxcom transmitter to my PC and on the RFY tab took the list of devices.
For exemple this device :

23-02-25 03:38:42:396= 14010324000400000500A706E77420524658434F4D
Packettype = Interface Message
subtype = RFY remote:4 ID:00 00 05 unitnbr:0 rfu1:A7 rfu2:6 rfu3:E7

I connect the transmitter on my Raspberry Pi 4 with HA installed.
INtegrate the RFXcom and add device with the code :
071a00000000050

The device was added.
But it seems that it’s not recognize has a store… And I’m not able to pilot him…

Can you help me?

thanks a lot

So, I don’t know why, but now everything works.
I’ve one more question, I’ve a second transmitter RFXCOM433 same as the first one working.
Is it possible to add the devices by uploeding them from the RFCcom working to the new one to avoid apparing?
I tryed to do it in the “RFY” Tab and with all devices listed from the first one, I connected the new one and fullfill all information to transmit them but error occured as follow
************** Texte de l’exception **************
System.OverflowException: L’opération arithmétique a provoqué un dépassement de capacité.
à RFXmngr.frmMain.btnRFY_Click(Object sender, EventArgs e)
à System.Windows.Forms.Control.OnClick(EventArgs e)
à System.Windows.Forms.Button.OnClick(EventArgs e)
à System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
à System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
à System.Windows.Forms.Control.WndProc(Message& m)
à System.Windows.Forms.ButtonBase.WndProc(Message& m)
à System.Windows.Forms.Button.WndProc(Message& m)
à System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
à System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Assemblys chargés **************
mscorlib
Version de l’assembly : 4.0.0.0
Version Win32 : 4.8.9277.0 built by: NET481REL1LAST_B
CodeBase : file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

RFXmngr
Version de l’assembly : 19.0.0.57
Version Win32 : 19.0.0.57
CodeBase : file:///C:/Users/bertr/Downloads/RFXmngr/RFXmngr.exe

Microsoft.VisualBasic
Version de l’assembly : 10.0.0.0
Version Win32 : 14.8.9032.0 built by: NET481REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll

System.Windows.Forms
Version de l’assembly : 4.0.0.0
Version Win32 : 4.8.9251.0 built by: NET481REL1LAST_C
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System
Version de l’assembly : 4.0.0.0
Version Win32 : 4.8.9261.0 built by: NET481REL1LAST_C
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

System.Drawing
Version de l’assembly : 4.0.0.0
Version Win32 : 4.8.9032.0 built by: NET481REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

System.Configuration
Version de l’assembly : 4.0.0.0
Version Win32 : 4.8.9032.0 built by: NET481REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

System.Core
Version de l’assembly : 4.0.0.0
Version Win32 : 4.8.9277.0 built by: NET481REL1LAST_B
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

System.Xml
Version de l’assembly : 4.0.0.0
Version Win32 : 4.8.9032.0 built by: NET481REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

Accessibility
Version de l’assembly : 4.0.0.0
Version Win32 : 4.8.9032.0 built by: NET481REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

System.Runtime.Remoting
Version de l’assembly : 4.0.0.0
Version Win32 : 4.8.9214.0 built by: NET481REL1LAST_B
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll

System.resources
Version de l’assembly : 4.0.0.0
Version Win32 : 4.8.9032.0 built by: NET481REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.resources/v4.0_4.0.0.0_fr_b77a5c561934e089/System.resources.dll

mscorlib.resources
Version de l’assembly : 4.0.0.0
Version Win32 : 4.8.9032.0 built by: NET481REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_fr_b77a5c561934e089/mscorlib.resources.dll

System.Windows.Forms.resources
Version de l’assembly : 4.0.0.0
Version Win32 : 4.8.9032.0 built by: NET481REL1
CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_fr_b77a5c561934e089/System.Windows.Forms.resources.dll

************** Débogage JIT **************
Pour activer le débogage juste-à-temps (JIT), le fichier de configuration pour cette
application ou cet ordinateur (machine.config) doit avoir la valeur
jitDebugging définie dans la section system.windows.forms.
L’application doit également être compilée avec le débogage
activé.

Par exemple :

Lorsque le débogage juste-à-temps est activé, les exceptions non gérées
seront envoyées au débogueur JIT inscrit sur l’ordinateur
plutôt que d’être gérées par cette boîte de dialogue.


I have two also. I had to pair the second one also with the blinds that they control.

I found, with rfx manager, you can list devices from the first, and you can upload with the RFY tabs, but you’ve to select from the scroll bar all the parameters before transmit them to the transmitter.
I was fulfill with my keyboard… you’ve just to select them.
Now both are working without any pairing mode