2020-07-08, 20:03
Yes, the server responded differently. 
401 means authentication failed (you are missing the token) 500 means, more stuff is garbled up.
- Its not so difficult. Get the glitch instance to work first. (Test with the internal testing option (sunglasses at the top))
- Set up one IFTTT command, the same it is described in the readme ( https://github.com/OmerTu/GoogleHomeKodi/ ), make it the one for playpause
- Then look at the screenshot above and make sure you set up pipedream exactly the same (except for different server url and a different token)
- then hit curl in the fist step in pipedream, and copy the url at the bottom into the IFTTT url field. Save. Thats it.
If you use the code from the link provided, you really just click into the node.js object in pipedream, and post it into 'whats already there'. Then you replace url and the token bracket, and then you hit deploy.
I can set up an action in less than 10 seconds. Its not rocketscience. Look at the image again. If you have to.
401 means authentication failed (you are missing the token) 500 means, more stuff is garbled up. - Its not so difficult. Get the glitch instance to work first. (Test with the internal testing option (sunglasses at the top))
- Set up one IFTTT command, the same it is described in the readme ( https://github.com/OmerTu/GoogleHomeKodi/ ), make it the one for playpause
- Then look at the screenshot above and make sure you set up pipedream exactly the same (except for different server url and a different token)
- then hit curl in the fist step in pipedream, and copy the url at the bottom into the IFTTT url field. Save. Thats it.
If you use the code from the link provided, you really just click into the node.js object in pipedream, and post it into 'whats already there'. Then you replace url and the token bracket, and then you hit deploy.
I can set up an action in less than 10 seconds.
Its not rocketscience. Look at the image again. If you have to.
