2020-08-10, 06:32
That defeats the purpose of having you learning it on your own. 
The entire process is pretty 'easy' when it comes to troubleshooting, because you can check functionality every step of the way.
Portforwarding and DDNS set up correctly? Do I get a website as a response (/password entry prompt), when I surf to address:port on my smartphone (using a browser
), using the cell network (not Wifi)? If yes, that part is done correctly.
Webserver with Omertus code set up correctly? (F.e. on repl.it) Do I get any error message on repl.it in the terminal? (If yes, kodi hosts config is not set correctly, look at the images in the github thread linked above). Do I see the "test functionality page" on repl.it after pressing start? (If yes, repl.it is set up correctly.) Does the "test functionality page" communicate with my Kodi installation correctly? (If yes, you've used the correct settings to set up the repl.it server.)
After that the only part that is left is setting up IFTTT following the glitch guide in the github readme, but using the repl.it (repl.co) url (the one you see above the testpage), with a simple / command added at first (try /playpause first). Once that works, you have everything in place.
You even can try it without DynDNS (DDNS) at first, just using your public ip address (google "what is my ip" without the quotes on a PC in your home network (WLAN or LAN)), but the problem here is, that the setup would break, whenever your ISP changes your IP address (if it doesnt offer you a static one, that only changes once every three years or so). So thats what you have your DDNS service for. (So you get an url/ip thats always the same, which gets dynamically mapped to the IP your home network is addressable under all the time.)
On repl.it the only part you "invent" is the "token" (choose any word or phrase), all the other fields in settings should be self explanatory. (IP address, public port (the one above 10.000), kodi username and password (see kodi settings page), ...)
The entire process is pretty 'easy' when it comes to troubleshooting, because you can check functionality every step of the way.
Portforwarding and DDNS set up correctly? Do I get a website as a response (/password entry prompt), when I surf to address:port on my smartphone (using a browser
), using the cell network (not Wifi)? If yes, that part is done correctly.Webserver with Omertus code set up correctly? (F.e. on repl.it) Do I get any error message on repl.it in the terminal? (If yes, kodi hosts config is not set correctly, look at the images in the github thread linked above). Do I see the "test functionality page" on repl.it after pressing start? (If yes, repl.it is set up correctly.) Does the "test functionality page" communicate with my Kodi installation correctly? (If yes, you've used the correct settings to set up the repl.it server.)
After that the only part that is left is setting up IFTTT following the glitch guide in the github readme, but using the repl.it (repl.co) url (the one you see above the testpage), with a simple / command added at first (try /playpause first). Once that works, you have everything in place.
You even can try it without DynDNS (DDNS) at first, just using your public ip address (google "what is my ip" without the quotes on a PC in your home network (WLAN or LAN)), but the problem here is, that the setup would break, whenever your ISP changes your IP address (if it doesnt offer you a static one, that only changes once every three years or so). So thats what you have your DDNS service for. (So you get an url/ip thats always the same, which gets dynamically mapped to the IP your home network is addressable under all the time.)
On repl.it the only part you "invent" is the "token" (choose any word or phrase), all the other fields in settings should be self explanatory. (IP address, public port (the one above 10.000), kodi username and password (see kodi settings page), ...)
