this is an Node for the API on the Velux© KLF-200 io-homecontrol© Gateway. (klf-200 provided by Velux©. I'm not affiliated.) Velux© KLF-200 io-homecontrol© Gateway support for Node-Red.
This implementation is based on the API documentation https://www.velux.com/api/klf200. It works only with the version 0.2.0.0.71 and above.
Up to the version 0.1.1.0.45 it was possible to access the KLF-200 web interface and rest API via the LAN interface. This does not work in version 0.2.0.0.71 anymore. Velux shared on demand with the Lan interface can only be addressed via the API.
Take a look at the technical specification for klf 200 api.pdf
For the latest updates see the CHANGELOG.md
cd ~/.node-red
npm install node-red-contrib-veluxGW_NODE_STATE_POSITION_CHANGED_NTF contains an incorrect timestamp. The lowest 2 bytes of the 4 bytes are sent to the higher 2 bytes and the lowest 2 bytes are 0. In response to the "GW_GET_ALL_NODES_INFORMATION_REQ" command, the correct time stamp is sent: 5be8d806 - 2018-11-12T01: 31: 50.000Z 15 sec Later a "GW_NODE_STATE_POSITION_CHANGED_NTF" hits. This contains a timestamp: d8160000 correct was here 5be8d816
If there is no communication with the KLF every 10 minutes to 15 minutes, the connection will be disconnected as described in the manual. If this happens when the home monitor "GW_HOUSE_STATUS_MONITOR_ENABLE_REQ" is activated, the KLF200 is no longer reachable. The KLF200 no longer sends the TLS command "Change Cipher Spec." on TLS start. This means that TLS encryption can no longer be initiated. I saw these in the wireshark. Should anyone else notice this error, it would be nice if that this someone also reports to the VELUX hotline.
The KLF200 needs more than 3 seconds to connect. It needs more then a second to send the key and more then a second for the TLS command "Change Cipher Spec.".
The KLF sometimes does not release the Sessin internally if the connection is lost. Since only 2 users are allowed to connect, it can happen that you are no longer allowed to connect to the KLF. Currently I am sending a GW_REBOOT_REQ from the API from the Node-Red once a day. This ensures that there is always a free slot available for connection.
- Velux KLF-200 on LAN
This API supported debugging. you have to set the environment variable DEBUG
set DEBUG=velux-klf200-api:*,velux-klf200:*,node-red-contrib-velux:*
This node establishes the connection to the KLF200. It is only possible to reach the KLF200 via a LAN. Some routers do not have a connection between the WLAN and the LAN from factory settings. Please read the manual if this is the case.
- Host: The IP address of the KLF 200
- Password: The password of the KLF200. Normally the WLAN password on the back
- Monitoring: Sets the monitoring method. At home monitor, the KLF200 sends automatically. The KLF200 in versio 0.2.0.0.71 can crash on a broken ip connection and deny any login until reset. Therefore you can also choose polling.
After the connection is established, the following actions are performed:
-
The date and time of the real-time clock in the KLF200 are set
-
The system state and the version of the klf200 are queried
-
The node states are queried
-
The house status monitor is turned on
-
Every 10 minutes, the system state is queried as a sign of life
Velux calls all actors in the network nodes. Velux nodes can be Shutter / Rollers, Window opener and so on. The output is output from time to time. Coming from the house status monitor. This sends the state of the velux node from time to time. When a status arrives, it is automatically written to the output of the node.
- Datasource: The data source is a velux-connection object. There should only be one for a KLF200. The KLF200 only allows two connections.
- node index: This is the index of the device (node) within the KLF200. In the dropdown, the index and the name are displayed when the combo box is empty.
- send value: This value is sent when a new value is received
- all values: The node object is completely output, the values can be looked up in the API description.
- currentPosition: only the current position is output.
- target: The target position is output.
- fp1CurrentPosition (-4): Some devices (nodes) have further function parameters. this is explained in the velux API description.
- remaining time: The remaining time to position.
- topic: This node sends a topic, either this text or the velux node name. and see input
- name: The name is displayed on the node
The msg.payload can be an numeric value or an object like
{value: <val>, valueType: <type>} or {rawValue: <val>}. The rawValue is preferred.
The msg.topic can control what happens to the input.
If the topic starts with velux: this is possible:
-
velux:readLike setting, see above, the value is output from the buffer -
velux:loadLike setting, see above, the value is requested and output at the KLF200 -
velux:read:id:<id>-1 all values or velux-node id for read. The settings are ignored. -
velux:load:id:<id>-1 all values or velux-node id for load. The settings are ignored. -
velux:read:name:<name>Read the value by velux-node name. The settings are ignored. -
velux:load:name:<name>Load the value by velux-node name. The settings are ignored. -
velux:writeLike setting, see above, the value is send to the velux-node -
velux:write:[name:<name>:][id:<id>:][valuetype:<valuetype>:]Overwrite the settings, the Payload must be an float value. []=optional, id and name together make no sense.
If a topic was specified in the settings and the tropic is not velux:... the topic must match or be empty otherwise the input will be discarded
| valuetype | Access Method name for Standard Parameter | Description | rawValue Range (Hex) |
| RELATIVE | Relative | Relative value (0 – 100%) | 0x0000–0xC800 |
| RELATIVE | Relative | No feed-back value known | 0xF7FF |
| PERCENT_PM | Percent+- | Percentage point plus or minus (-100% – 100%) | 0xC900-0xD0D0 |
| TARGET | Target | The target value for the parameter | 0xD100 |
| CURRENT | Current | The current value for the parameter | 0xD200 |
| DEFAULT | Default | The default value for the parameter | 0xD300 |
| IGNORE | Ignore | Ignore the parameter field where this Access Method is written | 0xD400 |
manages scenes and starts them. a scene is a sequence of commands stored in KLF.
- Datasource: The data source is a velux-connection object. There should only be one for a KLF200. The KLF200 only allows two connections.
- scene index: This is the index of the scene within the KLF200. In the dropdown, the index and the name are displayed when the combo box is empty.
- velocity: This value is sent when a new value is received
- DEFAULT: The scene operates by its default velocity.'
- SILENT: The scene operates in silent mode (slow).'
- FAST: The scene operates with fast velocity.'
- topic: This node sends a topic, either this text or the velux node name. and see input
- name: The name is displayed on the node
The msg.payload is ignored by the node.
The msg.topic can control what happens to the input.
If the topic starts with velux: this is possible:
veluxLike setting, see above, the scene is started at the KLF200velux:execute:id:<id>scene id for execute. The settings are ignored.velux:execute:name:<name>scene name for execute. The settings are ignored.velux:execute:[:id:<id>|:name:<name>]:velocity:<name>velocity by name for the scene. The settings are ignored.- DEFAULT: The scene operates by its default velocity.'
- SILENT: The scene operates in silent mode (slow).'
- FAST: The scene operates with fast velocity.'
veluxexecute:[:id:<id>|:name:<name>]:velocityid:<id>velocity by id for the scene. The settings are ignored.- 0: The scene operates by its default velocity.'
- 1: The scene operates in silent mode (slow).'
- 2: The scene operates with fast velocity.'
If a topic was specified in the settings and the tropic is not velux:... the topic must match or be empty otherwise the input will be discarded
The direct route to the velux API. You can send commands or receive notifications.
- Datasource: The data source is a velux-connection object. There should only be one for a KLF200. The KLF200 only allows two connections.
- API: The api command to send. The payload must be an Object. Maybe you must add some parameters. Take a look at the technical specification for klf 200 api.pdf. Also take an look at the API source. The parameters starts with a small bush letter. You can override the selected api with an payload.api or an payload.apiText parameter.
- listen NTF: The api notification to listen. You can choose from everything to nothing.
- topic: This node checks a topic. If the topic is entered the topic must match.
- name: The name is displayed on the node
Copyright (c) 2018 Chris Traeger
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.