Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Close
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
84419members
353605posts

Soap Rest Provider API Endpoint GetUpdatedAlarmEvents

SmartConnector Forum

Discussion of SmartConnector applications for integration of various other building management systems (BMS) into EcoStruxure Building Operation

Solved
Adam_Summers
Lt. Commander Lt. Commander
Lt. Commander
0 Likes
2
295

Soap Rest Provider API Endpoint GetUpdatedAlarmEvents

I'm looking at the Soap Rest Provider API Swagger docs and cannot see any way in which the GetUpdatedAlarmEvents can be called. Is this supported in the native Ews.RestExtensions.SoapEwsRestProvider class?

 

If not, has anyone custom implemented this already?

 

I've also looked at Subscriptions and whilst the EWS Specification suggests you can also register a subscription for AlarmEventCreated, I've never done this before and don't see how would work.


Accepted Solutions
JeffBowman
Schneider Alumni (Retired)
Schneider Alumni (Retired)

Re: Soap Rest Provider API Endpoint GetUpdatedAlarmEvents

Hi Adam,

 

With the SOAP rest endpoint, GetUpdatedAlarmEvents is called automatically when you send a subsequent request to the /AlarmEvents endpoint. The first time a request is sent, it uses GetAlarmEvents, and then uses GetUpdatedAlarmEvents afterwards.

 

As far as the EWS Subscriptions. Although it is part of the spec, it is not supported by the vast majoirty of EWS servers (Maybe SmartConnector's EWS server supports it, but i know EBO does not.)

 

Regards,

 

-Jeff

See Answer In Context

2 Replies 2
JeffBowman
Schneider Alumni (Retired)
Schneider Alumni (Retired)

Re: Soap Rest Provider API Endpoint GetUpdatedAlarmEvents

Hi Adam,

 

With the SOAP rest endpoint, GetUpdatedAlarmEvents is called automatically when you send a subsequent request to the /AlarmEvents endpoint. The first time a request is sent, it uses GetAlarmEvents, and then uses GetUpdatedAlarmEvents afterwards.

 

As far as the EWS Subscriptions. Although it is part of the spec, it is not supported by the vast majoirty of EWS servers (Maybe SmartConnector's EWS server supports it, but i know EBO does not.)

 

Regards,

 

-Jeff

Adam_Summers
Lt. Commander Lt. Commander
Lt. Commander
0 Likes
0
284

Re: Soap Rest Provider API Endpoint GetUpdatedAlarmEvents

Hi Jeff,

 

Thanks, so to clarify the behaviour you are describing is more of a background operation in the SC Endpoint? I noted that repeatedly polling the /AlarmEvents returns the same results on every request (assuming no change of alarm state on my ES) - so the Endpoint is holding that result and updating accordingly and returning it to me each time as a current alarm stack?

 

Obviously calling GetUpdatedAlarmEvents would return an empty list if no alarm updates happened since the last poll.

 

I kind of expected the first request to return the data, and subsequent to only contain changes (the way you have to handle that in EWS directly)

 

What you explained is that is abstracted away inside the endpoint, and consumers can openly just call the /AlarmEvents with no parameters to always get the "current alarm stack" - the most efficient way to do that is handled by the SC Endpoint.

 

That said - it still doesn't seem to work as I expected. I've only got 3 active alarms in my ES and the response is still containing the full stack of alarms, even after several requests. Could you elaborate a little on how I would only get the active alarms "now"

 

/AlarmEvents?state=Active returns all items in the "to active" state (12 alarms in total) even those that are no longer present in EBO.