Evaluate to change sniff filters

Put an x into all the boxes [ ] relevant to your issue (like this: [x])

What is the purpose of your issue?

• Bug report (encountered problems with amazon-dash)
• Feature request (request for a new functionality)
• Question
• Other

Guideline for bug reports

• amazon-dash version: 1.1.1
• Python version: 2.7.9
• Pip & Setuptools version: 18.0
• Operating System: Raspbian (Linux version 4.9.35-v7+)

• The pip install or setup install command has been completed without errors
• The python -m amazon_dash.install command has been completed without errors
• The amazon-dash discovery command works without errors
• I have created/edited the configuration file
• Amazon-dash service or amazon-dash --debug run works

Description

It seems amazon-dash service consumes a relevant share of CPU (around 15% average) in stand by. I think this is too much for a service like this, especially if you are using a Raspberry Pi as a server. In the same Raspberry Pi, other services like lighttpd, plexmediaserver, transmission and home assistant do not consume more than 2% in stand by.

What I Did

I ran ‘top’ and ‘htop’ for a while and observed the results (sorted by cpu usage).

[Nekmo]

Ok, It works. Thank you.

[Nekmo]

@etatus This change will be released in release 1.2.0. You can try this version using:

pip install git+https://github.com/Nekmo/amazon-dash.git@develop#egg=amazon-dash

http://docs.nekmo.org/amazon-dash/installation.html

Version 1.2.0 will be released in the coming weeks. There are still several months left for release 2.0.

Amazon-dash 2.0 is a major release and has many changes (+20 execution methods and more). It is still in development.