Initial release with GPIO output support

.gitignore

@@ -0,0 +1,107 @@
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+lerna-debug.log*
+
+# Diagnostic reports (https://nodejs.org/api/report.html)
+report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+*.lcov
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Bower dependency directory (https://bower.io/)
+bower_components
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (https://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules/
+jspm_packages/
+
+# TypeScript v1 declaration files
+typings/
+
+# TypeScript cache
+*.tsbuildinfo
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# Microbundle cache
+.rpt2_cache/
+.rts2_cache_cjs/
+.rts2_cache_es/
+.rts2_cache_umd/
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# dotenv environment variables file
+.env
+.env.test
+
+# parcel-bundler cache (https://parceljs.org/)
+.cache
+
+# Next.js build output
+.next
+
+# Nuxt.js build / generate output
+.nuxt
+dist
+
+# Gatsby files
+.cache/
+# Comment in the public line in if your project uses Gatsby and *not* Next.js
+# https://nextjs.org/blog/next-9-1#public-directory-support
+# public
+
+# vuepress build output
+.vuepress/dist
+
+# Serverless directories
+.serverless/
+
+# FuseBox cache
+.fusebox/
+
+# DynamoDB Local files
+.dynamodb/
+
+# TernJS port file
+.tern-port
+
+# Homey
+env.json

.homeychangelog.json

@@ -0,0 +1,5 @@
+{
+  "1.0.0": {
+    "en": "Initial release"
+  }
+}

.homeycompose/capabilities/custom_heap.json

@@ -0,0 +1,15 @@
+{
+    "type": "number",
+    "title": {
+        "en": "Heap Free",
+        "nl": "Heap Beschikbaar"
+	},
+	"icon": "/assets/icons/heap.svg",
+    "insights": true,
+    "uiComponent": "sensor",
+    "getable": true,
+    "setable": false,
+    "units": {
+        "en": "Blocks"
+    }
+}

.homeycompose/capabilities/custom_heartbeat.json

@@ -0,0 +1,10 @@
+{
+    "type": "string",
+    "title": {
+        "en": "Last seen"
+	},
+	"icon": "/assets/icons/heartbeat.svg",
+    "uiComponent": "sensor",
+    "getable": true,
+    "setable": false
+}

.homeycompose/capabilities/custom_load.json

@@ -0,0 +1,15 @@
+{
+    "type": "number",
+    "title": {
+        "en": "System load"
+	},
+	"icon": "/assets/icons/cpu.svg",
+    "decimals": 2,
+    "insights": true,
+    "uiComponent": "sensor",
+    "getable": true,
+    "setable": false,
+    "units": {
+        "en": "%"
+    }
+}

.homeycompose/capabilities/custom_ram.json

@@ -0,0 +1,15 @@
+{
+    "type": "number",
+    "title": {
+      "en": "Free RAM",
+      "nl": "RAM Beschikbaar"
+	},
+	"icon": "/assets/icons/ram-alt.svg",
+    "insights": true,
+    "uiComponent": "sensor",
+    "getable": true,
+    "setable": false,
+    "units": {
+      "en": "KB"
+    }
+  }

.homeycompose/capabilities/custom_uptime.json

@@ -0,0 +1,10 @@
+{
+    "type": "string",
+    "title": {
+        "en": "Uptime"
+	},
+	"icon": "/assets/icons/uptime.svg",
+    "uiComponent": "sensor",
+    "getable": true,
+    "setable": false
+}

.homeycompose/drivers/settings/connectionSettings.json

@@ -0,0 +1,43 @@
+{
+	"type": "group",
+	"label": {
+		"en": "Connection settings"
+	},
+	"children": [
+		{
+			"id": "mac",
+			"type": "label",
+			"label": {
+				"en": "MAC Address"
+			},
+			"value": "",
+			"hint": {
+				"en": "The MAC Address of your ESP Easy unit. This is the identifier Homey uses for your unit. Any incoming messages will be matched by MAC addres so if the IP address does not match, it is updated on Homey's end."
+			}
+		},
+		{
+			"id": "host",
+			"type": "text",
+			"label": {
+				"en": "IP Address or hostname"
+			},
+			"value": "",
+			"hint": {
+				"en": "The IP Address of your ESP Easy unit. Will be updated automatically if any events from the unit (identified by MAC address) arrive with a different IP address. If you only use output pins (which will not send events), you can add a 'System Info' device to the ESP unit, it will send events to Homey every minute."
+			}
+		},
+		{
+			"id": "port",
+			"type": "number",
+			"label": {
+				"en": "Port number"
+			},
+			"value": 80,
+			"min": 0,
+			"max": 65535,
+			"hint": {
+				"en": "Should be port 80 as ESP Easy doesn't support running on another port at the moment."
+			}
+		}
+	]
+}

.homeyplugins.json

@@ -0,0 +1,5 @@
+[
+	{
+		"id": "compose"
+	}
+]

CODE_OF_CONDUCT.md

@@ -0,0 +1,71 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+education, socio-economic status, nationality, personal appearance, race,
+religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

CONTRIBUTING.md

@@ -0,0 +1,53 @@
+# Contributing to Athom and Homey
+
+First off all, thank you for taking the time to contribute!
+
+The following is a set of guidelines for contributing to Athom and its packages, which are hosted in the [Athom Organization](https://github.com/athombv) on GitHub. These are just guidelines, not rules. Use your best judgment, and feel free to contact us if you have any questions.
+
+Please join our [community slack](https://slack.athom.com), if you have not done so already.
+We also have a [community forum](https://community.athom.com) for general discussions.
+
+
+## Before submitting a bug or feature request
+
+* **Have you actually read the error message**?
+* Have you searched for similar issues?
+* Have you updated homey, all apps, and the development tools (if applicable)?
+* Have you checked that it's not a problem with one of the apps you're using, rather than Homey itself?
+* Have you looked at what's involved in fixing/implementing this?
+
+Capable programmers should always attempt to investigate and fix problems themselves before asking for others to help. Submit a pull request instead of an issue!
+
+Regular support is provided through our [support staff]([email protected]).
+
+## A great bug report contains
+
+* Context – what were you trying to achieve?
+* Detailed steps to reproduce the error from scratch. Try isolating the minimal amount of code needed to reproduce the error.
+* Any applicable log files or ID's.
+* Evidence you've looked into solving the problem and ideally, a theory on the cause and a possible solution.
+
+## A great feature request contains
+
+* The current situation.
+* How and why the current situation is problematic.
+* A detailed proposal or pull request that demonstrates how the problem could be solved.
+* A use case – who needs this feature and why?
+* Any caveats.
+
+## A great pull request contains
+
+* Minimal changes. Only submit code relevant to the current issue. Other changes should go in new pull requests.
+* Minimal commits. Please squash to a single commit before sending your pull request.
+* No conflicts. Please rebase off the latest master before submitting.
+* Code conforming to the existing conventions and formats. i.e. Please don't reformat whitespace.
+* Passing tests in the test folder (if applicable). Use existing tests as a reference.
+* Relevant documentation.
+
+## Speeding up your pull request
+Merging pull requests takes time. While we always try to merge your pull request as soon as possible, there are certain things you can do to speed up this process.
+
+* Ask developers to review your code changes and post their feedback.
+* Ask users to test your changes and post their feedback.
+* Keep your changes to the minimal required amount, and dedicated to one issue/feature only.
+* If your PR introduces new features or more than just a small fix, please sign our [Contributor License Agreement](https://go.athom.com/cla).