I ran into problems with Node-RED on the UCM/Pi being out of date preventing node-red-contrib-home-assistant-websocket from connecting to Home Assistant. This resulted in all my flows being unable to run. I tried the upgrade.sh script but it failed and I had to restore from a backup.
When Raspberry Pi CM4s\' finally became available I took the plunge and ordered one along with a Waveshare CM4 to CM3 adapter board. My reasoning was that if the installation failed, I could put the CM3 back in.This turned out to be wise, as after doing a clean Raspbian install, the alphaWerk Quickstart Script (install.sh) immediately failed with a node.js install error. I went through the script and managed to fix all the errors as they occurred, which took quite some time as I\'m not a Linux scripting expert.I have done a clean install with this version of the script on both a CM3 and a CM4, and it works fine. Node-RED v3.1.6 installed without any errors, and the Cytech nodes work as expected. A few things to watch out for:

• Remember to export all your flows from Node-RED before starting, as you will be wiping the Pi.
  
• When installing Raspbian, follow the instructions on the AlphaWerk github - UCMPi_OS Install but be sure to setup a user named pi, as the script assumes it exists. Raspbian no longer defaults to username pi.
• To flash the Compute Module you will need the drivers and boot tool to mount it as a storage device. Use the Raspberry Pi Imager to install the 32-bit version of Pi OS Lite. I haven\'t tried the 64-bit version.
  
• Unzip and copy the attached version of the script into /home/pi and run the commands from there. You will need to make it executable with chmod +x install.sh
  
• Then just run it with ./install.sh
• Do not run it as sudo, or under any other user name.
  
• The UCM/Pi must be connected to the alarm system bus for the install to succeed.
• After the script completes, it can take several minutes for the login page to be available at [url=http://

Attached Files

  install_script.zip (Size: 2.91 KB / Downloads: 7)

Hi
I keep getting
Mar 26, 17:30, [35), Unknown Event, Code = 35, Param = 7

I\'m guessing here but does the [35] refer to.....
<EventType Number=\"35\" Text=\"Send SMS Custom Message #\" Parameter=\"None\"/>

my SMS messages are working Perfectly shown in the log

Apr 02, 16:33, [12), Unbypass Zone : 25
Apr 02, 16:33, [35), Unknown Event, Code = 35, Param = 7
Apr 02, 16:33, [2), Dial Out Index: Phone Index 6 


so why is it an unknown event


I did swap the new GSM Module over without re-doing any of the code
Any ideas
Mike

Hi,
I understand how to use a virtural node to change a flag or counter into comfort by associating it with a z wave device.  And I understant how to get comfort to control a z wave device in the z wave mapping with a flag. But can you use a virtual node to send the status of a comfort device to the z wave controller. I want a comfort switch to trigger a z-wave routine if possible.

Is it possible to remotely disable the dial out function? Perhaps through the Engineers Menu?

The system is currently persistently dialing the alarm monitoring service. The engineer that was knowledgeable with Comfort has left the company. So, until I can get out there (I am in the US the alarm is in Portugal) I need to stop it dialing them.

Hi all, I\'m just posting on the off chance that somebody who has upgraded their system to a new CM9001 might have either of those modules going spare and perhaps available for sale.
I\'d also consider a LEM01-M2 despite not really needing the outputs. If you have any of those you\'d be willing to let go of then please message me.

Known Bugs

1. Responses to send commands to Cbus and KNX using send text (action 197) will not be terminated, but continue to the next numeric Response, causing unexpected effects. This will be fixed in the next version
2. Initially the Event Log is not initialised so new events cannot be recorded. As a workaround, erase the event log, in Comfigurator Transfer > Event Log, Clear Event Log, OR on Keypad, enter engineer Menu press 5 for event log, 0 to erase event log
3. From firmware 7.198 - If UCM/knx, UCM/CBus, UCM/Modbus has address  mapped to Flag, Comfort broadcasts the flag to all UCMs but the source ID of the UCM changing the flag is not sent correctly by Comfort. This may cause the UCM to send an extra unneccessary message back to the external Interface for KNX, CBus, Modbus etc. This does not cause the UCM not to work , it just causes an extra message to be sent back to the Interface

1. Fixed bug for wifi  invalid login code reset timer
2. Fixed bug from   7.205  action 64 to 128 error. Timer action bug stack overflow
3. Prevent false AC Power failure and Low battery alarms caused by slow rise time of power supply by adding a sooft start delay timer.
4. Slave fixed BUG from 16/7/16 did not load zone numbers for each zone at reset. This caused the bug that slave initial zones is always off until the zone state is changed to active
   
5. fix bug SEM sometimes has problem replying to polls
6. Fixed Bug SEM may hang at reset of EEPROM is not present

1.  At reset, keep S12V off for a few seconds to prevent intial high current load from external device  from causing firmware to hang
2. u? query for Modules detected Processor 0 for toshiba, 1 for arm
3. CM9001-EX  has max Inputs  and Outputs  > 128 (EX) by adding Slaves
4. Slave  ID max increased from 5 to 9 so SEM ID can be 9. CM9001-EX can have 9 SEMs
   
5. Increased rs485 buffer size to 600. Comfort app has many queries at start so need more buffer
6. For phone  dialout - if by gsm dialout, ignore delay  after cms
7. Security zone trouble sensitivity time changed from 850 ms to 2 secs to reduce zone trouble occurence
8. Slave  does not hang at check size of EEPROM May fix bug slave caused comms fail at reset
   
9. For CM9001-OPT FS31 Eventlog address is based on 256 Kbits.  event log has 600 events If EEPROM size is 64 Kbits  no of events is only 254.
   
10. Fix bug at reset  Clear Flags should clear 32 bytes not 254 bytes
    

Seeing that there is a version 7.202 which is the next version from 7.200, not sure why I am seeing 7.201 as current and latest on mine.

Attached Files

Thumbnail(s)
   

I\'ve just moved my zwave controller from a Fibaro HC2 to Home assistant with a zwave dongle. I have been using a zwave door switch as a virtual input for several years.
I\'ve included the comfort alarm into the new system with no problems. I\'ve created a virtual node which I want to use as a virtural input just like before. I\'ve associated the virtual node with a door switch. All good so far. I can see the virtual input in my zone list. But it doesn\'t change state. If I change the node to link to a flag or output it works fine. I open the door and the flag/output toggles state. The other way also works. I can toggle lights off and on from within the comfigurator. Any thoughts on what I\'ve done wrong.

As the UK moves from analogue to digital phone lines I am looking at what functionality I need if I didn\'t have a phone line. Does the mobile app work in the background (Android) and so should the alarm sound I will get a notification on my phone, or does the app need to be loaded and logged in?
Cheers

I lost my router, so am rebuilding my network. Got everything by the ucmPi working, I tried getting my IP using SW4 (REQ) and  https://uhai.alphawerk.co.uk/finder.html, but it seems the site is down.