PHILIPS Master Connect App Installation Guide

PHILIPS Master Connect App

Specifications

Product: Philips MasterConnect App
Installer Manual Version: October 2025
Phone Requirements:
- iOS version 16 or higher
- BLE version 4.2 or higher

Product Usage Instructions

System Architecture
- The system architecture provides a high-level description of the MasterConnect system.
System Components
- The system components detail the various parts that make up the MasterConnect system.
Philips MasterConnect App Availability
- The Philips MasterConnect app can be installed on most modern smartphones with Android or iOS operating systems. It is available on Google PlayStore for Android-based devices and the App Store for iPhones.
Setup
- Order of Setup Steps:
  - Create Project
  - Create a group
  - Commission lights into a group
  - Create zones (if required)
  - Commission ZGP sensors or switches at group level
  - Configuration on device level (if required)
  - Configuration on zone level (if required)
- Configuration on group level
  - Commissioning ZGP sensors or switches at zone level (if required)
- Backup Project to Cloud
  - Share project with other installers/facility manager as required

FAQs

What are the known limitations of the system?

The known limitations of the system are detailed in the Troubleshooting section of the manual. It provides information on potential issues and how to address them.

How do I check the app version?

To check the app version, follow these steps: Open the Philips MasterConnect app on your smartphone. Go to the settings or about section of the app. You should see the app version information displayed.

210
Philips MasterConnect App
Installer Manual
Philips MasterConnect app – Installer Manual October 2025

Last published versions v2023.04.06 Update (New app version 1.12.5, EasyAir SNS212 MC) v2023.08.08 Update (Launch SNS212 MC) v2023.08.23 Update (Required Android version 10 or higher) v2023.11.16 Update (A few remarks added or removed) v2023.12.22 MasterConnect App 2.0 release (hybrid networks) v2024.03.19 Update problem reporting v2024.06.18 Update including EasySense MC products for NAM v2024.10.25 Update (Launch SNH(B)212 MC) v2025.01.15 Update (Launch of device renaming feature and new mains-powered area sensors) v2025.04.01 MasterConnect Gateway release v2025.06.11 General update v2025.06.25 General update v2025.10.24 Update (Launch of MasterConnect Emergency Test Reporting)
2

About the document

This document is an instruction guide for installers and end users of the MasterConnect (MC) systems working with the Philips MasterConnect app. The combination forms a costeffective and easy-to-install solution for wireless control of new luminaires, ideal for energy-savings. Commissioning and configuration during and after installation is quick and easy using the Philips MasterConnect app. This app works via Bluetooth Low Energy (BLE) technology and is available for free on App Store and Google Play Store.

This manual consists out of five parts:

System

High level description of a MasterConnect System

Setup

In detail description how to setup a system

Configuration

All information about configuration options

Maintenance

Operations you might need once the system is commissioned

Troubleshooting

Options to improve your System in case it does not function as expected

System
6

System architecture
A stand-alone system sets up multiple MasterConnect nodes – such as Xitanium Wireless Drivers MC, EasyAir SNS21x MC sensors or EasySense SNS21x MC into a single network or group, enabling sophisticated automatic light control as well as manual switch control over the group. The system can be set up via a phone app called `Philips MasterConnect’ which makes the phone act as a gateway. Therefore, a stand-alone system simply comprises MasterConnect devices, a manual switch, and the Philips MasterConnect app. For setting up the system, the app opens a Bluetooth Low Energy (BLE) connection between the app and the 1st MC device. The app creates a network ID-key, exchanges BLE security credentials to add a MC device to group A. When an installer proceeds to add the next device to the same group, it then assigns the same network id & key to the 2nd device. The process of adding more MC devices can continue up to 120 devices, beyond which creating another group is advised. Each of the MC devices when added to a group, gets connected with other MC devices in a ZigBee mesh sharing the same assigned network id. For adding a manual switch, the app opens the ZigBee Green Power (ZGP) network, and the installer can commission a ZGP switch to manually control the lights. Once a group is created, the light behavior can be configured from the Philips MasterConnect app to meet application requirements.
7

System components
Different components are available to compose a system. These components include: Lights Lights describe luminaires with integrated MasterConnect nodes. This can be a MasterConnect wireless driver, a MasterConnect wireless node or a MasterConnect sensor. All MC nodes include Bluetooth and Zigbee radio. Switches Switches can be used to manually control a MasterConnect system. These switches operate on Zigbee GreenPower and can be self-powered (energy harvesting). There are twobutton and four-button versions available. Sensors External, mains-powered or battery-powered sensors can be used to bring motion and daylight control to MasterConnect systems without luminaire-integrated sensors. These sensors are available for office and industry applications in an occupancy and an occupancy-daylight version. They can be added to a group or a zone. Gateways Gateways can be used to add reporting and scheduling features to a MasterConnect system. These are supplied by Signify and by partners companies.
8

Philips MasterConnect app Availability

Phone requirements The Philips MasterConnect app can be installed on most modern smartphones with Android or iOS operating system. The app is available on both Google PlayStore (for Android-based) and App Store for iPhones.

The minimum phone requirements are:

· Android-based phones: version 11 or higher

· iPhones:

iOS version 16 or higher.

· Bluetooth:

BLE version 4.2 or higher.

Remark · The list of smartphone types in the market is long and increasing. System performance can vary for different combinations of the operating system, version of the BLE device
and Bluetooth implementation in the phone model. Alterations from industry can have an impact too. Therefore, although we expect good performance in most cases, we do not guarantee expected performance of Philips MasterConnect app. · It is recommended to test your mobile device with a wireless lighting system with Philips MasterConnect app. · Huawei phones are not officially supported. · Redmi phones are not officially supported. · Samsung J3 is not officially supported. · Xiaomi Redmi Note 8 Pro and Xiaomi Redmi 8A are not recommended because of less stable BLE communication. · iPads and Android tablets have not been tested.

Setup

How to Setup a System Overview Diagram
The diagram below shows the advised order of Setup steps of your system. This order minimizes commissioning and configuration time (not all steps are always needed):

Create Project

Create a group ..

Commission lights into a group

Create zones (if required)

Commission ZGP sensors or switches
at group level

Configuration on device level (if
required)

Configuration on zone level (if required)

Configuration on group level

Commissioning ZGP sensors or switches
at zone level (if required)

Backup Project to Cloud

Share project with other installers/facility manager as required

App screen names

Purpose This section is meant to list the name of the key screens that are used in this manual.

Project screen

Group screen / overview

Commissioning screen

Configuration screen

Device detail screen

Login
Purpose Only registered users get access to setup or maintain a MasterConnect lighting system using the Philips MasterConnect app. How to · Download and install the Philips MasterConnect app from the Apple App Store or Google Play Store. Search for ‘Philips MasterConnect’. · When opening the app for the first time, you will be asked to read and accept our Terms of Use. · After accepting, register with your email address. You will receive an email with a 6-digit verification code that needs to be filled in the app. · Complete the login by assigning a name to your account. Step-by-step guide
13

Remarks · Make sure that you have a stable Internet connection. · A verification code is obtained at every log-in; no password needs to be remembered. · Regularly check for app-updates, it is recommended to use the most recent version for best performance and most options. Usually ‘auto-update’ can be enabled in the
smartphone settings. · If you also work with the Philips Field Apps for SNS200 or SNH200, use a different e-mail account to log-in to the Philips MasterConnect app.
14

Create a project and add groups
Purpose Define a new lighting project and plan the luminaire groups, in which the wireless devices need to operate together. How to · Creation of the first project is prompted automatically. For another project, click on the building icon to get a list of earlier projects made under the same account, and add a
new one. · Give a name to the lighting project and optionally fill in the location. Create the project. · For each group of luminaires that need to work together, a group needs to be created. A group is defined by a name that needs to be unique per project. · Creation of the first group is prompted automatically after project creation. For more groups push “+” on the project screen. Step-by-step guide
15

Group limitations
Purpose When using and planning a wireless network with Philips MasterConnect, you should keep these group size limitations in mind.
Devices running on firmware 2 or 3: · max. number of devices in a group: 120 · max. number of zones per group: 15 · max. number of switches per group: 15 · max. number of switches per zone: 5 · max. number of SR-drivers per sensor: 4 (limited to 1 driver per sensor for support of Tunable White and Energy Reporting features) · max. number of sensors per SR-driver: 1
Devices running on firmware 1: · max. number of devices in a group:
o 40 (use cases without switches) o 30 (use cases including switch) o 20 (all use cases including group level energy reporting) · max. number of zones per group: 5 · max. number of switches per group: 5 · max. number of switches per zone: 5 (see remarks in Adding switches section) · max. number of SR-drivers per SNS: 4 (limited to 1 driver per sensor for support of Tunable White and Energy Reporting features) · max. number of sensors per SR-driver: 1
16

Grouping – commissioning
Purpose The created groups can be used to connect lights. To assign lights to a group, they need to be grouped (or commissioned). Depending on the MasterConnect node, the lights can be commissioned using a list-based approach or using a torch light.
· Lights with integrated sensors (SNS21x MC, SNH21x MC, SNHB21x MC, SNM21x MC) There are two ways to add these kinds of lights to a group: o Through point and trigger approach using a flashlight/torchlight or o Through the received signal strength (RSSI), also known as list-based commissioning
· Lights with integrated wireless drivers or wireless node (SNS41x MC) There is one way to add these kinds of lights to a group: o Through the received signal strength (RSSI), also known as list-based commissioning
Remarks · Ensure that Bluetooth is activated on the smartphone used. In case Bluetooth is disabled, Philips MasterConnect app will prompt for activation, which the user needs to
confirm. Allow for Location Access services to be enabled, when requested by the app. · Ensure that all lights of your system are powered on. · Lights that are added to a group are considered claimed devices and therefore, not available for other groups, projects, or users. · Xitanium wireless drivers, SNS41x MC and lights with integrated MC sensors can be commissioned in one group when using firmware 2 or higher. Otherwise, they must be
commissioned in different groups. Xitanium wireless drivers and SNS41x MC nodes can be combined in one group. · The maximum distance as specified in the datasheet, between luminaires, and between the user and the luminaires must be respected. · Firmware versions 1 and 2 as well as 1 and 3 may not be mixed in a group. Firmware 2 and 3 can be combined in the same group. · When creating a new network or adding a device to an existing group, please note that the behavior during first occupancy cycle might deviate slightly. After the first cycle was
completed, the lights show the same light behavior when occupancy is detected next.
17

Flashlight commissioning
Purpose Lights with an integrated MasterConnect sensor can be added to a group by pointing to them with a flashlight. How to · Open the group, tap “+” and select “Lights” to start discovering all the MC nodes that are in close reach for commissioning. · Please wait 10 seconds for the lights to be discovered. · Direct the light of a torchlight to the MasterConnect sensor that you like to add to a group and move it over the sensor. The sensor is triggered by a steep change from a
relatively low light level to a higher light level. · The smartphone responds to the detection with a sound and a brief vibration. On the 2nd beep, the selected light dims down and shows up in the “Added” tap in the app. The
light is now commissioned. Wait for another 3 seconds before proceeding to the next light. · When all luminaires for a group have been selected, choose “Finish adding”. The devices that are bind to that group are now displayed in the group overview. Step-by-step guide
18

Remarks · Use a flashlight with a well-defined light cone. Please refer to the design-in guide of the product for more information. · Typically, illuminance of the sensor should increase by 5000lx suddenly. · It is advised to wait for 2 beeps, after which a light will show up in “Added” tab. · In case a light is not added when pointed by a flashlight, please re-try, or use the list-based commissioning. · In case a light is not discovered, it might be that it was not in the scan list because of a too big range, e.g., in case of a long corridor. A re-scan of the lights with closer range is
required to add this light to the list. · It is strongly recommended not to change the flashlight sensitivity in the app settings section.
19

List-based commissioning
Purpose Lights with an integrated MC node can be added using a list overview. How to · Open the group, tap “+” and select “Lights” to start discovering all the MC nodes that are in close reach for commissioning. Please wait 10 seconds. · If not selected already, click on the “Discovered” tab. A list of all the lights with wireless component sorted by signal strength is shown. · To identify a luminaire in the app, click on the device name: the corresponding luminaire will blink several times. · Press “+” for all lights that need to be added to the group. When multiple devices are added simultaneously, a loading bar pops up. Press “Finish adding” to finalize. Step-by-step guide
Remarks · In case not all lights are listed, please retry. The lights are sorted based on the signal strength received by the smartphone and only those with the strongest signal are listed.
20

Device renaming
Purpose For simplified identification during maintenance scenarios, lights with an integrated MC node can be renaming during and after the commissioning. How to rename during commissioning · Start the commissioning process and click on the “Discovered” tab to see the list of all lights. · Click on the pencil icon to open the name editing pages. · Enter the new luminaire name and confirm by pressing “Save”. · Repeat the process for all luminaires that need to be renamed. · Continue the commissioning by tapping “+” for all lights that need to be added to the group. Press “Finish adding” to finalize. Step-by-step guide renaming during commissioning
21

How to renaming after commissioning · Open the group overview screen. Press the three dots next to the MC node name. · Choose “Rename” from the menu to open the name editing page. · Enter the new luminaire name and confirm by pressing “Save”. · Repeat the process for all luminaires that need to be renamed. Step-by-step guide renaming after commissioning
Remarks · Avoid using multiple “.” or “-” in the custom name to ensure the name is stored properly on the devices.
23

Installer test
Purpose To make a quick check that all luminaires in a group are well-commissioned and work as expected. A simple switch on/off or dimming command can be given to the group to verify that commissioning was done as desired. How to · Tap the three dots and choose “Enable Test Mode”. Now the whole group of lights or individual luminaires can be switched on and off with the app. · With the blue bar the dim level of the luminaires in the group can be controlled. Verify that all luminaires respond properly! In test mode the response of the luminaires is not
immediate and might need a few seconds. · After testing leave the test environment by going back one screen (arrow in upper left corner). Step-by-step guide
Remarks · Dim levels of the luminaires using the test mode are influenced by the configured field task levels of the devices. A field task level of 100% is recommended.
24

Identifying groups and nodes by blinking
Purpose You can easily identify a group or node with the command “Turn on identifying by blinking”. How to – identify on group level · Press the three dots right of the group name. · Select “Identifying by blinking” from the list. · The luminaires in the Group start to blink. The blinking will stop automatically after a while. Step-by-step guide identify on group level
25

How to – identify on Node level · Open the group. · Press the three dots right of the node name · Select “Identifying by blinking” from the list. · The node starts to blink. The blinking will stop automatically after a while. Step-by-step guide identify on node level
26

Zoning
Purpose A group of lights can be split into different zones which can be controlled by different switches or sensors. How to · Tap the three dots and choose “create a zone”. After naming the zone, the luminaires for that zone can be selected. Finally choose “Add to a zone”. · To identify a luminaire in the app, click on the device name: the corresponding luminaire will blink several times. · Repeat this procedure for all the zones needed. Step-by-step guide
Remarks · The separation into zones can be verified via `Enable Test Mode’. For details, see page 24 about the test mode. · When moving a light into an existing zone or out of a zone, make sure you are in range of that device (within 5m distance)
27

Adding switches

Purpose A wireless Zigbee switch can be added to a group or zone for manual lighting control. Features of the switch are shown below. Position of each feature on the switch can vary depending on manufacturer.

Self-powered single rocker ZigBee wireless light switch

Self-powered dual rocker ZigBee wireless light switch

Philips EasyAir 2B switch

Philips EasyAir 4B switch

Short: ON Long: DIM UP
Short: OFF Long: DIM DOWN
Illumra ZBT-S1AWH

Short: ON Long: DIM UP
Short: OFF Long: DIM DOWN

Short: SCENE 1 Long: CCT UP
Short: SCENE 2 Long: CCT DOWN

Illumra ZBT-S2AWH

How to · Click on the “+” on the group screen and select “Switch”. · From the drop-down list of compatible switches select the brand and type of switch you like to add. · Next indicate whether you would like to add to a zone or to the whole group. · Follow the switch commissioning instructions shown in the app or on our website precisely. · Once commissioned, the app requests to test if the switch works correctly. · Test the switch by making another button press, and once it works as expected press “Everything is fine”. · In case of a four-button switch, you can assign and customize scenes in the next step. Step-by-step guide
29

Remarks: · Please follow the instructions carefully, e.g., press the correct buttons and do not press sequences too fast. · Add all luminaires in a group first and then add a switch. Switch binding mechanism is to each node within the Zigbee group at the time of commissioning. For firmware
versions 1.x, no switch binding takes place, when new nodes are commissioned after the switch was added. · A switch can be added either to a group or to a zone. · All switches attached within a group should belong to a single brand. Combining switches from different brands is not recommended. · In case switches are used for a group and at the same time for zones of that group, three things need to be considered:
· The switch of the group should be added first. · Only 2-button switches should be used for the group. · In the zones 4-button switches with scene setting can be used. · If two or more zones are used with a 4-button switch, the maximum number of lights is 20 per zone. · In case the switch is not detected during the commissioning procedure, please re-try. · The backside of the switch may show an “O” and an “I indicator. The switch needs to be mounted such that `I’ is at the TOP and `O’ at the BOTTOM. · Do not remove the rocker from the switch module. If the rocker is placed back incorrectly, the switch does not function properly. · During commissioning of ZGP switches (in test setups) the devices should not be too close to the lights (between 2m and 5m distance) to avoid commissioning failures. · After commissioning of groups with more than 50 lights, please wait a few minutes before adding the first switch to avoid commissioning failure.
30

Configuring scenes
Purpose Different lighting configuration settings can be stored in scenes. With any 4-button wireless switch, up to 2 scenes can be configured. How to · Choose “Assign a scene” at the end of the switch commissioning or select the device from the group overview. · Select the button with which that scene will be switched on and off. · The light levels of all the luminaires in the scene can be set individually or get the same value when set together. · Test the scene setting by pressing the selected button of the wireless switch. · Set the second scene for the second scene button and select light levels and CCTs. · Once all scenes have been configured and all light levels are as expected, tap “Finish”. Step-by-step guide
31

Adding external area sensors
Purpose To control a group or a zone with one sensor, external sensors can be commissioned to a group or to a zone. The MasterConnect system offers battery-powered (also known as external ZGP sensors) as well as main-powered external area sensors that are commissioned differently. How to battery-powered external sensor · Click on the “+” on the group screen and select “Sensors”. · Indicate whether you would like to add the sensor to a zone or to the entire group. · From the drop-down list of available sensors, select the type of sensor you like to add. · Follow the instructions for setting up the sensor.
o For factory new sensors, pull out the plastic strip that shields the battery. o If the sensor is not factory new, press the pinhole reset button at the rear side of the sensor until the red and green LED have lighted up twice. · Within a few seconds the app feeds back that the sensor was found, and the sensor is commissioned automatically. · When the sensor is added, you can choose to finish the process or assign lights to a daylight area, see the next part for more explanation. Step-by-step guide battery-powered external sensor
32

Remarks battery-powered external sensor · You cannot add battery-powered external sensors to groups consisting out of wireless drivers and luminaire-integrated sensors (hybrid networks) or to groups and zones
consisting out of luminaire-integrated sensors only. · During commissioning of battery-powered sensors the devices should not be too close to the lights (between 2m and 5m distance) to avoid commissioning failures. · In case battery-powered external sensors are used for a group, and at the same time for zones of that group, the sensor(s) of the group must be added first. · With firmware 2.1.1, situations may occur when battery-powered sensors cannot be added to the same group it was previously removed from. Try using a different sensor or
to recommission the entire group. · In case a wrong battery-powered sensor has been selected in the dropdown list and assigned (e.g. the `EasyAir Occ sensor MC’ instead of the `EasyAir Occ DL sensor MC’),
other battery-powered sensors or ZPG switches that are added to the group later might not work properly. To recover from this situation the lights in the group need to be rebooted or recommissioned and the battery-powered sensors must be recommissioned. · The sum of the ZGP sensors and wireless switches in a group should not exceed 5 if the lights (wireless drivers and SNS410 MC) are on a FW 1 version, and it should not exceed 15 if the lights are on FW 2 or FW 3. To read the firmware version of the lights see chapter `Device details’. · After commissioning of a battery-powered external sensor, it is recommended to verify the successful commissioning by waiting one occupancy cycle (short timers can help for testing).
33

How to mains-powered external sensor · Click on the “+” on the group screen and select “Sensors”. · Indicate whether you would like to add the sensor to a zone or to the entire group. · From the drop-down list of available sensors, select the type of sensor you like to add. · Please wait 10 seconds for the sensors to be discovered. · Direct the light of a torchlight to the MasterConnect sensor that you like to add to a group for a couple of seconds. Alternatively, select the sensor from the “Discovered” list
and commissioning it by pressing the “+”. Choose “Finish adding” to complete the commissioning. · When the sensor is added, you can choose to finish the process or assign lights to a daylight area, see the next part for more explanation. Step-by-step guide mains-powered external sensor
34

Remarks mains-powered external sensor · You can only add mains-powered external sensors to groups consisting out of wireless drivers and / or luminaire-integrated sensors with firmware 2 or higher. · You can only add wireless drivers with firmware 2.1 or higher to daylight areas associated to mains-powered external area sensors. · Please note that in case zone-occupancy sharing in a zone configuration is disabled, MC devices in that zone will react to the mains-powered external sensors of the group but
not to the mains-powered external sensors of that zone.
36

Daylight Area with external area sensors
Purpose Lights assigned to a daylight area, dim down when the amount of daylight as sensed by internal sensor increases. You can assign daylight areas to a group and/or to a zone. Only the lights in the daylight area will follow daylight regulation. Typically, those are the lights close to the window.
37

How to · Choose “Create daylight area” at the end of the sensor commissioning or via the device info screen of the sensor from the group overview. · Assign a name for the daylight area. · Select devices for the daylight area and click next. · Choose “Calibrate and turn on” to activate the calibration process. This process can be skipped by selecting “Calibrate later” and done via the device info screen from the
group overview. · After the calibration is done, hit “Finish” to finalize the commissioning. Step-by-step guide
Remarks: · A daylight area can be in a group or in a zone but cannot include lights of different zones, or lights of a zone and lights outside that zone. · Up to 25 lights can be moved into a daylight area. · For best lighting performance, it is recommended to calibrate daylight areas at night times. · Lights can be moved from one daylight area to another and can be added or removed. But repeated actions can cause wrong light behavior. It is recommended to plan daylight
areas carefully in advance.
38

Generating QR Code
Purpose To provide lighting control access for end users via smartphone or tablet with the Philips MC control app. How to · Generating a QR code can be done on group or zone level. · To generate QR code for a zone click on the 3 dots next to the zone name and select “Generate QR Code”. · To generate QR code for a group click on the 3 group dots at the top right and select “Generate QR Code”. · Confirm the creation by choosing “Start”. · A QR is ready to be shared and can be printed for placement at the intended application area, making it accessible for scanning by an end-user. Step-by-step guide
39

Remarks · It is not supported to mix tunable white and single-color white lights in one group. · For QR generation the user needs to be in range of the lights. · Within one group QR codes should be generated either for the whole group or for one or more zones, but not for the group and a zone. · The light settings of scenes 1 and 2 that show up with the Philips MasterConnect Control app, can be adjusted by setting scenes using a 4B switch before the QR code is
generated. However, this adjustment of scenes for end user control is only possible if the firmware versions FW 1.2.12 and higher.
40

Arrange your groups
Purpose Arrange your groups in the order you prefer. How to · Open the right-hand three-dot menu and choose reorder groups. · Choose the arrangement you prefer. Step-by-step guide
41

Adding a MasterConnect gateway
Purpose Add a MasterConnect gateway to a group to connect your lighting system to the cloud. How to · For commissioning, the indicator-LED of the gateway should be red. If it shows blue or green the gateway needs to be reset first. · Before starting to add the gateway, upload the project to the cloud. · Click on the “+” on the group screen and select “Gateway”. The system scans for available gateways. · Press the “+” next to the name of gateway you’d like to add. Press “Finish adding” to finalize the commissioning. · Make sure to upload the project to the cloud once more to activate the data link. Step-by-step guide
42

Advanced gateway network settings
Purpose When using a MasterConnect gateway in a group, the network settings can be changed between static IP addressing and the default dynamic IP addressing. How to · After successfully adding a gateway, open the group overview and select the “Gateways” tab. · Select the gateway by clicking on its name and open the menu by clicking on the three dots in the top right. · Choose “Advanced settings” from the list and ethernet port that is connected to the network. · Choose between the “Dynamic (DHCP)” and “Static” IP addressing mode. · When selecting the “Static” mode, enter the network details into the input mask. · Complete the settings change by clicking “Save”. Step-by-step guide
44

Enabling automatic energy reports
Purpose When using a MasterConnect gateway in one or more groups, automatic energy report sending can be activated for a project. How to · After successfully adding a gateway and uploading the project to the cloud, open the project settings screen by clicking on the 3 dots at the top right of the project screen and
select “Project settings”. · Go to “Automatic energy reports”. · Choose “Add recipients” and fill in the e-mail address of the recipient. Press “+”. Repeat this step for any other recipient. · Complete the setup by pressing “Add” and “Save”. Step-by-step guide
45

Remarks
· The recipients for automatic energy reports don’t have to be MasterConnect users. The reports are automatically sent to the provided e-mail addresses once a month. · The report covers the information from all gateways in the project. · An energy report shows the following information per group and zone:
o Group name o Zone name o Daylight area o Number of lights o Reporting period o Power consumption current period – in kWh o Power consumption previous period – in kWh o Power consumption project lifetime in kWh o Power consumption luminaire lifetime in kWh · If no recipients are added, no energy data are stored in the cloud, and it will not be possible for a user to retrieve energy data of the periods before the feature was enabled.
46

Setting emergency light test schedules
Purpose When using emergency-enabled lights, test schedules in a zone and a group can be modified to accommodate for project requirements. How to · Enter the group overview screen. · Tap the three dots at the top right to change group test schedules or the three dots next to a zone name to change zone test schedules. · Choose “Schedule emergency tests” and select whether to change the “Function (short) test” or the “Duration (long) test”. · Change the next test date, next test time as well as the desired frequency of the test. · Press “Save” to apply the test schedules. Step-by-step guide
47

Remarks · Scheduling done on group level will override the schedule of a zone. To ensure proper scheduling, schedule of a group level first before changing the zone schedules. · Emergency test schedules are maintained on the devices. Actual start time and scheduled start time can deviate.
48

Enabling automatic emergency test reports
Purpose When using a MasterConnect gateway and emergency-enabled lights in one or more groups, automatic emergency test report sending can be activated for a project. How to · After successfully adding a gateway and uploading the project to the cloud, open the project settings screen by clicking on the 3 dots at the top right of the project screen and
select “Project settings”. · Go to “Automatic emergency test reports”. · Choose “Add recipients” and fill in the e-mail address of the recipient. Press “+”. Repeat this step for any other recipient. · Complete the setup by pressing “Add” and “Save”. Step-by-step guide
49

Remarks
· The recipients for automatic emergency test reports don’t have to be MasterConnect users. · The reports are automatically sent to the provided e-mail addresses once a month and on ad hoc basis in case of a detected failure. · The reports cover the information from all gateways in the project and shows the following information:
o Group name o Zone name o Daylight area o Device name o Test date o Test type o Test result o Error code (if any) o Error description (if any) · The ad hoc report is sent within 48 hours after detecting a failure of the luminaires.
50

Sending a reporting test email
Purpose When using a MasterConnect gateway and one of the automatic reporting features, test emails can be sent to confirm proper functioning of the report recipient list. How to · After successfully adding a one or more recipients to the reporting recipient list and saving the list, the “Send test email” option will be enabled. · Press “Send test email” and proceed by pressing “Confirm”. Step-by-step guide
Remarks · The reporting can only be used twice a day per user. · Every recipient in the recipient list will receive a test mail not just newly added one.
51

Configuration

List of Configurable Parameters
MC devices can be configured using the Philips MasterConnect app. The following parameters can be configured via the app for an entire group of lights or a single light. Note that not all parameters are available for all MC devices.
Field Task Level Field task Level can be tuned to reduce the maximum output of a luminaire to a certain percentage of the maximum power of the driver. With a manual switch override, a user could dim up to this level. Task light level is a configurable parameter and can be adjusted to a value between 1% and 100% through the app.
Eco-on Level A configurable light level to enable eco-friendly light behavior, enabling energy savings. In automatic behavior, lights switch on to Eco-on Level and it can be set to a value between Field Task level and Background Light Level.
Background Light Level A configurable light level that can be set as the lowest dim level and enables comfort for end users. This light level comes into play when the hold time has expired.
Daylight based control When enabled, daylight-based dimming is activated to further enable energy savings. With this feature, when there is plenty of daylight, the light output from the luminaire adjusts to maintain a certain light level. Daylight based control is locally done for every light within a group. For more details see page Error! Bookmark not defined..
Group/Zone occupancy sharing A configurable feature which enables luminaire-integrated sensors to share its local occupancy detection status with the rest of the group. This can enable granular dimming i.e., when presence is detected within the group, the luminaires in non-occupied areas or `elsewhere’ areas can be configured to stay at a desired light level (specified by Group light behavior parameter). In case occupancy-based control is disabled while group occupancy sharing being enabled, elsewhere occupancy is taken as local occupancy trigger.
Zone occupancy sharing This parameter appears for a Zone only when the `Group/Zone occupancy sharing’ is enabled for the parent Group. If `Zone occupancy sharing’ is enabled as well, occupancy is shared only with the other lights in the same zone; if it is disabled, occupancy is shared with the whole group.
53

Group/Zone light behavior Enables choice of light behavior for the rest of the group i.e., to determine the light levels of lights within a group that reside in non-occupied areas. Group light behavior enables granular dimming of lights within a group and brings comfort to users via lighting.
Occupancy based Control When enabled, occupancy detection takes place to control the lighting.
Occupancy mode This feature can be configured to maximize lighting control behavior with wireless switches. The mode options are auto on/off, manual on/off and manual on/auto off. For more details, see Page 64.
Hold time A configurable timer that begins once occupancy is no longer detected. Lights continue to be at Eco-on level for a period set as Hold Time, before dimming down to Background Light Level. If occupancy is detected again during Hold Time, the timer stops, and the automated occupancy cycle re-starts.
Grace fading The transition period where the lights are being dimmed down from the Eco-on light level to the Background light level. This is a configurable parameter and enables slow change of light levels for improved comfort.
Prolong time A configurable timer that keeps the lights at Background Light Level for a certain time set as Prolong Time before switching off. Prolong Time comes into effect after the elapse of Hold Time period. In case Group light behavior is set to Eco-on level, lights in non-occupied areas continue to remain to Eco-on light level.
Infinite prolong time When enabled, lights do not switch off and continue to be in Background light level or Eco on level (when set via Group Light Behavior parameter).
Color Temperature Setting of the Color Temperature for the automatic and manual on level, more details can be found in the section Tenable White Configuring CCT levels on page Error! Bookmark not defined..
Circadian Rhythm
54

This feature can be enabled or disabled, allowing a peripheral gateway to run HCL schedules.
55

Group Configuration
Purpose To customize light levels, light behavior, and response times of all lights within a group. How to · Enter the group overview screen. · Tap the second icon from the top right. · Choose “Edit configuration” and change the parameters according to your needs. · Press “Save and apply” to modify configuration. Step-by-step guide
Remarks · The lighting parameters related to the sensors are explained in section “Configuration”.
56

Zone Level Configuration
Purpose To customize light levels, light behavior, and response times of all lights within a zone. How to · Enter the group overview screen. · Tap the configuration icon next to the zone name (second icon from the right). · Choose “Edit configuration” and change the parameters according to your needs. · Press “Save and apply” to modify configuration. Step-by-step guide
57

Single Light Configuration
Purpose To customize light levels, light behavior, and response times of a single device. How to · Enter the group overview screen and select a device by clicking on the name of the device. · Tap the configuration icon at the top of the screen (second icon from the right). · Choose “Edit configuration” and change the parameters according to your needs. · Press “Save and apply” to modify configuration. Step-by-step guide
Remarks · If a device does not respond to a single light configuration setting, it is recommended to trigger “Refresh network” as described on page 90.
58

Daylight regulation
Purpose In the presence of daylight, the output from a luminaire is regulated to achieve a target light level on the working plane to save energy. The light output from the luminaire will still be bound by Eco-on level on the upper side and Back Ground level on the lower side (see figures on pages 66, 67, and 68). How to · Enter the group and configuration screen for a device, zone, or group. · Choose “Edit configuration” and change the light level parameters. · Activate “Daylight based control” and choose “Calibrate daylight sensor”. · Choose “Save and proceed” to start the calibration. · Finalize process by selecting “Finish”. Step-by-step guide
59

Remarks · Any time after configurating the Eco-on level, a calibration routine shall be initiated. When the calibration routine is run, the light level adjusts to the full light output (given by
the operating current of the luminaire) times the percentage value set for the Eco-on level. By adjusting the operating current of the luminaire and the Eco-on level in the app, a user has full control on the light level realized on the desk. · If no calibration is performed, the light output adjusts approximately to a product dependent, predefined light level (500 lux for SNS21x MC) times the value set for the Eco-on level. If the Eco-on level of SNS21x MC products is set to 80% for example, the light output from the luminaire adjusts to 400 lux on desk level. · The calibration for daylight dependent light regulation needs to be done in the absence of daylight, i.e., at night or with blinds closed. · When the calibration is run, the light output of the luminaires first goes to a low level and to a high level before it regulates to the set light level. This procedure takes approximately 1 minute for luminaire-integrated sensors, and 5 minutes for wireless drivers in combination with external sensors. · The calibration must not be interrupted. Termination of a running calibration can compromise a following calibration process. In case the process has been accidentally terminated, please wait 7 minutes before restarting the calibration. · The lux levels are an estimation for a typical office configuration; the precise level depends on the amount of light reflecting surfaces in the field of view of the sensor. With different reflecting surfaces below the luminaires, e.g., light desks or dark carpets, the light output of the luminaires can be different. If the light level is not as wanted, please do the calibration, and adjust the light level via the Eco-on level. · To determine the optimum Eco-on level it is recommended to turn off daylight regulation temporary before calibration, and to measure illuminance as a function of Eco-on level. · Daylight areas must be created before switching on Daylight based control. · In case daylight-based control is disabled, luminaires with SNS21x MC switch on at field task level after a power cycle. This is different to SNS21x MC which switches on at Ecoon level. After the first occupancy cycle, SNS21x MC and SNS21x MC are aligned, and both go to Eco-on when presence is detected.
60

Tunable White Configuring CCT levels
Purpose When SNS21x MC is used with a FlexTune SR driver or when the wireless MC FlexTune driver is used, the Color Temperature (CCT) of the luminaire is an additional configuration parameter. This applies to the automatic/manual ON level as well as the two scene recall levels (short press of the scene buttons). In addition to the scene recalls, press, and hold of the Scene-1 button will gradually increase the CCT and press and hold the Scene-2button will gradually decrease the CCT. How to configure CCT for AUTO-ON · Configure the color temperature (CCT) for the automatic/manual ON-level in the “Edit configuration” screen. Step-by-step guide configure CCT for AUTO-ON
61

How to configure CCT for scenes · Configure the color temperature (CCT) for the Scene buttons in the “Configure a scene” flow as shown below. This can be done for each of 2 the scene buttons on the 4 button
ZGP switch. The Brightness can be configured as well. Step-by-step guide configure CCT for scenes
Remarks: · When configuring a scene with a four-button switch, two sliders appear on the screen: one for light-level setting and one for CCT setting. While adjusting the light level, the
system directly responds. While adjusting the CCT, the system does not respond immediately, and the set values appear after “save and apply” the configuration. · Mixing Tunable White fixtures with non-Tunable White fixtures in one group is not supported.
· In case different types of tunable white fixtures are mixed in a group, e.g., when combining TW point drivers with SNS41x + TW linear drivers, the system with smallest CCT
range must be commissioned first (TW linear driver in this example) to avoid issues at the edges of the CCT range.
62

Occupancy sharing within a group or a zone
Purpose Individual lights with SNS21x MC sensors within a group or a zone can share occupancy. If one light is triggered, it also triggers the other lights in the group or zone. How to · If `Group/Zone occupancy sharing’ is enabled, the light shares occupancy. · If `Zone occupancy sharing’ is enabled as well, occupancy is shared with the other lights in the zone only; if it is disabled, occupancy is shared with the whole group. Step-by-step guide
63

Occupancy modes
This feature can be configured to maximize lighting control behavior together with wireless switches. The mode options are auto-on/auto-off, manual-on/manual-off and manualon/auto-off. Auto on/Auto off Lights are switched on and off automatically based on occupancy detection and timer settings. This is the default operating mode for the sensor. In this automatic behavior, lights always switch on to Eco on level. For more details, see Figure 1 on page 65, Figure 2 on page 66, and Figure 3 on page 67. Manual on/Auto off Lights are turned on with a manual command from a wireless switch. A manual on command switches on the lights to Eco-on level and can be further tuned up to Task Level. Lights turn off automatically once vacancy is detected, and timers expire. This mode is typically selected to achieve maximum energy savings. For more details, see Figure 4 on page 68. Manual on/Manual off Lights are turned on and off manually through a wireless switch. This is typically used in applications which just need wireless manual control for switch on/off or dimming functionality. This setting must be selected for a MasterConnect System consisting of Xitanium Wireless Drivers only.
64

Auto-on / Auto-off mode
Figure 1 shows the occupancy cycle during automatic light behavior with Eco-on Level set lower than Field Task Level. On occupancy detection, lights switch on to Eco on level. Once vacancy is detected, Hold time starts. During Hold time, lights remain at Eco on level and then dim down to Background light level, with a configurable Grace Fading time. Lights remain at this dim level until Prolong Time expires; after which lights switch off.
65

Auto-on / Auto-off with Daylight Dimming
Figure 2 shows how daylight dimming takes place during Auto on/Auto off mode. Once occupancy is not detected anymore, the timers (Hold time and Prolong time) start. Once the timers expire, lights switch off.
66

Auto-on / Auto-off with Manual Override
Figure 3 shows how daylight dimming takes place during Auto on/Auto off mode and the effect of manual overrides. In case of manual override with a switch, lights can be dimmed up or down between the Task Level and Minimum dimming level. When no occupancy is detected anymore, the timers (Hold Time and Prolong Time) get started. In case occupancy is re-detected during Hold time, the existing light behavior continues, and the timers are reset. In case occupancy is re-detected during Prolong Time (or after), automatic light behavior starts, and the timers are reset (as shown).
67

Manual On / Auto Off
Figure 4 shows how daylight dimming takes place during Manual on/Auto off mode. Occupancy detection starts to determine the light behavior soon after manual trigger.
68

Manual On / Manual Off
Figure 5 shows how daylight dimming takes place during Manual on / Manual off mode. Occupancy detection starts to determine the light behavior soon after manual trigger.
69

Summary of Configuration Parameters

Parameter

Description

Range*

Field Task Level Eco-on level

Maximum dim level Switch-on light level

1% – 100% 1% – Field Task Level

Background light level Daylight based control
Occupancy mode Occupancy based control Group / Zone occupancy sharing Zone occupancy sharing

Non-occupied light level

1% – Eco-on Level

Activate or deactivate daylight regulation
Mode selection for customized light behavior
Activate or deactivate occupancy detection Activate or deactivate sharing of local occupancy

Enabled / Disabled Auto on / off Manual on / off Manual on / auto off Enabled / Disabled
Enabled / Disabled

Select occupancy on zone instead of group level

Enabled / disabled

* Range can differ based on the product combination in a group.

1 Luminaire-integrated sensors

Xitanium MC Driver SNS41x MC

Parameter

Description

Range*

Group / zone light behavior Hold time Grace fading Prolong time Infinite prolong time Color temperature Circadian Rhythm

Light level of non-occupied lights when occupancy is shared by other lights.
Timer for the eco-on level after the last movement has been detected.

Background light level / Eco-on level
2 100 min (1) 6 100 min (2)

Dimming transition time from the Eco-on to the background light level

1 25 sec

The time for which lights remain at the background light level.

2 100 min

When enabled, lights continue to stay on and do not switch off.

Enabled / disabled

White tone of tunable white lights when switching on.
This feature allows a peripheral gateway to run HCL schedules.

Driver range Enabled / disabled

Energy Reporting
The Philips MasterConnect app can be used to retrieve energy usage reports at group level. Each reading stores the time stamp along with the total energy (in kWh) used by all the light fixtures in the group. The screen displays the previous and current readings along with the energy used for this time interval. The interval data provides a quick snapshot for the energy consumed for a desired period, for example, 1 hour or 1month between readings. All the past reports are also stored in “History” and can be retrieved by the user at a later point. Light fixture energy data is for this report is read from the real measured energy counters of the Xitanium SR Drivers connected to EasySense SNS21x MC. Following parameters are displayed: · Previous Reading: Time stamp (date and time) and the total energy used by the group of lights at the time of last reading. · Current Reading: Time stamp (date and time) and the total energy used by the group of lights at this reading. This number is set to zero at first commissioning of the group. · Interval: The time interval between above two readings and the energy used by the group of lights during this period. How to · Open a group and select the menu via the 3 dots in the top right. · Choose “Group info” from the list. · Choose “Generate new report” to read out the energy data from the device. · Choose “View report history” to export data as a csv file.
71

Step-by-step guide
Remarks · For SNS41x MC, and wireless drivers, energy reporting is limited to 20 devices. · In rare cases a report may fail to capture all the devices in the allotted time. If this happens, we recommend waiting for a few minutes and generating another report. The
“current reading” number will always be correct when all the devices are captured. The Xitanium SR drivers in the fixtures maintain a continuous and accurate counter for energy used. · If the app indicates that the reported energy is not complete because a device has been missed, it is recommended to trigger “Refresh network”.
72

Device claiming
· MasterConnect devices out of the factory start out with open interfaces for BLE and Zigbee communication for easy set up. · Zigbee device communications become encrypted with secret keys and thus, secure on the first commissioning of MasterConnect devices into a project. · Once commissioned, the MasterConnect devices from a project will only be visible for users that claimed it first (and for invited users). Remark · Due to the open Zigbee interface, the MC devices may join another open (rogue) Zigbee network if significant time elapses between installation of luminaires and
commissioning with the Philips MasterConnect app. In this case, the app will still discover these devices and allow commissioning of these devices into a proper MC network.
73

Maintenance

Save a configuration profile
Purpose Profiles are used for saving a combination of configuration parameters (e.g., light levels, occupancy and daylight control and timers) for specific applications. How to · When changing a configuration instead of “Save and apply” select “Save as a new profile” and give the profile a name and optionally a location description. · To recall a profile, click on “Choose from profiles” instead of “Edit configuration”. Select the right profile from the list and tap “Choose”. Step-by-step guide
Remarks · Editing and deleting profiles is not possible. To store a new configuration a new profile should be made. · Profiles are stored locally on a phone and not backed up in the cloud. · It is recommended to provide meaningful names to the profiles based on associated application e.g., private office, corridor, classroom etc. for easy re-use at a future point.
75

Project Backup and Access Sharing
Purpose The Philips MasterConnect app offers the capability to store user created projects in the cloud. This capability allows users to access their projects (even when a phone is lost) and give project access to specific contributors. Definitions Upload: · Local data of a project are transferred to the Cloud. · When a Project has been created or edited, the app will ask if you want to upload the Project. Each time you upload a project the version in the cloud will be overwritten. Download: · Cloud data of a project are transferred to your device. · Each time you download a project the local version will be overwritten. Sync: · The app checks the local and the Cloud data of your projects. Projects that have an updated version in the Cloud will be downloaded, projects that have an updated local
version will be uploaded.
76

How to activate project backup feature · To use project backup, enter the “Settings” from the right-hand menu. · Choose “Project backup” and enable the “Sync project with the cloud” option. · On iOS, please fully close and reopen the app to apply the change. Step-by-step guide activate project backup feature
77

How to upload a project · When a project has been created or updated, the user will be prompted to upload the project to the cloud. · Click on upload to transfer changes to the cloud. This will overwrite the previous version of the project in the cloud. Step-by-step guide upload a project
78

How to invite a contributor · After uploading a project, open the project edit screen by clicking on the 3 dots at the top right and selecting “Edit project” from the list. · Choose “Invite more people” and enter the email address of the user. · Confirm by clicking the plus and invite. · Save the changes by choosing “Save”. Step-by-step guide invite a contributor
79

How to download a project · When opening the app or changing to a project, the user will be prompted to download changes that are available in the cloud. Step-by-step guide download a project
80

Remarks General: · Device Wi-Fi must be enabled (but commissioning can still take place offline). · The Internet connection must be stable during synchronization. If the upload fails due to a broken connection, it might be needed to log out from the app, and in again, to
recover the process. · Do not reset a device that is saved in the cloud. It is not removed from the project but cannot be controlled anymore. · To retrieve lost devices, please contact your local account manager for support.
Contributors & accounts: · When creating a project with a newly registered user, it may take up to 30 min to activate the project backup feature. · Only users who have already registered for Philips MasterConnect app can be added as contributors. · A contributor who invites a new contributor shall not invite his own account which is currently used. · If a project that has been uploaded with app version 2.4 or higher is shared for the first time with a contributor who still uses app version 2.3 or older, he/she does not get to
see the project for download. He needs to update the app first.
Projects: · Up- or downloading projects with daylight areas is only possible with app version 1.9.0. or newer. · Profiles are not part of the cloud back up process. · Scene parameters are stored in the devices, however, parameter settings from the app are not backed up in the cloud. · Simultaneous editing the same project on different phones is not allowed. · When another user has modified a joint project, a notification about the changes only appears when restarting the app. · Projects can only be deleted when all contributors have been removed first from the contributor list.
81

Syncing & Sharing: · It is recommended to always check if uploading, downloading, and syncing have been completed successfully. Downloading of an incomplete project can result in loss of
project data when changes are applied. · Energy reports are not backed up in the Cloud. Therefore, after downloading a project from the Cloud, previously generated energy reports will not be shown. Nevertheless,
when generating a new report, this report will be based on all previously generated energy data and provides accurate information. · Project backup sometimes fails. If it continues to fail after a retry, please use the “Report a Problem” feature (see page 103) to send the app data logs to the MasterConnect
Team for analysis. · The time for syncing depends on the number of devices in a project (typically 4 seconds per device). Please remain patient. · Ensure the screen timeout/auto lock is not activated during Syncing. Please adapt the phone settings accordingly. · Project size must not exceed 500 devices. · Do not use another app during up- or download. · When deleting or adding devices to a group, always sync (upload) the project to the Cloud. This syncing must be done every time a change is done per group. Make sure the
project is synced successfully by checking the syncing notification. · After sharing access to a new contributor, it can take some minutes for the new contributor to get the project fully downloaded. · If “Distinct cloud and local names” is enabled, each contributor of a project can adjust a project name. This name can differ from the one originally used when the project was
created and backed up in the cloud at that moment. Each contributor can use a different name for the same project.
Working in one project simultaneously: · You cannot work simultaneously in one project. If installers want to work simultaneously in one building, we suggest the following way of working: · User 1 creates project “Floor 1” and adds User 2 as contributor. User 1 commissions project “Floor 1”. · User 2 creates project “Floor 2” and adds User 1 as contributor. User 2 commissions project “Floor 2” · If needed more projects and users can be added. · All users are continuously updated about the status of all floors and work on their own projects only. · When one user uploads a project, this project is locked for downloads and uploads by any other user until the upload was completed successfully. This project lock feature is
preventing data corruption and data loss. When a user is presented with a project lock message, it is recommended to wait and try again at a later stage.
82

Remove components from network standard method
Purpose Each MasterConnect components is secured and cannot be used by another user that has not access to the project. In case any adaptations are needed on an existing installation, these MasterConnect wireless components need to be removed from the app. Only then, the removed devices can be used in other groups, projects or by other users. Either entire group or single devices can be removed via the Philips MasterConnect app.
How to · Remove all switches and battery-powered sensors
o In the group overview, click on the three dots and choose “Remove switches and ZGP sensors”. · Remove individual switches
o If ZGP switches are used in groups with FW 2.0.21 or higher, they can also be removed individually. o Click on the three dots next to the switch name and choose “Remove switch”. · Remove a single light o In the group overview, choose the light to be removed by clicking on the three dots next to the light and choose “Remove from group”. o The intensity of the light goes to full light level. Repeat this step for other individual lights in the group. · Remove a group o In the group overview, click on the three dots and choose “Remove group”. As feedback, the intensity of all lights goes to full light level. · Remove a battery-powered sensor o If battery-powered sensors are used in groups with FW 2.0.21 or higher, they can also be removed individually. o Click on the three dots next to the sensor name and choose “Remove sensor”. o A sensor can be reset as indicated in the sensor manual. There is a reset button that must be pressed for several seconds. · Remove a mains-powered sensors o Click on the three dots next to the sensor name and choose “Remove sensor”. · Remove a MasterConnect gateway o In the group overview choose the MC-GW to be removed by clicking on the three dots next to its name and choose “Remove this gateway”.
83

Step-by-step guide switch and sensor removal (all in one group) Step-by-Step guide single switch removal
84

Step-by-step guide single light removal Step-by-step guide group deletion
85

Step-by-step guide single external battery-powered sensor Step-by-step guide external mains-powered sensor
86

Remarks · When Remove Group does not finish in first attempt, advise to make a second attempt to finish. · For the removal of switches all devices of the group controlled by a switch need to be in range of the smartphone. · Please, make sure that all lights connected to a switch or ZGP sensor are powered on when the switch or sensor is removed. · When trying to remove an mains-powered external sensor on firmware 3.2 from a group while an open Zigbee network is in the environment, the sensor might get removed
without the app being able to confirm the deletion. In case this happens, please try again and remove the sensor locally from the app as prompted by the app.
87

Remove components from network Safe Mode
Purpose In some cases, for instance when a cell phone is lost, components cannot be removed via the standard method. In that situation, lights can be reset via the Safe Mode. How to The luminaires must be powered ON for more than 15 seconds. · Power OFF mains for more than 10 seconds but less than 15 seconds (disconnect device form mains). · Power ON mains for 2 to 3 seconds (reconnect device to mains). · Repeat above process for 4 more times. · On the 5th cycle, leave the fixtures powered ON at the end. You should see a short dim-down/dim-up signal (in case of SNS21x MC). Sensors are now in Safe Mode. · Scan with “Device Maintenance” in the “Settings” section of the app to discover the sensors that are now In Safe Mode and Reset them, see screenshots below: Step-by-step guide
88

Remarks · In case a project is on several phones, a light reset on phone A via Safe mode is not automatically removed from the project on phone B. If that light is recommissioned in the
project using phone B, it is needed to reapply the configuration to the light for proper light behavior.
89

Refresh network
Purpose In some cases, lights may not respond to configuration and energy report generation commands. Perform a refresh network to get the latest device data. How to · In the group overview, click the three dots and select “Refresh network”. · Finish the process by clicking on “Continue”. Step-by-step guide
90

How to check for app version
Purpose To look up the version number of the Philips MasterConnect app that is used. How to · Open the right-hand menu and choose settings. · The version number can be found at the bottom of the screen. Step-by-step guide
91

Set your language
Purpose Change the app language for simplified app use. How to · Open the right-hand menu and choose settings. · Click on “Settings” and choose “Language”. · Choose the language that you prefer. Step-by-step guide
92

Device details
Purpose All information of a device can be obtained. How to · Tap on the name of the device you want to learn more about. Step-by-step guide
93

Over the Air update
Purpose To enable a firmware update of MasterConnect components such as luminaire-integrated sensors via the app. Such updates may include new released features, security, and bug fixes. How to · Open the device details of a device and click on “Update”. · Select the latest version from the list and choose “Finish” after the update has been completed. Step-by-step guide
94

Remarks · It is recommended to restart the smartphone to clean the internal BLE memory before starting the BLE upgrade process. · Do not interrupt the upgrade process. Keep the smartphone in close reach of the device getting upgraded. · The upgrade is done at device level. · If an upgrade fails, an error message is displayed. Please try again. · It may happen that the firmware is properly loaded but the new firmware is not yet shown on the device info screen. By clicking “check version” the app connects to the device
and corrects the display if needed. · After firmware upgrade from FW 1.0.5, 1.1.11, 1.1.16, 1.2.12, 1.2.16 to any higher FW-version, recommissioning is required to make use of the latest functionality and to avoid
unexpected behavior. · Before updating from firmware 1 to firmware 2, please remove all switches, and commission them again after the entire group has been updated. · If the MasterConnect system is used with a supported peripheral gateway it is also possible to distribute a firmware upgrade to the sensors via the gateway. Please contact
your Signify account manager for support. · If group light behavior is set to “Eco-On level”, a firmware upgrade via the gateway may change the group light behavior to “Background light level”. To correct this, please
change the group light behavior to “Background light level”, apply the settings and change it back to “Eco-On level” afterwards.
95

Account deletion
Purpose This section describes how you can delete an account form the Philips MasterConnect App. How to · On one of the project screens, press the three lines in the right bottom corner · Press “Account details” and select “Delete account”. · Please review any warnings and if you understand and accept them, press “Continue” and “Confirm” · Check your email for a six-digit verification code, press “Next”, and fill in the code · Your account will be deleted, and the app will confirm it has been deleted successfully. Press “Dismiss” to return to the login screen Step-by-step guide
Remarks · On iOS systems, ensure that the MasterConnect app does not go to background during the account deletion process. Do not use another app and take care that the screen
time out/auto lock is not activated.
96

Troubleshooting

Known Limitations
These limitations are valid for FW version 2 or higher when combining luminaire-integrated sensors with wireless drivers in one network:
· Luminaire-integrated sensors can only be added in the same group as wireless drivers and SNS41x when using firmware 2 or higher. · You cannot create zones consisting out of wireless drivers and luminaire-integrated sensors. This will be enabled with a future app update. · You cannot add ZGP sensors to groups consisting out of wireless drivers and luminaire-integrated sensors. This will be enabled with a future app update. · Ensure that all areas are well covered with occupancy sensors. When using AUTO ON/OFF, the automatic occupancy cycling is based on the detection of luminaires with an
integrated sensor. In case only areas with wireless drivers are occupied, the group might turn off after the timers have passed. · When combining wireless drivers and luminaire-integrated sensors in one group, daylight dependent regulation will only take place on luminaires with an integrated sensor.
This will be changed in a later app release. · The default settings of a group consisting out of luminaire-integrated sensors and wireless drivers can be different from what you are used to. Please verify the configuration
matches with the project requirements after commissioning. If certain parameters are different or cannot be changed, please try to re-commission the entire group. · After an update to firmware 2 from firmware 1, recommissioning is required before starting a combined network out of luminaire-integrated sensors and wireless drivers. · Mixing TW and not-TW is not supported.
These limitations are valid for FW version 2.0.21 (SNS21x, SNH21x), 3.1.31 (SNS21x and SNH(B)21x), 1.2.16 (WDR and SNS41x), and 2.1.3 (WDR and SNS41x):
· Occasionally, project backup can fail. If it continues to fail after a retry, please use the “Report a Problem” feature (see page 103) to send the app data logs to the MasterConnect Team for analysis.
· When Circadian Rhythm is enabled AND infinite prolong time is selected, unexpected light behavior may occur, lights may not dim down to background light level. · Mixing TW and not-TW is not supported. · A mix of firmware versions may cause unpredicted behavior. · In case of an open Zigbee network close to luminaire-integrated sensors, the out-of-the-box sensor behavior may stop working, and the lights remain in their latest state. See,
feature “Out-of-the-box sensor behavior” in the Troubleshoot Tips table from page 100 on. · In case occupancy sharing is disabled, prolong time is 4 minutes longer than indicated in the app. With firmware 2.1.1, situations may occur when sensors cannot be added to
the same group it was previously removed from. Try using a different sensor or to recommission the entire group.
Remark
98

· In the annex 3, you can find a complete overview of the known limitations for earlier versions of the firmware. · Always use the latest app version.
99

Compatibility matrix

sensors

Battery- Wireless driver & Luminaire-integrated

Luminaire-integrated sensors

Wireless driver & nodes

Battery-powered sensors Mains-powered sensors

FW 1.0.x 1.1.x 1.2.x 2.0.x 3.0.x 3.1.x 3.3.x 1.1.x 1.2.x 2.0.x 2.1.x 3.1.x 3.3.x

n/a

3.2.x

3.3.x

1.0.x

1.1x

1.2.x

2.0.x

3.0.x only motion detection
3.1.x

3.3.x

1.1.x

1.2.x

2.0.x

only motion detection

2.1.x

3.1.x

3.3.x

nodes

sensors

powered

n/a
3.2.x only motion detection
3.3.x

compatibility based on luminaire firmware version

Mainspowered sensors

only motion detection

100

Troubleshooting Tips

Feature Login
Commissioning RSSI List based
Commissioning Torchlight List based Adding a wireless switch
Group removal after commissioning

Potential issue

Advised workaround

Occasionally an error message is received, or no confirmation code is received via email.

A re-try with a new account with same email address and username typically resolves the problem Otherwise re-try with another email address

At times, app reports an error

A re-try typically resolves the problem Ensure the smartphone is within range during commissioning Ensure the phone in use is from the recommended phone list

At times, commissioning using torchlight is not always successful

Wait for additional 3 seconds after the 2nd beep before proceeding to the next light

Switch commissioning fails

For non-Philips switches, remember to exit the linking mode on the switch by pressing any other button on the switch (as given in the switch instruction sheet). Test the switch by pressing ON/OFF buttons Ensure ZGP switch commissioning is carried out as described by manufacturer. Also available on our website Make sure only 1 brand of switches are used within a group

Removal on group level may not fully succeed. Occasionally a device may A complete reset is advised via the Safe Mode. Please contact your OEM

not get reset leading to unsuccessful re-commissioning thereafter

or Philips representative / customer care for further support.

A luminaire does not pick up the group configuration settings.

Luminaire does not show the right light behavior of the group

Always verify that all luminaires operate according to new settings. If not: This single luminaire must be reconfigured via a single device configuration.

101

Configuration

Some luminaires do not take over the configuration that is sent, without a warning in the app

The configuration of lights with Philips MasterConnect app can be impacted by other strong wireless traffic. Switch off RF-devises, like for example Wi-Fi routers, close to the system during the configuration process. Always verify that all luminaires operate according to new settings. When the configuration is ready the RF devices can be switched on again

Commissioning of ZGP sensors Sometimes occupancy detection does not work

Recommissioning of the ZGP sensor: via the sensors tab on group level choose “remove switches and ZGP sensors”. It is not possible to remove a single ZGP device only. Do a hardware reset of the removed ZGP sensor(s) via the button at the rear side. Refresh network, see below in the next feature.

Refresh network

A light doesn’t respond to a single light configuration setting. In test mode individual lights don’t respond to app commands (i.e., blinking), while with group commands all lights still react.
Energy reading is not complete, misses a light.

It can happen that in a mesh network one of the lights changes its short address. By the action `Refresh network’, this is corrected.

Remove Components from network Safe mode

The power cycling procedure does not work

Please, reach out to your local account manager for further assistance.

Out-of-the-box sensor behavior As our sensors include an auto-joining feature, they will join open Zigbee networks in their surroundings. Once connected, sensors will wait for commands of that gateway and remain in their last state (ON or OFF). This behavior is according to our specification but might come across as unintentional if not known. Closed Zigbee networks (normal state) do not affect the behavior.

Commission the sensors using the Philips MasterConnect app, finish the commissioning using the gateway (if applicable), or close the Zigbee network in the area and restart the sensors.

102

How to get support
Purpose In case you run into issues, you can use the “Customer Support”-button to report and share relevant data with Signify. First line of support is via a call. Second line of support is via mail. How to – first line of support via a call · Select the right-hand menu and choose “Customer Support”. · Choose “Call us”. · Choose your region. · Choose your country. · The telephone number will appear on your screen, and you can call the help desk. Step-by-step guide
103

How to – second line of support via mail · Select the right-hand menu and choose “Customer Support”. · Choose “Report a problem”. · You will be advised to call first for assistance, if you want to report via mail, press “Continue”. · Describe the issue, and, if you received a ticket number, please fill it in. Press “Continue”. · Select an email option for sharing the report with mcsupport@signify.com. · Send the email with the description and relevant data to Signify. Step-by-step guide
Remarks · On iPhones sending of error reports is only supported through the iPhone’s native email app. If you use other email apps like Outlook and don’t have a native email account
yet, we recommend adding it via your iPhone settings. Once configured, the report can be sent directly without additional setup.
104

Annex 1: Device renaming in the factory

Purpose Lights can be given a customized name via a registry in the driver memory bank with MultiOne. Use your own brand and luminaire name instead of default product names. The name is programmed inside the SR or wireless MC driver using the existing tools for MultiOne by Signify.

How to

· Use the Luminaire identification field that is part of Luminaire Info (DALI part 251)

· This Luminaire identification field is available for SR drivers and wireless MC drivers

· Use MultiOne to write a custom name into the driver. Following structure needs to be followed:

o Custom name

o Delimiting character:

^ or ;

o Example:

Brand Spot 930;

Remarks

· This option is available for SNS21x MC and SNH(B)21x MC with FW 2.0.20 or newer

in combination with D4i SR drivers.

· Custom naming via driver is fully optional. When field is not filled (properly),

the app will show the default product name.

· Please choose one delimiting character:

o Changes on Bluetooth interface (MC app):

;

o Changes on ZB and BLE interface (MC app or GW): ^

· Please only use universal characters. Avoid symbols and special characters.

· The length of the custom name in the MC app is limited to 15 characters.

Longer names can be used for the ZB interface and will be shortened

by the MC app if needed.

105

Annex 2: MasterConnect in combination with 3rd party gateways
Purpose Enabling projects with a coordinating role of a gateway and dashboard. How to · The Philips MasterConnect system can be setup in standalone way and works without a gateway. Out of the box,
MasterConnect products can be commissioned via the Philips MasterConnect app but are also open for joining Zigbee networks of gateways from partner companies like ubisys technologies GmbH. · To commission Philips MC wireless products with partner gateways, software and apps of the partners need to be used. · Please refer to gateway suppliers for more information on how to set up a system with their gateway.
106

Annex 3: Partner gateway – ubisys G1 gateway
Human Centric lighting feature
One of our supported gateways is the ubisys G1 gateway. Adding this gateway can enable further features for MasterConnect including running Human Centric Lighting (HCL) profile to mimic the changes in color temperature of natural sunlight. The default profile “HCL for Philips EasyAir SNS21x MC” starts with warm white light in the morning goes to cold white at mid-day and becomes warm white in the evening again. It is also possible to set customized lighting profiles with the Ubisys app: sample points (time, CCT and intensity) can be set throughout the day. In between those points CCT and intensity change gradually. When using a customized profile make sure that in the ubisys app the steering interval is set to 30s and that the parameter “suppress insignificant changes” is put to “no”. The gateway needs to be commissioned in MasterConnect. After commissioning the parameter “Circadian Rhythm” needs to be enabled. How to · Click on the “+” on the group screen and select “Gateway”. · Choose the gateway you want to commission. · Select the right gateway from the scan list by clicking “Add” and “Finish adding”. · Enter the group configuration screen and choose “Edit configuration” · Activate “Circadian Rhythm” and confirm by pressing “Save and apply”. · Follow the steps shown below to activate the profile in the ubisys app.
107

Step-by-step guide adding a peripheral gateway and changing the configuration
108

Step-by-step guide ubisys App
109

Remarks · When working with a peripheral gateway in combination with a Circadian Rhythm lighting profile, please work as follows: first add all the lights that should be included, then
add the gateway. If you want to add lights later, please remove the gateway, add the new lights, and add the gateway again. · During commissioning of the gateway in MasterConnect the gateway needs to be in Bluetooth range of the smartphone, i.e., within 5m. · On the Ubisys gateway an automatic update of sensor firmware via the gateway is enabled by default as soon as the gateway is commissioned. So, if the gateway in a
MasterConnect system is connected to internet, the firmware upgrade can happen without control of the user. This is an unwanted situation and can result in unexpected light behavior because the Philips MasterConnect app is not updated automatically either. Therefore, it is recommended to disable automatic firmware upgrade via the gateway, see annex on page 105. · When using a customized profile make sure that in the ubisys app the steering interval is set to 30s and that the parameter “suppress insignificant changes” is put to “no”. · Circadian does not work as expected in combination with Infinite Prolong time.
110

Disabling automatic firmware upgrade via the ubisys gateway
Automatic firmware upgrade needs to be disabled after the Gateway has been commissioned. How to · Gateway and smartphone/laptop need to be connected to the same local network, e.g., via a router. The Gateway is connected via an ethernet cable. · The Gateway will then be visible on the Network on Windows explorer. · By double clicking on the Gateway icon, you will be taken to the gateway’s website. Note: if no password has been set, it is “admin”. · At the tab “Updates” please uncheck “Use this gateway to supply the system with updates”. Step-by-step guide
111

Zigbee OTA via gateway
When using a gateway in a peripheral mode the gateway can be used to distribute firmware updates to device. After updating using a gateway, please confirm the update in the app. How to · Open the group that has been updated via the gateway. · Choose the “Gateway” tab and click on the three dots next to the gateway name. · Select “OTA via Gateway” and choose the new firmware version from the list. Confirm by pressing “Save”. Step-by-step guide
Remarks · See remarks in the “Over the air update” section of this manual. · In case group actions fail after the Zigbee OTA, please perform “Check version” on the device detail screen to verify the success of the Zigbee OTA.
112

Remove a Gateway
When a gateway needs to be removed from a group. How to · In the “Gateway” section of the group overview, click on the three dots next to the gateway. · Choose “Remove this gateway”. · Reset the gateway as described by the gateway instructions. · Choose “Check status” to confirm the gateway is reset and select “Finish” to complete the process. Step-by-step guide
Remarks · Before removing the gateway from the group, Circadian Rhythm shall be set to “Disabled” in the Group Configuration.
113

Annex 4: Known Limitations previous Firmware versions

Known Limitations

Luminaire-integrated sensors Wireless drivers and nodes

1.0.5

1.1.11

1.1.16 1.2.12

2.0.20 2.0.21

1.1.12

1.2.14 1.2.15

1.2.16

2.1.1
2.1.1 2.1.3

3.0.24 3.0.29 3.1.29 3.1.31
3.1.29 3.1.31

When occupancy sharing is disabled the sensors of a group still do not work standalone: all lights of the group still go to Eco-on level when occupancy is detected. Only granular dimming does not occur.

When daylight-based control is enabled, the following limitations apply: The calibration routine for daylight regulation takes longer (about 7 minutes) than with higher firmware versions. For luminaires, where the calibration fails due to too little light reflections from dark surfaces (e.g., a dark grey carpet) in the field of view of the daylight sensor, the luminaire goes to maximum light output. In contrast to higher firmware versions the light level is not capped at the Eco-on level. If this results in luminaires with too high light output, we recommend 2 disabling daylight regulation of these luminaires. In case daylight control is enabled, a double `ON’ press on a wireless switch is needed for lights to go to Eco on level. The 1st button press brings the lights to Background light level; a 2nd button press will bring the lights to Eco on level. Two occupancy triggers are needed for the lights to go to Eco-on level. In case people enter a room the luminaire that triggers occupancy first goes to background light level only while the other luminaires go to Eco-on when they trigger presence too. Within some minutes the light of the first luminaire slowly increases to Eco-on.

When group occupancy sharing is disabled on a single device, that device does not go to BG but remains in Eco during prolong time.

The reset of components from the network in Safe Mode as describe in our manual is not possible. For alternatives, please contact your local account manager.

5 Tunable White is not supported.

6 Occupancy sensing is only possible per group (so, not per zone).

7 Circadian Rhythm is not supported yet.

8 Daylight harvesting function is not supported in the Manual ON/OFF mode.

If Occupancy Based Control is disabled for one or more devices (e.g., for lights next to a fan), automatic light behavior is

incorrect after: short press “On” or short press “Off” on the switch added to the group.

Short press “On”: Lights with Occupancy Based Control disabled will remain at Eco-On level, the other lights in the group will remain in Background level when there is no occupancy.

Short press “Off”: All lights remain off, even when there is occupancy detected after Hold Time and Prolong Time expired.

The system can be recovered either by a long press (dim up / dim down) or a scene recall on the switch.

114

Known Limitations

Luminaire-integrated sensors 1.0.5 Wireless drivers and nodes

In the Auto ON/Auto OFF mode, pressing the switch to turn OFF lights may delay Auto ON. on automatically at all. Manual ON press is suggested to turn the lights back ON.

Sometimes

lights do

not

turn

11 The use of a peripheral gateway for Circadian Rhythm can result in unwanted light behavior.

If a group contains two zones and a separate switch is commissioned to each zone, the following behavior can be expected:
12 · 4B-switch of zone A, press “on”: zone A goes to Eco On, zone B to BG. · 2B-switch of zone B, press “on”: zone B goes to Eco On, zone A to BG. 4B-switch of zone A, press “scene”: zone A goes to scene setting, zone B remains off.

13 Wireless drivers with FW 1.1.12 do not work with stand-alone ZGP sensors.

After commissioning of lights with wireless drivers or with SNS410 MC radio nodes, it can happen that during a period of 3

minutes some of the lights turn off. This behavior is not desired and will be corrected. In the meantime, a message pops in the Philips MasterConnect app: “Some lights can turn off, please turn on via the `Test mode’ sliders in the app.” After

confirmation, the `Test mode’ screen opens automatically, and the lights can be put in the same state.

When a gateway with an automation profile is added otherwise, unpredictable light behavior will occur.

to a

group, circadian

rhythm

must

switched on

the

MC-app,

16 Adding and removing individual lights from daylight area is not possible. The daylight area needs to be recreated.

17 Group/zone size beyond 25 devices, coupled to a ZGP sensor or switch is not proven to be reliable.

Project backup sometimes fails. If it continues to fail after a app data logs to the MasterConnect Team for analysis.

retry,

please use the

“Report a Problem”

feature

send

the

When Circadian Rhythm is enabled AND not dim down to background light level.

infinite prolong

time is selected,

unexpected

light behavior may occur;

lights may

20 Wireless drivers and SNS410 CANNOT be added in the same group as SNS210.

21 After ZigBee/BLE OTA coming from an older firmware, recommissioning is needed.

22 Mixing TW and not-TW is not supported.

23 A mix of firmware 1 versions may cause unpredicted behavior.

With an open Zigbee network close to luminaire-integrated sensors, the out-of-the-box sensor and the lights remain in their latest state. Find more info in the Troubleshoot Tips section.

behavior may

stop

working,

1.1.11

1.1.16 1.2.12

2.0.20 2.0.21 2.1.1

1.1.12

1.2.14 1.2.15

1.2.16

2.1.1

3.0.24 3.0.29 3.1.29 3.1.31

115

Annex 5: MasterConnect LED Lamps specifics
Remarks firmware support · MasterConnect LED Lamps running on firmware 6.5.3 and 6.6.16 can be commissioned and used in combination with the Philips MasterConnect App starting with app version
1.8.0. · Any other firmware versions of the MasterConnect LED Lamps are not supported to be commissioned and used in the Philips MasterConnect App.
Remarks – Commissioning · Lights with integrated MasterConnect LED lamps can only use the list-based commissioning.
Remarks – Zoning · When creating a large-scale zone with MC lamps, set up the zone with a maximum of 10 MC lamps first and add more MC lamps to it in packages of 10 max. · The Gateway will then be visible on the Network on Windows explorer.
Remarks – Calibration · When the calibration is run, the light output of the luminaires first goes to a low level and to a high level before it regulates to the set light level. This procedure takes
approximately 7.5 minutes for MasterConnect lamps.
Remarks QR code generation · For groups with MC lamps, QR codes for Philips MasterConnect Control app cannot be generated.
Known limitations These limitations are valid for FW version 6.5.3 and 6.6.16 for MasterConnect lamps: · A mix of firmware versions may cause unpredicted behavior. · After removing MC lamps from a project – either by removing them from a group, deleting the whole group or by resetting them via Safe Mode – it occasionally happens that
light behavior of these MC lamps is not correct after recommissioning. In that case the MC lamps need to be decommissioned and recommissioned once more. · In case a system with MC lamps with occupancy mode setting “Auto on/off” or “Manual on/auto off” is switched off with a ZGP switch or via test mode while, the area is
occupied, lamps turn on at background level after the hold time and turn off again after the prolong time.
116

References

Apps Philips MasterConnect [iOS] Philips MasterConnect [Android] Philips MasterConnect Control app [iOS] Philips MasterConnect Control app [Android]
Weblinks MasterConnect website:
Technical documentation: OEM Warranty:
Contact Commercial questions: Technical problem:

https://apps.apple.com/us/app/philips-masterconnect/id1484451186 https://play.google.com/store/apps/details?id=com.signify.masterconnect&hl=en&gl=US https://apps.apple.com/us/app/philips-mc-control-app/id1567594477 https://play.google.com/store/apps/details?id=com.signify.masterconnect.enduserapp&hl=en&gl=US
https://www.lighting.philips.co.uk/oem-emea/products/connected-lighting/masterconnect NAM: https://www.usa.lighting.philips.com/products/lighting-components/masterconnect
https://www.lighting.philips.com/prof/led-electronics/masterconnect-system/LEDELECTRCONN_CA/category https://www.lighting.philips.co.uk/oem-emea/support/warranty NAM:
https://www.signify.com/en-us/support/warranties
masterconnect.info@signify.com mcsupport@signify.com

117

Disclaimer
© 2025 Signify Holding B.V. All rights reserved. Note that the information provided in this document is subject to change. This document is not an official testing certificate and cannot be used or construed as a document authorizing or otherwise supporting an official release of a luminaire. The user of this document always remains liable and responsible for all required testing and approbation prior to the manufacture and sale of any luminaire. The recommendations and other advice contained in this document, are provided solely for informational purposes for internal evaluation by the user of this document. Signify does not make and hereby expressly disclaims any warranties or assurances whatsoever as to the accuracy, completeness, reliability, content and/or quality of any recommendations and other advice contained in this document, whether express or implied including, without limitation, any warranties of satisfactory quality, fitness for a particular purpose or non-infringement. Signify has not investigated, and is under no obligation or duty to investigate, whether the recommendations and other advice contained in this document are, or may be, in conflict with existing patents or any other intellectual property rights. The recommendations and other advice contained herein are provided by Signify on an “as is” basis, at the user’s sole risk and expense. Specifically mentioned products, materials and/or tools from third parties are only indicative and reference to these products, materials and/or tools does not necessarily mean they are endorsed by Signify. Signify gives no warranties regarding these and assumes no legal liability or responsibility for any loss or damage resulting from the use of the information thereto given here.
118

© 2025 Signify Holding. All rights reserved. The information provided herein is subject to change, without notice. Signify does not give any representation or warranty as to the accuracy or completeness of the information included herein and shall not be liable for any action in reliance thereon. The information presented in this document is not intended as any commercial offer and does not form part of any quotation or contract.
Philips and the Philips Shield Emblem are registered trademarks of Koninklijke Philips N.V. All other trademarks are owned by Signify Holding or their respective owners.
10/2025

www.lighting.philips.co.uk/oem-emea/products/connected-lighting 119

Documents / Resources

Master Connect App

Installation Guide · Master Connect App, App

References

apps.apple.com/us/app/philips-masterconnect/id1484451186apps.apple.com
apps.apple.com/us/app/philips-mc-control-app/id1567594477apps.apple.com
Sign in to your accountdocs.lighting.com
play.google.com/store/apps/details?id=com.signify.masterconnect.enduserapp&hl=en&gl=USplay.google.com
play.google.com/store/apps/details?id=com.signify.masterconnect&hl=en&gl=USplay.google.com
mailto:masterconnect.info@signify.comsignify.com
mailto:mcsupport@signify.comsignify.com
Connected lighting | Philips lightingwww.lighting.philips.co.uk
MasterConnect system | Philips lightingwww.lighting.philips.co.uk
OEM Warranty | Philips lightingwww.lighting.philips.co.uk
User Manualmanual.tools

Published: January 26, 2026

Updated: January 27, 2026

PHILIPS Master Connect App Installation Guide

PHILIPS Master Connect App

Specifications

Product Usage Instructions

FAQs

About the document

Setup

Configuration

Maintenance

Troubleshooting

Documents / Resources

References

Ask a Question

Related Topics

PHILIPS Master Connect App

Specifications

Product Usage Instructions

FAQs

About the document

Setup

Configuration

Maintenance

Troubleshooting

Documents / Resources

References

Ask a Question

Ask a Question Cancel question

Related Topics

Latest Philips Manuals