RFXtrx devices is unavailable after reboot

I have enabled the “Enable newly added entities” function and press a button on my NEXA remote. Everything works without problems. I am using that device to learn another NEXA switch and that is also working correctly.

The problem is when I reboot HA all devices are unavailable until I use my physical remote and press the button.

Which version of Home Assistant are you using?

version 0.116.0

Ah, now I remember. It’s a bug in the integration. You can work around it by adding the event code of the remote to your yaml config. To do so, press the remote button, click the switch entity and look at the state attribute. Copy and paste this event code under devices in your yaml.

It’s not trivial to make a small fix for it. Code has already been merged for next release to be able to fully configure rfxtrx through UI, which will also fix this.

1 Like

Ok thanks for your answer!

Another question - it’s not possible to delete a device (without remove whole integration)

Technically, yes, but you’d have to go into ./storage folder and remove the devices from core.device_registry. Not something user friendly.

In next release, there will be an option in UI to delete devices.

1 Like

Perfect! Looking forward!

Which release is that ? I am on 0.116.2 and it still has this problem…

It will be in 0.117. It just missed 0.116 and because it’s part of a big change it won’t go in a maintenance release.

Maybe a heads up, an additional issue was found which is fixed in the same release, most likely first time you boot after upgrading it will still show unavailable. Once the first event is received internally it will write it to the config data and after that it should work.

1 Like

Thanks for your quick reply. Now the question is of course: when is 0.117 due ??

I don’t know the date, release cycles are approximately 3-4 weeks. It first needs to go in beta.

0.118.5 now, and the problem with rfxtrx devices unavailable after reboot is always there…

1 Like