Skip to content
Branch: master
Find file History
Latest commit b5749ef Apr 9, 2019
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
Dockerfile Update Dockerfile to comply with hass.io 0.64 build Oct 7, 2017
README.md Revert "Updated to support hass.io add-in options" Aug 29, 2017
config.json Update config.json Apr 9, 2019

README.md

Dasher!!

All credit to the author of Dasher: https://github.com/maddox/dasher

Dasher is a simple way to bridge your Amazon Dash buttons to HTTP services.

Do you have a Home Automation service set up like Home Assistant, openHab, or maybe a SmartThings hub? Using Dasher, you can easily command them to do something whenever your Dash button is pressed.

This of course goes for anything you can reach via HTTP. That includes IFTTT by way of the Maker channel 🤘

How it works

It's pretty simple. Press a button and an HTTP request is made or local command is ran. That's it.

You configure your Dash button(s) via config.json. You add its network address and either a url, an http method, and optionally a content body and headers or a local command to execute.

When Dasher starts, it will listen for your button being pressed. Once it sees it, it will then make the HTTP request or run the command that you defined for it in your config.

Configuration

You define your buttons via the config.json file. It's a simple JSON file that holds an array of buttons.

Your config file should be placed in the hassio config dir in a subdir called dasher i.e.

.../config/dasher/config.json

Here's an example. Note that button two "Party Time" is a home assistant example...

{"buttons":[
  {
    "name": "Notify",
    "address": "43:02:dc:b2:ab:23",
    "interface": "en0",
    "timeout": "60000",
    "protocol": "udp",
    "url": "https://maker.ifttt.com/trigger/Notify/with/key/5212ssx2k23k2k",
    "method": "POST",
    "json": true,
    "body": {"value1": "any value", "value2": "another value", "value3": "wow, even more value"}
  },
  {
    "name": "Party Time",
    "address": "d8:02:dc:98:63:49",
    "url": "http://192.168.1.55:8123/api/services/scene/turn_on",
    "method": "POST",
    "headers": {"authorization": "your_password"},
    "json": true,
    "body": {"entity_id": "scene.party_time"},
    "formData": {
      "var1":"val1",
      "var2":" val2"
    }
  },
  {
    "name": "Start Cooking Playlist",
    "address": "66:a0:dc:98:d2:63",
    "url": "http://192.168.1.55:8181/playlists/cooking/play",
    "method": "PUT"
  },
  {
    "name": "Debug Dash Button",
    "address": "41:02:dc:b2:ab:23",
    "debug": true
  },
  {
    "name": "Command Exec Button",
    "address": "41:02:dc:b2:10:12",
    "cmd": "/home/user/dash_button.sh"
  }  
]}

Another example:

{"buttons":[
  {
    "name": "Lounge Lights",
    "address": "50:f5:da:07:e1:fa",
    "interface": "ens160",
    "url": "http://hassio:8123/api/services/light/toggle",
    "method": "POST",
    "headers": {"x-ha-access": "password"},
    "json": true,
    "body": {"entity_id": "light.living_room"}
  },
  {
    "name": "Downstairs Lights",
    "address": "44:65:0d:2e:7a:11",
    "interface": "ens160",
    "url": "http://hassio:8123/api/services/light/turn_off",
    "method": "POST",
    "headers": {"x-ha-access": "password"},
    "json": true,
    "body": {"entity_id": "group.downstairs_switches"}
  },
  {
    "name": "Downstairs Switches",
    "address": "44:65:0d:2e:7a:11",
    "interface": "ens160",
    "url": "http://hassio:8123/api/services/switch/turn_off",
    "method": "POST",
    "headers": {"x-ha-access": "password"},
    "json": true,
    "body": {"entity_id": "group.downstairs_switches"}
  }
]}

Note that the interface specified is the network interface on your hassio host. Often eth0.

Buttons take up to 13 options.

  • name - Optionally give the button action a name.
  • address - The MAC address of the button.
  • interface - Optionally listen for the button on a specific network interface. (enX on OS X and ethX on Linux)
  • timeout - Optionally set the time required between button press detections (if multiple pressese are detected) in milliseconds. Default is 5000.
  • protocol - Optionally set the protocol for your Dash button. Options are udp, arp, and all. Default listens to arp. The "newer" JK29LP button from ~Q2 2016+ tends to use udp.
  • url - The URL that will be requested.
  • method - The HTTP method of the request.
  • headers - Optional headers to use in the request.
  • json - Optionally declare the content body as being JSON in the request.
  • body - Optionally provide a content-body that will be sent with the request.
  • formData - Optionally add formData that will be sent with the request.
  • debug - Used for testing button presses and will -not- perform a request.
  • cmd - Used to run a local command rather than an HTTP request. Setting this will override the url parameter.

Setting and using these values should be enough to cover almost every kind of request you need to make.

Protips

Here are few protips about Dash buttons that will help you plan how to use them.

  • Dash buttons take ~5 seconds to trigger your action.
  • Use DHCP Reservation on your Dash button to lower the latency from ~5s to ~1s.
  • Dash buttons are discrete buttons. There is no on or off. They just do a single command.
  • Dash buttons can not be used for another ~10 seconds after they've been pressed.
  • If your Dash button is using udp, specify it in the button config.
  • Listening over wifi is unreliable. I highly recommend using ethernet, especially on Raspberry Pi

Dash buttons should be used to trigger specific things. I.E. a scene in your home automation, as a way to turn everything off in your house, or as a simple counter.

Setup

You'll want to set up your Dash buttons as well as Dasher.

Dash button

Setting up your Dash button is as simple as following the instructions provided by Amazon EXCEPT FOR THE LAST STEP. Just follow the instructions to set it up in their mobile app. When you get to the step where it asks you to pick which product you want to map it to, just quit the setup process.

The button will be set up and available on your network.

Find Dash Button

Once your Dash button is set up and on your network, you need to determine its MAC address. Because Dasher is running in a Docker container, scanning for Dash buttons requires you to open a shell in the container. You can achieve this by opening a shell on the Hass.io host, and then running:

docker ps

Find the Dasher container's name -e.g. addon_dasher

Then open a bash shell on the container with:

docker exec -i -t addon_dasher /bin/bash

You can also use a Docker management tool such as Portainer https://github.com/portainer/portainer.

Check that your dir is /root/dasher then run this:

node node_modules/node-dash-button/bin/findbutton

Click your Dash button and the script will listen for your device. Dash buttons should appear as manufactured by 'Amazon Technologies Inc.'. Once you have its MAC address you will be able to configure it in Dasher by modifying config.json after installing Dasher.

Then create a config.json in the hass.io config dir config/dasher to set up your Dash buttons. Use the example to help you. If you just want to test the button press, use the debug button example with the MAC address you found running script/find_button.

Contributions

  • fork
  • create a feature branch
  • open a Pull Request
You can’t perform that action at this time.