Touch Connection Question

[matt (support)]

There are a lot of posts about connection issues recently .. this says something is not quite right!!

What posts besides this one, which is specific to the Indigo Touch 1.5 upgrade just released yesterday (you had a connectivity problem before 1.5, right?), are you referring to? The only posts concerning Indigo Touch network connectivity issues I'm aware of are on this thread, and all but the your case is resolved. Can you provide links to what forum threads you are talking about? Definitely do try disabling your Firewall so we can isolate where the problem is coming from exactly.

setting the firewall to allow all connections yields the same results "connection to indigo server failed"

[matt (support)]

Questions:

1) What is shown in Indigo's Event Log window when you try to connect? Copy/paste whatever is seen into a forum post.

2) In the Settings panel of Indigo Touch, what are you clicking on exactly? Did you manually add connection settings or are you clicking on the one that is found automatically via Bonjour when Indigo Server launches?

3) If the latter on #2, then delete that Bonjour added connection, quit Indigo Touch, and then re-launch Indigo Touch. Does it automatically get added back (to the settings list) upon relaunch?

firewall log - Nov 7 21:21:23 MasterCore Firewall[41]: Allow perl connecting from 192.168.1.101:50133 uid = 0 proto=6
Nov 8 08:11:51 MasterCore Firewall[41]: IndigoServer is listening from 127.0.0.1:50004 uid = 501 proto=6
Nov 8 08:11:51 MasterCore Firewall[41]: IndigoServer is listening from 0.0.0.0:1176 uid = 501 proto=6
Nov 8 08:11:51 MasterCore Firewall[41]: IndigoServer is listening from 0.0.0.0:5317 uid = 501 proto=6
Nov 8 08:11:54 MasterCore Firewall[41]: Python is listening from 0.0.0.0:8176 uid = 501 proto=6
Nov 8 08:12:18 MasterCore Firewall[41]: Allow Python connecting from 192.168.1.101:50342 uid = 0 proto=6
Nov 8 08:12:31 MasterCore Firewall[41]: Allow perl connecting from 192.168.1.101:50343 uid = 0 proto=6
Nov 8 08:12:32 MasterCore Firewall[41]: Allow perl connecting from 192.168.1.101:50344 uid = 0 proto=6
Nov 8 08:12:32 MasterCore Firewall[41]: Allow perl connecting from 192.168.1.101:50345 uid = 0 proto=6
Nov 8 08:12:32 MasterCore Firewall[41]: Allow perl connecting from 192.168.1.101:50346 uid = 0 proto=6
Nov 8 08:12:32 MasterCore Firewall[41]: Allow perl connecting from 192.168.1.101:50347 uid = 0 proto=6
Nov 8 08:12:40 MasterCore Firewall[41]: Allow Python connecting from 192.168.1.101:50348 uid = 0 proto=6
Nov 8 08:14:06 MasterCore Firewall[41]: Allow Python connecting from 192.168.1.101:50369 uid = 0 proto=6
Nov 8 08:24:13 MasterCore Firewall[41]: Allow perl connecting from 192.168.1.101:50378 uid = 0 proto=6
Nov 8 08:24:14 MasterCore Firewall[41]: Allow perl connecting from 192.168.1.101:50379 uid = 0 proto=6
Nov 8 08:24:14 MasterCore Firewall[41]: Allow perl connecting from 192.168.1.101:50380 uid = 0 proto=6
Nov 8 08:24:14 MasterCore Firewall[41]: Allow perl connecting from 192.168.1.101:50381 uid = 0 proto=6
Nov 8 08:24:14 MasterCore Firewall[41]: Allow perl connecting from 192.168.1.101:50382 uid = 0 proto=6
Nov 8 08:24:22 MasterCore Firewall[41]: Allow perl connecting from 192.168.1.101:50383 uid = 0 proto=6
Nov 8 08:58:09 MasterCore Firewall[41]: iTunes is listening from 0.0.0.0:3689 uid = 501 proto=6
Nov 8 08:58:09 MasterCore Firewall[41]: iTunes is listening from :::3689 uid = 501 proto=6
Nov 8 17:41:24 MasterCore Firewall[41]: Allow perl connecting from 192.168.1.101:50546 uid = 0 proto=6
Nov 8 17:41:26 MasterCore Firewall[41]: Allow perl connecting from 192.168.1.101:50547 uid = 0 proto=6
indigo event log =
Nov 8, 2009 5:34:10 PM
Starting Indigo Server version 4.1.1
Loading attachments
"device target attachment.scpt" script loaded
"group target attachment.scpt" script loaded
"growl attachment.scpt" script loaded
"iTunes attachment.scpt" script loaded
"scenes attachment.scpt" script loaded
"time stamp attachment.scpt" script loaded
Bonjour registered "Indigo - 268Lans"
Indigo Cocoa client authenticated
WebServer client authenticated
WebServer started on port 8176 -- authentication disabled

Nov 8, 2009 5:34:13 PM
Error usb connection failed -- retrying connection for 5 seconds
Connected to SmartHome PowerLinc Controller
PowerLinc firmware version 5.13
PowerLinc standalone operation disabled
Indigo directly controlling automation logic
WebServer Indigo Touch client connected from 192.168.1.101

Nov 8, 2009 5:35:00 PM
WebServer Indigo Touch client connected from 192.168.1.101
Time/Date Action Parlor1 Spot ON
Time/Date Action Studio Desk ON
Time/Date Action Studio Reading Lamp ON
Time/Date Action Guest Lamp ON
Time/Date Action Den Torch ON
Time/Date Action Den Lamp ON
Time/Date Action Parlor2 Ceiling ON
Time/Date Action LampPOST ON
Sent X10 "Parlor1 Spot" on
Sent X10 "Studio Desk" on (address)
Sent X10 "Studio Reading Lamp" on (address)
Sent X10 "Guest Lamp" on (address)
Sent X10 "Den Torch" on (address)
Sent X10 "Den Lamp" on
Sent X10 "Parlor2 Ceiling" on (address)
Sent X10 "LAMP POST" on

Nov 8, 2009 5:36:06 PM
WebServer Indigo Touch client connected from 192.168.1.101

Nov 8, 2009 5:45:00 PM
Time/Date Action Studio Desk DIM
Time/Date Action Den Torch DIM
Time/Date Action Parlor2 Ceiling DIM
Sent X10 "Studio Desk" dim by 40
Sent X10 "Den Torch" dim by 45
Sent X10 "Parlor2 Ceiling" dim by 55

The touch client is trying to connect - the firwall log shows no appended information - the indigo event log shows nothing indicative of trouble.

if is stop the indigo server and restart the touch app will register the server and connect - leave iindigo app on the touch use another app and return and the touch will not connect - the firewalll sees no activity and the cycle continues and is repeatable.

if i stop/start the indigo server the touch connects - leave the indigo touch app or turn off the touch then return to the indigo app or launch it - the touch will not reconnect as if the server is no longer listening or the touch is not broadcasting the request- since the firewall sees no activity it's hard to know where to look.

[matt (support)]

Please answer my #2 and #3 questions above.

2) - i've used the discovered connection as well as setting the manual connection .. once it fails it's done until the server is restarted.

3).i deleted the server a new one will reappear when i restart the server.

i have changed the firewall settings from specific to allow all

i've deleted the incoming requests in the firewall restarted the indigo and touch clients and i've gotten that window asking to allow connections ...

i've done all these things ... i've even calmed my rage and found humor in the cycle of software updates ... so let me also say thank you for any assistance you can offer!!

[matt (support)]

First - everything worked well in prior versions to 4.1.1.

Prior to version 4.1.1, were you using 4.1.0? Based on the version tracking I've looked at, I'm not seeing anything related to Indigo's Web server engine that changed from 4.1.0 to 4.1.1 that could have caused this type of problem. If you were running a version older than 4.1.0, then there might have been relevant changes.

Once it gets into the bad state (after the initial connect), what happens if you launch Safari on your iPhone and try to connect to the Indigo Web Server? Does that work, or does that connection fail as well?

If that connection fails as well, then what happens if you try Safari on your Mac itself?

i have a ipod touch but all other network based aps work in addition to slimserver and ipeng which also use bonjour to communicate and can also be seen in the firewall log as they connect. i upgraded to 4.1.1 and then indigo touch 1.5.0 ... the problem existed prior to 1.5.0

but not prior to 4.1.1

[matt (support)]

My question is what version you were running before 4.1.1 -- was it 4.1.0? Also see my other questions above and steps I want you to perform. Without that troubleshooting, I can not help you diagnosis the problem.

Prior to version 4.1.1, were you using 4.1.0? = Yes

Based on the version tracking I've looked at, I'm not seeing anything related to Indigo's Web server engine that changed from 4.1.0 to 4.1.1 that could have caused this type of problem. If you were running a version older than 4.1.0, then there might have been relevant changes.

Once it gets into the bad state (after the initial connect), what happens if you launch Safari on your iPhone and try to connect to the Indigo Web Server?

I can reach web pages with safari on my ipod touch - i cannot at that time connect to the web server.

Does that work, or does that connection fail as well? - it fails

If that connection fails as well, then what happens if you try Safari on your Mac itself

[matt (support)]

So once it gets into the bad state you cannot, using Safari on your Mac, connect to the Indigo Web Server using a URL like this:

Code: Select all

http://127.0.0.1:8176/

But the same URL does work immediately after you restart the Indigo Server?

What is the result from the Terminal when you copy/paste this line (once it is in the bad state):

Code: Select all

ps -axww | grep Indigo

once in failed mode i can reach http://192.168.1.105:8176 oddly enough. i've never used the webpages ... this is a work-around then?!!

[matt (support)]

once in failed mode i can reach http://192.168.1.105:8176 oddly enough. i've never used the webpages ... this is a work-around then?!!

Are you saying you can reach it via that URL on your iPod touch from Safari, or are you on your Mac Safari? (try both please)

What happens if from Indigo Touch you create a new connection that looks like this:

Code: Select all

192.168.1.105:8176

I'm not looking for workarounds yet, I'm trying to figure out where the failure is.