thejeffreystone
commented
1 year ago Do you have the USB dongle in an extension cable? I think plugging it in directly sometimes causes issues like this.
Open hartman44 opened 2 years ago
thejeffreystone
commented
1 year ago Do you have the USB dongle in an extension cable? I think plugging it in directly sometimes causes issues like this.
hartman44
commented
1 year ago Yes, I have had it plugged into an extension USB cable from day one.
thejeffreystone
commented
1 year ago So after doing some digging this error has to do with the hardware. Something happening with the connection between the device and the usb stick.
I will have to see if there is a way for me to catch these and then auto restart the add-on. But unfortunately my solution is only going to be trying to recover from this state since I cannot control or see the connection between the stick and the device.
hartman44
commented
1 year ago I think I narrowed it down to a conflict with rtlamr2mqtt which also uses the RTL Dongle. Not sure how to fix it but if I turn off rtlamr2mqtt your add-on works fine. I just ran your new update and have disabled my auto restart automation workaround to see what happens.
I am getting strange behavior where this will work for about two minutes and then error out. If I restart the add-on it starts working again for a few minutes and then erroring out again.
My setup it is running HA on a Virtual Box on a Windows 11 machine. I am also using my RTL Dongle with rtlamr2mqtt. Not sure if this is causing a conflict. Would like some insight on whether I can get this running reliably, thanks.
Config:
mqtt_host: XXXX mqtt_port: 1883 mqtt_user: XXXX mqtt_password: XXXX mqtt_topic: rtl_433 mqtt_retain: 'true' protocol: '-R 11 -R 40 -R 41 -R 55 -R 74' whitelist_enable: true whitelist: '11877' expire_after: 0 units: customary discovery_prefix: homeassistant discovery_interval: 600 debug: false