hassio_addons icon indicating copy to clipboard operation
hassio_addons copied to clipboard

Coexistance of acurite2mqtt with WMBUS reader for the same SDR

Open convicte opened this issue 3 years ago • 4 comments

This is not really an issue, but more an inquiry regarding the ability to integrate this project, with WMBUSMeters , using a single SDR in Home Assistant.

So far I was able to run one or the other using the same SDR and each works just fine. I am a long term user of this add-on and very new to WMBUSMeters, so I am not sure if there are some hard limitations which cannot be overcome.

Best case scenario would be to run, both the WMBUS and this add-on, in parallel, where one would be able to decode both signals at the same time, or they would share the signals received from the devices on the 433 or 868Mhz bands.

Looking forward to everyone's thoughts.

convicte avatar Feb 20 '22 22:02 convicte

I dont know, I will have to look at that. Thea reality is as long as the device is supported but the rtf_433 project it will work with this add-on. The only gatekeeper is the autodiscovery part. Its defined to just send certain data to Home Assistant, but anything the SDR picks up that it can read goes to MQTT.

thejeffreystone avatar Feb 26 '22 01:02 thejeffreystone

Any ideas??

convicte avatar Jun 26 '22 00:06 convicte

I am actually running into even more problems, because even with two independent SDRs the acurite2mqtt clashes with it often (usb_claim_interface error -6) and either one or both lose connection to their respective ports.

Even worse, they typically take down the Zigbee dongle and Modbus dongle in the process. Getting all of them disconnected, acurite2mqtt disabled and re-enabled only when everything is started resolved the issue, but this requires crawling in my attic, which I am not a big fan off.

Any help would be greatly appreciated!!

convicte avatar Jul 13 '22 23:07 convicte

Still dealing with issues where this addon tries to take over an RTL adapter used by another addon, while it has one all to itself. Is there any way to deal with this natively - assing the device to the addon?

Another option would be to delay start, maybe??

convicte avatar Aug 04 '22 20:08 convicte