diff --git a/source/hassio/addon_testing.markdown b/source/hassio/addon_testing.markdown
index 6b53ae1e225..849c387a746 100644
--- a/source/hassio/addon_testing.markdown
+++ b/source/hassio/addon_testing.markdown
@@ -13,6 +13,18 @@ The fastest way to develop add-ons is by adding them to your local add-on reposi
 
 Right now add-ons will only work with images that are stored on Dockerhub (using `image` from add-on config). We're working on enabling local add-ons to be built on the device.
 
+## {% linkable_title Local run %}
+
+You can build an try the addon on your developer machine also. Move all addon stuff into a temp folder. Replace on Dockerfile: `%%VERSION%%` with your version and `%%BASE_IMAGE%%` with:
+- armhf: `resin/armhf-alpine:3.5`
+- aarch64: `resin/aarch64-alpine:3.5`
+- amd64: `resin/amd64-alpine:3.5`
+- i386: `resin/i386-alpine:3.5`
+
+Use docker to build the test addon: `docker build -t local/my-test-addon .`
+
+Create a new folder for data and add a test _options.json_. After that you can run our addon with: `docker run --rm -v /tmp/my_test_data:/data -P PORT_STUFF_IF_NEEDED local/my-test-addon`
+
 ## {% linkable_title Logs %}
 
 All stdout and stderr is redirected to the Docker logs. The logs can be fetched from the add-on page inside the Hass.io panel in Home Assistant.