iobroker.nuki2 v1.0.5

ioBroker.nuki2

This ioBroker adapter allows to control and monitor the Nuki Smart Lock by using both the Nuki Bridge API (v1.8.0, 06.03.2019) and the Nuki Web API (v1.1.1, 30.08.2018).

Table of contents 1. Installation 1. Get a API token 2. Callback function 3. States 2. Smart Home / Alexa integration using ioBroker.javascript 1. Lock door at 10pm in the evening 2. Let Alexa inform you about lock changes 3. Let Telegram inform you about lock changes 3. Changelog 4. Credits 5. Licence

Installation

Get a API token

How to get your hardware bridge token (does not work for software bridges):

1. Call http://<bridge_ip>:<bridge_port>/auth from any browser in your network. The bridge turns on its LED.
2. Press the button of the bridge within 30 seconds.
3. Result of the browser call should be something like this:

    {
    "token": "token123",
    "success": true
    }

4. Use the generated token in the Nuki2 adapter.

Manually set callback (optionally)

If the callback function is being used, the adapter will automatically set the callback on the Nuki bridge when the instance is being saved. Respective Nuki states (see below) will be kept up-to-date by the Nuki bridge while callback is activated.

Callbacks can also be set and removed manually from any browser with following URLs:

• set Callback: http://<bridge_ip>:<bridge_port>/callback/add?url=http%3A%2F%2F<host_ip>%3A<host_port>%2Fnuki-api-bridge&token=<bridgeToken>
• remove Callback: http://<bridge_ip>:<bridge_port>/callback/remove?id=<callback_id>&token=<bridgeToken>
• list all Callbacks: http://<bridge_ip>:<bridge_port>/callback/list?token=<bridgeToken>

States

If you successfully setup ioBroker.nuki2, the following channels and states are created:

Bridges (with Nuki Bridge API)

A bridge will be created as device with the name pattern bridge__<name of bridge>. The following channels / states will be created in each bridge:

Locks (with Nuki Bridge API)

A lock will be created as device with the name pattern door__<name of door>. The following channels / states will be created in each lock (when using the Nuki Bridge API):

** marked states will be updated on a Nuki action if callback is set

Locks (with Nuki Web API)

A lock will be created as device with the name pattern door__<name of door>. The following channels / states will be created in each lock (when using the Nuki Web API):

Smart Home / Alexa integration using ioBroker.javascript

Some examples of a possible integration within your smart home.

Lock door at 10pm in the evening

var states = {
    "0": "uncalibrated",
    "1": "locked",
    "2": "unlocking",
    "3": "unlocked",
    "4": "locking",
    "5": "unlatched",
    "6": "unlocked (lock n go)",
    "7": "unlatching",
    "254": "motor blocked",
    "255": "undefined"
};

schedule('0 22 * * *', function()
{
    var status = (getState('nuki2.0.door__home_door.status.lockState').val);
    var msg = 'Main Door door is ' + (states[status]) + '. ';

    if (status == '3')
    {
        setState('nuki2.0.door__home_door.action', 2);
        msg += 'Locking door..'
    }
    else
        msg += 'No action taken.'

    log(msg, {m: 'Nuki', o: ['msg']});
});

Replace `nuki2.0.doorhome_door.status.lockStatewith the lockState of your lock!__ You may also customize the message viamsg`.

Let Alexa inform you about lock changes

This requires the ioBroker adapter ioBroker.alexa2 (https://github.com/Apollon77/ioBroker.alexa2).

In order to use the voice output of Alexa we define a function say. Place the following function in a script in the "global" folder of ioBroker.javascript. IMPORTANT: Replace #YOUR ALEXA ID# (also replace #) with your Alexa ID. You may find the Alexa ID in the Objects tree of ioBroker alexa2.0.Echo-Devices.

/**
 * Say something with Alexa.
 * 
 * @param       {string}        message         Message to say
 * @param       {string|array}  alexas          Alexa Device to say the voice message
 * @return      void
 * 
 */
function say(message, alexas = '#YOUR ALEXA ID#') // use alexas = ['#YOUR ALEXA ID 1#', '#YOUR ALEXA ID 2#'] for default voice output from multiple devices (also replace #)
{
    alexas = typeof alexas === 'string' ? [alexas] : alexas;
    alexas.forEach(function(alexa)
    {
        setState('alexa2.0.Echo-Devices.' + alexa + '.Commands.speak', message);
    });
}

You can use this function within ioBroker.javascript to say a phrase using Alexa say('Hello World') or say('Hello World', ['#YOUR ALEXA ID 1#', '#YOUR ALEXA ID 2#']) for voice output from multiple devices.

Create a script in the "common" folder of ioBroker.javascript and add the following listener to it. IMPORTANT: Replace #LOCK STATE ID# (also replace #) with the state holding the lock status (e.g. nuki2.0.door__home_door.status.lockState):

const DOOR_STATES = {
    "0": "uncalibrated",
    "1": "locked",
    "2": "unlocking",
    "3": "unlocked",
    "4": "locking",
    "5": "unlatched",
    "6": "unlocked (lock n go)",
    "7": "unlatching",
    "254": "motor blocked",
    "255": "undefined"
};

/*
 * LISTEN TO CHANGES TO LOCK STATE
 * 
 */
on({id: '#LOCK STATE ID#', change: 'any'}, function(obj)
{
    if (obj !== undefined && obj.state !== undefined)
      say('Door is ' + DOOR_STATES[obj.state.val] + '!')
});

Let Telegram inform you about lock changes

This requires the ioBroker adapter ioBroker.telegram (https://github.com/iobroker-community-adapters/ioBroker.telegram).

In order to use the message output of Telegram we define a function msg and messenger. Place the following function in a script in the "global" folder of ioBroker.javascript:

/**
 * Send something via telegram.
 * 
 * @param       {string}        message         Message to print
 * @param       {string|array}  receiver        Users to send the message to
 * @return      void
 * 
 */
function msg(message, receiver = 'ALL')
{
    if (receiver == 'ALL')
        messenger(message);
    
    else
    {
        receiver = typeof receiver == 'string' ? [receiver] : receiver;
        receiver.forEach(function(user)
        {
            messenger(message, user);
        });
    }
}

/**
 * Sends a message / text.
 * 
 * @param   {string}            content         Message to send
 * @param   {string}            user            (optional) Specific user to send the message to (defaults to all registered users)
 * @return  void
 * 
 */
function messenger(content, user = '')
{
    var config = {
        text: content,
        parse_mode: 'HTML',
        reply_markup: {
            resize_keyboard: true,
            one_time_keyboard: false
        }
    };
    
    sendTo('telegram', user ? Object.assign({user: user}, config) : config);
}

You can use this function within ioBroker.javascript to send anything to Telegram via msg('Hello World') (to all users) or msg('Hello World', 'Zefau') (to specific users).

Create a script in the "common" folder of ioBroker.javascript and add the following listener to it. IMPORTANT: Replace #LOCK STATE ID# (also replace #) with the state holding the lock status (e.g. nuki2.0.door__home_door.status.lockState):

const DOOR_STATES = {
    "0": "uncalibrated",
    "1": "locked",
    "2": "unlocking",
    "3": "unlocked",
    "4": "locking",
    "5": "unlatched",
    "6": "unlocked (lock n go)",
    "7": "unlatching",
    "254": "motor blocked",
    "255": "undefined"
};

/*
 * LISTEN TO CHANGES TO LOCK STATE
 * 
 */
on({id: '#LOCK STATE ID#', change: 'any'}, function(obj)
{
    if (obj !== undefined && obj.state !== undefined)
      msg('Door is ' + DOOR_STATES[obj.state.val] + '!')
});

NOTE: If you are using both the Alexa and the Telegram script, you may only define one listener for both actions:

const DOOR_STATES = {
    "0": "uncalibrated",
    "1": "locked",
    "2": "unlocking",
    "3": "unlocked",
    "4": "locking",
    "5": "unlatched",
    "6": "unlocked (lock n go)",
    "7": "unlatching",
    "254": "motor blocked",
    "255": "undefined"
};

/*
 * LISTEN TO CHANGES TO LOCK STATE
 * 
 */
on({id: '#LOCK STATE ID#', change: 'any'}, function(obj)
{
    if (obj !== undefined && obj.state !== undefined)
    {
      say('Door is ' + DOOR_STATES[obj.state.val] + '!')
      msg('Door is ' + DOOR_STATES[obj.state.val] + '!')
    }
});

Changelog

1.0.2 (2019-08-14)

• (Zefau) Fixed Bug with incorrect callbacks

1.0.1 (2019-08-11)

• (Zefau) Performance improvements
• (Zefau) Small re-design of admin panel
• (Zefau) Fixed Bug within user retrieval

1.0.0 (2019-08-03)

• (Zefau) bump to stable release (no changes)

0.9.13 (2019-07-20)

• (Zefau) updated dependencies to fix security vulnerabilities in depending packages

0.9.12 (2019-05-16)

• (Zefau) fixed an issue causing the same callback set multiple times (see #9)

0.9.11 (2019-05-13)

• (Zefau) added info-message when setting refresh rate to less than 10 seconds

0.9.10 (2019-05-10)

• (Zefau) added states to reflect current callbacks set on the Nuki Bridge as well as action to delete the callbacks
• (Zefau) updated dependency of nuki-bridge-api to v1.5.0

0.9.9 (2019-05-05)

• (Zefau) updated dependency of nuki-bridge-api to v1.4.0

0.9.8 (2019-05-05)

Thanks to @systemofapwne for testing and identifying quite a few bugs.

• (Zefau) added delay between requests / actions applied on the Nuki Bridge (to prevent overload, see #9)
• (Zefau) fixed an issue causing the adapter to crash when polling was enabled, but Web API is not used (see #10)

0.9.7 (2019-05-05)

• (Zefau) added verification if callback URL is already added on Nuki Bridge (see #9)

0.9.6 (2019-05-03)

• (Zefau) added Web Adapter as dependency
• (Zefau) add warning when opening web / log view but Nuki Web API has not been setup
• (Zefau) removed empty folders when Nuki Web API has not been setup
• (Zefau) fixed an issue with Webhook when time for refreshing all settings was set (#9)

0.9.4 / 0.9.5 (2019-03-22)

• (Zefau) Useless versions to fix incorrect configuration in io-package.json

0.9.3 (2019-03-22)

• (Zefau) Limited log retrieval to 1000 entries

0.9.2 (2019-02-11)

• (Zefau) Updated dependency

0.9.1 (2019-02-10)

• (Zefau) Added Web Interface to view logs

0.9.0 (2019-02-09)

• (Zefau) Using both Bridge API and Web API
• (Zefau) Support for multiple bridges
• (Zefau) Support for discovery within admin panel
• (Zefau) Additional states for bridges and better separation between software / hardware bridge
  • retrieve the basic and advanced configuration from your lock
  • retrieve all users having access to your lock

Credits

Thanks to @Mik13 for the Nuki Bridge API implementation.

Icons made by Smashicons (Essential Set) and Freepik (Doors) from www.flaticon.com is licensed by CC 3.0 BY

License

The MIT License (MIT)

Copyright (c) 2019 Zefau zefau@mailbox.org

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.