The current implementation requires the user to predict and generate stimulus that should be ignored, and set the sensor sensitivity in advance. But after deployment, imperfections of that guesswork manifest as false positives.

The sound logs should indicate the db level that triggered the event as well as the peak level in that event. Motion logs should give the triggering value as well, for

In case of some trail multiple detection (static+N), to put detection "cloud" in info section with detection names were met in all triggered trails.

Doable?

That's a odd issue I have at the moment. The onFar method (from ProximityListener) is triggered when I switch to the Android N multi view.

• The median heuristic function utils.medianHeuristic is missing in the pytorch branch. Please copy it to edgeml_pytorch.utils.
• It is being called from here when you run the example. That is

Add install/usage instructions for non yaml mode users.

According to the I2C spec, if you are using the SMBus method to RD/WR you need do the I2C_SLAVE ioctl only once and then proceed with multiple read/write calls.

See here: https://www.kernel.org/doc/Documentation/i2c/dev-interface
"_When you have opened the device, you must specify with what device
address you want to communicate:

int addr = 0x40; /* The I2C address */

if (ioctl(fil

Expected Behavior

Per wiki "Getting Started With a Raspberry Pi 3 and the Bosch XDK": "The sensors from the XDK should now be visible in the Sensors & Devices app in the web user interface."

Actual Behavior

After last step in wiki (bin/Linux/armv7l/macchina), got the following result:
bin/Linux/armv7l/macchina: error while loading shared libraries: libPocoOSP.so.2: cannot open shar

There should be an FAQ in the wiki.
The closed issue contain a lot of knowledge and ways to debug issues.
I'd like to have them available in a wiki and also issue templates
which states what information is needed for debugging.

The characters 0 and 8 displayed on the SSD1306 are easily confused because in the used font the zero is a slashes zero. Because of that some people have a hard time connecting to the correct IP address or finding their sensor graphs in madavi.de.

As a visitor, I want to see what devices look like so that I can understand how they would integrate into the environment.

Acceptance criteria

• It's done when product pictures are added for relevant README.md files.
• It's done when usage pictures/videos are added for relevant README.md files.
• It's done when all images and videos used are open-source.

It appears that the description for the shutdown delay refers to "startup" instead of "shutdown"

The description should refer to the time delay for turning "off" GPIO when print "stops"
This could have been a simple cut and paste error.

I am using Enclosure version 4.12 on Octoprint 1.3.10.

![image](https://user-images.githubusercontent.com/31289713/55700029-8a27de80-5982-11e9-8691-db143

I have read the documentation and library code and I first have tot thank you for putting this project together! My ultimate goal is to get your DS2433 example working.

The master I am using is the DS9490R USB/1-wire interface from Maxim from their iButton starter kit. I am using Maxim's [OneWireViewer](https://www.max

It would be useful for the update methods to accept a timestamp at which the sensor data was recorded, rather than use time.now which assumes a constant latency between sensor reading and calling the update function.