Custom Notifications

[mgreinke]

Anyone on this board familiar with Custom Notifications? The documentation is rather light. I'm trying to send something like the following to a webserver that can process the request that indicates a zone fault or restore. The full post to the webserver including the URL, Path and variables would look something like this....

graph-na02-useast1.api.smartthingscom/api/token/207073df-729f-4f8f-b900-f8ee061a8919/smartapps/installations/5a860faf-7089-4ca9-b481-691eb7a5e506/execute/:cea2a9da5bfd0438f84721a7756fa3fe:?zone=2&fault=yes

The tail end of this long string includes the URL encoded variables for the zone # and whether its faulted or not.

As I said, the documentation is very light and I've had very little luck deciphering Webapp Custom Notifications through hours of Google searches.

My goal is to create a temporary workaround for the current inability to interface the Alarmdecoder with Smartthings. By using Custom Notifications and Webcore, these WebApp generated notifications can trigger Smarthings events through Webcore pistons.

At this point, if been trying to reverse engineer by looking at Wireshark logs but this has so far been fruitless.

Kudos to anyone who can offer assistance.

[gkdavids57]

From what I've been able to glean, the default configuration for notifications uses "port" as the means to address the notification receiver (e.g., your SmartThings service) beyond just its FQDN. In your example post, I did not see a port number. If SmartThings uses some other addressing mechanism (e.g., a "key"), you'll need to add this as a custom field to the notification using key:value notation as you'll see when you select Add Field at the bottom of the Custom Setting section of the Notifications settings dialog.