Merge branch 'develop'

.editorconfig

@@ -0,0 +1,16 @@
+# top-most EditorConfig file
+root = true
+
+# Unix-style newlines with a newline ending every file
+[*]
+end_of_line = lf
+insert_final_newline = true
+
+[*.js]
+indent_style = space
+indent_size = 2
+
+# Matches the exact files either package.json or .travis.yml
+[{package.json,.travis.yml}]
+indent_style = space
+indent_size = 2

.gitignore

@@ -142,3 +142,4 @@ $RECYCLE.BIN/
 *.lnk
 
 # End of https://www.gitignore.io/api/osx,git,node,linux,macos,windows
+dist/

.npmrc

@@ -0,0 +1 @@
+save-exact=true

.travis.yml

@@ -0,0 +1,6 @@
+language: node_js
+node_js:
+  - lts/*
+script:
+  - "npm run lint"
+  - "npm run build"

CHANGELOG.md

@@ -1,6 +1,28 @@
 # Changelog
 All notable changes to this project will be documented in this file.
 
+## [2.0.0] - 2020-03-01
+
+****
+🚨 **This release is a major version and contains some breaking changes. Please read the list below.**
+****
+
+### Changed
+
+- Implementation of Somfy Open API, replacing unofficial TahomaLink API
+- Migration of the network layer from deprecated [request](https://www.npmjs.com/package/request) to [axios](https://www.npmjs.com/package/axios)
+- `tahoma-read` node now returns the raw response from the [Somfy Open API](https://developer.somfy.com/somfy-open-api/apis/get/site/%7BsiteId%7D/device}) (a remapping of your flows might be needed)
+
+### Added
+
+- New code quality control using TSLint 
+
+## [1.0.1] - 2019-08-21
+
+### Changed
+
+- Added door handle state support, contributed by [@matthub](https://github.com/matthub)
+
 ## [1.0.0] - 2018-12-13
 
 ### Changed
@@ -16,7 +38,6 @@ All notable changes to this project will be documented in this file.
 - New `stop` action to immediatly stop the current action on the devices (See [#5](https://github.com/nikkow/node-red-contrib-tahoma/pull/5), thanks to [@Genosse274](https://github.com/Genosse274))
 - New CHANGELOG.md file to keep track of all updates.
 
-
 ### Changed
 
-- Fix path in getSetup() (See [#7](https://github.com/nikkow/node-red-contrib-tahoma/pull/7), thanks to [@hobbyquaker](https://github.com/hobbyquaker))
+- Fix path in getSetup() (See [#7](https://github.com/nikkow/node-red-contrib-tahoma/pull/7), thanks to [@hobbyquaker](https://github.com/hobbyquaker))

README.md

@@ -1,27 +1,48 @@
+<p align="center">
+	<img src="docs/images/somfy-logo.png">
+</p>
+
 # Somfy Tahoma for Node-RED
 
-![npm](https://img.shields.io/npm/v/node-red-contrib-tahoma.svg)
-![npm](https://img.shields.io/npm/dt/node-red-contrib-tahoma.svg) 
+
+[![npm](https://img.shields.io/npm/v/node-red-contrib-tahoma.svg)](https://www.npmjs.com/package/node-red-contrib-tahoma)
+[![Build Status](https://travis-ci.org/nikkow/node-red-contrib-tahoma.svg?branch=develop-v2)](https://travis-ci.org/nikkow/node-red-contrib-tahoma)
+[![npm](https://img.shields.io/npm/dt/node-red-contrib-tahoma.svg)](https://www.npmjs.com/package/node-red-contrib-tahoma)
 ![license](https://img.shields.io/github/license/nikkow/node-red-contrib-tahoma.svg)
+![code size](https://img.shields.io/github/languages/code-size/nikkow/node-red-contrib-tahoma)
+
+## 🚨 Important Note vor v1.x users
+
+Due to a recent change in the API used in v1, most of you were encountering issues during the configuration of your node (e.g. empty device list...). **This API was unofficial and we had no control over it** :) 
+
+This new v2.0 version implements the Somfy Open API, which is officially available for third-party software as this one.
+
+Even though your flows should not be modified, the [config-node](https://nodered.org/docs/user-guide/editor/workspace/nodes#configuration-nodes) must be reconfigured using this new API.
+
+**However**, please note that even though this release was tested before being published, you might encounter unexpected issues. **Please backup your flow before proceeding with this major release**.
 
 ## Setup
 
 You can read this [guide](https://nodered.org/docs/getting-started/adding-nodes) from Node-RED official portal. This will help you install this node. Typically, the command are as follows:
 
 	cd $HOME/.node-red
-	npm install node-red-contrib-tahoma
+	npm install node-red-contrib-tahoma 
 
 ## Disclaimer
-This software is provided as-is. Be careful: your devices can be totally controlled via API actions. I am not responsible of any mis-usage or corruption of the devices configuration.
+This software is provided **as-is**. Be careful: your devices can be fully controlled via API actions. I am not responsible of any mis-usage or corruption of the devices configuration.
 
 ## Configuration
 
-In order to use this node, you need to have a Tahoma Link account. If you already use the Tahoma Box and the mobile apps, you should have one.
+In order to use this node, you need to have a Somfy account. If you already use the Tahoma Box and the mobile apps, you should have one.
+
+You will also need to create an app on the developer portal in order to retrieve a set of required credentials. This [guide](https://github.com/nikkow/node-red-contrib-tahoma/wiki/How-to-create-an-Somfy-Open-API-app%3F) will walk you through this process.
 
-When creating your first node, you will be asked to provide your e-mail and password used to login to your Tahoma Link account. These will be used to connect to the API (of course, they will only be used locally, they are not forwarded to me :)).
+When creating your first node, you will be asked to provide your e-mail and password used to login to your Somfy account. These will be used to connect to the API (of course, they will only be used locally, they are not forwarded to me :)).
 
 ## Usage
 
+### Node `tahoma`
+
 This node accepts an object as input. The following properties will be parsed:
 
 | Property | Type | Required? | Description |
@@ -30,7 +51,7 @@ This node accepts an object as input. The following properties will be parsed:
 | `position` | int (0-100) | *No* | The position you want to set your blinds/door to |
 | `lowspeed` | boolean | *No* | Should the action be triggered in low-speed mode? |
 
-### Actions
+#### Actions
 
 Currently, only a few commands are understood by this node. The possible values for the `action` property are:
 
@@ -39,17 +60,25 @@ Currently, only a few commands are understood by this node. The possible values
 * `stop`: This will stop all running actions
 * `customPosition`: This will set the device to a custom position. The position is passed using the `position` property, which is required in this mode.
 
-### Output
+#### Output
 
 The node will output its original `msg.payload` enriched with the result of the expected action. `msg.payload.output` will contain 2 properties:
 
 * `open`: a boolean. Set to true if the device is open, or false otherwise
 * `position`: an integer (0-100). Set to the position returned by the Tahoma box.
 * `luminance`: in case of a Sun Sensor, returns the current value of core:LuminanceState (See issue [#6](https://github.com/nikkow/node-red-contrib-tahoma/issues/6))
 
+### Node `tahoma-read`
+
+This node does not accept any input. You can specify the desired device by editing the node properties.
+
+#### Output
+
+The node will output its original `msg.payload` enriched with the selected device information. A full example can be found on the Somfy Open API [documentation](https://developer.somfy.com/somfy-open-api/apis/get/site/%7BsiteId%7D/device).
+
 ## Example flow
 
-![Example Flow](docs/example-flow.png)
+![Example Flow](docs/images/example-flow.png)
 
 An example flow can be found in the docs/ folder. Basically, all it does is close and open shutters based on manual triggers. Those can be replaced by some logic (e.g. a node calculating the sunset and sunrise times). The output is sent to a local MQTT broker. 
 
@@ -63,9 +92,28 @@ This was tested with the following devices:
 
 Feel free to send any feedback of any other compatible items or known limitations :)
 
-## To-do
+## FAQ / Troubleshooting
+
+### I received a "Session expired" error, what happned?
+
+![Session expired error](docs/images/ts-session-expired-node.png) 
+
+During the login process, Somfy generates a set of credentials composed of two tokens: the first is called an **access token** and the second a **refresh token** (following the [OAuth2](https://oauth.net/2/) protocol). 
+
+Both these tokens expire at some point. 
+
+The **access token** (used to authenticate each request sent to Somfy API) has a very short lifetime (1 hour) and needs to be regenerated afterwards. To prevent you from entering your e-mail/password each hour, the **refresh token** handles this new authentication. Whenever the access token expires, a new authentication request is sent and Somfy generates a brand-new set of tokens.
+
+However, the **refresh token** has not an infinite lifetime. It expires after **14 days**. Basically, it means that if node-red hasn't reached the Somfy API for 14 days + 1 hour, both your token have expired and you need to login again. 
+
+#### What should I do?
+
+This error is also described in the "Debug" tab of your node:
+
+![Session expired error](docs/images/ts-session-expired-log.png) 
+
+All you need to do is open your node configuration, edit your account and follow the instructions on the yellow box:
 
-These are the things that should be updated (and will be later) on this module:
+![Yellow box](docs/images/ts-session-expires-tip.png)
 
-* Filter elements that can actually be controlled (e.g. do not display the "Active Button")
-* Find a way to properly handle "my" position
+**Note:** do not forget to **deploy** your flow, so the new credentials are properly saved.