operating-system: USB ftdi_sio problem with RFXCOM
Describe the issue you are experiencing
Hi !
I can’t get my RFXCOM to work, I get the following error message:
Look like this issue : https://github.com/home-assistant/operating-system/issues/1800
I use 4 USB devices :
- RFXCOM RFXrtx433
- Bluetooth SENA UD-100
- Itead Sonoff Zigbee 3.0
- Ziblue RFPLAYER
Only the RFXCOM had problem. Tested on my Ubuntu laptop it’s working well.
I’m using a VM on a QNAP Nas TS-253D
What operating system image do you use?
ova (for Virtual Machines)
What version of Home Assistant Operating System is installed?
10.5
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
- Plug RFXCOM into HA’s usb port
- Got error message on HA startup
Anything in the Supervisor logs that might be useful for us?
Nothing usefull
Anything in the Host logs that might be useful for us?
Nothing usefull
System information
System Information
| version | core-2023.9.3 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.11.5 |
| os_name | Linux |
| os_version | 6.1.45 |
| arch | x86_64 |
| timezone | Europe/Paris |
| config_dir | /config |
Home Assistant Community Store
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| GitHub API Calls Remaining | 5000 |
| Installed Version | 1.33.0 |
| Stage | running |
| Available Repositories | 1306 |
| Downloaded Repositories | 20 |
Home Assistant Cloud
| logged_in | true |
|---|---|
| subscription_expiration | 3 janvier 2024 à 01:00 |
| relayer_connected | true |
| relayer_region | eu-central-1 |
| remote_enabled | true |
| remote_connected | true |
| alexa_enabled | true |
| google_enabled | true |
| remote_server | eu-central-1-2.ui.nabu.casa |
| certificate_status | ready |
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
Home Assistant Supervisor
| host_os | Home Assistant OS 10.5 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2023.09.2 |
| agent_version | 1.5.1 |
| docker_version | 23.0.6 |
| disk_total | 117.4 GB |
| disk_used | 7.4 GB |
| healthy | true |
| supported | true |
| board | ova |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | File editor (5.6.0), Glances (0.19.3), Home Assistant Google Drive Backup (0.111.1), Mosquitto broker (6.3.1), Node-RED (14.5.0), Terminal & SSH (9.7.1), Zigbee2MQTT (1.33.0-1), Crowdsec (1.5.2-ha1), Crowdsec Firewall Bouncer (v0.0.26) |
Dashboards
| dashboards | 1 |
|---|---|
| resources | 5 |
| views | 10 |
| mode | storage |
Recorder
| oldest_recorder_run | 24 septembre 2023 à 14:00 |
|---|---|
| current_recorder_run | 3 octobre 2023 à 14:47 |
| estimated_db_size | 359.24 MiB |
| database_engine | sqlite |
| database_version | 3.41.2 |
Xiaomi Miot Auto
| component_version | 0.7.11 |
|---|---|
| can_reach_server | ok |
| can_reach_spec | ok |
| logged_accounts | 1 |
| total_devices | 1 |
Additional information
Thank you for help
About this issue
- Original URL
- State: closed
- Created 9 months ago
- Comments: 20 (2 by maintainers)
OK thank you all for possible “workaround” and @agners for explanation
In the end, this is probably a device which is on the edge (or even violating) some USB specs. Depending on exact hardware configuration (USB host IP/type), and USB bus configuration (with/without hub(s)) things might just work, or just not work.
Home Assistant OS uses a rather vanilla upstream Linux kernel version 6.1 for the OS 10 and 11 series. So on the same hardware, with a operating system using the same kernel version, I’d expect the same issues in the end.
Possible that different kernel version lead to slightly different timing, but I don’t think there is a general fix we can come up with from HAOS side 😢
Removing the addon and reisntalling chosing the other USB connection method worked for me too!
same bug here on synology vm