SendAttendance Action

The SendAttendance action sends one of two available event occupancy data fields; expected count or  % occupancy to an MSEA object when an event item is triggered.  This allows you to send capacity related control signals to your HVAC system in response to actual or expected people load in the room. The priority that you will command the value with is also sent.

Not all event providers support expected count and % capacity data in their events.  For unsupported event providers, the % capacity will always equal 100% and expected count will equal 0.

 

 

This action only applies to the following event triggers

      EventStart

      EventSetupStart

 

  Field Name

  Description

  Range

Item Reference

The fully qualified reference to the specific item to be written to.

  Priority

Priority value for commanding a commandable object and property.

1-16 (1=highest)

16 = Recommended default

Only applies to Present_Value property on commandable objects (ie. AO, AV, BO, BV, MSO, MSV)

Expected Count

This expected number of attendees for the event in a room.

0 = not available

1-X = number of people expected

% Occupancy

The calculated value of % of room occupancy.  The is the percent of (expected count)/(max room capacity)

100% = default value if expected count or max room capacity is not available from event provider.

0-100%

Send Raw Value

Sends the value from the event data

 

Calculate State

(FUTURE)

 

 

Verify Button

Click on the button to verify that the selected object and property can be read directly from the MSEA network without errors.  The results of the verification will be shown in the Results window.

Test Button

Click on the Test link to attempt to write a value to the object.  The results of the test will be shown in the Results window.

Note:  The SendAttendance action does not take into account total attendance or total % occupancy for zones that have multiple rooms assigned to it.  This action will trigger at the start of an event and will use the values for that event.  If events overlap for different rooms the data sent will be for the last event that triggered and will not adjust for the multiple events occuring at the same time in different rooms.