Yes! That’s it. Wonder why I didn’t notice this, so obvious.
Thanks for the quick help!
Have the same issue as TS; but the integration config option has been removed so it seems; there is no option to remove any set of automatic added devices currently. Only one by one, which in the case of the RFXtrx integration can be many…
Yes, I’m also missing this. I have about 100 RFXCOM devices that I would like to remove, but that is really tedious to do by selecting them individually. Also deleting the Entities is also not possible.
Any change the option to select and delete multiple RfxCom devices in one ego will be implemented soon? Or another workaround?
1 Like
Yes, I’m also missing this. I have about 5828 RFXCOM devices that I would like to remove minus 16 devices of mine. 
yes pls i have over 800 entities i want to remove from my neigbours…
1 Like
Just in case somebody is looking for the delete option, you need now to open de device info and click on the three dots to delete the device.
Yea, we know. Thing is that is just a bit tedious to do this to get rid of 100 or 1000 entities…
1 Like
Hi all,
I’m also very interested to remove over 1500 unwanted devices located to my neighbors.
Thanks in advance for any suggestion : script or sql
Vincent
Also interested in remove option.
I normally do a remove integration and add it again and hopefully remember to remove the check mark
hello, I have the same issue with over 2800 unwanted, (not existing) devices.
You need 5 mouseclicks to remove 1 (one) device.
So I need 5*2800=14000 mouseclicks to get them removed. And hoping they will not return in case I want a new device to be added.
This is a working but stupid way. Is it not possible to use the method as in the mqtt integration?
I think this integration is pretty much dead. It was always very low activity and always had a terrible UX, but if you look at the repo on github, it’s mostly just bumps of various dependencies, translation updates and the occasional small bugfix by external contributors by now.
I have an RFXCOM myself and I have given up on this integration a long time ago. It’s just really really bad. I quickly threw together a minimalist RFXCOM to MQTT interface for the protocols I use in my home. That works (for me) but it’s not very generic. I have been looking into something a bit more general and well maintained lately and stumbled across this:
So this is a NodeJS API to the RFXCOM transceiver and looks pretty well designed. It shouldn’t be too hard to add an MQTT interface to this and make it talk to HA. Then all RFXCOM devices could be specified as MQTT devices in HA and bye bye rfxtrx HA integration forever.
3 Likes
Just as an addendum to my last post above. I wrote a simple RFXCOM to MQTT driver in NodeJS using the library I linked to above and it works really well. It completely replaces the built-in HA rfxtrx integration. No more awkward and limited UI. All devices, options, everything in defined in YAML. Right now the protocol support is rather basic (mostly those I use myself), but it can be easily extended. Being independent of HA and using MQTT, it can also run on a separate system over the network.
If there is some interest, I can upload this to github.
4 Likes
Really interesting! Would love to be able to put RFXCOM on a separate machine/location from my Home Assistance system.
I’m not a developer however, so couldn’t do much with the code, but if this would be available as an application e.g. with a Docker image with some configuration Yaml that I would love to try this.
Out of curiosity, what kind of devices do you run on your RFXCOM ?
Mainly KlikAanKlikUit remotes (“AC” type) and a couple of TFA TS34C Cresta temperature sensors.
My RFXTRX2MQTT driver is now available on my github:
The readme is still very basic, but the driver runs very well (at least for me). So far it supports most temperature, humidity, rain, wind and weather sensors, as well as lighting2 (DIO, CHACON, KlikAanKlikUit, etc) and lighting5 (OTIO, Conrad) protocols for switches, remotes and relays. Feedback is welcome !
Once I wrote a better readme I’ll create a separate topic about this with more detailed usage instructions.
2 Likes
Thanks for sharing this!
I tried it this weekend and got it working quite easily. Worked pretty nice, so thanks for all the work!
Still need to find out how to get the node working as a service. Need to Google that, so any pointers would be great.
And of course then I have to scan for the id’s of all my devices and manually create mqtt configuration items for them in Home Assistant (auto-discovery would be a great addition 
).
Great ! I created an independent thread for the driver over here.
Well, considering the latest breaking changes in MQTT auto discovery… The idea with this driver is to keep it independent of HA, specifically to avoid HA breaking changes as much as possible. Adding auto-discovery would be against that concept, tying it again to HA.
Hi,
Have a look at autodecovery docker container of rfx2com/backend. Yesterday installed the container and it worked for all my “klikklak” devices and more both on Homeassistant and Domoticz (with auto zigbee2mqtt auto discovery).
Maybe the authors above can join this repository ?
Tried this. but the instructions on Installing NodeJS on the Raspberry Pi - Pi My Life Up already give me problems with the sudo apt stuff. It seems that apt is not installed or can’t be found.