Hi

I have recently upgraded my home network to use the Unifi products and as part of this I have created separate VLANs with appropriate firewall rules for all my various devices ("Secure". "IOT", "Camera", "Guest" etc)

After I moved my two comfort ETH03 to the new IOT VLAN I can no longer access them with the Server Manager software. They are defiantly on the correct VLAN because the switch port enforces the VLAN and IP address. I can access both systems with the app through those IP addresses.

My main PC with "Configurator" is on the "Secure" VLAN so I have also tried a laptop which I can easily connect to the IOT VLAN so its the same as the ETH03 but it still wont see them. I have even changed the configuration of the IOT into the "Trusted Group" so there are no firewall rules interfering but still no good. I have checked the Firewall log and cant see anything about it being blocked. Have added Server Manager as an allowed app to the Windows Firewall.

I have seen mentioned of using Wireshark to look for packets but it appears you need to be an expert to know the filters etc necessary.

Any suggestions?
Phil

I have a long running problem where I usually cannot sign-in to Comfort when it dials me after an alarm. (separate forum thread about that)

Is there any way I can force the dial-outs to stop?  If it is in Night Mode and I'm at home, I have signed in on a keypad and set Security Off but the system still keeps trying to dial-out.

Is there any Action I can execute which will cancel the ongoing dial-out attempts?

Hi, my alarm went off at 4:00am last Thursday and woke me out of a deep sleep. In my rush to turn it off I managed to stub my toe on the edge of a door, leading to much swearing  . Anyway, the keypad was showing trouble on Zone 16 - an outside gate sensor. I bypassed the zone and disabled the alarm.

Over the weekend I investigated the problem. I disconnected the zone connector and checked the loop resistance which was 2.2k with the gate closed and 6.9k with it open and I confirmed that the EOL jumper was in the correct position. Cycling the power for the alarm didn't fix it, so I tried a full write from PC -> Comfort and then COMFORT -> UCM EEPROM. This cleared the Zone Trouble alarm but I'm concerned that it may happen again. 

Any thoughts on what might have caused it?

Hi,
I was on 8.013 and tried to upgrade to 8.030 - it just doesn't take it.
I then manually upgraded to 8.017 (which was never offered to me automatically) and it upgraded fine.
Any thoughts?
Thanks
Mark

Hi,

I've been the very happy user of a comfort system since 2001 - it's been so problem free that I've not had to change/upgrade/add anything to the system since that date.

With the upcoming change in the UK, to no longer support copper, my phone line will be upgrading to digital, so I think now is the time to add a UCM-4G to my comfort system - I believe this will allow me to control comfort - activate/de-activate comfort, have DTMF control over comfort, and be called whenever there is an alarm, over the 4G network.

My question is, will my hardware be compatible, and what firmware needs updating ?

My comfort system is:
8001/E Comfort CPU/8-zone/8-output with "Outside 4.115" printed on the "main chip" on the circuit board
UCM-CWI (with the RS232 cable connected (to a Raspberry Pii)) with "UCM 5.11" printed on the "main chip" on the UCM board

Many many thanks for any help - I've had a bit of a trawl through the forum, but I fear my system may be much older than many.

Thanks
Russ

Since last month (which happens to be when I upgraded all firmware and started using Comfigurator 4.0.3) the alarm panel reports communication failure with keypad 03, which is then reported as resolved a few seconds later.

This morning the alarm panel reported communication failure with keypad 01 and a few seconds later it was reported as resolved.

What could be causing this?

I don't see this topic being published. Was trying to use it for a doorbell press. 

   

using comfort2mqtt there is an alarm refresh (comfort2mqtt/alarm/refresh) .. which is useful when HA reloads the configuration.  

Is there a way to get the zones / counters / flags refreshed too .. other than restarting the comfort mqtt add-on ?

I guess another way is to default sensors (smoke, fire) to off state .. mine are appearing 'unknown' .. need to research how to do this !

I am guessing that the app will no longer work if I change my internet provider (like may ISP's) to one that uses CGNAT so port forwarding / NoIP setup won't work?

Is there a work around?

Would I have to go down the home assistant route / integration and then access home assistant remotely via Home Assistant Cloud or Reverse tunnel (Tailscale, ZeroTier, Cloudflare Tunnel)  - ChatGPT suggestion not my own knowledge!

What is the easiest way to bypass a zone (input) using comfort2mqtt addon?