First working version

.eslintrc.json

@@ -0,0 +1,3 @@
+{
+    "extends": "athom"
+}

.github/workflows/validate.yml

@@ -0,0 +1,21 @@
+name: Validate Homey App
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  validate:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 12
+          cache: npm
+      - run: npm ci
+      - run: npm install --global --no-optional homey
+      - run: npm run build
+      - run: npm run test

.gitignore

@@ -0,0 +1,3 @@
+/env.json
+/node_modules/
+/.homeybuild/

.homeychangelog.json

@@ -0,0 +1,5 @@
+{
+    "0.0.1": {
+        "en": "First test release"
+    }
+}

.homeycompose/app.json

@@ -0,0 +1,35 @@
+{
+    "id": "com.christerbeke.homey-uponor",
+    "version": "0.0.1",
+    "compatibility": ">=5.0.0",
+    "sdk": 3,
+    "platforms": [
+        "local"
+    ],
+    "name": {
+        "en": "Uponor Smatrix Pulse"
+    },
+    "description": {
+        "en": "Adds support for Uponor Smatrix Pulse."
+    },
+    "category": [
+        "climate"
+    ],
+    "permissions": [],
+    "images": {
+        "small": "/assets/images/small.png",
+        "large": "/assets/images/large.png",
+        "xlarge": "/assets/images/xlarge.png"
+    },
+    "author": {
+        "name": "Chris ter Beke",
+        "email": "contact+homey@christerbeke.com"
+    },
+    "brandColor": "#0062C8",
+    "source": "https://github.com/ChrisTerBeke/homey-uponor",
+    "support": "https://github.com/ChrisTerBeke/homey-uponor/issues",
+    "homepage": "https://github.com/ChrisTerBeke/homey-uponor",
+    "bugs": {
+        "url": "https://github.com/ChrisTerBeke/homey-uponor/issues"
+    }
+}

.homeycompose/discovery/uponor.json

@@ -0,0 +1,13 @@
+{
+    "type": "mac",
+    "mac": {
+        "manufacturer": [
+            [
+                40,
+                245,
+                55
+            ]
+        ]
+    },
+    "id": "{{address}}"
+}

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 support@athom.com. 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,50 @@
+# 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.homey.app) 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!
+
+## 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.