SE8000 does not retain settings after power loss


Power cycling the SE8000 room controller will cause the settings to revert to default. This requires reconfiguring each of the parameters once again.

Product Line

SmartStruxure Lite


Multi Purpose Manager

Automation Server

SE8xxx Room controller
SE8000 Series
SER8300, SE8300, SE8350
Ex. Viconics branding VT8000 Series


This has to do with BACnet priority; if the configuration was not written with the appropriate priorty, the Room controller will overwrite the parameters upon a power cycle and set them to default.


There are a few ways to prevent the SE8000 from reverting to its default settings after a power cycle:

1 - Configuring each Room Controller locally by navigating to the configuration menu. (Centralized and Standalone system)
2 - Using a LUA4RC script (Centralized and Standalone system)
3 - Writing to points with a specific priority via the BACnet front-end (Centralized system)

NOTE: Since Zigbee does not have any command prioritization mechanisms, setting the parameters from an MPM via Zigbee will not be retained after a power cycle and is strongly not recommended.


All three methods can be used to configure a Room Controller prior to or after its installation. Configuration prior to installation can save a lot of time for the technician on site.  

1 - Configuration on SE8000 (Local)

- Changing the parameters on the SE8000 locally will permanently save the settings and will also allow the user to change the parameters settings locally (e.g. Occupied cooling setpoint). This however can be time consuming.


2 - Configuration via LUA4RC

This method is especially useful in standalone applications with no BACnet front end. If there are many parameters that need to be adjusted, it will be quicker to upload the script to each of the Room controllers rather than navigate to each parameter manually.

-By default, when you assign a value to a BACnet point, the write priority will be priority 16

Example:  ME.MV6 = 2            --Set "Network Units" to Imperial (blocked by using priority 16, not user-adjustable)

-To write to another priority, an array is used

Example:  ME.MV4_PV[3] = 1            --Language will be blocked by user, room controller and bacnet front-end. Will be saved to memory and will stay after a power cycle

NOTE: To release this priority, you can set it to nil (example: ME.AV25_PV[8] = nil).
-To access the relinquish default, priority 17 can be used

Example:  ME.MV10_PV[17] = 1    --Set "Occupancy Command" to "Local Occupancy"; here it is mandatory to have (_PV[17]) because thermostat must be able to toggle between "Occupied" and "Unoccupied" temperature

Use the script below as a template for your LUA4RC script (remove comments to use less memory)

if not init then

ME.MV6 = 2                       --"Network Units"
ME.MV10_PV[17] = 1        --"Occupancy Command" 
ME.AV46_PV[17] = 3         --"Standby Temperature Differential"
ME.MV5 = 2                       -- "Time Format"
ME.AV67_PV[17] = 4         --Standby Time
ME.AV68_PV[17] = 12       --Unoccupied Time
ME.MV46_PV[17] = 3        --UI 16 Configuration
ME.MV4_PV[3] = 1            --Language
--Add all required configuration parameters

init = true


3 - Configuration Via BACnet:

SE8000 parameters can be configured via the BACnet front end by using the following priorities:

- Priority 2 or 3: Using these priorities will permanently save the setting on the SE8000 and will not allow the user to change the settings locally.
- Relinquish defualt: This will allow the user to change the value locally on the SE8000. This is typically used with setpoints

NOTE: using Priority 16 will not allow the user to change the value locally on the SE8000, however, the SE8000 will revert to value to default upon a power cycle.


Another effective method is to push the configuration to multiple SE8000s across the network using a lua script. See Lessons Learned article 18320