Ask our Experts
Didn't find what you are looking for? Ask our experts!
Launch of Consumer/Home Owner registration process! We are pleased to announce the commencement of the Consumer/Home Owner Registration Process on Community. Consumers/Home Owners may now proceed to register by clicking on Login/Register. The process is straightforward and designed to be completed in just a few steps.
Schneider Electric support forum about SmartConnector applications for integration of other building management systems (BMS) into EcoStruxure Building Operation.
Search in
Link copied. Please paste this link to share this article on your social media post.
Lately when I developing an extension and I try to acknowledge the alarm events of SBO, it always tells PERMISSION_DENIED ,I am not sure any configuration incorrect.
For example when I try to acknowledge alarm event as:
{ "AlarmId": "02/Server 1/Test/OverTemp", "Acknowledgeable": 1, "OccurredOn": "2017-06-07T14:07:36Z", "LastTransitionedOn": "2017-06-08T00:07:08Z", "Message": "The room temp is too low", "Priority": 100, "State": 1, "Type": "GeneralAlarm", "Id": "/Server 1|/Server 1/Test/OverTemp|4c7f52bb-5450-41f9-9387-4a260242d023" },
And I recall the GUID of the alarm is the ID to be used for acknowledgement, then I use the Id=4c7f52bb-5450-41f9-9387-4a260242d023 to acknowledge this alarm, the response will be as:
{ "Message": "PERMISSION_DENIED" }
The SBO endpoint and credential is all correctly.
---Austen
Link copied. Please paste this link to share this article on your social media post.
I have figure it out, I should use Id="%2FServer%201%7C%2FServer%201%2FTest%2FOverTemp%7C11873d28-6e3c-4d03-8f8c-7f8d01e6e495" to acknowledge the alarm of my example.
Thanks.
Link copied. Please paste this link to share this article on your social media post.
You’ve reached the end of your document
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.