Jimbo.Automates Posted February 28, 2022 Share Posted February 28, 2022 The Polyglot Version 3 Node server for IFTTT Maker Webooks https://ifttt.com/maker_webhooks version 3.0.3 is released. See the README for more information. The Release Notes are also available. Link to comment
Adam Ant Posted March 2, 2022 Share Posted March 2, 2022 @JimboAutomates, Thanks for building this nodesever! I am afraid is not clear to me how to use it. I have the nodeserver all configured in PG3 with the correct api_key etc. The node server is also showing up in my ISY. I have created my webhook on IFTTT that triggers an action. How do add that webhook to my ISY? Thanks! Link to comment
Jimbo.Automates Posted March 2, 2022 Author Share Posted March 2, 2022 Hey nice to see it may be useful for someone else! On the configuration page where you added your API Key should see these instructions: https://github.com/UniversalDevicesInc-PG3/udi-poly-IFTTT-Webhooks/blob/master/CONFIGURATION.md Although there is bug in bug in PG3 where sometimes doesn't show the configuration documentation. Hopefully those instructions clear it up? Link to comment
Adam Ant Posted March 2, 2022 Share Posted March 2, 2022 17 minutes ago, JimboAutomates said: Hey nice to see it may be useful for someone else! On the configuration page where you added your API Key should see these instructions: https://github.com/UniversalDevicesInc-PG3/udi-poly-IFTTT-Webhooks/blob/master/CONFIGURATION.md Although there is bug in bug in PG3 where sometimes doesn't show the configuration documentation. Hopefully those instructions clear it up? I have found it after I made my post but not sure what values go into each field . >>Node Address: Enter a short, 8 characters or less node address. Must be unique and should never change I have use the name "Spotoff" as in spotify off. Is that correct? Can be anything as long as it is short, right >>Node Name: Enter a descriptive node name I entered: This is used to pause Spotify >>On Event Name: The IFFTT Webhooks event name to trigger for "On". Not required Not sure what goes here. There is no "on" action so I left this empty >>Off Event Name: The IFFTT Webhooks event name to trigger for "Off". Not required I entered the name of the webhook here. I named it "Spotoff" on IFTTT. Is that the right value? Thanks! Adam Link to comment
Jimbo.Automates Posted March 3, 2022 Author Share Posted March 3, 2022 That all looks good, yes the nodeaddress is what you want the node address to be in the ISY, the Node name is what you really se in the ISY so something like "Spotify Pause" would make sense. So each node it creates can have an "On" trigger and "Off" trigger, this is useful if it's something where on and off make sense. But you don't have to enter both. I would put your "Spotoff" in the On event name, then when you turn on the "Spotify Pause" node it will pause spotify. Link to comment
Adam Ant Posted March 3, 2022 Share Posted March 3, 2022 55 minutes ago, JimboAutomates said: That all looks good, yes the nodeaddress is what you want the node address to be in the ISY, the Node name is what you really se in the ISY so something like "Spotify Pause" would make sense. So each node it creates can have an "On" trigger and "Off" trigger, this is useful if it's something where on and off make sense. But you don't have to enter both. I would put your "Spotoff" in the On event name, then when you turn on the "Spotify Pause" node it will pause spotify. Getting close! I now have the Trigger off event in ISY but it does not seem to be firing the webhook. Seems like I am missing the linkage.. Any ideas? Link to comment
Jimbo.Automates Posted March 3, 2022 Author Share Posted March 3, 2022 If it encounters an error the node status will show change. But IFTTT doesn't error out for things like misspelled trigger. Check the Nodeserver log and you should see it send the request to IFTTT?Sent from my Pixel 6 Pro using Tapatalk Link to comment
Adam Ant Posted March 3, 2022 Share Posted March 3, 2022 22 minutes ago, JimboAutomates said: If it encounters an error the node status will show change. But IFTTT doesn't error out for things like misspelled trigger. Check the Nodeserver log and you should see it send the request to IFTTT? Sent from my Pixel 6 Pro using Tapatalk Getting this error: 2022-03-02 18:28:16,044 Command udi_interface.node ERROR node:runCmd: command DOFF not defined Link to comment
Jimbo.Automates Posted March 3, 2022 Author Share Posted March 3, 2022 Oops, guess I broke it and didn't re-test before releasing. I'll fix it tonight, but you can move it to the On event. Link to comment
Jimbo.Automates Posted March 3, 2022 Author Share Posted March 3, 2022 PG3 IFTTT Maker Webooks version 3.0.1 is released, see the Release Notes Link to comment
Adam Ant Posted March 3, 2022 Share Posted March 3, 2022 10 hours ago, JimboAutomates said: PG3 IFTTT Maker Webooks version 3.0.1 is released, see the Release Notes Afraid there is still an issue... While I do indeed see 3.0.1 in the node store, my system doesn't want to automatically apply the upgrade. I am showing the current running version as 3.0.0. I have: 1. Restarted the node server 2. Ran the upgrade process from PG 3. Dropped to the command line and ran an update/upgrade 4. Rebooted the Polisy 5. just for good measure restarted the IFTTT nodeserver again.. Still shows 3.0.0 and the problem remains. Any ideas? Link to comment
Jimbo.Automates Posted March 3, 2022 Author Share Posted March 3, 2022 Ok, sounds like my upload of the new version didn't go through completely. I'll check later.Sent from my Pixel 6 Pro using Tapatalk Link to comment
Adam Ant Posted March 4, 2022 Share Posted March 4, 2022 11 hours ago, JimboAutomates said: Ok, sounds like my upload of the new version didn't go through completely. I'll check later. Sent from my Pixel 6 Pro using Tapatalk Any luck? Link to comment
Jimbo.Automates Posted March 4, 2022 Author Share Posted March 4, 2022 22 minutes ago, Adam Ant said: Any luck? Need more time in the day not luck, day job kept me slammed today. Just uploaded again and confirmed it took. Link to comment
Adam Ant Posted March 4, 2022 Share Posted March 4, 2022 6 minutes ago, JimboAutomates said: Need more time in the day not luck, day job kept me slammed today. Just uploaded again and confirmed it took. Thanks! It did indeed take and I am now running the 3.0.1 version. However, I am still getting the same error. Could it be a problem on my end?. 2022-03-03 20:47:19,051 Command udi_interface.node ERROR node:runCmd: command DOFF not defined Link to comment
Jimbo.Automates Posted March 4, 2022 Author Share Posted March 4, 2022 Thanks! It did indeed take and I am now running the 3.0.1 version. However, I am still getting the same error. Could it be a problem on my end?. 2022-03-03 20:47:19,051 Command udi_interface.node ERROR node:runCmd: command DOFF not definedThat's weird. Please download log package and PM it to meSent from my Pixel 6 Pro using Tapatalk Link to comment
Adam Ant Posted March 4, 2022 Share Posted March 4, 2022 11 hours ago, JimboAutomates said: That's weird. Please download log package and PM it to me Sent from my Pixel 6 Pro using Tapatalk Thanks for your help, @JimboAutomates! As discussed, I should have been using just the key for my api_key in the configuration vs the entire path+key. Link to comment
Adam Ant Posted March 4, 2022 Share Posted March 4, 2022 For those considering the IFTTT nodeserver, it works great! I love how you can reference these IFTTT devices right in your scenes and programs. Very cool Link to comment
Athlon Posted April 8, 2022 Share Posted April 8, 2022 I fear I'm going to need a little hand holding to get this to work. Goal: Turn a Sensibo connected mini-split on when an Ecobee sensor shows less than desired temperature. I've added the IFTTT PG3 Node server (today). I'm running it on a Policy. I added my API Key to the Configuration page. I created an Applet naming it BRSenOn. Then I chose 'Receive a web request'. Then I chose Sensibo, registered Sensibo with IFTTT and filled in the form to indicate On, Heat Mode, Fan Auto. Then I did this: What do I do next? It shows in my admin panel, however I do not see how I can make it work in a program. Link to comment
Jimbo.Automates Posted April 8, 2022 Author Share Posted April 8, 2022 In the AC you can test the node by turning it "On", same with a program. Just make sure you close and re-open the AC after the node was added. BTW, don't you ever one to turn the device off? If so, I would create a node called BRSensibo then define an On and Off Event. Link to comment
Jimbo.Automates Posted April 8, 2022 Author Share Posted April 8, 2022 Also, while testing you can turn on the option in IFTTT to send you a notification when the automation is run, and watch the log in PG3 with debug level enabled. Link to comment
Athlon Posted April 8, 2022 Share Posted April 8, 2022 Thank you for your quick reply! I just turned the unit on from my AC after restarting the AC - I had not restarted it (always the simple stuff that stymies me). And yes, because I have 4 units I will create 4 On and 4 Off events. I'll attempt that now. Thank you very much! Link to comment
Athlon Posted April 8, 2022 Share Posted April 8, 2022 Is it possible to trigger both an on event and an off event from one node (Applet)? The Applet I created only turns the unit on. I've searched their docs and cannot find a way to use one Applet for both states. Link to comment
Jimbo.Automates Posted April 8, 2022 Author Share Posted April 8, 2022 No, you create 2 applets, but in PG you create one node and set the applet for in and off Link to comment
Athlon Posted April 8, 2022 Share Posted April 8, 2022 Ahhh- Thanks again. Because I have 4 mini-splits I'll need 8 applets then. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.