2022.2 issue?

Although I have a handful of incoming text message triggers setup, I almost never use them. But I've noticed that they have stopped working, at least with the 2022.2 update. I can log into the Twilio website, and see that messages are getting to their servers, but Indigo doesn't seem to "see" them and doesn't act on them. Twilio, for me, is a very complex solution, so am far from sure where the problem may be, or where to start troubleshooting....

So found some bread crumbs and realized that I had changed the password for Indigo, which I did not change in the Webhook in Twilio. Additionally, for some reason, web access isn't working with my personal URL, but does work with the reflector. Here is my current Webhook for messages: (slightly altered)

Code: Select all

http://indigo:jltnol@xxxx.indigodomo.net:8176/twilio/ping

as I recall, "indigo" is the username I have for Indigo, "jltnol" is the password I have for indigo. and xxx.indigodomo.net:8176 should send the traffic to my home and 8176 should get the into to Indigo in the right port.
But this too doesn't generate any response in Indigo.

If I remove the port # from the long URL string, at least Indigo gets this message:

Code: Select all

Web Server Warning              undefined page for request /twilio/ping from 54.242.114.1


I've also tried putting in my home IP address and port number, in the web hook, but that too doesn't generate any response.

As I said, Twilio is well beyond my understanding, but only managed to get it to work with a LOT of help, but I'm pretty sure the Webhook is the issue, or there is something else wrong either with the plugin, or with the Indigo Webserver.
*****************************************************************
Just a note I rolled back to 2022.1, and everything works as designed. So I'm assuming there is something with either the plugin and 2022.2, or with 2022.2

<and of course, outgoing text messages work fine>

[jay (support)]

There are several things wrong here:

1)/twilio/ping is not a valid URL path. It looks like the Twilio plugin also required that you install an IWS plugin, so that functionality is not going to work moving forward (IWS plugins are very old and no longer work on our new web server).

2) http://indigo:jltnol@xxxx.indigodomo.net:8176/ - that won't work because reflector connections need HTTPS and do not operate on port 8176 (this never would have worked even before 2022.2).

3) Rather than using username:password, append your API Key to the end of the url: https://xxxx.indigodomo.net/url/path/here?api-key=YOUR-API-KEY-HERE

Note that @FlyingDiver is going to be out of pocket for a couple of weeks I think, so I wouldn't expect a reply any time soon.

Hey Jay

Hope Joe is ok and nothing serious.

I like the idea of the key instead of the password. but am unsure about the URL PATH HERE ? part. I just got finished updating some GPS settings that involved the API key, and that URL contained my reflector and info that pointed to the plugin, like below.

https:/xxx.indigodomo.net/message/se.furtenbach.indigo.plugin.beacon/webhook?api_key=xxxxxxxxxxxxx

So does that mean I need to add the same info for the Twilio plugin to my URL? If so, where do I find this info for the Twilio Plugin? Guessing this might be it?

com.flyingdiver.indigoplugin.twilio

So my final webhook should look something like this?:

Code: Select all

https://xxx.indigodomo.net/message/com.flyingdiver.indigoplugin.twilio/webhook?api-key=xxxxxxxxxx

If I have it right ( and not at all sure I do....) I get this error message in Indigo:

Code: Select all

Web Server Error                message handler failed: plugin with id 'com.flyingdiver.indigoplugin.twilio' doesn't expose an action with id 'webhook'
   Web Server Warning              HTTP 501 error for request /message/com.flyingdiver.indigoplugin.twilio/webhook from 52.55.121.15


If this needs to wait 'til Joe its back, its no big deal.

(api key obscured)

[jay (support)]

As I said above, the Twilio plugin also (apparently) requires an IWS plugin. @FlyingDiver will have to move the functionality from the IWS plugin to the actual Twilio plugin for it to work correctly. At least, that's my understanding. Best to wait for him to catch up on this later.

Got it.

No prob.

The IWS method pre-dates the reflector. See the wiki at https://github.com/FlyingDiver/Indigo-T ... ifications

Use the api token as above instead of username/password.

Sent from my iPhone using Tapatalk

OK so this took awhile.

In reading over the Wiki, I've come up with this URL that goes on the Twilio website Webhook:

Code: Select all

https://usernane:mypassword@xxx.indigodomo.net/message/com.flyingdiver.indigoplugin.twilio/check_messages

And when I sent the first text message, ALL of the message triggers that didn't work before, fired. THAT took me a minute to figure out, but now all is well.

But just our of curiosity, I think I've misread, or at least didn't understand about the API key. So this Twilio website webhook won't work, correct?

Code: Select all

http://xxxxxxxxxx@myurl.com/message/com.flyingdiver.indigoplugin.twilio/check_messages

As always, THANKS!

Use option #3 from Jay’s post that appends the API key to the end of the url.


Sent from my iPhone using Tapatalk

OK

Got it!

Code: Select all

https://xxxxx.indigodomo.net/message/com.flyingdiver.indigoplugin.twilio/check_messages?api-key=XXXXXXXXXX

Thanks!

[matt (support)]

I blanked out the API key in your post, since you don't ever want that to be public.

Yep. I had already changed 5 or 6 digits in the post..