Known issues

The following known issues are included in the 2.7 release:

  • The ability to create an energy report only works from the date that the feature was released (June 2020)

  • A firmware upgrade will fail if a light is physically deleted (or reset) but still exists in the system (app). Please remove the light from the app and the upgrade will finish.

  • The app cannot be used for control when an update is in progress. Sensor and panel switch control will remain working as well as control via the web portal (Signify Interact for Intelligent Buildings connected-only)

  • A gateway that gets online may already find a number of lights as it opens the network for a very short time. This only applies when you first add the gateway and then the lights. This may already find a number of lights that are discoverable (Signify Interact for Intelligent Buildings connected-only).

  • Level 6 of Manual demand response (North America-only) does not turn off the lights but sets the intensity of the lights to very low.

  • Demand Response (DR) not working as intended for Gen2 Smart T-LEDs.

    • Gen2 Smart T-LEDs - When the switch off command is triggered, lights go to a minimum dim level instead of switching off

  • Hold Time is longer than configured. This is as it was intended. See the explanation.

  • Lights with firmware version lower than 6.4.2 are not supported for Signify Interact for Intelligent Buildings projects. Update the firmware before commissioning.
    Lights with firmware version 6.4.2 and 6.5.3 must be reset.

    • Using Signify Interact for Intelligent Buildings standalone:

      1. Power and commission the lights

      2. Decommission the lights in the Signify Interact for Intelligent Buildings standalone system

      3. The lights dim and blink

      4. Recommission the lights in the Signify Interact for Intelligent Buildings standalone system

    • Using an IR remote - Signify IRT9015 or IRT9090

      1. Install the lights

      2. Reset the lights using the remote

      3. Commission the lights in the Signify Interact for Intelligent Buildings standalone system

  • Background deployment is not supported in the mobile app which causes the deployment to fail when minimizing the application or locking the screen of the device.
    Disable the screen auto lock or set the time to 20+ minutes on devices used for commissioning

  • When detecting occupancy, the lights switch on to task level rather than the selected scene. This also affects the color temperature if it’s set differently between the light template and scene

  • The tunable white color temperature slider value doesn’t change in the web portal when a scene is selected

  • To change the color temperature, light must be switched on first

  • Minimum/maximum color temperature range is not restricted when using push-button switch

  • ZGP sensors fail to trigger the lights when installed in the corner of an area or when there is interference from other wireless devices, such as wireless cameras or medical devices, running on the same channels as the Zigbee devices.

    Ensure other wireless devices are not running on channels 11, 15, 20 and 25.

  • Signify Interact for Intelligent Buildings standalone network cannot sync with cloud if more than 64 groups and zones are created per network. Delete the extra groups or zones to start syncing again.

  • (North America) The Parking sensor name in the portal is different from one in the app

  • If level 5 Demand response is chosen, the lights are not controllable for as long as the timer is active.

  • Signify Interact for Intelligent Buildings standalone project overview doesn’t display the lock icon for projects with one or more locked networks. Go to Project  Networks to see the list of locked networks.

  • The Retry Update button is, at times, not visible in the mobile app after update failure. Retry the update via the web portal (Signify Interact for Intelligent Buildings connected-only)

  • After commissioning and deploying Zigbee Green Power switches, intermittent command execution failures may occur under certain network conditions. As a result, only some of the assigned luminaires may respond to ON, OFF, dimming, or scene commands.

    Workaround: If the scene does not execute as expected, press the button again. The subsequent command is processed successfully, and the affected luminaires return to normal operation. No recommissioning or redeployment is required.

  • After switching a Light behavior V2 group from Auto On Auto Off (AOAO) to Manual On Auto Off (MOAO) state, lights may still turn on automatically when motion is detected shortly after the state change. This behavior is temporary and may occur even though the group is configured for manual-on operation. The group will begin operating as expected after a short period, and motion will no longer automatically turn the lights on.

  • After switching a Light behavior V2 group from Manual On Auto Off (MOAO) to Auto On Auto Off (AOAO) state while motion is already detected in the area, the lights may take up to 10 seconds to reach the expected brightness level. During this time, the lights can remain at the configured Vacant Level before automatically transitioning to the Task Level.

  • After deploying updated light level settings to a Light behavior V2 group, the new light levels may not be applied immediately. Depending on the occupancy state of the group, lights can continue operating at their previous levels for several minutes or until the space becomes vacant and the configured hold time expires. Once this occurs, the updated light levels are applied and normal operation resumes.

    Light behavior scenarios:

    • If the group is vacant when the update is deployed and remains vacant, the lights may continue using the previous light levels for approximately 6 minutes before the new settings take effect.

    • If the group is vacant when the update is deployed but becomes occupied within the 6-minute period, the previous light levels remain active until the area becomes vacant again and the hold time expires.

    • If the group is occupied when the update is deployed, the previous light levels remain active until the area becomes vacant and the hold time expires.

  • To support Light behavior V2, devices running with firmware versions below 8.x.x must be fully reset (deleted from the project) after being upgraded to firmware version 8.x.x or later. The current Unassign function does not perform a complete reset of light behavior settings and therefore cannot be used for this purpose. To avoid potential issues and user confusion, the Unassign option has been temporarily removed from the mobile app. It will be reintroduced in a future release once it supports a full reset of light behavior settings, allowing users to unassign and reassign devices after upgrading them for Light behavior V2 support.

  • In connected networks, the iOS app may crash when opening a group with a pending group deployment after upgrading the app from version 5.1.21 to 5.1.22.

    Workaround:
    Always uninstall the existing intermediate build before installing a new build or ensure the new build properly overrides the previous feature build during installation.

  • In Monitoring → Energy consumption → Monthly per group, the sorting functionality for the This month and Last month columns does not correctly arrange values when sorting in either ascending or descending order. (Signify Interact for Intelligent Buildings connected-only)

Legacy devices

  • When using the RF Connector DALI Gen 1 in mains-only mode with switchable lights, the portal erroneously reports this as a 'Failed Device' in Health status overview.

  • Smart T-LEDs Gen 1 are phased out and do not support the latest firmware version of the Wireless Gateway. To use the latest version, replace the lights with Smart T-LEDs Gen 2.

  • Smart T-LEDs Gen 1 devices do not support optimized calibration. This means the lights turn off when occupancy is not detected during calibration.

    Remain in the sensor’s field of view so it detects occupancy until the calibration process is finished.

  • Smart TLEDs Gen 1 do not support Signify Interact for Intelligent Buildings  connected Wireless Gateway replacement.

  • The tunable white feature is not supported on legacy devices and Smart T-LED Gen1

  • Demand Response (DR) not working as intended for Gen1 Smart T-LEDs

    • Gen1 Smart T-LEDs - The Demand Response command doesn’t dim or switch off the light.

      The Demand Response feature is not supported due to hardware limitations. Customers who require the feature must replace the Gen1 Smart T-LEDs with Gen2 Smart T-LEDs.

  • BLE advertising is activated every time the lights are power cycled, therefore lights can be reassigned or hijacked.

    Don’t power cycle the lights unless the intention is to re-commission them.

  • Total energy column in the web dashboard is not visible.