Connecting to both ETH03 ports?

[caravanboy]

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

[slychiu]

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

[caravanboy]

Ok, thanks for confirming.

[Ian]

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.

[slychiu]

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

[Ian]

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.

[caravanboy]

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.

[caravanboy]

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?

[Ian]

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.

[slychiu]

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