2018-07-26, 10:43
Just set this up this morning and so far is working great!
Thank you for all your work tkislan
Thank you for all your work tkislan
(2018-07-31, 00:52)Bryangauvin Wrote: Ok, so Just got this up and running. Works great. However, to get it up and running I had to delink my echo from the fireTV so I cant use the echo to command my firetv & kodi. Is this correct? Is there a way to make it work both ways?Multiple users are having issues with this, and my best suggestion was to contact Amazon support. As I can't affect where the Alexa forwards the requests
(2018-07-25, 18:29)tkislan Wrote:I updated my living room Windows 8 machine to Windows 10 hoping it would solve this problem, but no still having also this same issue. It's weird though that in my other windows 10 computer it works just fine.(2018-07-25, 18:26)Shaboobala Wrote: If I go to the Kodi connect website it is secure. However the IP address https://46.101.194.37/ the app is using to connect is showing as unsecure from chrome browser for some reasonBecause certificate is always issued to domain, no to IP address.
Kodi connect addon is actually using a normal hostname to connect to the server, which gets translated to IP address.
But certificate validation should happen against the hostname.
As I said before, there is something wrong with the underlying implementation of network library, which causes this to fail.