The device is working great with rfxmnger. But in hass iv got: ERROR (MainThread) [homeassistant.components.rfxtrx] Connection timeout: failed to receive response from RFXtrx device
When the hass container is started i cant connect with rfxmnger anymore, so hass i using the tcp poort but is failing to communicate with the rfxcom.
Seeing the same issue with a similar configuration. RFXtrx433 is plugged into a raspberry pi running ser2net. When HA OS is booted, often it hangs on RFXTRX with the following error.
ERROR (MainThread) [homeassistant.components.rfxtrx] Connection timeout: failed to receive response from RFXtrx device
Restarting core resolves the problem every time. It’s like the RFXCOM integration is started before the HA OS network is fully active.
I finaly have a reliable solution now…
Rfxcom is on the pi and controlled with node-red. Node-red connects through the serial port with the rfxcom and converts the rfstuff to mqtt.
Changed from Home Assistant OS running in a virtual machine to Home Assistant Core only (No Supervisor) running in a Docker in an LXC container on a Proxmox PXE server and it appears to have resolved the issue. Can now restart the LXC container and RFXCOM starts fine. More responsive and it was very easy to do, just copy over the config folder. Sounds like this would be more complicated than running a recommended configuration but i’ts actually very simple, wish I would have known this was an option.
Highly recommend this configuration for anyone looking for a little more access to the OS, a more performant system and is comfortable with doing a little configuration in linux.
