Got, as expected, 2 entries in the corresponding Device Events List : 6:38:07. httpGet() makes an HTTP GET request, for example. The various APIs are named for the underlying HTTP method they will use. There are several APIs available to you to handle making these requests. The Device Custom Attribute declaration in my Custom Device Type Handler : definition (name: "JJ's Fibaro FGK-101 Handler", namespace: "JJG2014", author: "Jean-Jacques GUILLEMAUD") " Calling Web Services¶ SmartApps or device handlers may need to make calls to external web services. Unfortunately, I DID create both attribute and command in my metadata (see relevant portions of the code below), so the error message is something else.Īlso, please confirm your code does work PRESENTLY, because so many things went wrong with the ST platform recently, that something OK in the past may not be anymore. So has anybody here ever been able to SUCCESSFULLY use either a Custom Device Attribute or a Custom Device Command ?Īnd if yes, anything special to do to avoid those bothersome messages ?Īny help and : thanks for the confirmation it CAN work. The SmartThings support did register my 2 support requests ( #99365 and #98757), but they were not able to help me further. “: No signature of method: () is applicable for argument types: (, ) values: line 93”.Ĭuriously, I get this error message AFTER the custom command HAS BEEN properly executed by the Hub but it works only once, and the error message aborts my SmartApp, which defeats its whole purpose (periodic watchdog) When installed along with the proper services at AWS (Amazon Web Services), a simple voice command allows you to control your devices along with querying. When invoking a custom device Command from my SmartApp, I get a very similar error message : Ask Alexa is an add-in to the SmartThings mobile application that allows you to control a broad array of devices with your Amazon Alexa Enabled Devices. “: No such property: reportASAP for class: line 445” When setting up a custom Attribute from within my Device Handler : the handler crashes with this message : These also include automations that allow enabling different features. Follow the API description and enter params if necessary. The SmartApps and Device Handlers work together to provide integration to the SmartThings ecosystem using Nests Official API. Copy your Private or Alias Key to your SmartApp preferences. I have been trying, unsuccessfully, to use in a custom Device Handler and in a custom SmartApp a custom Device Attribute and a custom Device Command.Īccording to SmartThings documentation, both usages seem quite straightforward, but I was unable to use either : These SmartThings SmartApps are the core of the Nest integration with SmartThings.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |