Hi,  I am/was one of the original beta testers, and have a UCMPI with CM3 with just 4gb of memory. I have the UCMPI running openhab, with the primary aim of inegrating my alarm system and HA devices (velbus priarily) into google assistant. 

Most of my HA logic is done directly within comfort, and has been for years, is very very stable, and rarely if ever requires changes etc, so i am pretty happy, in fact I would almost insist that most of the HA logic is kept within comfort purely because it is so reliable and stable. 

So, the UCM PI for me, is an interface to google assistant and priro to this, I was running Openhab on a seperate RPI to integrate velbus togoogle assistant, but migrated all of this over to the UCMPI to get rid of hardware and consoldiate everything. 

I still retain another RPI with the community edition of alphawerks as this had been providing google assistant interface of comfort (alarms, sensors etc), but has now started to play up a bit, and overall its a very complex setup just to link in alarm status, and sensors for comfort to google assistant. 

Anyway, over the christmas period, Ive been tinkering, and trying to get my UCMPI running Openhab to expose comfort to Google Assistant, but have failed miserably. 

My first obstacle was upgrading to openhab3, which I have managed to do, after finding out through the guys on the slack forum, that I was low on disk space, 4Gb is quite tight.
I now have issues with node red, which has failed, and have been trying to re-install it, but think I am running in to disk space issues again. 

So, after the above rant, I suppose my question is, do I need to upgrade my disk space, purchase a cm3+ and migrate to that before looking to add and fix my issues ? 

When really, the UCMPI to me was a method of integrating comfort to google asisstant , it hasnt acheived that for me (and I admit, this is mostly down to my own lack of knowledge and time to delve into the system), so is this the best route for me ? 

Are there other options that people see to integrate comfort to home assistant, perhaps I go for a basic RPI install of Home Assistant ?
All I really want to do is remove smartthings and Alphawerk Community edition from my setup.
I think the UCMPI is great, and well done to Matt and Alphawerk, but while I work in a technical field, and would be reasonably good at getting a grip on things, the learning curve and time required to get it working is just too steep for me at the moment, and that is the main reason the UCMPI hasnt delivered for me.
Regards,Eamon

I picked a problem with my Vocabulary (voice) on my keypad. The keypad is not picking up the text file (according to the error received on the keypad). Then I tried to do a Vocab Upgrade. After the indicator goes to 0%, it almost immediately displays an error Vocab Errors on the screen (using Comfigurator V3.13.6.0).
Not sure what else I can do to fix this scenario? The rest of the Comfort system seems to work fine.
Any suggestions?   

I needed to temporarily disable a zone/input as I have a problem with the sensor. I can\'t find anything in the manual or on the forum but have concluded that you can use the DigitalNC/DigitalNO zone types to do this. The steps I took where

Make sure you have saved the current configuration
To temporarily disable a circuit change \'Zone Type\' in Zones/Inputs to DigitalNC [30]/DigitalNO [31] - to reflect the sensor type NO/NC
Write this to a new configuration file - I used an extension of int for intermediate
Then Transfer/Write (PC -> Comfort)Alarm circuit to test
When the sensor issue is resolved then the old configuration should be restored

I am running V3.13.6.0 on Win10 and have tried to print to PDF using the installed windows driver. Win10 use the PORTPROMPT: destination/port which should lead to the file dialog being opened so you can add the file name.
I\'ve tried this with other apps and it works fine but in Comfigurator it just goes back to the event log

I received a new thread message notification email yesterday evening (first time for a while) but it was in Italian!  I\'ve just checked my profile and I\'m down as having English as a preference and my location being United Kingdom.  Anyone else seen this?

UCM 7.141
Bugs

1. If ERR red LED remains on after reset or power on, it means the wifi submodule has been detected. If this occurs when USB or eth03 submodule is inserted in CM9001 or UCM, the ucm will not communicate. If tis happens power off and ON the UCN by removing and inserting the 4 way cable to the UCM. Similarly if wifi is inserted in the UCM baseboard the ERR red LED should be on. If it i not, then power off an on the UCM in the same way

•   Implemented wifi01 NTP update time at 00:10 hours or 10 minutes after each hour if not updated on the same day
•   \"SB\" strobe proc232_strobe command
•   Fixed BUG - report_counter counter value was corrupted so Comfort Increment Counter, Decreent Counterr actions  did not return correct value in saveuservalue
•   If UCM is doing firmware upgrade by UCM programming cable,  suppress mesages Cs01 or Cs02  which may interfere with upgrading firmware
  

[size=\"3\"][size=\"2\"]Firmware 7.183
[/size][/size][size=\"3\"][size=\"2\"]Known Bugs[/size][/size]

• [size=\"2\"]Action 1 (Announce Zone Name) in Zone Off Response will skip announcing the 1st word in the zone[/size]
  

• [size=\"2\"]Fixed BUG for eth03 plug in to CM9001 - UL with 2 bytes always returns the 2 same bytes[/size]
• [size=\"2\"]Event Log  fixed BUG last event 27 was 68 may  cause event log to crash from 28/6/18 [/size]
• [size=\"2\"]Fix BUG for partitions arm to away sometimes dis not work[/size]
• [size=\"2\"]Fix bug from 13/6/19 Security check may use wrong partition [/size]
• [size=\"2\"]Fix bug  from 6/3/20 if log in wrong code using ext232 there is no reply LU00, comfigurator waits and times out[/size]
• [size=\"2\"]Fix Bug  Monitor Mode MO00 cannot exit from monitor mode[/size]
• [size=\"2\"]Fixed bug Monitor Mode MO00 cannot exit from monitor mode [/size]
• [size=\"2\"]Fixed Bug Action 158 clear and set counter did not work, but toggle worked [/size]
• [size=\"2\"]Fixed BUG dR report was not sent when ETH03/Wifi01 was plug in on CM9001[/size]
• [size=\"2\"]Event Log  fixed BUG last event number was wrong, may   cause event log to crash from 28/6/18 [/size]

• [size=\"2\"]Change in Event Log indexing. Reduces Wear on the EEPROM due to writing the event log pointer with every event. Also reduces time to erase the whole event log Fixed other bugs[/size]
• [size=\"2\"]Event Log  fixed BUG last event number was wrong, may   cause event log to crash from 28/6/18 [/size]
• [size=\"2\"]Event Log will not announce month 0 if it is encountered[/size]

• [size=\"2\"]Action 162 Assign Reminder to Alarm to assign a recorded reminder message to an Alarm to replace sentence. If no the assigned Reminder number is recorded, the alarm message will be played[/size]
• [size=\"2\"]Action 163 assign reminder no to zone. if zone has reminder message, it will play the reminder message in event log,  zone announcement and security check, but zone menu will continue to play the zone words. If the Reminder is assigned to a zone, but the reminder message is not recorded, the zone words are played[/size]
• [size=\"2\"]Added Action get parameter  61 Login Partition[/size]

• [size=\"2\"]Partitions If all keypads are in partition 0, allow parttions to be enabled.  some systems disarm by switch[/size]
• [size=\"2\"]Announce  Area/Partition  number in user menu if partitions exist[/size]
• [size=\"2\"]For partitioned system,  arm and disarm security will announce Area (Partition) Number after announcing security mode. Requires Vocab version 42[/size]

• [size=\"2\"]Dial out announcements -   changed order for dial out alarm announcements. 1st play recorded alarm message, then alarm type, then alarm pararameter announcement[/size]
• [size=\"2\"]Vocabulary version 42 sentence 87 is Area (N)[/size]
• [size=\"2\"]Detector_announcement -  if not trouble or restore, announce reminder call detector_name so reminder can be announced  detector_announce if restore zone but no words in zone, call say_zoneNrestore. require vocab v43[/size]
• [size=\"2\"]Voice menu add 8 for zone announce Require vocab 43[/size]
• [size=\"2\"]zone restore announcement -  zone name restore instead of just Restore without zone[/size]

• E[size=\"2\"]MS enable reminders for zones and alarms. disable Scheduled Remimders for EMS for play reminder action only[/size]
• [size=\"2\"]Enabled 16 Reminders  for ems[/size]
• [size=\"2\"]Allow  Ems without Incoming recorded messages,  with Reminders in Responses[/size]
• [size=\"2\"]EMS Voice menu  add 5 for  reminder messages f[/size]
• [size=\"2\"]EMS sensors fix bug sensor - setpoint comparison was unsigned, ie negative values are taken as positive.  process_sensortab fix bug counter compare with max and min setpoints was unsiged should be signed.[/size]
• [size=\"2\"]EMS sensors.mac process_sensortab limit counter setpoint to -128 to 127. fix bug counter >255 was set to 255 ie -1[/size]
• [size=\"2\"]EMS Sensor Setpoint Counter prevent max/min setpoint check from doing endless loop
  [/size]
• [size=\"2\"]EMS sensors - adjust_sensor limit final sensor values to -128 to + 127 after adjustment, but allow signed 16 bits intermediate. Aallowed sensor values for scaling (;1 = 0 to 99. sensor 0 to 255,   2 = multiply by scale factor. sensor -128 to + 127, 3 = divide by scale factor, sensor -32768 to 32767. allow larger range for division. final value will be -128 to + 127[/size]

• [size=\"2\"]Motion sensor Timer enabled for EMS. query d? got reply NA before[/size]
• [size=\"2\"]For wifi NTP, update time daily at 12: 05 am instead of 4 AM[/size]

PLEASE BE AWARE
I have now experienced several occasions whereby I have started to carry out a main board firmware upgrade and the PC or laptop I\'m using has gone to screen saver !
AAAAAGh
The firmware update crashes !
The consequences of which can be pretty nasty.......
Cytech something you can take a look at !

Hello. I install the 7.183 firmware in my Comfort II Ultra. I have KP04 keyboards. The LEDs do not light up on the keyboards. When I put the day mode, through the application I see that it is in day mode but on the keyboards it continues as if it were in OFF mode. LEDs do not light up. Keyboards do not indicate. I have had to go back to the 7.153 firm although the zones in alert mode do not work well with it.
I hope they review it.
Thank you.

We service and maintain a number of older comfort installations that are pre 7.xxx updateable
We have found that Comfigurator 3.12.16 is the last useable version on older C1 and 5.xxx 6.xxx installations (later versions cause all sort of corruptions).
Unfortunately we are unable to install 2 versions of comfigurator at once.Would it be possible to alter this so that we can run 3.12.16 at the same time as the most current version.
Would save us quite some time and would be useful for any one with older versions.