Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums

(Advanced Search)

Latest Threads
Moving from Alfawerks to ...
Last Post: DavidJ
Yesterday, 10:38 AM
Comfort Bus Monitor 2
Last Post: slychiu
Yesterday, 09:54 AM
Spammers - Stay Away
Last Post: slychiu
Yesterday, 09:17 AM
Comfort Bus Monitor 2
Last Post: slychiu
Yesterday, 08:53 AM
Comfort Server Manager 2
Last Post: slychiu
Yesterday, 08:27 AM
System not announcing are...
Last Post: raygregg114
11-09-2026, 04:11 PM
alarm activation
Last Post: slychiu
11-05-2026, 02:03 AM
Problem with UCM3
Last Post: slychiu
10-29-2026, 11:01 AM
Using AI wiith Home Assis...
Last Post: slychiu
10-25-2026, 06:53 AM
Upgrading Ultra II to ins...
Last Post: slychiu
10-25-2026, 05:53 AM

Forum Statistics
» Members: 53,665,   » Latest member: isabellathomas,   » Forum threads: 5,232,   » Forum posts: 28,753,  
Full Statistics

  Comfort Bus Monitor 2
Posted by: slychiu - Yesterday, 09:54 AM - Forum: NEWS & Announcements - No Replies

Please visit http://www.comfortforums.com/thread-6017.html for information about Bus Monitor 2

Print this item

  Comfort Bus Monitor 2
Posted by: slychiu - Yesterday, 08:53 AM - Forum: Software Tools and Misc Interfaces - No Replies

Comfort Bus Monitor 2 will replace the exiting Comfort Bus Monitor that is launched by Comfigurator > Tools menu. This shows the Comfort messages on the RS485  Bus 

Bus Monitor 2  improves on the old software;

  • It decodes all RS485 messages as well as the parameters
  • Saved messages have trmestamp up to miliseconds for each line.
  • The software can be upgraded automatically or manually when a new version is available
  • Fixes bugs on the old software

The next Comfigurator (after 4.0.6) will launch Bus monitor 2, but for now the software can run stand alone. Download from https://www.cytech.biz/comfort_bus_monitor_2.html








The log display example is below;

Tuesday, 10 November 2026
No bus traffic after 3s - re-sent login + MO01 (UCM had sent "LU01" bytes=[03 4C 55 30 31 0D])

16:35:38:468---03 41 45 30 31 37 36 02--- ►[41][45]0176◄
              Keypad 01 key 01 is pressed
16:35:38:578---03 41 80 33 43 02--- ►[41][80]3C◄
              Keypad 01 reports all keys released
16:35:39:012---03 41 45 30 32 37 35 02--- ►[41][45]0275◄
              Keypad 01 key 02 is pressed
16:35:39:153---03 41 80 33 43 02--- ►[41][80]3C◄
              Keypad 01 reports all keys released
16:35:39:465---03 41 45 30 33 37 34 02--- ►[41][45]0374◄
              Keypad 01 key 03 is pressed
16:35:39:620---03 41 80 33 43 02--- ►[41][80]3C◄
              Keypad 01 reports all keys released
16:35:40:712---03 41 45 30 34 37 33 02--- ►[41][45]0473◄
              Keypad 01 key 04 is pressed
16:35:40:869---03 41 80 33 43 02--- ►[41][80]3C◄
              Keypad 01 reports all keys released
16:35:41:444---03 41 45 30 43 36 42 02--- ►[41][45]0C6B◄
              Keypad 01 key 0C is pressed
16:35:41:475---03 41 80 33 43 02--- ►[41][80]3C◄
              Keypad 01 reports all keys released
16:35:41:490---03 41 61 30 31 30 30 35 41 02--- ►[41][61]01005A◄
              Code validation reply command
16:35:41:521---03 00 42 30 30 30 30 42 42 02--- ►[00][42]0000BB◄
                Request Broadcast to turn off mic, turn off speaker
16:35:41:569---03 41 42 30 30 30 31 37 39 02--- ►[41][42]000179◄
                Request Keypad 01 to turn off mic, turn on speaker
16:35:41:614---03 41 4F 30 31 36 43 02--- ►[41][4F]016C◄
                Request Keypad 01 backlight on
16:35:43:560---03 12 60 30 31 30 32 30 33 30 34 38 31 02--- ►[12][60]0102030481◄
              Code validation submission command
16:35:43:592---03 12 61 30 31 30 30 38 39 02--- ►[12][61]010089◄
              Code validation reply command
16:35:43:733---03 12 6E 37 44 02--- ►[12][6E]7D◄
              Request/Report current alarm type
16:35:43:792---03 00 46 42 37 02--- ►[00][46]B7◄
                Turns off siren
16:35:43:824---03 00 3D 31 38 30 31 30 31 46 38 30 33 34 32 36 39 02--- ►[00][3D]180101F8034269◄
              Alarm report for Broadcast: alarm type 18H, priority state trouble (01H), new state trouble (01H), sentence 248, param type ID (03H), param ID 42H
16:35:43:886---03 00 6E 31 38 30 31 30 38 30 30 30 30 30 30 34 32 30 30 30 30 32 43 02--- ►[00][6E]1801080000004200002C◄
                Alarm type 18H, state trouble (01H), trouble: RS485 comms fail, low battery ID 00H, zone trouble 00H, comms fail ID 42H, tamper ID 00H, GSM ID 00H
16:35:43:948---03 40 41 30 30 30 32 30 30 30 30 37 41 02--- ►[40][41]000200007A◄
                Request All Keypad turn off ARM LED, flash OFF LED, turn off AC LED, turn off MSG LED
16:35:44:011---03 12 6E 31 38 30 31 30 38 30 30 30 30 30 30 34 32 30 30 30 30 31 41 02--- ►[12][6E]1801080000004200001A◄
                Alarm type 18H, state trouble (01H), trouble: RS485 comms fail, low battery ID 00H, zone trouble 00H, comms fail ID 42H, tamper ID 00H, GSM ID 00H
16:35:54:045---03 12 73 30 30 37 38 02--- ►[12][73]0078◄
              Zone bypass query/reply
16:35:54:076---03 12 73 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 37 38 02--- ►[12][73]0000000000000000000000000078◄
              Zone bypass query/reply
16:35:54:116---03 12 67 38 34 02--- ►[12][67]84◄
              Ucm 02 requests version information
16:35:54:153---03 12 67 46 39 30 38 34 33 32 32 34 30 30 31 30 30 44 44 02--- ►[12][67]F9084322400100DD◄
                Version information sent
16:35:54:161---03 12 97 30 31 35 33 02--- ►[12][97]0153◄
              Ucm 02 request comfort about 01's information
16:35:54:177---03 12 97 30 31 34 30 30 38 33 38 30 30 30 31 44 32 02--- ►[12][97]014008380001D2◄
              Unhandled command 97H frame (length 11)
16:35:54:200---03 12 B6 30 35 30 31 30 31 32 45 02--- ►[12][B6]0501012E◄
              DC/battery voltage query/reply
16:35:54:215---03 12 B6 30 38 30 31 30 31 44 36 35 35 02--- ►[12][B6]080101D655◄
              DC/battery voltage query/reply
16:35:54:226---03 12 B6 30 35 30 31 30 32 32 44 02--- ►[12][B6]0501022D◄
              DC/battery voltage query/reply
16:35:54:263---03 12 B6 30 38 30 31 30 32 44 46 34 42 02--- ►[12][B6]080102DF4B◄
              DC/battery voltage query/reply
16:35:54:278---03 12 A3 30 31 34 37 02--- ►[12][A3]0147◄
              Ucm 02 Query CM EOL Setting
16:35:54:309---03 12 A3 30 34 31 30 46 46 46 46 46 46 46 46 46 46 33 39 02--- ►[12][A3]0410FFFFFFFFFF39◄
              Ucm 02 CM Reply with EOL of itself
16:35:54:347---03 12 35 37 46 46 39 30 34 33 41 02--- ►[12][35]7FF9043A◄
                Upload to Ucm 02
16:35:54:373---03 12 36 37 46 46 39 46 46 46 46 46 46 46 46 34 31 02--- ►[12][36]7FF9FFFFFFFF41◄

Print this item

  Using AI wiith Home Assistantr/UCMA/Pi
Posted by: slychiu - 10-25-2026, 05:19 AM - Forum: UCMA/Pi - Replies (1)

Cytech has created a public Support Guide in its GitHub repository. Claude (and other AI assistants such as ChatGPT or DeepSeek) can read that guide and the public configuration repository, then explain messages, walk you through troubleshooting, and help you build your own automations and dashboards. No special setup and no Cytech involvement is required.

1. WHAT YOU NEED

- A Claude account - claude.ai in a browser, or the Claude app. The free version is enough. A version that can open web links works best. Other AI toos would also work.
- Your system version: Config Files page, "System Version" card.
- The exact message you are seeing, or a clear description of what you want to build.

2. GIVE CLAUDE THE GUIDE FIRST

Paste this public link into the chat and ask Claude to read it before answering:

https://raw.githubusercontent.com/slychi...SUPPORT.md

These public links are also safe to share: the configuration repository at https://github.com/slychiu/ComfortHA-yaml and the Comfort bridge app at https://github.com/cytechtech/ucmpi4. Nothing secret is kept in them - email passwords and private data live only on your own system.

If Claude cannot open web links, open the raw link yourself, copy the whole page, and paste it into the chat (or attach this text file).

3. PROMPT FOR TROUBLESHOOTING

Copy this, fill in the blanks, and send it:

I own a UCMA/Pi system from Cytech running on Home Assistant.

Please read this public support guide before answering:
https://raw.githubusercontent.com/slychi...SUPPORT.md

My system version is: ___
My Home Assistant version is: ___ (find it under Settings > About)
What my system shows: ___ (paste the exact message, or describe what is not working)
What I have already tried: ___

Question: what does this mean, what can I safely do myself, and when should I contact support@cytech.biz?

Good things to paste into "What my system shows": "SD card problem detected", "SD card write test failed", "Repeated restarts detected", "Generating Secure Remote Link... Please wait", the Network line warning, "MQTT_DEVICE_COMFORT not ready", or the "Unsupported system - DNS server issues" banner.

4. PROMPT FOR CREATING AN AUTOMATION

Copy this and describe what you want:

I own a UCMA/Pi running on Home Assistant. Please read this public support guide first, especially section 9:
https://raw.githubusercontent.com/slychi...SUPPORT.md

I want to: ___ (for example: "send a phone notification when the front door opens while the alarm is armed", or "remind me if a zone is left open for 10 minutes")

Facts about my system:
- The alarm is alarm_control_panel.comfort_alarm with states disarmed, armed_home, armed_away and armed_night.
- The arm buttons call script.comfort_arm_away, script.comfort_arm_night and script.comfort_arm_home.
- Each Comfort zone is a binary sensor named like binary_sensor.cytech_comfort_mqtt_input005 (on = open, off = closed).
- Bypass controls are button.<zone name>_set_bypass and button.<zone name>_clear_bypass, with the state in sensor.<zone name>_bypass_status.
- Battery readings are sensor.cytech_comfort_mqtt_battery_status, sensor.cytech_comfort_mqtt_charger_status, sensor.cytech_comfort_mqtt_battery_main_voltage and sensor.cytech_comfort_mqtt_dc_supply_main_voltage. Alarm and trouble status is sensor.comfort_am_status.

Give me step-by-step instructions using the current Home Assistant menus, starting from Settings > Automations & Scenes, and use the visual editor rather than editing configuration files. Tell me which screen to start from. If anything could affect the alarm or lose my settings, warn me first.

5. PROMPT FOR YOUR OWN DASHBOARD

Copy this and describe what you want to see:

I own a UCMA/Pi running on Home Assistant. Please read this public support guide first, especially section 9:
https://raw.githubusercontent.com/slychi...SUPPORT.md

I want to create my own dashboard showing: ___ (for example "the alarm status, each zone and whether it is open, and the battery voltage")

Give me step-by-step instructions using the current Home Assistant menus. I want to create a NEW dashboard and leave Cytech's existing pages untouched, because Cytech updates replace those pages. Warn me first if anything I do could affect the alarm or lose settings.

6. OTHER USEFUL THINGS TO ASK

- "Explain what my Comfort battery readings mean and when I should replace the battery."
- "Send a phone notification when the alarm is armed and a zone opens."
- "Send me a daily message listing any zones that were left open."
- "Create a page showing every zone and its bypass state."
- "Explain what this warning means and whether I need to act today."
- "My automation is not firing - help me troubleshoot it." Claude can ask you to check Settings > Automations & Scenes > your automation > Traces.
- "Help me add a new phone to my Home Assistant notifications."

7. TIPS FOR GETTING GOOD ANSWERS

- Paste the exact text of a warning rather than paraphrasing it.
- Always tell Claude your Home Assistant version (Settings > About) - menus change between versions.
- If the steps do not match your screens, say so and give the version; ask Claude to adjust.
- Ask Claude to go one step at a time if you are unsure.
- Tell it what you already tried.
- Before pressing anything, ask "what could go wrong, and how do I undo it?"
- If Claude's advice conflicts with the support guide, follow the support guide and email support@cytech.biz.

8. NEVER SHARE WITH CLAUDE OR ANYONE OUTSIDE YOUR HOUSEHOLD

- Your remote access link or its QR code.
- Your Home Assistant login, username or password.
- Any file whose name contains cytech_secrets, or any password from it.
- Backup archives.
- Your alarm PIN or user code.

Claude cannot see or change your system - it only gives you instructions to carry out yourself. No legitimate request from Claude or any assistant needs those items. If an assistant asks for them, stop.

9. RULES THAT STILL APPLY

- The four Cytech pages (Remote Access, Alarm, Battery Levels, Config Files) are replaced by Cytech updates. Create a new dashboard for your own ideas; do not edit the Cytech pages.
- Do not edit configuration files or the .storage folder by hand.
- Do not change or delete the automations Cytech installed - they run the self-checks, updates and alert emails.
- An automation can control the alarm. Be careful with anything that disarms it, and never put your PIN on a dashboard or in a notification.
- For the Comfort panel itself (zones, users, codes and programming), contact Cytech support - the panel is programmed in Comfigurator, not in Home Assistant.
- This is the same advice as the support guide: AI can explain and suggest, but for anything destructive or unresolved, use support@cytech.biz.

10. WHERE THE GUIDE LIVES

- Repository: https://github.com/slychiu/ComfortHA-yaml - open SUPPORT.md there.
- Direct raw link for pasting into Claude: https://raw.githubusercontent.com/slychi...SUPPORT.md
- The Config Files page on your system also links to the Owner Support Guide.

Keep this file for reference. You can paste the same prompts each time, changing only the parts you fill in.

Print this item

  Comfort Home Assistant Updates - Changes
Posted by: slychiu - 10-25-2026, 02:40 AM - Forum: UCMA/Pi - No Replies

These are free updates to the Home Assistant software that runs alongside your Comfort system.

They do NOT change your alarm programming or your Comfort settings - your zones, codes, users and automation all stay exactly as they are. 

To install: open the Config Files page, press "Check for Update", then "Update Now". Each update now also explains in plain language what it changed.

SECURE REMOTE ACCESS THAT LOOKS AFTER ITSELF

- Every system has its own private web link and QR code for reaching the house from a phone.
- Systems whose storage card was copied from another system used to share that link. They now recognise this, give themselves their own new link, and finish setup by themselves - there is nothing you need to do beyond updating.
- "Remote Support Access" lets Cytech help you without you being present. It still switches itself off automatically, and the window is now 10 hours instead of 4, so support can pick it up from another time zone.

ALERT EMAILS THAT SET THEMSELVES UP

- The system fetches its own email account automatically -
- On older systems that cannot fetch it, the system opens a temporary support window, shows an on-screen notice explaining why, and lets Cytech finish the one-time activation without asking you for anything.
- "Send Test Email" now only reports success when the mail really went out.
- "Register" now tells you plainly when activation is still in progress.

EARLY WARNING FOR STORAGE CARD PROBLEMS

- The storage card is checked every hour, with a small write test once a day.
- If a problem is found you get an on-screen warning and an email, plus advice to save a backup to your PC or Google Drive while the card still works.
- If Home Assistant itself offers an update while the card is already failing, the system warns you NOT to install it yet and emails Cytech - a large update could make a failing card worse.

UPDATES 

- Pressing Update Now now reliably restarts the system to complete the install, and the system notices and recovers if a restart was missed.
- Pressing Update Now again on a half-finished update finishes it, instead of saying "you are already on the latest version".
- Each update now delivers the complete set of files, so a repaired system no longer keeps stale pieces of older versions.

A CLEARER, MORE USEFUL DASHBOARD

- Alarm Message Log: a "newest first" toggle ie Newest evemt or oldest event first)
- A "Dismiss Warning" button once a warning has been dealt with.
- The System Health network row now shows whether the network port is connected and whether the internet is reachable.
- A new alarm-status view, per-zone bypass controls, and a Bypassed tile.
- An Owner Support Guide link on the Config Files page - what each message means, what is safe to do yourself, and how to use an AI assistant to build your own automations and dashboards.

BEHIND THE SCENES (no visible change, but more reliable)

- Automatic self-healing: a protected copy of the configuration is restored if it ever gets damaged.
- Compatibility repairs for Home Assistant 2026.9, a self-repairing update download address, and version-check fixes.

VERSION BY VERSION

  • v43 - Self-healing configuration, alert emails, clearer health and warning rows
  • v44 - Alert emails moved to Gmail; credential rotation handled automatically
  • v45 - Honest Send Test Email; fewer false restart warnings
  • v46 - Internal version-check fix (no visible change)
  • v47 - Alarm log "newest first"; Dismiss Warning button
  • v48 - Network port check; Home Assistant 2026.9 compatibility
  • v49 - Remote Support window increased from 1 hour to 4 hours
  • v50 - Internet-reachability line; complete update file set
  • v51 - New alarm-status view, zone bypass controls, Bypassed tile
  • v52 - Storage-card early warning, update hold, self-setting email, backup reminder
  • v54 - Copied systems that could not connect get their own new secure link
  • v55 - Updates restart reliably; older systems activate email automatically
  • v56 - Fix so that v55 automatic activation works at boot
  • v57 - Copied systems with a still-working old link get their own identity; Remote Support window extended to 10 hours

IN SHORT

The system now sets itself up, warns early when its storage card is failing, tells you to back up while it still can, repairs copies of itself, and completes its own updates - while your alarm and Comfort settings stay untouched.

Print this item

  UCM/KNX2: "Security Off" in KNX→Comfort doesn't disarm
Posted by: shayr - 10-18-2026, 09:14 PM - Forum: UCM/KNX Firmware - Replies (1)

Hi,

I've just commissioned a Comfort II Ultra with a UCM/KNX2. Comfigurator offers "Security Off" as a Security Mode in the KNX→Comfort table, but the panel doesn't act on it. Can you confirm whether that's expected?

System:
- Comfort II Ultra firmware 8.006 (File System 34)
- UCM/KNX2 firmware 8.002 (upgraded tonight from 7.211; same behaviour on both)
- Comfigurator 3.14.12

Setup: 1 bit Switching (EIS 1), Register Type "Arm Security", one group address per Security Mode.

Results:
- Away and Night arm immediately, and the status reports back over KNX.
- Security Off: a 1 on its group address is ignored while armed in Night or Away. No disarm and no event.
- Keypad Key (1 byte EIS 6, code digits then 26) disarms correctly, so that's what I'm using now.

The first post of the UCM/KNX2 forum thread (comfortforums.com/forum12/4470.html) says both "Disarm to Security Off is not allowed, although it is listed in the options" and "Disarm to Security Off by 1 bit KNX address is possible", which made this hard to pin down.

Could you confirm:
1. Is disarming to Security Off through an Arm Security mapping deliberately blocked, with Keypad Key the intended method?
2. If so, could Comfigurator hide or label Security Off in that dropdown, and could the forum post be corrected?

I can send the .cclx and a module scan if that helps.

Thanks,
Shay

Print this item

  Upgrading Ultra II to install ETH03 and integrate with HA
Posted by: mindi65 - 10-13-2026, 04:47 PM - Forum: Firmware Upgrading Problems - Replies (3)

Hi
It been some years since I upgraded my Ultra II and I purchased ETH03 in order to integrate with HA

Comfort II Ultra
Version 7.192
File system 34
UCM Type 10 - new
version 8.007 - new

HA is recomending UCM version >7.2xx

Latest available v7 7.215 v8 8.030

Is version 8.xxx requiring new HW? Is 7.215 latest then?

BR//Mindaugas

Print this item

  Restore Zone 16 - repeated multiple times
Posted by: Home - 10-07-2026, 08:30 AM - Forum: Problems & Troubleshooting - Replies (4)

Restore Zone 16 - repeated multiple times 

The keypad was simply text 'zone trouble' (no zone name or no)
The event log is TOTALLY full with 
"time Restore - Zone # HallPIR (16)

Logged in from keypad and it cleared

Firmware 7.194
Comfig V4.0.5.0


I AM UNABLE TO ATTACH THE LOG FILE AS IT SAYS "type of file not allowed"
Have attached the program file if that helps!


Any ideas ?



Attached Files
.cclx   V10,1(Comfig 4.0.5) GardenCottage.cclx (Size: 338.01 KB / Downloads: 1)
Print this item

  Cytech Comfort 2 Alarm Lot – Working Boards, GSM, Texecom Sensors, X10
Posted by: lenny aeon - 10-03-2026, 06:45 AM - Forum: Forum/Website - No Replies

This is a comfort system which I had installed and working in my house. The only thing missing is the exterior bell box which is easy to acquire.

Comfort II Ultra parts lot, collection NI or posted UK.
Main board ULT 7.009, working. Includes UCM/USB, GSM module and antenna, auxiliary distribution modules, X10 dimmers, plug-in switch, relay, DMO, X10 main unit, PIRs, Texecom optical/heat detectors, sounder, second enclosure, wiring, program cable and manual.
Keypad and door-station speakers have been removed. A larger standalone speaker is included.
Not a Comfort 3. On eBay, search “Comfort 2” or message me.

Here's the link which I hope is OK to post on the forum

https://www.ebay.co.uk/sch/i.html?_nkw=C...ors%2C+X10&_sacat=0&_from=R40&_trksid=m570.l1313

Cheers 
Lenny



Attached Files Thumbnail(s)
   
Print this item

  Problem with UCM3
Posted by: DavidJ - 10-01-2026, 01:54 PM - Forum: Alphawerks UCM/Pi - Replies (7)

   
I have had the Alphawerks RPI in for around 5 years, The connection to Home Assistant dies every few weeks so I decided to try to upgrade the  Commute module. I was unsuccesful in getting to mount the module in windows, though numerous restarts. After giving up I put it all back how it was now I get a UCM3 Communication error that I cant clear as you see theres a red light on the bottom row that wont go out. Ive put everything exactly back how it was, done a reset through comfigurator, restarted the alarm (pulling out batteries). Really at wits end after nearly 10 hours battling with this. Any ideas?

Print this item

  Logic control confusion !
Posted by: Home - 10-01-2026, 12:45 PM - Forum: Logic Controllers - Replies (1)

Can someone explain - I'm really confused ?


UCM/Logic - page on web site but no info at all

[b]FW-UCMALOG - web site had down loadable file 7.219 but NO description ![/b]

UCMA/Logic - description but no downloadable page

Print this item


Online Users
There are currently 456 online users. » 1 Member(s) | 451 Guest(s)
Applebot, Bing, Facebook, Google, slychiu

Powered By MyBB, © 2002-2026 Melroy van den Berg.