New plugin pimatic-amazing-dash-button
Good job! I built something similar with ESP-01 (the bottom chart even if PIR is so interesting) and modified your module for its MAC address. Works also auto discovery 
If the button is turned off, the consumption is 12 µA (without red LED).
But the reaction time is quite long. About 2 seconds.But definitely faster than the ping plugin.
What times achieves Amazon dash button with this plugin?
Not thinking about the universal module for detecting MAC addresses? I think that would be used.
Pimatic = Smart Home
@wutu said in New plugin pimatic-amazing-dash-button:
What times achieves Amazon dash button with this plugin?
It varies between 1 and 3 seconds. I think the delay is mainly arising from the time required for the dash-button to reconnect to the WFi network.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
Has anyone tried to make multiple functions with one button?
1 press - dim light
2 press - turn off lights
pimatic + MySensors + Homeduino + z-way
https://github.com/n3roGit/MySensors_n3ro
@n3ro I don’t think thjis will work because it will always execute the one-press rule, too. And i don’t think you can say
when DashButton is closed two times then do somethingpimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten
@michbeck100 @n3ro It is also inpractical as two immediate button presses won’t be recognized. For the second butto press you have to wait until the status LED stops flashing red. In other words, you’ll have to wait for about 7-8 seconds until you can press the button again to trigger an “contact closed” event…
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
@mwittig hmmm 
pimatic + MySensors + Homeduino + z-way
https://github.com/n3roGit/MySensors_n3ro
@n3ro you’ll probably have to order one button per action…
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten
For clarification, the waiting time of 7-8 seconds is due to the design of the dash-button.
If you roll your own button using an ESP8266, for example, you may be able to build a decent smart button with lower waiting time (~ 3 secs) and the ability to count button presses. The following project looks interesting to me and seems to have the “count button presses” feature. https://www.hackster.io/iboboc/smartbutton-pro-06ce5d
Another interesting route to follow is the ongoing firmware hacking for dash-buttons. However, I think it is tricky to solder the wires needed for programming. http://hackaday.com/2015/08/12/amazon-dash-hack-it-to-run-your-own-code/
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
It’s working like a charm, thanks!
Hmm… I can’t get it to work - I stopped the setup before selecting a product but the dash button doesn’t flash white, only red and I can’t auto-discover it. Maybe Amazon changed the process in the app to make it mandatory to select a product before they update the button with the WiFi settings? That’s what I would do if I would want to prevent those kinds of hacks…
@GuybrushMR80 said in New plugin pimatic-amazing-dash-button:
Hmm… I can’t get it to work - I stopped the setup before selecting a product but the dash button doesn’t flash white, only red and I can’t auto-discover it. Maybe Amazon changed the process in the app to make it mandatory to select a product before they update the button with the WiFi settings? That’s what I would do if I would want to prevent those kinds of hacks…
I think something goes wrong with the prozedure. Have you look for an Update of the Amazon App? I have to update my Underground App (Download it from https://amazon.de/app )before I can get the Dash-Button to work. That is 2 days ago.
I think to Change the Prozess the have to Change the Firmware of the button.
I just realized that this might be more a problem with pimatic: I can’t seem to find the class “AmazingDashButton” when trying to add a new device manually via the webinterface.
EDIT: There was a Homduino update available - now that I did update, it works!
@GuybrushMR80 said in New plugin pimatic-amazing-dash-button:
There was a Homduino update available
You probably forgot to restart pimatic after the previous Plugin installation.
Maybe Amazon changed the process in the app to make it mandatory to select a product before they update the button with the WiFi settings? That’s what I would do if I would want to prevent those kinds of hacks…
I don’t think so. I think it is a bug not a feature. It is true here have been serveral App updates, recently. For this reason I also tried again to register my dash button again using the iPhone App which was an almost complete fail. To make it clear the failure occurs before one can select a product.
Basically, I got the same errors trying all three configuration modes provided on iPhone and none of them succeeded. However, eventhough the setup failed my dash still connects to the WiFi network. Maybe this is because it falls back to the previous configuration, I don’t know. When I press the putton it starts slowly blinking white which means it is connected. It will turn to blinking red after a few seconds. I’ll try to get hold of an Android device and try later with the Underground App.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
I have two dash-buttons. The first has the autodiscover function good recognized but by the second it has get a wrong mac-address.
I have changed it manually and the second button works also.
@V1per said in New plugin pimatic-amazing-dash-button:
the second it has get a wrong mac-address
Can you please let me know the first three bytes (6 digits) of the MAC address?
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
Published V0.9.6
* Added missing MAC vendor id
If you like this plugin, please consider ★ starring the project on github.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
@mwittig said in New plugin pimatic-amazing-dash-button:
@V1per said in New plugin pimatic-amazing-dash-button:
the second it has get a wrong mac-address
Can you please let me know the first three bytes (6 digits) of the MAC address?
It is
AC:63:BE:
@V1per said in New plugin pimatic-amazing-dash-button:
It is AC:63:BE:
Thanks, but this should also be found during auto-discovery. It’s on the list vendor ids filtered during autodiscovery.
Amazon has 10 vendor ids assigned, btw.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
Maybe it founds one of my Amazon-Box or Amazon-Stick?
@V1per said in New plugin pimatic-amazing-dash-button:
Maybe it founds one of my Amazon-Box or Amazon-Stick
Yes, this may happen, as there is no information about which of the 10 vendor ids assigned to Amazon are used for dash-buttons. So, I am filtering for all of them and this will also find other Amazon gear in your network. I may find measures to detect Amazon boxes and sticks to filter them out - maybe be checking for some open port - well, I need to look into this.
EDIT: Possibly boxes and sticks listen on ports 8008 and 8009 for Chromecast.
EDIT2: http://fiquett.com/2013/07/chromecast-traffic-sniffing/
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law