Dali controllers must have dali power to boot and may not apply or even go into bootloader if this is not found.  If the controller does not find dali power, you will see the ON/OFF led flash slow flash red.  

A successful controller firmware upgrade consists of the following process.

1. The controller will go into bootloader and attempt to contact the update server to receive the bootload file.  During this, you will see an alternating green flash on the LEDS (green and red on the field controllers).
2. The file will begin transferring.  The leds will freeze (generally, one of them will be on).  
3. The update will be applied and the leds will resume alternating green (green and red field controllers) 
4. The controller returns to main code and begins flashing yellow for startup (field controller will fast flash green on a single led for wireless traffic).

Error scenarios

Controller appears to bootload and be functioning but shows no cloud connection

If you have a static IP set, you may have a faulty DNS setting in your DNS Servers.  If this is the case, the controller will bootload but then fail to appear back on the cloud.   A faulty DNS on older versions would previously work and thus, hide the bad network setting.  This has been correct in later versions.

You can use the controller button press scheme in this article to revert back to DHCP for the current power cycle that you are on.   If your controller is a room controller / LCM, you can reset to DHCP via the alternate method of unplugging/plugging in the network shown in this article.

As soon as the controller appears on the cloud, please amend your network settings as this DHCP state is temporary.

Note: If the controller has been sitting powered for quite some time with connection, you may require a reboot of the controller before performing this action. 

Controller goes into bootloader and returns without updating

If you are experiencing issues with bootloading where the device goes into bootloader and returns back to main code successfully, having not updated, your network is not allowing the controller to bootloader.  Please contact your network administrator with the details in the following guide

Alternatively, you can also connect the controller to a backup internet solution to get through the update.

Controller sits with both leds solid yellow or flashing for some time and then goes back to alternating green

Please allow the controller to perform this cycle for sufficient time before carrying out any adjustment.

This seems to be a very low occurrence issue that is mostly found on the first bootload of a controller  from factory, though we are still investigating the true origins of this issue.

Your controller must be factory reset to restore its credentials.  You can do this by applying the factory reset button press scheme in this article.

You must apply the button press scheme when the controller is in solid yellow led state.

Factory resetting will wipe the database.  If your controller was previously commissioned, once bootloader, please restore your controllers data via this article.   

Stuck in bootloader and second DNS populated

Controller products released with the initial firmware version between 1.1.0.x-1.3.21.x or 1.4.1.x-1.4.16.x have an issue with their bootloader getting stuck when the controller has a secondary DNS entry recorded. 

You can find your controller's initial firmware via the Control system overview page. 

Scroll to the bottom of the control system overview page for the first Firmware version changed entry.

If this is the case, you should check the last Network changed entry at the top of the same page to see if the controller has received a secondary DNS entry from DHCP server or check your DHCP server settings.

If your controller has both the above mentioned issues; you can continue getting firmware updates by either updating the DHCP server to only report one DNS entry or set a static IP for the controllers in question. 

If you have controllers offline due to being stuck in the bootloader, you can solve this via the following:

1. Turn off the site Upgrade preferences option under Site details -> Settings

2. Disconnect the ethernet cable from the controller(s) that are stuck.

3. Power cycle the controller(s) that are stuck.

4. After 10 minutes, reconnect the ethernet cable to the controller(s).

5. If you do set a static IP, please ensure it is outside the DHCP IP pool to avoid conflicts. Once your controller is back online, you can set the controller's network settings to static. 

Once the controller has reconnected to the cloud with the new network settings, you can proceed with updating the controller's firmware. 

Once you have confirmed the controller can successfully upgrade, you can re-engage the site settings Upgrade preference option if you prefer.

Please note: this DNS fix is required for the life of the controller since the affecting code can not be updated outside of the factory.