search

va7eex / docker-rtl433

merbanan/rtl_433 in docker
MIT License
2 stars 0 forks source link

No supported devices found. #1

Open ghost opened 4 years ago

ghost commented 4 years ago

Hello,

Thanks for the image. The following error occurs when I run sudo docker run va7eex/rtl433:latest-mqtt :

rtl_433 version 19.08-145-g81ce034 branch master at 202001170105 inputs file rtl_tcp RTL-SDR Use -h for usage help and see https://triq.org/ for documentation. Trying conf file at "rtl_433.conf"... Trying conf file at "/root/.config/rtl_433/rtl_433.conf"... Trying conf file at "/usr/local/etc/rtl_433/rtl_433.conf"... Trying conf file at "/etc/rtl_433/rtl_433.conf"... Publishing MQTT data to mqtt-broker port 1883 Publishing device info to MQTT topic "sensors/rtl_433/[model:]/[id:0]". Registered 116 out of 145 device decoding protocols [ 1-4 8 11-12 15-17 19-21 23 25-26 29-36 38-60 63 67-71 73-100 102-104 108-116 119 121 124-128 131-145 ] No supported devices found.

What can I do ?

Running Solus with the dongle attached

va7eex commented 4 years ago

Hi,

Are you running your container as --privileged?

On Sun, Feb 16, 2020, 4:29 AM ashtez notifications@github.com wrote:

Hello,

Thanks for the image. The following error occurs when I run sudo docker run va7eex/rtl433:latest-mqtt :

rtl_433 version 19.08-145-g81ce034 branch master at 202001170105 inputs file rtl_tcp RTL-SDR Use -h for usage help and see https://triq.org/ for documentation. Trying conf file at "rtl_433.conf"... Trying conf file at "/root/.config/rtl_433/rtl_433.conf"... Trying conf file at "/usr/local/etc/rtl_433/rtl_433.conf"... Trying conf file at "/etc/rtl_433/rtl_433.conf"... Publishing MQTT data to mqtt-broker port 1883 Publishing device info to MQTT topic "sensors/rtl_433/[model:]/[id:0]". Registered 116 out of 145 device decoding protocols [ 1-4 8 11-12 15-17 19-21 23 25-26 29-36 38-60 63 67-71 73-100 102-104 108-116 119 121 124-128 131-145 ] No supported devices found.

What can I do ?

Running Solus with the dongle attached

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/va7eex/docker-rtl433/issues/1?email_source=notifications&email_token=AGDAFBZKGSN67JPQAZNUCT3RDEWR7A5CNFSM4KWCXLM2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IN25GKQ, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGDAFBZRN3RHWFJRAPFM5QLRDEWR7ANCNFSM4KWCXLMQ .

ghost commented 4 years ago

Yes

va7eex commented 4 years ago

Please try docker run --privileged va7eex/rtl433:latest-mqtt or docker run --device "/dev/bus/usb/00x/00y:/dev/bus/usb/001/002" va7eex/rtl433:latest-mqtt where 00x and 00y can be found by lsusb. An example output of lsusb would be Bus 00x Device 00y: ID abcd:1234 Realtek Semiconductor Corp. RTL2838 DVB-T

You should be greeted with a new error MQTT connect error:, this is requires setting the environment vars for your preferred MQTT broker.

ghost commented 4 years ago

Forget it, I can't, for the love of god, get it to work. Now I get this message :

docker run --privileged va7eex/rtl433:latest-mqtt

/bin/sh: /usr/src/entrypoint.sh: Permission denied

va7eex commented 4 years ago

Are you cloning this repo or downloading from the docker hub? Either way that message shouldn't be happening and I'll have to investigate it.

On Sat, Apr 18, 2020, 4:49 AM ashtez notifications@github.com wrote:

Forget it, I can't, for the love of god, get it to work. Now I get this message :

docker run --privileged va7eex/rtl433:latest-mqtt

/bin/sh: /usr/src/entrypoint.sh: Permission denied

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/va7eex/docker-rtl433/issues/1#issuecomment-615850563, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGDAFB3KG5VYKKI6EC67OQDRNGHUJANCNFSM4KWCXLMQ .

ghost commented 4 years ago

it downloads it from docker hub

va7eex commented 4 years ago

Just confirmed this myself, that'll teach me for pushing things and assuming it works.

Expect a fix pushed to docker hub sometime tonight or tomorrow.

On Sat, Apr 18, 2020, 12:25 PM ashtez notifications@github.com wrote:

it downloads it from docker hub

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/va7eex/docker-rtl433/issues/1#issuecomment-615931596, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGDAFB3MCFDXUQXE4WM3BA3RNH5BFANCNFSM4KWCXLMQ .

ghost commented 4 years ago

Funny. Thanks !

va7eex commented 4 years ago

Through some amount of struggling with a phone based SSH terminal I've pushed an update to Dockerfile-mqtt, you can either build it yourself or wait.

It should be noted that almost all the issues related to this docker image are regarding changing the timezone

On Sat, Apr 18, 2020, 12:57 PM ashtez notifications@github.com wrote:

Funny. Thanks !

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/va7eex/docker-rtl433/issues/1#issuecomment-615936010, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGDAFB6XCHL6SIQOP4P5QT3RNIA3XANCNFSM4KWCXLMQ .

ghost commented 4 years ago

So I built it myself (will have to anyway):

FROM va7eex/rtl433:latest ENV MQTT_IP=broker.mqttdashboard.com ENV MQTT_PORT=1883 ENV UNITS=si ENV TZ=Etc/UTC

#ENTRYPOINT rtl_433 -f 868M -R 119

ENTRYPOINT rtl_433 -f 868M -C $UNITS -R 119 -F mqtt://$MQTT_IP:$MQTT_PORT,retain=0,devices=sensors/rtl_433/z765dkkhd

Now the #ENTRYPOINT rtl_433 -f 868M -R 119 works just fine, but the MQTT line doesn't (tho this is not, to my knowledge, related to docker).