Comfort Home Automation/ Security System Forums Home
Home Search search Menu menu Not logged in - Login | Register

Connecting to both ETH03 ports?
 Moderated by: ident Page:    1  2  Next Page Last Page  
 New Topic   Reply   Printer Friendly 
 Rate Topic 
AuthorPost
 Posted: Tuesday Mar 2nd, 2021 09:26 pm
   PM  Quote  Reply 
1st Post
caravanboy
Member
 

Joined: Wednesday Mar 8th, 2017
Location: United Kingdom
Posts: 114
Status: 
Offline

  back to top

Hi,
My ETH03 has 2 ports configured 1001 and 1002.
I usually use the first one for Comfigurator and I've recently been testing a separate Comfort->MQTT Bridge connecting to the port too.
I had forgotten there was a second port and I've now proved I can connect both at the same time - e.g. Comfigurator to 1001, and my MQTTBridge to 1002.
However, my bridge also seems to see messages to/from Comfigurator, so I assume the Comfort connection is more of a bus than an individual point-to-point connection?
So... can I assume it would NOT be safe to use Comfigurator to do any programming if my module was also connected and active? i.e. I should only have 1 device connected to Comfort via ETH03 when programming?
Thanks



 Posted: Wednesday Mar 3rd, 2021 12:42 am
   PM  Quote  Reply 
2nd Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 5160
Status: 
Offline

  back to top

However, my bridge also seems to see messages to/from Comfigurator, so I assume the Comfort connection is more of a bus than an individual point-to-point connection? So..

Your 3nd port will see messages to /from Comfort, not Comfigurator

can I assume it would NOT be safe to use Comfigurator to do any programming if my module was also connected and active? i.e. I should only have 1 device connected to Comfort via ETH03 when programming?

It is safe to use Cmfigurator. However you cannot use Comfigurator to read and write to Comfort at the same time as that will block the 2nd port



 Posted: Wednesday Mar 3rd, 2021 07:44 am
   PM  Quote  Reply 
3rd Post
caravanboy
Member
 

Joined: Wednesday Mar 8th, 2017
Location: United Kingdom
Posts: 114
Status: 
Offline

  back to top

Ok, thanks for confirming.



 Posted: Wednesday Mar 3rd, 2021 07:45 am
   PM  Quote  Reply 
4th Post
Ian
Member
 

Joined: Saturday Aug 19th, 2006
Location: United Kingdom
Posts: 209
Status: 
Offline

  back to top

I use both ports in the way described and have been doing for some time. It works well. I recently moved to MQTT and have been impressed with how well it works.



 Posted: Wednesday Mar 3rd, 2021 07:58 am
   PM  Quote  Reply 
5th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 5160
Status: 
Offline

  back to top

what MQTT bridge are you two  using? We would like to test it



 Posted: Wednesday Mar 3rd, 2021 08:08 am
   PM  Quote  Reply 
6th Post
Ian
Member
 

Joined: Saturday Aug 19th, 2006
Location: United Kingdom
Posts: 209
Status: 
Offline

  back to top

I have paho; https://pypi.org/project/paho-mqtt/ I then use a pyhon script that reads Comfort. It was created by a member on here - I think Koochyrat may be his/her name.

Last edited on Wednesday Mar 3rd, 2021 11:52 am by Ian



 Posted: Wednesday Mar 3rd, 2021 08:09 am
   PM  Quote  Reply 
7th Post
caravanboy
Member
 

Joined: Wednesday Mar 8th, 2017
Location: United Kingdom
Posts: 114
Status: 
Offline

  back to top

I'm using this one that is described on another thread on this forum: https://github.com/koochyrat/comfort2

The quirk I am having is without timeouts though. When I just have my MQTT bridge connected to Comfort on the 2nd port it does not seem to timeout. However, when I'm using the 1st port it times out at random intervals, which is annoying.

Both ports are set in ETHO03 to timeout after 2 mins. The MQTT bridge uses the "cc" echo command every 30 seconds to avoid timeouts, so I do not understand why port 1 would still regularly lose connection every few mins.



 Posted: Wednesday Mar 3rd, 2021 11:22 am
   PM  Quote  Reply 
8th Post
caravanboy
Member
 

Joined: Wednesday Mar 8th, 2017
Location: United Kingdom
Posts: 114
Status: 
Offline

  back to top

slychiu - re. my timeout comments in the message above. Any thoughts on that? I've switched the MQTT bridge back to port 1 this morning check and it has started doing the frequent timeouts again. When connected to port 2 it is rock solid and never seems to time out. Is this an expected difference between the ports even though Comfort Server Manager claims they are both set at 2 minute timeouts? I'm on firmware 2.23 on ETH03

Do you see that behaviour too, Ian?



 Posted: Wednesday Mar 3rd, 2021 12:06 pm
   PM  Quote  Reply 
9th Post
Ian
Member
 

Joined: Saturday Aug 19th, 2006
Location: United Kingdom
Posts: 209
Status: 
Offline

  back to top

I'm not. I do recall that I reset the timeout for another reason. At the moment Comfort Server Manager is not seeing the ETH03 0 don't know why - so I can't look. I think I may have set it to 0, meaning don't timeout. I suspect slychui will advise.



 Posted: Thursday Mar 4th, 2021 01:55 am
   PM  Quote  Reply 
10th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 5160
Status: 
Offline

  back to top

The time out should also work on Port 1.
Could it be that you did a write or read to comfort. This would have disconnected the other port



 Posted: Thursday Mar 4th, 2021 07:40 am
   PM  Quote  Reply 
11th Post
caravanboy
Member
 

Joined: Wednesday Mar 8th, 2017
Location: United Kingdom
Posts: 114
Status: 
Offline

  back to top

No, Comfigurator is not running. The only thing ever connecting to Comfort in my solution is Comfigurator or the MQTT Bridge.

The timeout does seem to be related to activity from Comfort. After we go to bed (i.e. no PIR movement) then the MQTT bridge stays connected all night on Port 1 with no timeouts at all. As soon as we start moving around zones again then the timeouts start happen.

When there is plenty of normal activity the connections seem to be at exactly 2 minutes to the second. When there are gaps in zone activity then the timeout takes long. That is VERY strange. Even yesterday when I was home alone sat working in a room with a single PIR the timeouts still happened fairly often.

I'll download my log this evening and see if I can spot any patterns.

I will also swap back to port 2 and run it today and check that it definitely does not timeout on that port.



 Posted: Thursday Mar 4th, 2021 07:53 am
   PM  Quote  Reply 
12th Post
Ian
Member
 

Joined: Saturday Aug 19th, 2006
Location: United Kingdom
Posts: 209
Status: 
Offline

  back to top

I've had my MQTT running on both ports, I swapped for another reason, with no issues.



 Posted: Thursday Mar 4th, 2021 08:01 am
   PM  Quote  Reply 
13th Post
caravanboy
Member
 

Joined: Wednesday Mar 8th, 2017
Location: United Kingdom
Posts: 114
Status: 
Offline

  back to top

Hmm, well, in the last 10 mins port 2 has not timed out so far yet, which would be unusual for port 1.

Maybe this is a difference in behaviour between different firmwares, Ian - what versions do you have?

I can see in the MQTT bridge log that I receive an unsolicited "LU00" just before the bridge reports a timeout, so Comfort seemed to be deliberately choosing to send the LU00 for some reason, but only from Port 1.



 Posted: Thursday Mar 4th, 2021 11:12 am
   PM  Quote  Reply 
14th Post
Ian
Member
 

Joined: Saturday Aug 19th, 2006
Location: United Kingdom
Posts: 209
Status: 
Offline

  back to top

The board is 7.183, UCM is 7.141



 Posted: Thursday Mar 4th, 2021 12:45 pm
   PM  Quote  Reply 
15th Post
caravanboy
Member
 

Joined: Wednesday Mar 8th, 2017
Location: United Kingdom
Posts: 114
Status: 
Offline

  back to top

Hmm. My mainboard is 7.116 and the ETH03's UCM is 7.098

Are there any known issues with differences in timeout behaviour between firmwares slychiu?

Port 2 has also been connected fine for the last 5 hours with no timeout and plenty of zone activity.



 Posted: Thursday Mar 4th, 2021 02:41 pm
   PM  Quote  Reply 
16th Post
Ian
Member
 

Joined: Saturday Aug 19th, 2006
Location: United Kingdom
Posts: 209
Status: 
Offline

  back to top

Any reason why you shouldn't update?



 Posted: Thursday Mar 4th, 2021 02:54 pm
   PM  Quote  Reply 
17th Post
caravanboy
Member
 

Joined: Wednesday Mar 8th, 2017
Location: United Kingdom
Posts: 114
Status: 
Offline

  back to top

I did consider updating a few weeks ago but when I read some of the firmware release notes I think there was something that mildly concerned me, I forget what. I work in IT so I shouldn't be averse to updates but they always make me a little more nervous on hardware, especially when everything else all seems okay :) Although we've never resolved my long-running issue with why the SMS messages get delayed during power failures and I do recall seeing the GSM4 firmware mentioned SMS buffer increases. Anyway, I'm digressing... no real reason, so I may just refresh my memory on how to do one (been a couple of years I think) and then bit the bullet and update them all.

I'll come back here and post an update in a few days to say if it makes any difference



 Posted: Friday Mar 5th, 2021 12:53 am
   PM  Quote  Reply 
18th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 5160
Status: 
Offline

  back to top

try setting the time out to 0 for testing if it still logs out



 Posted: Tuesday Mar 9th, 2021 04:31 pm
   PM  Quote  Reply 
19th Post
caravanboy
Member
 

Joined: Wednesday Mar 8th, 2017
Location: United Kingdom
Posts: 114
Status: 
Offline

  back to top

Hi Slychiu - I set timeout to zero on port 1001. It then behaves same as port 1002 and never times out.

Setting it back to "02" (which I assume is minutes and not seconds, as the UI doesn't say) means port 1001 has now gone back to timing out again every few mins.

I have not yet had time to try the firmware upgrades.

Does the timeout 0 behaviour give you any clues/thoughts?



 Posted: Wednesday Mar 10th, 2021 12:31 am
   PM  Quote  Reply 
20th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 5160
Status: 
Offline

  back to top

02 means 2 minutes. That should time out every 2 minutes so it looks like it is workng
Anyway please upgrade to the latest firmware, as we should not be troubleshooting using old firmware which may have other bugs which have been fixed



 Current time is 10:55 amPage:    1  2  Next Page Last Page  
Top




UltraBB 1.172 Copyright © 2007-2014 Data 1 Systems