After discovery of how the Scheduler add on actually works, we've documented some best practices when setting up your zones along with some known issues and caveats. If you are controlling zone schedules using this Add On and E2H, it is assumed that E2H will be sending primary schedule data, not WebCtrl schedules. Attempting to add exception schedules in WebCtrl may not have the desired affect.
It is strongly advised that you test your zone scheduling strategy, including overrides, before applying a specific configuration to all of your zones.
Scheduling Add-On Best Practices
Check the "Ignores Schedules Above" in WebCtrl so only the zone schedules are considered and not anything above it (e.g. building schedules). This should eliminate weekly schedules from the zone so these schedules can't occupy the zone in periods when E2H schedules are off.
It apparently doesn't matter what event priority E2H uses to send its schedules. All exceptions sent by E2H are converted to WebCtrl override exception schedules.
If you don't want a weekly schedule running while E2H is scheduling, then make sure "Initialize Midnight" is checked and the Stop Value = Unoccupied CMD value (Not NULL). This will effectively override the entire day with the exception schedule. If nothing is scheduled in E2H, the zone will be overridden OFF.
Check "Overwrite All Exception Schedules". This will ensure that any exceptions that are read back from WebCtrl are removed before E2H writes back the schedules. The schedules coming back from WebCtrl are NOT BACnet compliant (priorities are reversed) and should not be sent back to WebCtrl as overrides. Even if you uncheck this option, DO NOT rely on a WebCtrl override schedule to be preserved because it will not override as expected. If you want to ensure an operator override of the zone, override the zone occupancy point instead.
If you want E2H to override unoccupied periods like Holidays in WebCtrl, you must enable the WebCtrl option for the zone to enable overrides. See the "Allow Exception-Schedules to write Unoccupied periods" in the options page in WebCtrl.
When a "Verify" is used to read current schedule data from BACnet, Exceptions returned may not accurately represent actual schedules and priorities in the WebCtrl zone. View the zone's WebCtrl schedule to see what the actual schedules are.
Use of NULL vs OFF Values
Reverting to Default Schedules
v1.0 Known Issues
After a controller is downloaded, the Add On schedules don't get restored after the download. This can cause the zone to be unoccupied until Events2HVAC sends another schedule push, which is determined by any changes to event schedules within the 24 hr event window. To force schedules in E2H, you would need to open the action for that zone and "Send Test Schedules".
When viewing the exception schedules in the Add On schedule objects, the exceptions are translated/transformed from the internal zone schedules and the priorities shown (1=lowest, 16=highest) are in reverse from what the BACnet specification calls for (1=highest, 16=lowest). This can be very confusing to the E2H users looking at the current exception data for the zone. Moreover, WebCtrl doesn't assign static priorities for each type, but instead they recalculate the schedules and assign the lowest priority group = 1, then incrementally add 1 for other higher priority schedules like Holiday and Override schedules. So if all 3 types are present, 1=lowest (normal), 2=Holiday, 3=highest (Override) and they will look like this below in E2H.