I can’t tell, It has been happening since upgrading to HA 0.75.0 / 0.75.1
meanwhile I’ve gone back to the traditional url+password config
It works for me.
HassOS
0.75.1
api password
Maybe a stupid question but can you buy any Dash button or need it be a specific model?
Any.
AFAIK.
I wanted to just say “any” because I am 99.99999% sure but it seems that a post has to be a minimum of 10 characters so you get a little hedging 
1 Like
You can use any Dash button
There is a problem with version 0.3.1 where the layer isn’t found, how can we fix this?
Taceback (most recent call last):
File "/dasshio.py", line 27, in arp_display
mac = pkt[ARP].hwsrc.lower()
File "/usr/lib/python3.6/site-packages/scapy/packet.py", line 966, in __getitem__
raise IndexError("Layer [%s] not found" % lname)
IndexError: Layer [ARP] not found
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/dasshio.py", line 149, in <module>
count=0)
File "/usr/lib/python3.6/site-packages/scapy/sendrecv.py", line 783, in sniff
if stop_filter and stop_filter(p):
File "/dasshio.py", line 29, in arp_display
mac = pkt[Ether].src.lower()
File "/usr/lib/python3.6/site-packages/scapy/packet.py", line 966, in __getitem__
raise IndexError("Layer [%s] not found" % lname)
IndexError: Layer [Ether] not found
1 Like
Hello there.
Is it possible to manually install Dasshio (not as a third party addon)?. I made a manual installation of Home Assistant so I don’t have the addons interface to install it.
For those who are having the “Layer [ARP] not found” and “Layer [Ether] not found” issue, I’ve found the cause and made a Dasshio fork with a temporary kludge fix. All the details of the issue and the repository that you can use as a temporary workaround can be found in the issue I raised for it here:
2 Likes
Working just fineee
1 Like
Works great! Now just a reminder for when the buttons go on sale, buy the Amazon Generic Labelled ones (like Amazon Batteries) 'cause the label is white and can be covered easily and with reasonable appearance with your label maker.
Did you ever get this working?
Thanks for the reply.
You mention (in the link) about installing Home Assistant in a virtual environment. Is this required? I have Hassbian all set up, so don’t want to run another virtual environment.
You should be able to use one of the older solutions from before hassio became a thing, have a look for Dasher but be warned 99% of dev is now done for hassio / vanilla docker.
I think it is not necessary to have a virtual environment. It’s a generic set up, you can place dasshio files in other directory.
I used Hassio before, but it was too restrictive for all that I need. I’m just rubbish at setting all this up
Followed your guide, now get the following error:
sudo systemctl status dasshio
● dasshio.service - dasshio - Amazon Dash Buttons
Loaded: loaded (/lib/systemd/system/dasshio.service; enabled; vendor preset:
Active: activating (auto-restart) (Result: exit-code) since Thu 2018-09-27 15
Process: 816 ExecStart=/srv/homeassistant/bin/python3 /srv/homeassistant/dassh
Main PID: 816 (code=exited, status=1/FAILURE)
Sep 27 15:32:08 hassbian systemd[1]: dasshio.service: Unit entered failed state.
Sep 27 15:32:08 hassbian systemd[1]: dasshio.service: Failed with result 'exit-c
lines 1-8/8 (END)…skipping…
● dasshio.service - dasshio - Amazon Dash Buttons
Loaded: loaded (/lib/systemd/system/dasshio.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2018-09-27 15:32:08 UTC; 282ms ag
Process: 816 ExecStart=/srv/homeassistant/bin/python3 /srv/homeassistant/dasshio/dasshio.py (code=
Main PID: 816 (code=exited, status=1/FAILURE)
Sep 27 15:32:08 hassbian systemd[1]: dasshio.service: Unit entered failed state.
Sep 27 15:32:08 hassbian systemd[1]: dasshio.service: Failed with result ‘exit-code’.