Hi,
I am trying to setup 2 CM3+ modules with NodeRed, will send one to a friend when setup and keep one myself. I followed the instructions in the UCM/Pi manual and managed to get the Raspbian image flashed, IP address established, and connecting to it with a monitor no issue.
On first card, I used the standard image linked from the manual, and then followed the steps here to enable serial port etc. When I did the \"[highlight= initial; font-family: SFMono-Regular, Consolas, \"Liberation Mono\", Menlo, monospace; color: rgb(36, 41, 46); font-size: 13.6px;]curl -sL https://uhai.alphawerk.co.uk/scripts/quickstart | bash -\" command, nothing happened. 
I then installed the Alphawerk image on the 2nd CM3+ module and when I did that \"[highlight= initial; font-family: SFMono-Regular, Consolas, \"Liberation Mono\", Menlo, monospace; color: rgb(36, 41, 46); font-size: 13.6px;]curl -sL https://uhai.alphawerk.co.uk/scripts/quickstart | bash -\" command, it seemed to be working as files were downloaded and a lot of updates seemed to be successful. Then it finished with the errors shown in the attached image.
I have mapped a static IP address to the module in my router\'s settings, and when I went to that address http://192.168.1.68:1080 I get a site can\'t be reached error and the admin page does not load. When I load this page and press the REQ button for 1 second nothing happens (I guess due to the errors in the image?). 
Just in case it\'s relevant, I used \'pi\' as the username and \'raspberry\' as the password to login to the CM3+ operating system. And it was a Windows 10 PC I was using to try to load the admin page in Chrome (in case there could be any issues that side).
Is there anything I need to do differently to get the alphawerk resources installed correctly, or is it a server-side connection issue?
Thanks

Attached Files

Thumbnail(s)
   

Firstly I am not an installer - I am a tinkerer. My system was installed professionally some time ago but the installers are no longer keen on Comfort and given current circumstances I thought I would have had a tinker. 

I have had problems over the year with smoke detectors they are temperamentally go off and to resolve I have  removed them, via zonetype (setting to an empty entry). 
In the past despite replacing the unit the problem has reoccurred after a few months.  All but one (the most important, the landing) has over the years been removed through the GUI.  That one went off in the middle of the night a few weeks ago so again I removed via GUI. 

I them managed to source a number of identical replacement units and thought I would try the process of reinstalling through the GUI again.  I reinstalled the landing unit and uploaded the changes however the alarm went off reporting fire - I entered the security pad code and it went off, I had no idea what the process of changing these are so assumed that must be normal.  

A few days later all is fine so I decided to replace another (Garage), this time when uploading the config changes the alarm went off again (as I expected) but only reported the original replacement Landing as an alert.I then removed Landing from config (leaving just garage) and after upload it behaved with no alarm.  What could be the problem with landing smoke please?

This feature applicable in Comfort Firmware 7.175 allows sign in on the keypad for any specified user to activate a User Response, which may be programmed for any purpose, for example to unlock a door, turn on lights or appliances
The screen for Misc Events > User Responses is shown below




an example of a user response is below



The response is programmed to open the door, turn on lighrs and the photocopier machine if User 1 signs in.

The action Skip Annoucement has a different function when used in User Responses. It causes the keypad to exit without going on to the user menu eg \"Welcome, Security off.. etc\"Hence the keypad when signed in by a specirfic user will triiger the programmed user responses only and will bto go to user menu  as usual. This allows the keypad to be used for access control

see http://www.comfortforums.com/view_topic.php?id=5161&forum_id=79&jump_to=24912#p24912 for Comfort 7175 firmware

Firmware 7.175
Known Issues

• Partition keypad Security Check function (F,3,2) caused Zones for the wrong partition to be   announced. Zone Detection for all partitions is t  is OK. From 7.163
• From 7.159 increment counter, decrement counter actions did not return counter value as last action value so If action which follows uses the wrong value
• For Partitioned systme, when user logs in for partition >0, every minute the partition may be changed to to 0 so the user may arm or disarm to partition 0
•  For wifi01 plugin  if ucm does not log out,  idle timer from EEPROM expires does not reset Wifi module. so if wifi lost connection, the module is not reset
• Old bug - if there is zone trouble in a partitioned system at reset, the partition keypad will show \"Communications Failure\"  without ID (instead of zone trouble)- This is removed after sign in on keypad. When the user signs in on the Keypad, it shows \"Zone 1 Trouble\" instead of the correct zone number.
• Old Bug - if zone trouble is force armed when armed, after disarmed, the zone trouble is not shown until armed again or security check
• when sign in when zone trouble announce zone and user name was wrong
  
  

• Fixed bug - Protocol Input OFF message IPnn did not report  after unbypass and zone closed
• Fixed bug  from 5/11/18 sent serial no broadcast to RS485 at reset instead of query, causes delay at reset before start Dont query serial no at reset, Only query serial no when id info reply is received, so UCM can get it
• Doorbell action  set ID=31H doostation ID1 instead of 241 which is F1 partition 1 Fixed Bug DA09 did not turn on Doorbell mic and speaker
• Fixed bug sometimes virtual input is missed.  Multiple zones trigger during sensitivity timer was missed
• Fixed old BUG record greeting message press # will return to program menu. Voice menu not corect
• Fixed BUG upgrade CM9001 by bus sometimes fails at UB02 but firmware was not erased
• Fixed Bug Counter report CT – if counter reponse changes anothr  counter, the counter report for the changed counter has the same  conterid as the original. So if KNX send counter, counter response  change another counter and the counter iss reported to knx, the  counterid remaiins as KNX ucm id so the KNX ignores the new counter  report
• Fixed Bug Doorbell Response creating endless loop
• Fix Bug Counter report – if counter reponse changes another counter, the counter report for the changed counter has the same conterid as the original. So if KNX send counter, counter response change another counter and the counter iss reported to knx, the counter id remaiins as KNX ucm id so the KNX ignores the new counter report
• CM9001-EMS fix bug from EMS 7.159 – if counter setpoint is out of limits, setpoint is changed to within limit but the counter value is not updated correctly and causes endless loop

• Action 161 Change Login Partition,. If User is enabled for several parttions, user is logged into the lowest partition. Change Log in Partition changes the partition to another enabled partition. Cytech app will process different partitions correctly for alarm states and commands and arming and disarming for plug in ETH03 and UCM 7.124
• Action 9 Doorbell in test mode dont send DB31
  
• Action 27 motion detector zone response for hotel monitoring for ULT and OPT
• Action 65 add add parameter 2 for check status Bell
• Action 73 add parameter  32 occupancy

• Motion for Occupancy sensor  enable for OPT, ULT LGX
• Action 27 motion detector zone response for hotel monitoring for ULT and OPT
• Implement dR and d? For occupancy detection

• For  BS8243,  if the zone is the same as (unconfirmzone) then it is not confirmed alarm
• For BS8243, fire alarm will not set notification fixed from 10/11/19 which did not work

• Support wifi01 submodule on CM9001
• If wifi01 detected leave baudrate at 38400, and leave parity as none
• FS34 FS31.FS36. FS37 FS39 add eeprom location 255 idle time out in minutes for wifi (default 5 minutes)
• Add rs485 message  0b2h for wifi timeout value reply to ucm query
• Every hour for wifi do  auto update time from NTP for wifi submodule
• If wifi  eeprom time out in location 0x00ff= 255, dont start_wifitimeout. Only 0 did not start timer before
• For wifi run timer to reset wifi based on location 255 in minutes (default 5 minutes)  when receiving is idle, or when log in and log out, and continue to run the timer after that so wifi is reset at regular intervaes when not logged in

• Implement Timer value message Trttvv sent to the  UCM which logged in only, instead of broadcast to prevent too much delays, Timer value will update every second to the UCM logged in, but when the UCM logs out, The timer RS485 message will not be sent to the UCM. Supports Timer Status in Register Monitor see http://www.comfortforums.com/forum20/5149.html
• No of Timers change from  16 to 32 for LGX01 and ucm/logic , also 32 for ems

• Misc Events >User Responses is enabled for sign-in on keypad. Previously this was for fingerprint reader, now obsolete. Skip announce action 23 in the keypad User response will exit and not go into  the keypad menu . If skip announce action 23 is not in the user response, sign in will go to the user menu as normal. if keypad user response is not zero, the keypad sign in is recorded in the event log
• see http://www.comfortforums.com/view_topic.php?id=5162&forum_id=126 for example
  

• Save 32 counters in eeprom and 256 Flags  enabled for ucm/log, lgx01,knx/log, EMS not for OPT and ULT
  
• KNX/Logic  implement  nonvolatile 32 counters  
  
  

• KP06A Keypad volume is increased for the same setting (75% instead of 50%)

• Supports DTMF key detected by GSM module not depending  on DSP for GSM4 (3G) and LTE.
  
  

• RS485 Receive time out adjusted to increase time out
• For  test mode, only allow 1 UCM and 1 KP ID. Production  test problem when cm9001 detects no of keypads and ucms >1 get comms fail.
  
• Test mode Flag warm start will not clear test mode, so that test mode does not scan IDs modules again

Bugs Fixed

• Fixed intermittent problem with firmware upgrade using UB02 in reset preventing  firmware upgrade by Comfigurator
• 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

• UCM sensor fixed bugs for  fractional value
• Sensor report sr and sensor reply s?  send 3  bytes fractional value of sensor
• RS485 receive message  if (ucmpartition) = 0ffh, accept all partition broadcasts
• When UCM/ETH03   is logged out  set no ucmpartition at so eth03 can send emails for all partitions
• UCM receives and   process all partition broadcasts, check is match to UCM partition.
• Added  d? query and dR report
• Support wifi01 submodule plug in for UCM and CM9001, automatic detection and set 38400 baud
• UP, DP commands supported. dont include event log 
  
• UP  send progress UPxxxx whhere XXXX is address 0400H boundary. DP send prgress DPXXXXevery 0400H addresses
• UP for ETH03 will time out more than 2 minutes because no receved data from CF but it completres if idle time out in CS Manager is set to 5 minutes
  
• U? add parameter SS 3 = wifi01
•  Added  Timer  report TRttVVVV only when UCM is logged in Supports Register Monitor for Timers.
• UCM log out sends  LU00  so that CM knows when ucm is log out and TR message is not sent
  
• UCM counter: when external device updates counter, dont update local UCM counter, sebd counter change to CM, and when CM broadcasts new counter value, then udate CM local counter so if the update counter nessage RS485 is missed, the counter update is stil sent later  Fixed probem sometimes modbus counter was not updated
• UCM log out will see LU00, will not have LUFF following.
• RS485 Transmit Buffer ize incraesed from 500 to 600 bytes
  

The UCMs (UCM/USB, UCM/ETH03) have an EEPROM that is used for backing up of the configuration in the Comfort controller.
This is useful when the configuration has been corrupted. It also backs up the user codes so when the user has forgotten the user and or engineer codes this can be used to restore the codes.
Comfigurator 3.13.1 has a function to write Comfort > UCM EEPROM and Read UCM EEPROM to Comfort in the Transfer Menu
This requires UCM Firmware 7.131 minimum.



Note: This does not apply to UCMs for Cbus, KNX, Modbus etc which are 3rd party interfaces






If the UCM is an old model that does not have an EEROM (in U2 socket) then an error message will be seen
Also if you are using the plug in ETH03 on the CM9001 PCB this is invalid because there is no backup EEPROM on the plug in eth03 submodule


Write Comfort to UCM EEPROM takes several minutes. The progress bar is seen as shown below




Transfer UCM/EEPROM to Comfort will read from the UCM to Comfort to restore the saved configuration  including user codes
However the Event Log is nt saved or restored

In Comfigurator 3.13.1, (requires Comfort Firmware 7.174 and above) a useful feature has been introduced - Occupancy Status
This allows Comfigurator to display the Occupancy Status is active, ie if there has been any movement in the selected zones in the premises



In the above screenshot, the occupancy status is Inactive. If there were movement detected in selected zones, the occupancy Status would be Active

This is programmed as follows;


Select the zones which will detect occupancy. These are normally Motion detectors (PIRS)

Create a Response called eg Occupancy






In the Zone On and Off Response, assign to the  Response which was created  (Occupancy in this example)






In Alarms  Misc Settings> Occupancy Time, enter the time to detect occupancy eg 30 minutes. This means that the occupancy will be inactive if the zone does not detect movement for 30 mnutes
Assign the same Response to all the  zones which will take art in Occupancy Detection





for example if 4 zones are assigned to Occupancy detection, and the occupancy time is 30 minutes, the Occupancy Status will be Inactive if zone of the zones detect occupancy within that time. If any zone detects movement in that time interval, then Occupancy is Active

Hi  folks,
On this page http://comfortforums.com/forum67/873.html there is a link to download Comfigurator.  It looks like any V2 entries have dropped off the end of the list.  
From reading around here, it looks like I need V2 to read from Comfort 1 back to my PC (don\'t ask!).
Any pointers?
Thanks,
Nick

I\'m leaning towards purchasing the following Hikvision cameras and was wondering how I could confirm if they will work with the Comfort app?
https://www.use-ip.co.uk/hikvision-ds-2cd2385g1-i.html
https://www.use-ip.co.uk/hikvision-ds-2c...wd-is.html

Known Bugs (Remaining)

• Responses  with AND and OR Conditions  after Read from Comfort are decoded incorrectly. If you have such conditional actions in any Response, do not Read from Comfort except for checking only. This bug is from long ago
• [color=\"#ff0000\"]Action Set Virtual Input does not select Virtual Input, selects physical input instead[/color]
• [color=\"#ff0000\"]UCM/Cus2 Cbus to Comfort Output status is wrong when map to lighting group address. Output -1 status is shown instead of output number status[/color]
• [color=\"#ff0000\"]Set login partition action has error[/color]
• [color=\"#ff0000\"]Security Node Responses and siren outputs programmed in old cclx files are not in Partition events when opened in 3.13.5[/color]
  

• Fixed Bug IRIO analog output registers not shown as referenced
• Fixed Bug IRIO with modules.  eg ISM01. Open new file and scan for modules. IRIO is detected, click on IRIO, ISM01 is seen but we  cannot see any IO under ISM01. We must select None or other submodules then select ISM01 then the I/Os under ISM01  can be seen
• Fixed Bug \"Subtract sensor from last action\" was wrong
  

• Added Occupancy status on the status bar, to show if the premises is occupied. See http://www.comfortforums.com/forum20/5158.html
  
• Occupancy commands dR or d? Occupancy Active/Inactive
• Action 73, 32 Get Occupancy Status (73,32)
• added Support for Wifi submodule (coming)
  
• Added Timers status to register monitor.sort by name and number. However the register values canbot be changed. See http://www.comfortforums.com/forum20/5149.html
  
• IRIO  modules if IRIO was present but now is not found, dont give error messagfe to avoid several error messages due to Submodule not correct