rfxtrx failed to connect after restart
The problem
As described many times before the rfxcom integration refuses to start if you restart HA, claiming it can't connect to the USB device
What version of Home Assistant Core has the issue?
core-2024.9.1
What was the last working version of Home Assistant Core?
any prior to restarting
What type of installation are you running?
Home Assistant OS
Integration causing the issue
RFXCOM
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
I have isolated the cause, which may be of benefit to others .. the RFXCOM integration (and USB dongle) is INCREDIBLY sensitive to other USB devices playing in the same wavebands, in my case Zigbee and Z-wave. The integration starts fine in the absence of the dongles for those two (or even if I just shield them a lot).
Not sure HA can do much to fix it, except if other integrations can be 'silenced' while this one tries to connect. Once connected it seems to work fine.
Hey there @danielhiversen, @elupus, @robbie1221, mind taking a look at this issue as it has been labeled with an integration (rfxtrx) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of rfxtrx can trigger bot actions by commenting:
@home-assistant closeCloses the issue.@home-assistant rename Awesome new titleRenames the issue.@home-assistant reopenReopen the issue.@home-assistant unassign rfxtrxRemoves the current integration label and assignees on the issue, add the integration domain after the command.@home-assistant add-label needs-more-informationAdd a label (needs-more-information, problem in dependency, problem in custom component) to the issue.@home-assistant remove-label needs-more-informationRemove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
(message by CodeOwnersMention)
rfxtrx documentation rfxtrx source (message by IssueLinks)
Same problem here after restart.
So what other devices do you have plugged in near your rfxcom usb port, and how far to your 2.4ghz WiFi router? Seems interference is likely cause, assuming rfxcom has found the correct usb port (if it has the right device list, it probably did I think).
I'm having the same problem and no zigbee or zwave dongle.....
2024.9.2 fixed it for me
Wow....just encountered the same thing. Mind you, the RFX has always been a bit 'needy' but this is a critical one. I have just worked out I need to load my SkyConnect (Nabu Casa) Zigbee dongle AFTER the RFX one. I'm on 2024.10.3 and it still does it. I'd do some more diagnosing but I've just wasted an hour buggering about with it and it's 2:30am.
Maybe the same as this?: https://github.com/home-assistant/core/issues/133591#issuecomment-2558266376
Not exactly in my situation. I was connected via USB. In the end, I gave up and purchased a Bond bridge to use with my Somfy blinds. It works extremely well and uses Wifi and not a direct connection. Interestingly, I moved the RFX to a Raspberry Pi that I have in the shed that does all the doors and windows in there and I haven't had a problem...so far. It's all a bit weird but it seems that the Zwave and the RFX can co-exist but adding an extra dongle, causes problems. Once of these days, I'll do some more detailed/structured testing.
I think the issue is down at the usb port (usb2, 3?) hardware level, where there is some interference caused with rfxcom. Personally I am migrating a lot of zwave, and rfxcom, functions to zigbee or wifi, where the hardware is cheaper (than zwave) , and connects more reliably.
Rgds, Dave Storey
On 23 Dec 2024, 10:25, at 10:25, Lloyd Bayley @.***> wrote:
Not exactly in my situation. I was connected via USB. In the end, I gave up and purchased a Bond bridge to use with my Somfy blinds. It works extremely well and uses Wifi and not a direct connection. Interestingly, I moved the RFX to a Raspberry Pi that I have in the shed that does all the doors and windows in there and I haven't had a problem...so far. It's all a bit weird but it seems that the Zwave and the RFX can co-exist but adding an extra dongle, causes problems. Once of these days, I'll do some more detailed/structured testing.
-- Reply to this email directly or view it on GitHub: https://github.com/home-assistant/core/issues/125842#issuecomment-2559385014 You are receiving this because you authored the thread.
Message ID: @.***>
I'm not so sure it's radio interference. That should only affect signaling. Not the setup procedure.
It could be usb power limitation i suppose. Those other devices drawing too much power at setup causing issues for rfx.
Anybody tried a powered usb hub?
Yeh, I don't think it's RF interference because all was well until I added a 4th USB device in the form of a Skyconnect but I can't see how a Zigbee device would affect the setup. If I unplugged and re-plugged, it would come online most of the time. It's a weird one!
I have also issues with RFXTRX integration and zigbee2mqtt add-on. Both dongles (rfxtrx433) and Sonoff Dongle-P are connected to the system via USB. Both are connected as tty devices (so ttyUSB0 and ttyUSB1). Zigbee2mqtt is configured to use the device by id.
2025-02-17 21:32:37.928 DEBUG (SyncWorker_0) [homeassistant.components.rfxtrx] No modes defined, using device configuration
2025-02-17 21:32:37.934 DEBUG (Thread-14 (_connect)) [RFXtrx] Send: 0x0d 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
2025-02-17 21:32:38.235 DEBUG (Thread-14 (_connect)) [RFXtrx] Send: 0x0d 0x00 0x00 0x01 0x02 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
2025-02-17 21:32:43.507 DEBUG (Thread-14 (_connect)) [RFXtrx] receive failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/RFXtrx/__init__.py", line 807, in __errors
return func(instance, *args, **kargs)
File "/usr/local/lib/python3.13/site-packages/RFXtrx/__init__.py", line 845, in receive_blocking
return self._receive_packet()
~~~~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.13/site-packages/RFXtrx/__init__.py", line 854, in _receive_packet
data = self.serial.read(pkt[0]+1 - len(pkt))
File "/usr/local/lib/python3.13/site-packages/serial/serialposix.py", line 595, in read
raise SerialException(
'device reports readiness to read but returned no data '
'(device disconnected or multiple access on port?)')
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2025-02-17 21:32:43.508 INFO (Thread-14 (_connect)) [RFXtrx] Connection lost receive failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
Is there a way to specifiy the port to use for rfxtrx integration?
As far as i know you can only tell rfxcom what port to use when you set it up. Depending on how you run ha, you may be able to map the tty port to a particular device earlier, in the os?
However try starting rfxcom with zigbee stopped, or even unplugged. Try also different physical usb ports, and/or running usb extension cables, if interference maybe the issue. Since I moved my zigbee dongle 2m up the wall, away from the pc/rfxcom usb port, many problems went away (the actual rfxcom device is already 3m away, sideways).
Rgds, Dave Storey
On 17 Feb 2025, 20:39, at 20:39, "André Heuer" @.***> wrote:
andreheuer left a comment (home-assistant/core#125842)
I have also issues with RFXTRX integration and zigbee2mqtt add-on. Both dongles (rfxtrx433) and Sonoff Dongle-P are connected to the system via USB. Both are connected as tty devices (so ttyUSB0 and ttyUSB1). Zigbee2mqtt is configured to use the device by id.
2025-02-17 21:32:37.928 DEBUG (SyncWorker_0) [homeassistant.components.rfxtrx] No modes defined, using device configuration 2025-02-17 21:32:37.934 DEBUG (Thread-14 (_connect)) [RFXtrx] Send: 0x0d 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 2025-02-17 21:32:38.235 DEBUG (Thread-14 (_connect)) [RFXtrx] Send: 0x0d 0x00 0x00 0x01 0x02 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 2025-02-17 21:32:43.507 DEBUG (Thread-14 (_connect)) [RFXtrx] receive failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?) Traceback (most recent call last): File "/usr/local/lib/python3.13/site-packages/RFXtrx/__init__.py", line 807, in __errors return func(instance, *args, **kargs) File "/usr/local/lib/python3.13/site-packages/RFXtrx/__init__.py", line 845, in receive_blocking return self._receive_packet() ~~~~~~~~~~~~~~~~~~~~^^ File "/usr/local/lib/python3.13/site-packages/RFXtrx/__init__.py", line 854, in _receive_packet data = self.serial.read(pkt[0]+1 - len(pkt)) File "/usr/local/lib/python3.13/site-packages/serial/serialposix.py", line 595, in read raise SerialException( 'device reports readiness to read but returned no data ' '(device disconnected or multiple access on port?)') serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?) 2025-02-17 21:32:43.508 INFO (Thread-14 (_connect)) [RFXtrx] Connection lost receive failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)Is there a way to specifiy the port to use for rfxtrx integration?
-- Reply to this email directly or view it on GitHub: https://github.com/home-assistant/core/issues/125842#issuecomment-2664032105 You are receiving this because you authored the thread.
Message ID: @.***>
Thanks for your quick reply.
I checked the forum and found this post https://community.home-assistant.io/t/rfxtrx-change-usb-port/401710/4
So I manually edited the .storage\core.config_entries file to use the device by id (and not ttyUSB0). Now, everything works like a charm!
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.