| Posted: Thursday Feb 9th, 2012 11:51 am |
|
1st Post |
koutsogiannis
Comfort Installers
| Joined: | Tuesday Oct 23rd, 2007 |
| Location: | Athens, Greece |
| Posts: | 40 |
| Status: |
Offline
|
back to top
|
I try to connect remotely to the comfort with client. The error message I get is that the photo upload. The version I have is the past. In earlier versions remotely connect without any problems. The Wizards Comfort connect normally. Attachment: client problem connection111.jpg (Downloaded 52 times)
|
| Posted: Thursday Feb 9th, 2012 01:13 pm |
|
2nd Post |
Ingo
UCM Pi Users
| Joined: | Sunday Jan 21st, 2007 |
| Location: | South Africa |
| Posts: | 562 |
| Status: |
Offline
|
back to top
|
Does it work on the local LAN?
Perhaps when you try to connect remotely you forgot to open UDP port 65535 on your router. That is the port that the Tibbo Module uses for connection information.
Newer Client versions check the Tibbo Module before it makes a connection.
Regards,
Ingo
|
| Posted: Thursday Feb 9th, 2012 05:04 pm |
|
3rd Post |
koutsogiannis
Comfort Installers
| Joined: | Tuesday Oct 23rd, 2007 |
| Location: | Athens, Greece |
| Posts: | 40 |
| Status: |
Offline
|
back to top
|
I opened the door, and 65535, but not connect. Version 1.20.2.35 is linked properly. What could be the problem? Last edited on Thursday Feb 9th, 2012 05:05 pm by koutsogiannis
|
| Posted: Thursday Feb 9th, 2012 06:16 pm |
|
4th Post |
ninotorres
Member
| Joined: | Tuesday Nov 10th, 2009 |
| Location: | |
| Posts: | 36 |
| Status: |
Offline
|
back to top
|
I have the same problem.
|
| Posted: Thursday Feb 9th, 2012 07:12 pm |
|
5th Post |
juwi_uk
Member
back to top
|
So as Ingo says you need whatever TCP port you are connecting on (1001 typically) and UDP port 65535.
The timeout for the UDP response is hardcoded at 3 seconds so it looks like you didnt get a reponse within that time. Does it repeatedly fail or just sometimes?
I'll make the Tibbo checking an option in the next build so you can turn off.
Julian
|
| Posted: Thursday Feb 9th, 2012 08:11 pm |
|
6th Post |
| Posted: Thursday Feb 9th, 2012 08:42 pm |
|
7th Post |
| Posted: Thursday Feb 9th, 2012 08:45 pm |
|
8th Post |
juwi_uk
Member
back to top
|
So it's either UDP port 65535 being blocked then or the link being slow and you not getting a response back from the Tibbo within 3 seconds. I'll make more configurable next release for these scenarios.
J
|
| Posted: Sunday Feb 12th, 2012 09:55 am |
|
9th Post |
ninotorres
Member
| Joined: | Tuesday Nov 10th, 2009 |
| Location: | |
| Posts: | 36 |
| Status: |
Offline
|
back to top
|
The patched version worked perfectly.
And yes I don't have the mentioned UDP port opened, so that's why it fails.
My question now is, what does that checking for Tibo module adds? I was fine with only one well defined port opened in my firewall.
Thanks,
Nino
|
| Posted: Sunday Feb 12th, 2012 03:45 pm |
|
10th Post |
juwi_uk
Member
back to top
|
Hi
I added this functionality because the tibbo module can only accept one connection at a time. So via this tibbo management port i can check if the ucm is already connected to something (eg comfigurator, iphone app, Wizcomfort etc) and warn the user appropriately either to gracefully concede to the existing connection or force it to close so you can grab it! I found this useful for eth02 modules though less important with later Eth02 ones as they now auto disconnect on logoff.
J
|
| Posted: Monday Feb 13th, 2012 10:17 am |
|
11th Post |
ninotorres
Member
| Joined: | Tuesday Nov 10th, 2009 |
| Location: | |
| Posts: | 36 |
| Status: |
Offline
|
back to top
|
Ok, I understand that need. And I want it too.
But my feedback is that checking should be made optional in the ComfortClient.
In my current implementation I would disable it for sure.
Thanks,
Nino Torres
|
|
