Niko Home Control Manual

1 view

Skip to first unread message

Fermina Enge

unread,

Aug 3, 2024, 4:15:05 PM8/3/24

to kainewsterngest

Yes, it is a known problem in version 3.0.2 (and before for that matter). It was raised by another user. I solved it recently. I am not sure it ever worked, but it could also be caused be a change on the Niko side. They send energy readings with a decimal while the API definition states it should be integers. The binding does handle it now, but it is only in recent snapshots (last few days).

Hi, my niko controller 550-00003 just DIED on me. When I power it on the orange status light lights for 30s and then goes out. Nothing can be controlled, not even on the light modules directly. It has ethernet link but no packed are going out. Also the bus is powered 14v.

Upgrade notice for Niko Home Control II and openHAB 2.5.3 or later:Starting with openHAB 2.5.3 the binding uses Niko Home Control hobby API token based authentication.The Niko Home Control hobby API is available with Niko Home Control system version 2.5.1 or newer.If currently using a profile and password based authentication with the binding (upgrading from an openHAB version before 2.5.3), you will need to start using hobby API token based authentication.Make sure your Niko Home Control system is at version 2.5.1 or newer.Request a hobby API token at mynikohomecontrol (opens new window).In the bridge configuration, put the received token in the API Token parameter.Delete the values for Bridge Port and Profile parameters.

For Niko Home Control I, the binding has been tested with a Niko Home Control IP-interface (550-00508).This IP-interface provides access on the LAN.The binding does not require a Niko Home Control Gateway (550-00580), but does work with it in the LAN.It has also been confirmed to work with the Niko Home Control Connected Controller (550-00003) in a Niko Home Control I installation.

For Niko Home Control II, the binding requires the Niko Home Control Connected Controller (550-00003) or Niko Home Control Wireless Smart Hub (552-00001).The installation only needs to be 'connected' (registered on the Niko Home Control website) when first connecting to validate the authentication, and will work strictly in the LAN thereafter.

For Niko Home Control I, the binding exposes all actions from the Niko Home Control System that can be triggered from the smartphone/tablet interface, as defined in the Niko Home Control I programming software.For Niko Home Control II, the binding exposes all devices in the system.

Supported device types are switches, dimmers and rollershutters or blinds, thermostats, energy meters (Niko Home Control I only) and access control (Niko Home Control II only).Niko Home Control alarm and notice messages are retrieved and made available in the binding.

The Niko Home Control Controller is represented as a bridge in the binding.Connected to a bridge, the Niko Home Control Binding supports all off actions, on/off actions (e.g. for lights or groups of lights), dimmers, rollershutters or blinds, thermostats, energy meters, access control devices (Niko Home Control II only) and alarm systems (Niko Home Control II only).

The bridge representing the Niko Home Control IP-interface needs to be added first.A bridge can be auto-discovered or created manually.An auto-discovered bridge will have an IP-address parameter automatically filled with the current IP-address of the IP-interface.This IP-address for the discovered bridge will automatically update when the IP-address of the IP-interface changes.

If the IP-address is set on a manually created bridge, no attempt will be made to discover the correct IP-address.You are responsible to force a fixed IP address on the Niko Home Control IP-interface through settings in your DHCP server.

For Niko Home Control I, the port is set to 8000 by default and should match the port used by the Niko Home Control I IP-interface or Niko Home Control I Connected Controller.For Niko Home Control II, the port is set to the default Hobby API 8884 port.

The Niko Home Control II bridge has an extra required parameter for the API token.The API token can be retrieved from your Niko Home Control profile page on the Niko Home Control website.For that, you will need to add the Hobby API as a connected service on your profile.Note that the API token is only valid for one year after creation.The token expiry date is visible in the bridge properties.Entries will also be written in the log when the token is about to expire (starting 14 days in advance).

An optional refresh interval will be used to restart the bridge at regular intervals (every 300 minutes by default).Restarting the bridge at regular times improves the connection stability and avoids loss of connection.It can be turned off completely by setting the parameter to 0.

A discovery scan will first discover Niko Home Control IP-interfaces or Niko Home Control Connected Controllers in the network as bridges.Default parameters will be used.Note that this may fail to find the Niko Home Control IP-interface when traffic to port 10000 on the openHAB server is blocked.

Subsequently, all defined actions that can be triggered from a smartphone/tablet in the Niko Home Control I system, respectively all actions in the Niko Home Control II system, will be discovered and put in the inbox.It is possible to trigger a manual scan for things on the Niko Home Control bridge.Note that Niko Home Control II will require the API token to be set on the bridge before the scan for actions can succeed.The bridge will remain offline as long as these parameters are not set.

Advanced configuration note for Niko Home Control II:It is possible to use authentication based on a touch panel profile, bypassing the Hobby API token authentication.To make this work, you have to define a password protected touch profile in the Niko Home Control programming software.Extract the embedded SQLite database from the configuration file.Look for the profile you created in the Profile table (using a SQLite database browser tool) and copy the CreationId into the profile parameter for the bridge.The port parameter on the bridge has to be set to 8883.The password parameter should be set to the profile password.

For Niko Home Control I, the actionId, thermostatId or meterId parameter are the unique IP Interface Object ID (ipInterfaceObjectId) as automatically assigned in the Niko Home Control Controller when programming the Niko Home Control system using the Niko Home Control I programming software.It is not directly visible in the Niko Home Control programming or user software, but will be detected and automatically set by openHAB discovery.For textual configuration, you can manually retrieve it from the content of the .nhcp configuration file created by the programming software.Open the file with an unzip tool to read its content.

For Niko Home Control II, the actionId parameter is a unique ID for the action in the controller.It can only be auto-discovered.If you want to define the action through textual configuration, the easiest way is to first do discovery on the bridge to get the correct actionId to use in the textual configuration.Discover and add the thing you want to add.Note down the actionId parameter from the thing, remove it before adding it again through textual configuration, with the same actionId parameter.Alternatively the actionId can be retrieved from the configuration file.The file contains a SQLLite database.The database contains a table Action with column FifthplayId corresponding to the required actionId parameter.The same applies applies for thermostatId, meterId, accessId and alarmId.

The binding has been tested with a Niko Home Control I IP-interface (550-00508) and the Niko Home Control Connected Controller (550-00003) for Niko Home Control I and II, and the Niko Home Control Wireless Smart Hub for Niko Home Control II.

Not all action and device types supported in Niko Home Control I and II controllers are supported by the binding.Refer to the list of things and their support for Niko Home Control I and II respectively.

The niko_home_control integrationIntegrations connect and integrate Home Assistant with your devices, services, and more.[Learn more] allows you to integrate your Niko Home Control into Home Assistant.

To enable this lights, add the following lines to your configuration.yamlThe configuration.yaml file is the main configuration file for Home Assistant. It lists the integrations to be loaded and their specific configurations. In some cases, the configuration needs to be edited manually directly in the configuration.yaml file. Most integrations can be configured in the UI.[Learn more] file.After changing the configuration.yamlThe configuration.yaml file is the main configuration file for Home Assistant. It lists the integrations to be loaded and their specific configurations. In some cases, the configuration needs to be edited manually directly in the configuration.yaml file. Most integrations can be configured in the UI.[Learn more] file, restart Home Assistant to apply the changes. To view the changes, go to Settings > Devices & services > Entities.

Function: The Niko Home Control touchscreen offers residents a user-friendly interface to operate all functions within their Niko Home Control installation. The symbol displayed next to each action represents the current status of that action. In addition, the touchscreen provides a detailed overview of the electricity, gas and water consumption in the home, provided that these functions have been included in the instal-lation. Access control is also possible with this touchscreen when it is used in combination with the Niko Home Control external video unit (550-2100X). Thanks to its wired connection to the home network you can always count on the touchscreen. This is why we recommend providing at least one touchscreen in the installation, on top of the mobile devices. The symbols on the touchscreen are used by the resident to operate the functions that you assigned while programming the installation. The resident can also use the touchscreen to request more information about the electricity, gas and water consumption in the home. Connect the touchscreen with the connected controller using a twisted pair cable, such as a UTP, FTP or STP cable. Both the touchscreen and the connected controller have an RJ45 jack. You will need to mount RJ45 plugs onto the cable to be able to connect one end of the cable to the controller, and the other end to the touchscreen. The touchscreen can be supplied with power using Power over Ethernet (PoE) via the same twisted pair cable, for which you use the Niko PoE power supply (550-00502). Alternatively, you can provide a separate power supply cable, which you connect to a separate 24 Vdc power supply module in the electrical cabinet. In that case, you will need a 24 V power supply cable such as an SVV, JYSTY, TPVF or UTP cable in addition to the twisted pair cable. The touchscreen itself is not suitable for flush mounting. Mount the touchscreen onto the wall using a standard flush-mounting box with a depth of at least 40 mm.Technical data: