The Project page is used to state information regarding the project BeoLiving Intelligence is part of. This information could be useful in any later service situation.
- Project name: Name for the project.
- Display name: Name of the BLI PRO that will be shown in all interfaces (e.g.: BeoLiving App, Webpanel, etc.).
For example, a display name could be the family name or the street address of the house.
- Installer name: Name of installer/company in charge of this project for reference.
- Installer contact: Any type of contact information to reach the installer/company in charge of this project for further questions/comments.
Date & Time
Correct time setting is important for the monitoring of events, astronomic clock events and for error log time stamping.
Date & Time settings
- Date: Date corresponing to the selected Time zone.
- Time: Time corresponing to the selected Time zone.
- Time zone: Setting for the time zone is chosen from the drop down list. Choices are made based on an appropriate match of “Continent”/”City”.
Location settings (Astronomical Clock and Location events)
The location settings are used by the BLI PRO to calculate time related events (e.g. sunrise and sunset). Events can then be set relative to this. Latitude and longitude are the settings for the astronomic clock. The settings are in decimal degrees. Values are entered in format ‘degrees.minutes’. Seconds are only used to round the minute-value. Positive values are for North and East. Negative values are for South and West.
Home Integration protocol allow other devices to interact with BLI. This protocol is used by mobile applications or by other home automation controllers.
Home Integration protocols provide two-way control of all resource types. This protocol can be enabled on the local network, with mandatory authentication. You should provide a TCP port (default port is 9100). Port numbers below 1024 are reserved for standard TCP services, so use values above this range.
The network page contains the BLI’s network connectivity configuration.
The following options are available:
- Hostname: BLI’s name as it’s found in the LAN.
- DHCP: Enable/Disable DHCP mode. Per factory default, DHCP mode is enabled.
- Address: If DHCP is disabled, the static BLI network address could be set in Address.
- Mask: Mask related to the BLI’s LAN.
- DNS Server: DNS Server network address in the LAN.
- Gateway: Gateway address in LAN.
The settings must be confirmed by clicking on Apply.
Khimo cloud link
BLI is configured from factory to be connected to Khimo’s cloud service. This service is used to enable features like voice control (e.g.: Amazon Alexa) and remote access to your installation (with BLI PRO mode). If this service is disabled those features will no longer work.
Access restrictions regarding which zones will be able to be controlled could be set from the selection of a specific BLI user. This means that all accounts will share the same zone access restrictions as the selected user. Zone access restriction could be modified in the Interfaces page.
To remotely access your installation through BLApp, remote access must be enabled in the application.
At the bottom of this page, a list with the current remote users is displayed.
Enable remote access in BeoLiving App
To enable Remote Access in the BLApp you must:
- Go to the Settings menu and select your BLI.
- Go to Device Settings and press Request Remote Access.
The next video shows interactively how to accomplish this feature:
BLI PRO can have any number of System modes, which can be used to enable or disable the execution of macros, as follows:
- System modes can be activated by the BLI PRO command SET MODE.
- Any number of modes can exist, but only one can be active at any given time.
- A macro can have any number of modes, and a mode can be set to any number of macros.
- A macro with no mode set will behave normally.
- If a macro has one or more modes set, then it will be triggered by events only if one of those modes is active.
Typical examples of system modes: Vacation and Normal. You can set up a button to toggle between normal and vacation modes. Macros for setting thermostats, or for controlling lighting and shades may be assigned individually to each mode.
The systems temperature unit can be configured to be Fahrenheit or Celsius, affecting all the clients connected to the BLI PRO. For example, if the current temperature unit is Fahrenheit, then all the thermostats will report the temperature in these units to all connected clients.
This setting only affects what is displayed on the BLI PRO user interface. It does not affect the units displayed on the actual thermostats.
Everything in BLI is organized into zones. Zones represent rooms or other locations in the home such as kitchen, hallway, garden, garage, etc. In order to accommodate for big installations, zones themselves are organized into areas. Examples of areas are: upstairs and downstairs, guest house, barbecue.
Areas & Zones
Areas are indicated by text on a grey background in the left column. Zones that are subdividing the areas are indicated by text on a white background in the left column.
Adding areas and zones
Areas are added using the “Add new area” button. At this point the area’s name may be stated. An area can be deleted by activating the “x” sign in the greyed area-boxes and renamed by activating the edition-sign next to “x” sign. Zones are added to the areas by activating the “+” sign in the greyed area-boxes.
- Name: Name of zone. In BLI a zone can be one or more rooms in the house or even part of a room, e.g. : living room, kitchen, bedroom. The Name is stated as desired.
- Area: Drop down list of all existent Areas in the configuration to select where to place the Zone.
- Icon: An icon can be assigned that will be visible in the user interfaces, for easy recognition.
- Delete: A selected zone can be deleted by activating the Delete button. Systems and resources in the zone that is to be deleted must be rearranged or removed.
The main area has two special zones:
- global: placeholder zone for systems (and their resources) that apply to the entire house (recommended; although systems may be placed in areas/zones as desired. Likewise macros that act on several zones at a time such as ‘Party mode’, ‘Welcome’ and ‘Good Night’ may all be added to the ‘Global’ zone. The global zone cannot be deleted and cannot be assigned an icon).
- unassigned resources: placeholder zone for automatically discovered B&O products. BLI discovers and adds all products found in its network. It’s up to the installer to move those products into their respective Area/Zone.
The systems settings is for setting-up systems connected to BLI PRO. BeoLink system and HA systems are ‘systems’.
Example of supported systems are: Nest, Philips Hue, Lutron, KNX. Check Systems Drivers PRO page to know all HA systems that BLI PRO supports.
Each system has in BLI PRO a correspondent driver. There are two driver types:
- Native driver, included in BLI PRO firmware and ready to be added to your BLI.
- External driver, located in our cloud. BLI PRO will download and install the external driver if desired.
In this section, only Native drivers will be included. Go to Install external drivers for more information.
Select “+” sign to add a new HA system from the drop down list and click on Add system. A System may be added in a specific Area/Zone if it only serves functions there. If the system serves more zones it may be added to the Main/global zone. Any of the supported systems can be added, except internal systems, which only appear once in the installation, such as BeoLink and Virtual Resources that are added by default. When selecting a system added to a certain zone, it’s possible to select another zone in the Zone drop down list, by which the system is moved to that zone. A system can be renamed and its configuration and connection settings can be changed.
Systems are assigned to zones by the installer, but they are invisible in the users interface. For example, assigning a System to a specific zone could be used by the installer to locate system hardware in the installation.
Connection settings depend on each system. Examples of Connection settings are:
- Connection type
- Check server certificate
For specific details on different systems please refer to the online help. The default values must be changed according to the settings used in the installation.
Press Apply button to confirm settings.
System status icons
For each system installed, a text string icon is shown in the bottom of the screen. The status of each system is indicated by the colour of the background of the text string icon.
This gives a quick status indication on each system. Moving the mouse pointer to each icon displays a pop-up that shows specific logs for that system.
If a system cannot connect, the system logs should be checked for information about the problem.
Resources are provided by the installed systems:
- BeoLink system (NL A/V products and its connected sources)
- Home Automation system(s) (e.g. buttons, sensors)
- Virtual resources (programmed resources e.g. related to a button on a user interface or based on an event)
The resources have the following parameters:
- Zone: The zone to which the resource belongs.
- Name: Enter a name to ease identification of the resources.
- Type: Select type from the drop down list. The only available resource type is NL product.
- Address: Unique identification of a resource. The format depends on the system. For NL products, address will be the serial number.
- Force Discovery: Forces the product discovery in case it could not be done automatically.
Home Automation system resources
The resources have the following parameters:
- Zone: The zone to which the resource belongs.
This defines from which zone you will be able to effectively control the resource. Independently of what zone the system is in.
- Name: Name to ease identification of the resources.
- Type: Resource type. The type of available resources depends on the actual system, for instance: button, dimmer, shade etc.
Some systems can extend the standard button to provide extra features (see this in the drop down list). The purpose of having standard resource types is that such common set of features are shared by most supported systems.
E.g. a standard button supports PRESS, HOLD and RELEASE actions plus a status indication (e.g. a LED that can be On or Off).
- Address: Unique identification of a resource. The format depends on the HA system - using various number schemes.
- Capture: Used to capture resources by their activity, captured by the BLI. Resource selected from the capture list are added automatically to the table of defined resources. The capture functionality is supported by most systems.
- Import resources: Used to import HA system resources into BLI uploading a specific HA system file or just requesting them directly. This feature depends on each HA system driver.
An example of a Virtual Resource is a button on the user interface (BLApp, TV overlay, Webpanel - see Interfaces section for more information).
E.g. a virtual button for cinema scene, or a boolean variable to indicate that a specific condition has been reached. Virtual Resources make it possible to define buttons and variables of String, Integer and Boolean types for systems, without implementing these directly.
The BLApp currently uses virtual buttons to display scene buttons. Virtual Resources have no functionality by themselves. Macros must be defined to link user actions on a virtual resource, with events and commands in the system.
The address of a Virtual Resource is a unique number and if isn’t set manually, BLI PRO generates automatically an un-used address for that resource.
The interaction between the devices connected to the BLI is defined by means of a Macro. A Macro consists in a set of events and commands. When any of the events that are defined in a Macro occur (e.g. a key press on a keypad; a Control Command on a Bang & Olufsen remote control etc .), the macro will be triggered. This means that the commands in the macro will be executed in order.
A Macro is also assigned to an Area/Zone to which it belongs even if it handles activity outside the zone. Having Macros assigned to zones helps when setting up user interfaces. The left column shows all Macros contained in each Area/Zone. To add a Macro in a specific Area/Zone press “+” in the column entry.
- Mode: Before setting the macro up, the system mode (E.g.: Normal, Vacation, etc.) to which the Macro will belong is programable. The default Any will make it available independently of the mode the system is in.
For each macro, the next options are available:
- Add event: used to add an Event to a Macro. The two buttons (see figure above) can be used to set the cinema scene. See Resource Event section.
- Capture: when the Capture button is pressed, all system/resource events fired from that moment will be displayed so that they can be added.
An example of captured events could be: the press of a virtual or physical button or the source selection in a A/V renderer device.
- Add command: used to define the commands of a Macro. See Resource Command section.
- Clone: creates an exact copy of the Macro adding “- Clone n” as suffix to the cloned Macro name, where n is the number of clones made.
- Remove: deletes Macro.
- Fire: fires/triggers Macro.
- Convert to code: switches Macro commands configuration into a Lua editor, turning existant Macro commands into Lua code. Lua commands help is showed after pressing Show Help button. Pressing Convert to table will convert Lua commands into table format.
- Cut/Copy/Paste: when selecting an event/command (pressing left side of the event/command), Cut/Copy/Paste buttons become available. The purpose, as the meaning of their names illustrate, is to Cut/Copy/Paste Events or Commands on the same Macro or between Macros.
When pressing the Add event button, the window expands, fields for the Resource Event are shown and are filled in by selecting from the drop down lists with each entry field. The illustration is an example only and the drop down list may vary depending on the choices made.
The list of events (for triggering a macro) can be filled in manually or selected from captured events.
There are three types of events:
- Generic: Generic events apply to a number of similar events throughout the house. See Generic Programming section for more information.
- Resource: Resource events match a specific event on a specific resource.
- System: System events include calendar and astronomical clock events and system connectivity events.
When pressing the Add command button, the window expands, fields for the resource command are shown and are filled in by making selections from the drop down lists with each entry field. The illustration is an example only, and drop down lists may vary depending on the choices made.
Commands are the actions executed when a Macro is triggered. The list of commands are executed in order, and a delay can be set before each command as a combination of seconds and milliseconds. The list can be reordered by dragging the handles at the left of each row, or by clicking on the arrows on the far right of each row.
There are four types of commands:
- Generic: applies to any area or zone, with the possibility of selecting the same area or zone where the event was generated.
- Resource: applies to a specific resource.
- System: acts directly on the systems, which support them.
- Macro: calls other macros, or acts on other macros.
Actions on macros
Several command options are available to act on macros:
- FIRE: Call the macro, as if an event for that macro had happened. This is the default action.
- CANCEL: Will stop executing the ongoing macro.
- COLLAPSE: Will execute remaining commands in the ongoing macro, but with no delays between commands.
Although not recommended, it is possible to make a loop where a macro calls itself as the last command, e.g. switching Off growth light for plants; night and day temperature control, etc. It is required to make a macro that stops such loops.
Firing a new macro makes it possible to take advantage of a existing functionality without having to maintain several copies inside different macros.
As a macro execution can take some time due to delays between commands, it is important to take care of what could happen if another macro is triggered during the execution.
For instance if a macro called “THEATER ON” (for setting- up a home theater) takes more than one minute to execute, what will happen if this macro is called repeatedly? Will all commands start to overlap each other? What will happen if the “THEATER OFF” macro is called to switch the home theater off during the set-up? It is important to understand that a possible messy overlap of command executions from different macros may occur. The possibility to cancel or collapse a macro being executed ensures that the ongoing macro will end immediately.
In the above mentioned example, the macro to switch the home theater Off should first cancel the macro for setting-up the home theater:
“THEATER OFF” macro commands:
- Cancel “THEATER ON” macro.
- Raise screen.
- Shut down projector.
- Switch Avant to STAND BY.
Orphan commands and events
If commands and events are defined for a resource and the resource is deleted or modified to another address, events and commands will become orphan (without an associated resource). Orphan events and commands will still be available and refer to the original addressing of the resource. The macro screen will signal the presence of orphan commands or events by colour coding and text in the macro header.
Standard events and commands apply to a single specific resource. Generic programming makes it possible to refer to a whole set of resources at once.
E.g.: It’s possible to specify:
- A single command to mute all products.
- An event specification that matches any button pressed.
This has the following advantages:
- A single macro can now substitute a lot of macros previously tailored for individual resources and the list of events and commands on a macro can be reduced.
- It encourages a consistent setup throughout the installation.
NOTE: Generic events and commands are matched against all possible resources every time an event occurs or a command is executed. If the name of a resource is changed on a working configuration, the resource will no longer match an existing generic event or command. Therefore, it is important to be consistent when naming resources. It is also important to avoid spoiling functionality by renaming resources.
Commands are also represented by a code. The main difference is that there is a new type of selector for matching the same area or zone as of the generating event. A command code starting with $area/$zone/AV renderer/TV will act on all audio and video renderers named “TV” on the same area where the event generated and a command code starting with “*/*/AV renderer/TV” can be used to work with all TVs in the house.
This is the user setup menu, their rights and interfaces are generated by BLI PRO.
It’s possible to configure the following features:
- Users that can access the system and access restrictions.
- Sources and features of A/V products.
- Access to IP cameras in the house.
- Resources and macros that appear in a zone.
- Virtual resources that provide a friendly way of interacting with some systems.
- Lists with favourite TV channels and radio stations.
The resources to be accessed via the user interfaces are configured in this page. The user interfaces are:
- BLApp: BLI specific user control application that could be installed on any iOS based device.
- Webpanel: User control interface accessible through BLI web interface.
- TV overlay: User control interface application accessible through any Bang & Olufsen NetworkLink TV as Home Control. Same layout as Webpanel.
Configurations are synchronized in real time towards the Webpanel and the TV overlay. Synchronization with the BLApp is done periodically and could be forced by activating Configuration > Quick save revision.
Users - admin
The user named admin is a user that exists per default and is meant for the technician/installer. It has access to set up the BLI PRO and is allowed to access all zones via browser or BLApp.
Change password for admin user
Per default, admin password is unknown but it can be set to “admin” by activating the Setup button function No.2 (See button functions). This password will last 5 minutes (for security purposes) during which a new one must be set. Press the admin entry in the left column to change password (see figure above).
Users - new user
To add a new user press “+” sign in the Users header (left column).
Configure User properties by entering a name under the Name field and password in the Password field. Then select options according to the following:
- User management access: when selected, the user is allowed to administer users and user-rights. This option should be set for the owner of the installation or a ‘superuser’ who is responsible for managing user access.
- Edition of user macros: when selected, the user is allowed to create and edit macros for the BLApp.
- Controller: should normally be selected. Allows the user to access BLI via BLApp. When disabled, the only access is via the Webpanel.
Select zone access for user
Finally, choices should be made in Select zone access for user. All zone access may be selected or a selection of individual zones from the list presented.
For A/V products there are some basic options and a source list that can be presented to the user.
When selecting any product, the next sections are displayed.
NetworkLink product: area/zone/product
- Name: Possibilty to rename the product.
- Address: The product’s serial number.
- Force IP address: Define a fixed IP address to connect to the product. This is not recommended and should only be used as a workaround in
situations where product discovery has shown not to be reliable.
It may also be used to access equipment installed on another (reachable) network.
- Beo4 navigation: Whether the product is set up for the old Beo4 navigation or the new navigation with cursor keys and SELECT.
- Show product sources on their zone: Hides product sources in its zone if not selected.
- Set new automatically synchronized sources as visible: New synchronized sources are not set as hidden.
For each product all local and distributed sources are shown in the Sources in product table.
This is synchronized automatically from the product configuration (if the product is online). In case of any problem with automatic source synchronization, Force synchronization with product button will get the current sources of the product.
The information provided in the Sources in product section for each source is the following:
- Source: Type of source.
- Name: Source label in all user interfaces.
- UI Type: Reference for the mobile application about what type of user interface is needed for operating the product.
- Favourites list: This makes it possible to select a favourite list defined in the Favourites section.
- Hidden: Selects if source must be hidden in all user interfaces or not.
The configuration of several network cameras is permitted. To add a camera, press the “+” sign in the Cameras header (found in the left column).
Both ONVIF protocol cameras and HTTP cameras are supported, when adding a camera ONVIF cameras available on the network will be automatically detected. These can also be added to your system directly through the BeoLiving App on a smartphone.
Please be aware that there are companies improperly claiming ONVIF conformance for their products, compatibility can be verified on https://www.onvif.org/conformant-prod…. You must also take into account that some ONVIF compatible cameras don’t have the functionality enabled by default (e.g.: Hikvision https://www.hikvision.com/ueditor/net…) and must be “manually” enabled.
HTTP Camera basic configuration
BLI PRO has a simple and strong capability integration with most CCTV systems or IP Cameras found in the market.
To add a camera you must fill the next form:
- Name: Name that identifies the camera. The name will be shown in the user interfaces.
- Zone: Drop down list to select the zone in which the camera is placed.
- IP: An IP number, to which all commands will be appended, must be provided. HTTP(snapshots) or RTSP(video) ports will then be declared separately.
- HTTP Port: Snapshot feed camera port number (default: 80).
- RTSP Port: Video feed camera port number (default: 554).
These camera RTSP streams will not be available through webpanel and may only be seen on the App or by opening rtsp://$GATEWAY_HOST:554/$AREA/$ZONE/CAMERA/$NAME (for example with VLC)
- Username and Password: The optional Username and Password fields may be used for basic HTTP authentication to access the camera from the user interfaces.
If a camera must be removed from the list, choose the Camera header in the left column and press the Remove button.
HTTP Camera resources path
By pressing the Raw edit button a text representation of all the fields appears for setting camera resolutions and commands. It is possible to copy and paste the text when setting up other similar cameras and for each of these to adapt to the actual camera.
E.g. adjust to the correct IP-address.
Video & Images
At least one of the resource paths for obtaining Video & Images both in high and low resolution or RTSP stream must be provided.
E.g. mjpg/video.cgi for high resolution video.
All the commands will be appended to the correspondent base URL.
Pan, Tilt and Zoom commands
If your camera is able to control lens direction and zoom, Pan, Tilt and Zoom paths could be specified and controlled through all user interfaces.
In this section of the Interfaces page, for each zone it is possible to reorder, hide/show and rename the resources to be seen in the user interfaces.
Resources for area/zone
For the resource to be moved in the list, place the cursor over the left button (three horizontal lines), then click and drag the resource until the line-marking is where the resource should be placed and release the mouse button.
- Name: Possibility to rename the resource.
- Type: The type of the resource is stated.
- Hidden: Set if the resource must be hidden in the user interface.
- Options/Hints: For macros and buttons that are visible on the user interfaces the following options are available:
- Confirm: If this option is enabled, after a button press or after a macro is triggered the action will need confirmation on a hand held device.
E.g. pressing a Yes button to avoid unintended activation before the desired function is executed. This could be when an action should not take place unintended, e.g. activating ‘Vacation mode’.
- Compact: When enabled the button in the user interface will be shown in a half-width button.
E.g. there is room for two buttons per line.
- On camera view: With ‘On camera’ enabled, when using WebPanel the half-width button will be shown next to the IP camera images in that zone. When BLApp is used, the button will be shown in the Cameras section of BLApp.
- On scenes view: When enabled, the button will be shown in the Scenes section of BLApp
- On dimmer view: When enabled, the button will be shown in the Lights section of BLApp.
- On shade view: When enabled, the button will be shown in the Shade section of BLApp.
- On thermostat view: When enabled, the button will be shown in the Thermostat section of BLApp.
- Confirm: If this option is enabled, after a button press or after a macro is triggered the action will need confirmation on a hand held device.
In this section of the Interfaces page, favourites lists for TV channels as well as radio stations can be added. In the hand held devices the favourite channels/stations are listed by name and logo if such is selected.
To add a new favourites list, press the “+” sign in the Favourites Lists column entry. In the top left field of the display, enter the source provider’s name. The Clone button (top right) is used to clone an existing source provider of favourites. The new one will show in the left column list, adding ‘Clone of’ to the name. The Remove button is used to remove a source provider of favourites chosen in the left column.
Commands global options
For each favourite list a global End command, a global Delay and a global Delay on source selection that will affect each favourite command can be set.
- End command: The end command is added at the end of each favourite command sequence and can be either NONE, PLAY or SELECT.
- Delay: The global delay is a delay value added between all digits and between digits and the end command for each favourite command.
- Delay on source selection: Delay that will be added previous to the first digit for each favourite command sequence, if source was effectively selected (i.e.: if the source was already selected, this delay will not be set).
List of favourites
For each listed TV channel/radio station the following information should be provided:
- Caption: A short description for the favourite. The caption will be filled in automatically when the logo picker is used. If edited it will remain unmodified. The caption will appear in the user interface.
- Command: The command that is executed when a logo is selected in the BLApp. See in Help for full explanation of combining elements in the command string. The command must be filled in manually.
- Logo: A logo can be fetched using the logopicker, see below, or by entering sufficient information in the URL field for the favourite. The logo will be shown in the user interfaces.
- URL: The full URL of the logo image to show. The URL must point out the valid image as it will be used periodically by BLApp to retrieve the logo. The URL will be filled in automatically when the logo picker is used. The URL can be entered manually.
The logo picker shows a pop-up window for selecting logos from the B&O repository and shows up by clicking the logo. Available logos are shown in groups of 50. It is possible to search for a channel using the filter. A search string will immediately restrict the channels displayed to only the matching entries. When a logo has been chosen the picker window will close and complete the URL path and command fields, and show the selected logo. The caption will also be updated, but not if it has been edited explicitly.
Note: The logo picker only works when an Internet connection is available.