Repository: Dasher; RTL433 to MQTT Bridge; Ink printer ink reporting

hijinx · October 13, 2017, 11:01pm

You’re welcome!

traslin · October 19, 2017, 4:02am

How can I modify the etc/hosts file that dasher uses? I modified the main etc/hosts file of the OS, but that doesn’t seem to effect dasher. I’m using https and duckdns, so I need to modify the hosts file to have the web address resolve to a localhost. Thanks.

EDIT - I’m not sure if this is the best way to fix it, but I got around the issue using the Dnsmasq addon, which allowed me to have the duckdns address resolve as the local ip of my hassio box. I’m afraid that using Dnsmasq as my initial DNS server might slow things down, but I’ll try it like this for a while to see how it goes.

hijinx · October 19, 2017, 8:13am

My suggestion was going to be to get it working via DNS.
The DNSmasq addon would have been my 1st suggestion (although I have no experience with it personally).

Is there a reason why you cannot resolve your own domain to your external IP and configure dasher with that?
Or configure dasher with internal IP?
Both work for me. I guess if your router is not supporting hairpin NAT then the 1st would not work.

With docker you can pass arguments to add hosts to etc hosts on run time like this:
--add-host github.com:192.30.253.113
But I’m not sure if hassio add-ons support this arg. I didn’t see anywhere in config to set it, and it probably because working DNS is expected.

traslin · October 19, 2017, 7:20pm

Configuring with an internal IP didn’t work because of https. Dasher throws an error because the ssl certificate does not match the web page.

I’m not sure what resolving my own domain to the external IP refers to. If you mean simply using the external IP address in the dasher configuration, for whatever reason it does not resolve on my network and simply times out, so I guess my router (Google Wifi) doesn’t support hairpin NAT. I’ve noticed the same behavior on my Windows PC and had already updated my host files on Windows machines as necessary.

DNS seems to be working well though, and I haven’t noticed any slowdown from adding the extra hop. Thanks for the response.

harry1 · October 29, 2017, 7:46pm

Please help

hijinx · October 29, 2017, 7:49pm

Maybe use the IP address of your hassio server instead of hassio.local?

harry1 · October 29, 2017, 7:53pm

ok I’ll try thanks

harry1 · October 29, 2017, 7:55pm

IT WORKED!!!
Your a genius thank you

hijinx · October 29, 2017, 7:57pm

No problem!

hijinx · October 29, 2017, 11:00pm

I’ve just updated my repo to include an add-on that uses rtl_433 to provide a 433MHz RF to MQTT bridge.
This allows use of a cheap USB DVB-T tuner (based on RTL chipset) to be re-purposed as a software defined radio… in this case specifically to sniff and decode 433MHz signals.
Currently 93 protocols are supported.

Addon details here:

rtl_433 details, including supported protocol list here:

Note that the addon requires a subdirectory to be created in your hassio config dir that will include the script that executes rtl_433. This is to provide flexibility for the numerous features that rtl_433 provides, and any other flexibility that script provides - e.g.
e.g.

alternative frequencies/frequency hopping
using multiple protocols
parsing/transforming JSON before publishing to topic etc

This addon currently builds locally.

Feedback welcome.

motoolfan · November 2, 2017, 11:55am

I’m getting this error when trying to start it,

starting version 3.2.2
/rtl2mqtt.sh: line 1: syntax error: unexpected newline

Btw, Thanks for making this addon as well as Dasher! Very useful

hijinx · November 2, 2017, 12:00pm

Did you copy the rtl2mqtt.sh into hassio config dir per the readme step 3?

Copy rtl2mqtt.sh to your hass.io config dir in a subdir called rtl4332mqtt. i.e. …/config/rtl4332mqtt/rtl2mqtt.sh This allows you to edit the start script if you need to make any changes

The reason for this is that rtl_433 is flexible and I saw lots of ways people are using it.
e.g. maybe you want to use a different freq (e.g. Honeywell @ 345mhz) or you want to hop frequencies, or you want to use two protocols etc.
So I decided to keep the script outside of the docker container so people can modify it as needed.

hijinx · November 2, 2017, 12:03pm

To grab the script easily you can copy it from here:

https://raw.githubusercontent.com/james-fry/hassio-addons/master/rtl4332mqtt/rtl2mqtt.sh

motoolfan · November 2, 2017, 12:05pm

Never mind, the link to the file worked. sorry bout that.

starting version 3.2.2
Starting RTL_433 with parameters:
MQTT Host =
MQTT User =
MQTT Password =
MQTT Topic = homeassistant/sensor/currentcost
RTL_433 Protocol = 44
Registering protocol [1] “CurrentCost Current Sensor”
Registered 1 out of 93 device decoding protocols
No supported devices found.

hijinx · November 2, 2017, 1:06pm

This is where is gets a bit harder to debug…
Are you running hassio on resinos - ie from the Raspberry Pi image?
If so case I’m not sure how/if I can help debug as I am running hassio on ubuntu.
Its possible that resinos does not have the necessary RTL DVB drivers/kernel modules.

If you are running on a standard linux you can check that a device was found with lsusb.
You should see “Realtek Semiconductor Corp. RTL2838 DVB-T”
e.g.:

james@hassio:~$ lsusb
Bus 001 Device 007: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

With hassio resinos/image you can check this with the terminal addon from here:

In the terminal run lsusb:

➜  / lsusb
Bus 001 Device 007: ID 0bda:2838
Bus 002 Device 002: ID 0e0f:0003
Bus 002 Device 003: ID 0e0f:0002
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001

It’s the device ID 0bda:2838 that you’re looking for…
https://www.linuxtv.org/wiki/index.php/RealTek_RTL2832U

Not sure how far this gets us with debugging, but it’s a start.
Could be that the USB device ID will still be shown even if the kernel mod/drivers are not loaded. I don’t know I’m afraid.

If you are running rpi image maybe there are some others on in the community here that can help further?

motoolfan · November 2, 2017, 2:37pm

Working now

hijinx · November 2, 2017, 3:14pm

Nice!
Thanks for updating with your success…

namadori · November 5, 2017, 2:28pm

Thanks for your great job!

To share my setup: i had a RTL-capable usb tuner (https://www.amazon.it/gp/product/B013Q94CT6) and got from AliExpress a cheap 433MHz temperature and humidity sensor.

The configuration was quick and easy

{
  "mqtt_host": "192.168.2.33",
  "mqtt_user": "homeassistant",
  "mqtt_password": "xxxxxxxx",
  "mqtt_topic": "homeassistant/sensor/temperature",
  "protocol": 3
}

This is the received payload (got from mqtt-spy):

{"time" : "2017-11-05 15:24:28", "model" : "Prologue sensor", "id" : 5, 
"rid" : 198, "channel" : 1, "battery" : "OK", "button" : 0, 
"temperature_C" : 21.500, "humidity" : 62}

This is the sensor configuration:

  - platform: mqtt
    name: sensore_433_temperatura
    state_topic: "homeassistant/sensor/temperature"
    unit_of_measurement: "°C"
    value_template: '{{ value_json.temperature_C }}'
  - platform: mqtt
    name: sensore_433_umidita
    state_topic: "homeassistant/sensor/temperature"
    unit_of_measurement: "%"
    value_template: '{{ value_json.humidity }}'

The final result:

hijinx · November 5, 2017, 3:24pm

Glad it’s working for you! Thanks for the feedback

hgelpke · November 12, 2017, 5:03pm

Dasher isn’t auto starting despite being told to do so.

I have it configured properly and it starts/works fine when I hit start. Just not auto starting for some reason.