Amazon Dash Button - Stops working after one or two days

Hi openHAB community,

I need your help. I’m using openHAB 2.0 and I’ve installed the Amazon Dash Button binding (based on master branch 06/12/2017). The first day everything works as expected. But then the button stops working. Does anyone have an idea what the reason might be?

I’ve installed openHAB on a Raspberry Pi 3.

Logs:

2017-05-10 20:20:55.264 [WARN ] [org.pcap4j.util.PropertiesLoader    ] - [org/pcap4j/pcap4j.properties] Could not get value by org.pcap4j.af.inet, use default value: null
2017-05-10 20:20:55.265 [WARN ] [org.pcap4j.util.PropertiesLoader    ] - [org/pcap4j/pcap4j.properties] Could not get value by org.pcap4j.af.inet6, use default value: null
2017-05-10 20:20:55.271 [WARN ] [org.pcap4j.util.PropertiesLoader    ] - [org/pcap4j/pcap4j.properties] Could not get value by org.pcap4j.af.packet, use default value: null
2017-05-10 20:20:55.272 [WARN ] [org.pcap4j.util.PropertiesLoader    ] - [org/pcap4j/pcap4j.properties] Could not get value by org.pcap4j.af.link, use default value: null
2017-05-10 20:20:55.332 [INFO ] [org.pcap4j.core.Pcaps               ] - 7 NIF(s) found.
2017-05-10 20:20:55.441 [WARN ] [org.pcap4j.util.PropertiesLoader    ] - [org/pcap4j/pcap4j.properties] Could not get value by org.pcap4j.dlt.raw, use default value: null
2017-05-10 20:20:55.461 [INFO ] [org.pcap4j.core.PcapHandle          ] - Starting loop.
2017-05-10 20:21:18.484 [INFO ] [cap4j.packet.factory.PacketFactories] - Succeeded in FactoryBinder.getInstance()
2017-05-11 07:00:52.023 [INFO ] [org.pcap4j.core.PcapHandle          ] - Closed.

Cap settings:

[13:13:55] openhabian@openHABianPi:/var/log/openhab2$ sudo getcap `realpath /usr/bin/java`
/usr/lib/jvm/zulu-embedded-8-armhf/bin/java = cap_net_admin,cap_net_raw+eip cap_net_bind_service+ep

Thing configuration

{
  "statusInfo": {
    "status": "ONLINE",
    "statusDetail": "NONE"
  },
  "label": "Dash Button",
  "configuration": {
    "packetInterval": 5000,
    "macAddress": "88:71:e5:3c:XX:XX",
    "pcapNetworkInterfaceName": "wlan0"
  },
  "properties": {},
  "UID": "amazondashbutton:dashbutton:88-71-e5-3c-XX-XX",
  "thingTypeUID": "amazondashbutton:dashbutton",
  "channels": [
    {
      "linkedItems": [],
      "uid": "amazondashbutton:dashbutton:88-71-e5-3c-XX-XX:press",
      "id": "press",
      "channelTypeUID": "system:trigger",
      "kind": "TRIGGER",
      "label": "Amazon Dash Button press",
      "description": "Amazon Dash Button press",
      "defaultTags": [],
      "properties": {},
      "configuration": {}
    }
  ],
  "location": "Kammer"
}

Thanks for your help,
Jonas

I also have a hard time getting my Amazon Dash button work.
I’m using it along with Network binding, so I’m granting the following capabilities:

sudo setcap cap_net_raw,cap_net_admin=eip `realpath /usr/bin/java`

My Dash button is constantly in the INITIALIZING state.
I have latest distro (#914)

I’ve got the same issue here too. Is there a fix for this?

Have you tried manually stopping and restarting the dash button binding from the karaf console?

I have a similar problem whenever I reboot my raspberry pi, 99% of the time it’s stuck in INITIALIZING. Restarting OH usually sorts it out, but isn’t 100%. Using karaf console always seems to get it going for me.

I stumbled upon this problem as well. Unfortunately I won’t find the time to look into this issue in the near future.

Thanks. I’ve done both restart the RPi and the bundle through Karaf to no avail. Still won’t change its status. how can I diagnose this further?

Major PITA, I’ve literally spent days troubleshooting through all sorts of scenarios :frowning:
When I first set them up all was working just fine, and if I restore a full backup of my openhab setup it works all fine like that day.
The thing that seems to break it most reliably is restarting the system (an Orange Pi Zero running Armbian). Restarting OH usually works fine, but after rebooting the system (even if OH was already shut down before initiating reboot) there’s a 95% chance that some of the dash buttons will be stuck in “Initializing” afterwards.