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?

I upgrade to Comfort 4.x a few days back, I had to restart the ucmPi tonight after updating my network gear.  The ucm can no longer be polled,  the pi seems to reboot as node-red seems to be running.

Trace produced the shared results

Attached Files

Thumbnail(s)
   

I have just set up the comfort/HA addon and with a little help from hear have it working nicely. I am now trying to explore what I can and cannot do. I am wondering if it is possible to trigger the alarm on and off using node red. I've been trying to replicate the automation for remote arming. I can send messages to the alarm via mqtt and they appear when I monitor it with mqtt explorer. But cannot get it to turn on. (or off). Any thoughts on a) is this possible and b) what message do I need to send.

The new Version of Comfigurator 4.03  has the following changes
Comfigurator 4 can be installed with  Comfigurator 3.x.x in the PC, This allows  the old comfigurator 3 to be used eg with old cclx files if necessary due to compatibility problems

Known Bugs

• when  upgrading firmware ;after logging in and right clicking on Controller to  "upgrade firmware from local file" and selecting the cbf file, the message "CBF file not compatible with the firmware to be upgraded" is seen, but after a scan for modules  then it can upgrade. Also if start a new template, an  upgrade can be done without any error message.
  
• if comfort is Optimum firmware, opening ULT or EMS file system and connecting and logging in to the system will get exception. This will not happen for EMS or ULT. Normally iComfigurator should warn that the file system is not matched to the firmware
  
• When  firmware upgrade fails, for any reason and there is an attempt to upgrade again,  Comfigurator log in fails because many commands are sent at log in while UCM in bootmode can only reply to 1 command at a time.
  
• After log in if ther eis no  scan for modules, download firmware upgrade will select the non-arm firmware
  
• Scan for Modules sometimes gets error "Scan for Modules failed"
  
• Write to Sunset Response writes 0 instead of the response number so sunset response does not work
  

• Corrupted cclx files were sometimes scanned wrongly as ARM
  
• Phone numbers screen  does not show sms permissions when 1st phone is not Voice or SMS (eg phone is is CMS)
  
• HIO could not be detected after scan for modules
  
• fixed bugs with multiple repeated outputs in responses or displayed Outputs in Comfort register
  
• fixed bug with UCM ID 0 or 1  wrongly detected when there is a plug in ETH03 in CM9001
  

• In Zones "Duplicate EOL settings" checkbox shows a warning message before confirming so the box is not checked by mistake
  
• supports new  gsm5 module