Connecting to both ETH03 ports?

[caravanboy]

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.

[Ian]

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

[caravanboy]

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.

[Ian]

The board is 7.183, UCM is 7.141

[caravanboy]

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.

[Ian]

Any reason why you shouldn\'t update?

[caravanboy]

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

[slychiu]

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

[caravanboy]

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?

[slychiu]

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