Errors configuring Immediate Notifications

Posted on
Fri May 14, 2021 12:06 pm
FlyingDiver offline
User avatar
Posts: 7189
Joined: Jun 07, 2014
Location: Southwest Florida, USA

Re: Errors configuring Immediate Notifications

You need to create a twilio folder in the plugins folder of the Indigo Web Server, and put those two files in it. That's why the path to those files in the GitHub repository is "IWS/plugins/twilio". If you downloaded the release zip, you could have dragged the twilio folder to the existing plugin folder.

joe (aka FlyingDiver)
my plugins: http://forums.indigodomo.com/viewforum.php?f=177

Posted on
Fri May 14, 2021 12:07 pm
FlyingDiver offline
User avatar
Posts: 7189
Joined: Jun 07, 2014
Location: Southwest Florida, USA

Re: Errors configuring Immediate Notifications

And make sure you're not confusing the twilio folder inside the plugin (which is the twilio API library) with the twilio folder in the Indigo webserver plugins folder.

joe (aka FlyingDiver)
my plugins: http://forums.indigodomo.com/viewforum.php?f=177

Posted on
Fri May 14, 2021 3:03 pm
jltnol offline
Posts: 989
Joined: Oct 15, 2013

Re: Errors configuring Immediate Notifications

So still no go. I'm attaching a pic of the files and path to my web server plugin... the files now match yours. I've re-started the server and the router, but still get the same error messages.

Code: Select all
 Error                           XML Parse Error: not well-formed (invalid token)
   Error                           On character 0 of line number 1.
   Client authentication failed - bad XML received (54.198.93.16)
   Client disconnected (54.198.93.16)

I can access Indigo from my phone over the cell network and have access via both the Touch App, and a web browser, so I know I've got the ports set up correctly both on my router and in Indigo.

Clearly Twilio is getting thru to the Indigo web server, but something is still not working.

I don't understand the "curl" command or where to issue it from, so will do some learning' about that to see if I can get at least this to work at least locally.

If I may humbly suggest, you might consider temporarily replacing the URL on your Twilio account to your current IP address with the port number, bypassing the reflector, just to see if that solution even works. Could be I'm just beating a dead horse. :roll:

And since this seems to be some kind of authentication issue, I went ahead and changed both the username and password in Indigo, just to BE SURE I have the right, and entered the new credentials in the Twilio URL... exact same error messages..
Attachments
Screen Shot 2021-05-14 at 3.14.45 PM.png
Screen Shot 2021-05-14 at 3.14.45 PM.png (483.16 KiB) Viewed 9081 times
Last edited by jltnol on Fri May 14, 2021 3:10 pm, edited 1 time in total.

Posted on
Fri May 14, 2021 3:09 pm
FlyingDiver offline
User avatar
Posts: 7189
Joined: Jun 07, 2014
Location: Southwest Florida, USA

Re: Errors configuring Immediate Notifications

I expect you're still trying to use port 1176. That won't work. You need to use 8176.

joe

joe (aka FlyingDiver)
my plugins: http://forums.indigodomo.com/viewforum.php?f=177

Posted on
Fri May 14, 2021 3:13 pm
FlyingDiver offline
User avatar
Posts: 7189
Joined: Jun 07, 2014
Location: Southwest Florida, USA

Re: Errors configuring Immediate Notifications

Hard to see, but the web server is on port 8176.
Attachments
Screen Shot 2021-05-14 at 5.11.40 PM.png
Screen Shot 2021-05-14 at 5.11.40 PM.png (1.07 MiB) Viewed 9077 times

joe (aka FlyingDiver)
my plugins: http://forums.indigodomo.com/viewforum.php?f=177

Posted on
Fri May 14, 2021 3:35 pm
jltnol offline
Posts: 989
Joined: Oct 15, 2013

Re: Errors configuring Immediate Notifications

Actually, I've been trying both port 1176 and 8176 in the URL every time I make a change... with 8176, there is absolutely no response from Indigo. Nothing in the log. And again, I can reach both Indigo ports from the cell network, so the router and Indigo are both setup correctly.

I only have the trigger set up to fire when the variable becomes equal to True. When that happens the only thing the trigger does is to Check for Messages. I haven't set it to reset the variable yet.

So just not sure what else would be causing the authentication to fail.

With that said, is there possibly something on the Twilio site that might be wrong?
I have the "Configure With" pop up set to Webhook, TwiMl Bins, Functions, Studio, or Proxy

When a message comes in, that pop up is set to Webhook, and my URL is in the field, followed by another pop up set to HTTP GET
The Primary Handler Fails are all default... Webhooks --blank-- HTTP Post

Posted on
Fri May 14, 2021 3:37 pm
FlyingDiver offline
User avatar
Posts: 7189
Joined: Jun 07, 2014
Location: Southwest Florida, USA

Re: Errors configuring Immediate Notifications

Open a Terminal window. Type in "curl" space, then the URL you put into the Twilio webhook. Paste the output here.

And stop trying to use 1176. It's never going to work.

joe (aka FlyingDiver)
my plugins: http://forums.indigodomo.com/viewforum.php?f=177

Posted on
Fri May 14, 2021 3:45 pm
jltnol offline
Posts: 989
Joined: Oct 15, 2013

Re: Errors configuring Immediate Notifications

Code: Select all
curl: (35) error:1400410B:SSL routines:CONNECT_CR_SRVR_HELLO:wrong version number

Posted on
Fri May 14, 2021 3:46 pm
FlyingDiver offline
User avatar
Posts: 7189
Joined: Jun 07, 2014
Location: Southwest Florida, USA

Re: Errors configuring Immediate Notifications

Use http not https.

joe (aka FlyingDiver)
my plugins: http://forums.indigodomo.com/viewforum.php?f=177

Posted on
Fri May 14, 2021 3:58 pm
jltnol offline
Posts: 989
Joined: Oct 15, 2013

Re: Errors configuring Immediate Notifications

Code: Select all
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
   <head>
      <title>Indigo Home Control Server</title>
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
      <link rel="stylesheet" media="screen" type="text/css" href="/twilio/css/global4.css" />
      <link rel="stylesheet" media="screen" type="text/css" href="/twilio/css/indigo4.css" />
      <link rel="stylesheet" media="screen" type="text/css" href="/twilio/css/fonts.css" />
   </head>
   <body>
      <center>
   access denied
      </center>
   </body>
</html>
Automation-iMac:~ kitchen$

Posted on
Fri May 14, 2021 4:01 pm
FlyingDiver offline
User avatar
Posts: 7189
Joined: Jun 07, 2014
Location: Southwest Florida, USA

Re: Errors configuring Immediate Notifications

Progress. You're actually talking to the Indigo web server. Now the problem is the probably username and password, as specified in the Indigo "Start Local Server..." dialog. To avoid issues when passing those through the HTTP process, make sure they're only alphanumeric with no special characters.

joe (aka FlyingDiver)
my plugins: http://forums.indigodomo.com/viewforum.php?f=177

Posted on
Fri May 14, 2021 4:14 pm
jltnol offline
Posts: 989
Joined: Oct 15, 2013

Re: Errors configuring Immediate Notifications

no special characters

BINGO

Got rid of those in the password, and got a 'true' in the variable.

So two things: Since I'm not using a reflector, what is the potential danger of my Twilio URL being http and not https...

and secondarily, you mentioned revising the GitHub instructions... something I'd be more than happy to take a stab at for you. I can send what I come up with, you can use it, revise it, or trash it.

And I can't possibly thank you enough for taking time for this today.

Posted on
Fri May 14, 2021 4:20 pm
FlyingDiver offline
User avatar
Posts: 7189
Joined: Jun 07, 2014
Location: Southwest Florida, USA

Re: Errors configuring Immediate Notifications

The wiki instructions are correct for the reflector. I could probably add something about going direct to 8176.

You've also discovered the issue with NOT using the reflector. The web server can't do https, and you have to send your actual Indigo access credentials. Which is a problem, IMO. It's been brought up before, and there are ways around it, none of which are simple. You can modify the the cherrypy web server to do https, or you can set up a reverse proxy to convert from https to http.

Or you can use the HTTPd plugin so that you're using single purpose credentials. There's a problem using the HTTPd-2 plugin, though, so you'd have to use the older one which isn't on the store anymore. I'm thinking about how to fix the newer plugin so it can be used for this.

joe (aka FlyingDiver)
my plugins: http://forums.indigodomo.com/viewforum.php?f=177

Who is online

Users browsing this forum: No registered users and 4 guests