You say you checked auto-add, and then you show yaml-config. You should either use GUI or yaml, not both. No idea if this has any negative impact.
You can find the correct device in supervisor > host > … > Hardware.
There should not be any quotes around the device-id. But the GUI integration should take care of that.
I just tried commenting out the yaml, restarted, and the devices are still not added. I also tried disabling automatic add and my device is still not added.
However in the RFXCom docs under RFY it says " The RFXtrx433e is required for RFY support, however, it does not support receive for the RFY protocol - as such devices cannot be automatically added." I think I need the YAML and I don’t think having automatic add does anything for my case whether it’s on or not.
Under hardware this is what I see. It’s not clear which path I’m supposed to use. If I had the wrong path I don’t think the integration would start up which makes me think this isn’t the issue.
Everything you write makes sense. You seem to be using the correct USB-device.
I have configured my RFXtrx433e a long time ago in yaml, so I don’t remember the details.
I had to program it by uploading the custom firmware with the RFXmngr to the RFXtrx433e.
This will make the Somfy deviceids available in HA.
They indeed do only communicate one way
Sometime last year the configuration was automatically imported, and I deleted the yaml.
How can I tell if I have the correct firmware on the RFXtrx?
I can control my blinds using RFXmngr which I assumed meant that I was on the correct firmware. Or maybe there’s something else I need to do in RFXmngr to save the configuration to the RFXrtx?
Which version of HA are you using ? because since a couple of releases, you have to configure RFXTRX devices via the integration menu (not in yaml anymore)… If your RFXTRX is recognized by HA, you should have a RFXTRX integration like this:
Via the integration menu, you can configure it and add the devices you have identified previously…
Oh wow. That was the issue. My device is appearing correctly now. Thank you!
I interpreted “Enter event code to add” as an actual code to send to specific devices that have already been added. Not adding my device code. Looking at the documentation again that is mentioned right above the RFY section too RFXCOM RFXtrx - Home Assistant
I had to reread the manual again. You are right: if you can control the devices with the RFXmngr, everything is right on that end. The RFXtrx433e has been registered as a remote on the devices.
Notice that I have a different rfx-device (433e not 433xl). Could that be a Problem?
As mentioned in the documentation, The RFXtrx433e is required for RFY support, however, it does not support receive for the RFY protocol - as such devices cannot be automatically added.
I know this an old topic, but i’m looking for a way to migrate from RFXCOM ser2net implementation to just USB.
I moved away from a docker install to just hassio and connected the RFXCOM directly to the usb port on the device. But RFXCOM is already configured with Ser2net. Is it configurable by config file somewhere?
I edited core.config_enteties to have a device entry instead of the server / port information.
I have a different issue controlling blinds with RFXTRX. I’m endeavouring to migrate control of 3 Motolux blind motors from an Indigo system to Home Assistant (using the same RFXtrx device). The blinds are controlled by one remote control (by selecting different unit codes), and this functionality is working fine in the Indigo implementation.
Home assistant has correctly auto-recognised the protocol (BlindsT3 / A-OK AC114) and created a device. But evidently unit codes are being ignored: it is controlling only the device that has unit code 1 (and is updating the state of that HA device regardless of what unit code is being sent).
There is no-where in the UI to define the unit code…any other way to create duplicate devices sending different unit codes??
Edit: The UI does report the unit code as ‘1’… in spite of which unit code is sent. I always see
‘blindst3_a_ok_ac114_24f505_1’
where i assume the final 1 is meant to be unit code.
Doing more investigation, the RFXtrx guide states that Motoblux blinds are fully supported only for transmit. Evidently that is because the unit code is not decoded correctly on reception (extensive discussion of this on the Indigo forum).
So auto-creation isn’t going to work except for code 1, and the UI doesn’t allow this to be manually configured, which is annoying.
But I’ve managed to create devices correctly by tweaking the configuration string.