SmartConnector Forum
Schneider Electric support forum about SmartConnector applications for integration of other building management systems (BMS) into EcoStruxure Building Operation.
Link copied. Please paste this link to share this article on your social media post.
Hello
I have couple question about subscription and notifications which I have not found answer in forum.
How often we should offer data transfert by using notification? We have third party companies which would like to read EBO data points. This third party company request read 1000 points every minute.
Is this recommended way to get data using subscription and notification every 1min
1. Create Subscription
2. Create Notification
3. Retrieve Notirication items
4. Delete Notification
then after example 1 minute
2. Create Notification
3. Retrieve Notirication items
4. Delete Notification
Then also every 5 minute subscription will be renewed. Is there any case where subscription need to be terminate?
If third party company need to have 1min interval data, 5min interval data and 15min interval data then do they create 3 subscriptions and every subscription have 1 notifications or do they create 1 subscription and 3 notifications ?
Other forum message suggest that in one notification should be max 500 points. Is it still the same? To be safe we are thinking about 300 point per notification. Total points can be around 1500 in one project.
How throttling limits are calculate in subscription and notification request?
Is there way to deny /Get Values command? So that third party company need to use subscription and notification function?
--
Esa
Link copied. Please paste this link to share this article on your social media post.
Hi Esa,
To answer your questions:
- It is possible to do as you are mentioned every 1 minute. Also, in general, you don't need to delete the notification, but this will help keep the in-memory cache cleaner, so it is probably a good practice. In general, we tend to see asking for data much less often (usually every 5 minutes or so), but if 1 minute is required, it will work as well.
- As far as subscriptions requiring to be terminated. There is really not a specific case where you need to terminate. In general, a subscription made to EBO will automatically terminate after 30 minutes, if it is not renewed. That said, if you plan on creating new subscriptions, and don't plan on using the existing anymore, then it doesn't hurt to terminate the old one, to let EBO release its internal subscriptions before the 30 minutes.
- The max points of 500 is just a suggestion, and not a real hard-coded limit, and this suggestion hasn't changed :). 300 will also be ok.
- By throttling limits, I am assuming you are talking about the throttling in the REST Gateway. Each and every request sent to the REST Gateway counts towards the throttling. So if the throttle is set to 100 requests per minute, and you have 5 subscriptions getting data every minute. Based on your plan for requests, you will be using 15 requests per minute, well within the throttling limit.
- I can't think of anyways we can deny the /Get/Values request.
Best Regards,
-Jeff
Link copied. Please paste this link to share this article on your social media post.
Hi Esa,
To answer your questions:
- It is possible to do as you are mentioned every 1 minute. Also, in general, you don't need to delete the notification, but this will help keep the in-memory cache cleaner, so it is probably a good practice. In general, we tend to see asking for data much less often (usually every 5 minutes or so), but if 1 minute is required, it will work as well.
- As far as subscriptions requiring to be terminated. There is really not a specific case where you need to terminate. In general, a subscription made to EBO will automatically terminate after 30 minutes, if it is not renewed. That said, if you plan on creating new subscriptions, and don't plan on using the existing anymore, then it doesn't hurt to terminate the old one, to let EBO release its internal subscriptions before the 30 minutes.
- The max points of 500 is just a suggestion, and not a real hard-coded limit, and this suggestion hasn't changed :). 300 will also be ok.
- By throttling limits, I am assuming you are talking about the throttling in the REST Gateway. Each and every request sent to the REST Gateway counts towards the throttling. So if the throttle is set to 100 requests per minute, and you have 5 subscriptions getting data every minute. Based on your plan for requests, you will be using 15 requests per minute, well within the throttling limit.
- I can't think of anyways we can deny the /Get/Values request.
Best Regards,
-Jeff
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.