Subscribing is a smart move!
You can subscribe to this forum after you log in or create your free account.
How can I get a batch of values if I use SoapEwsRestProvider in SmartConnector?
SmartConnector Forum
Schneider Electric support forum about SmartConnector applications for integration of other building management systems (BMS) into EcoStruxure Building Operation.
Invite a Co-worker
Send a co-worker an invite to the 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
Solved
Go to Solution
Accepted Solutions
Link copied. Please paste this link to share this article on your social media post.
Hi Jessie,
For doing something like this, you will want to use the subscription mechanism built in with the following workflow:
With the /Subscriptions Endpoint do a:
REQUEST 1:
POST /Subscriptions/Create with a body like:
{
"DurationInMinutes": 15,
"SubscriptionType": "ValueItemChanged",
"Ids": [
"01/Server 1/AV1",
"01/Server 1/AV2",
"01/Server 1/etc..."
]
}
RESPONSE 1:
This will return a body with an ID. When you want to check these values
REQUEST 2:
POST /Notifications/Create
{
"SubscriptionId": "ID From above response",
"ChangesOnly": true
}
RESPONSE 2:
This will return a notification ID. Then you do:
REQUEST 3:
GET /Notifications/{ID FROM ABOVE RESPONSE, without the {}}/Items
RESPONSE 3:
This will return a list of all values that have changes since the last notification response (since the notification has ChangesOnly = true. The first time you do this always, you will get the current value of ALL objects asked for, and subsuquent requests will return just the changes from the last notification.
Now basically just keep doing the POST /Notifications/Create and the GET /Notifications/{id}/Items over and over again. If you always want all the values, simply change ChangesOnly to false instead of true. But the vast majority of use cases can simply get the values that have changed, and determine the rest have remained the same 
.
Before the subscription expires, you will want to do a:
PUT /Subscriptions/{id}/Renew where the ID is the id returned from RESPONSE 1 with a body of:
{
"minutes": 15
}
In order to keep your subscription alive, you can also terminate your subscription early if you want via the user of:
PUT /Subscriptions/{id}/Terminate where ID is the id returned from response 1.
If you end up getting a bad response from the web server on your subscription, just recreate it and start over.
Regards,
-Jeff
Link copied. Please paste this link to share this article on your social media post.
Hi Jessie,
For doing something like this, you will want to use the subscription mechanism built in with the following workflow:
With the /Subscriptions Endpoint do a:
REQUEST 1:
POST /Subscriptions/Create with a body like:
{
"DurationInMinutes": 15,
"SubscriptionType": "ValueItemChanged",
"Ids": [
"01/Server 1/AV1",
"01/Server 1/AV2",
"01/Server 1/etc..."
]
}
RESPONSE 1:
This will return a body with an ID. When you want to check these values
REQUEST 2:
POST /Notifications/Create
{
"SubscriptionId": "ID From above response",
"ChangesOnly": true
}
RESPONSE 2:
This will return a notification ID. Then you do:
REQUEST 3:
GET /Notifications/{ID FROM ABOVE RESPONSE, without the {}}/Items
RESPONSE 3:
This will return a list of all values that have changes since the last notification response (since the notification has ChangesOnly = true. The first time you do this always, you will get the current value of ALL objects asked for, and subsuquent requests will return just the changes from the last notification.
Now basically just keep doing the POST /Notifications/Create and the GET /Notifications/{id}/Items over and over again. If you always want all the values, simply change ChangesOnly to false instead of true. But the vast majority of use cases can simply get the values that have changed, and determine the rest have remained the same .
Before the subscription expires, you will want to do a:
PUT /Subscriptions/{id}/Renew where the ID is the id returned from RESPONSE 1 with a body of:
{
"minutes": 15
}
In order to keep your subscription alive, you can also terminate your subscription early if you want via the user of:
PUT /Subscriptions/{id}/Terminate where ID is the id returned from response 1.
If you end up getting a bad response from the web server on your subscription, just recreate it and start over.
Regards,
-Jeff
Link copied. Please paste this link to share this article on your social media post.
For REQUEST 2, regardless of "ChangesOnly" parameter set to true or false, the result are the same - only get the changed value. Then how to get all subscription values? Thanks!
Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.