Hi,

After solving my ETH03 issues I\'m now testing my new UCM/GSM4.  I have a new SIM from idMobile which runs on the UK\'s \"Three\" network (standard pay-monthly voice & data 3G & 4G SIM).  I keep getting the Busy1 and Busy2 lights lit though which implies there is a SIM error. After scratching my head and looking around the forum I gather that you still sell the two versions of the UCM/GSM4 and renamed them (2G) and (3G).  The UK supplier didn\'t tell me that, they only advertise a GSM4 and I assumed that only the 3G version was sold now. I\'ve checked and the invoice also just says \"UCM/GSM4\" as does the little label on the Cytech box (it just has the \"4\" written in pen). 

Can anyone confirm which module I have from the photograph?  I really hope they haven\'t sent me the wrong one. I think the Three network only supports 3G and 4G.

If that is a 3G module - any suggestions on what might be wrong? I haven\'t been able to test the SIM in a standard phone as all my phones take smaller SIMs.

Thanks

Attached Files

Thumbnail(s)
   

Known Issues

1. Engineer Menu 4,5 Keypad Area (Anouncement) is wrong.
   
2. Execute Response in Comfigurator (DA) with multiple actions - security alarm actions eg bypass, Do Alarm cause subsequent actions do not work. eg Bypass zone 1, bypass zone 2, output 1 on Only Bypass zone 1 will work. However the Response executed by Comfort events will work
3. Bypass action has other problem of clearing a memory bit
4. Partition keypad disarm does not off siren when disarm partition if there is a trouble alarm, until the code is entered 2 times
5. CM9000- OPT firmware bug Clear all outputs action 8 does not work
6. Do Action 190 serial command DABE does not do the actions following action 190 correctly. The 1st action is continually repeated
7. Action 73, 16 Get  keypadId/ If Keypad ID does not work
   

1. Fixed bug Security Check sometimes announced zones from several Partitions instead of the keypad\'s own partition
   

1. Infrared Transmission improved performance for narrow IR signals mark/space. This requires UCM IR learner with improved IR receiver
2. When there is a Sensor  value change  from external UCM ids, the sensor Report from Comfort will be ignored by the UCM which originated it, so as to avoid dpuble updating which may cause a race condition
3. For Time Programs  if a day is Holiday, then Days of week Monday to Sunday will be disabled. Hence a day in Time program is Monday to Sunday only if the day is NOT also a Holiday. The old way of operation was if the day is Holday, the Time program is also activated based on Monday to Sunday
4. Comfort automatically detects LEM03 connected, and overrides Comfigurator > Configuration> Modules and Settings checkbox for \"LEM03 Connected\"

The new firmware has the following change

When a Counter is mapped to a Zwave Node, any change in the Zwave node obtained by polling by the UCM/Zwave of the node will trigger  the Counter Response based on its value

This makes it consistent with Sensor mapped to Zwave node - any change in the zwave node triggers the Sensor Response based on the value

Note that the polling time varies from a few seconds to 20 seconds maximum so the update and response may not be immediate

This new feature allows Zwave nodes to trigger Responses in Comfort without needing to Associate the Zwave node to a Virtuak Node

UCM 7.098
Changes from UCM 7.076

Known Bugs

1. COPY Button set ID could not set to maximum 8 From UCM 7.072 Bugs Fixes

1. Fixed bug UCM/ETH03 upgrade by cable fails 1st time Allow LT to be received without login so UCM can reply OK, not NA.
2. Fixed BUG from UCM 7.075. for Sensor commands  s!NNVVVV if repeated same value ucm replies NA. s? gave wrong reply
3. Fixed bug F!nn03 toggle reply FL was wrong. Bug From UCM 7.060

1. Increased message size of rs485 messages to 140 bytes
2. When UCM reports a sensor value, and Comfort broadcasts the new sensor value, the original reporting UCM ignores the sensor value in order to prevent multiple racing commands
   
3. UCM sends output command to Comfort only if output changed
4. Messages S? BP, DI, EV, O? A? I? a? DT, FL  will not be sent to PC unless logged in
5. Support H! and H? Commands for HIO
6. Support EL command
7. Login add partition  (0-3 or FF),
8. use \"Nonascii hex\" method for Vocab Upgrade depending on Comfort firmware
   

In UCM/Modbus Properties, set Modbus Master/Slave as Slave. Modbus Slave ID in this mode is the Modbus ID of the UCM/Modbus. The other Tabs Modbus > Comfort and Alarm> Modbus are not applicable in this mode.

In this mode, third party devices and software are able to control Comfort by sending commands and getting responses.  UCM/Modbus is a Slave and the Modbus device is Master. In Comfigurator, the Modbus Master/Slave is set to Server/Slave. The Modbus ID field applies to the UCM/Modbus Modbus ID as a Slave.
The following Modbus functions are supported

Function Code  Function                        Parameters
1                       Read Coils                      Read from starting address, no of addresses
2                       Read Discrete Inputs     Read from starting address, no of addresses
3                       Read Holding Registers  Read from starting address, no of addresses
4                       Read Input Registers     Read from starting address, no of addresses
5                       Write Single Coil            Write from Address, Value
6                       Write Holding Register   Write from Address, Value


Write Multiple Coils and Write Multiple Holding Registers are not supported


When Modbus Slave is selected, the screen below should be seen in the Modbus Server Tab
This is a convenient lookup reference table which shows the Modbus Addresses  in Decimal and Hexadecimal format of all the Comfort events and registers that are exposed to Modbus.






Each of the items above is a Category that can be expanded by selecting the item


Zones/Inputs
Comfort Zones/Inputs are mapped to Modbus discrete Inputs





Outputs
Comfort Outputs are mapped to Modbus Coils



Flags
Comfort Flags are mapped to Modbus Discrete Inputs




Bypass Inputs
Bypass Inputs are mapped to Modbus Coils.




Counters
Comfort Counters are mapped to Modbus Holding Registers




Sensors
Comfort sensors are mapped to Modbus Holding Regsters




Security/Keypad commands
Key arm security and Autoarm security commands to Comfort are mapped to Holding Registers

Modbus Monitor mode is a great help when you are setting up the Modbus Interface.
This shows the Modbus communications in both Transmit and receive directions.
It works for Modbus Master and Modbus Slave modes

Lines beginning with > show Transmit data ie transmit from UCM/Modbus to Modbus
Line beginning with < show Receive data ie receive from Modbus to UCM/Modbus

This is esepcailly useful in TCP mode as the IP addresses and port must be entered correctly for master and slave in order for communications to be successful

The information is raw modbus data. Refer to the Modbus standard documentation for the meaning of the data.

Modbus TCP and Modbus RTU have slightly different message structure. The example below is for TCP



To turn on Modbus Monitor, click on the Modbus Monitor Tab. To leave the Modbus Monitor, select another tab.


UCM/Modbus as Modbus Master will continually poll the Modbus Slave to which it is connected according to the Modbus to Comfort Table. Each modbus address will be polled in turn - when the slave address replies, the next Modbus address is polled, until the end of the table when it starts again from the top of the table

Note that in Modbus Monitor in Master Mode, the polling rate is slightly slower about 300 ms in order to avoid overflowing the monitor buffer

UCM/Modbus in Slave Mode replies only to a Poll from the Modbus Master which is connected to the UCM/Modbus.

So, its really important that your Pi has a static IP. If you leave it to DHCP and for any reason your Pi is assigned a new IP via DHCP from your router, then all of your devices will become inactive. This is because their network address, which includes the original IP is stored by SmartThings. This has happened to me a couple of times and is really frustrating. At this point you have two choices, either delete all devices and smartapps and start again, or set your Pi to the static IP that SmartThings has stored. If you are still in your initial set-up or have only just started and don\'t mind starting again, then I would recommend the former so you can choose an IP address from outside the range allocated to DHCP in your router (this way you can move straight to part B).
So here are the steps needed to:
A: Recover the old IP address that SmartThings has recorded

1. Go to the SmartThings IDE
2. Go to the My Devices page, and look down the table of devices.
3. Pick one of your comfort devices other than the bridge.
4. Look across to the Device Network Id column and you will see string that looks like xxxxxxxx:xxxx
5. Copy the first bit before the colon. This is basically your Hex address.
6. In a new tab navigate to this page
7. Use the form on the right hand side to convert \'Hex to IP Address\', and the IP address you need will be displayed below

1. This bit requires you to be familiar with the CLI (Command Line Interface) and happy using SSH. On a mac start \'Terminal\' or on a Windows pc download and use Putty (instructions)
2. Type in ssh pi@alpha-uhai.local
3. When prompted type \'@lphaWerk\' as the password. If you are worried that it is insecure to have this password posted here, then be aware that this is only useful if you have are already inside your network. So if your network is not secure or if you are still worried, then please feel free to change this password by typing \'sudo raspi-config\' and the changing the user password.
4. Follow the instructions here to set your Pi to use the static IP you discovered or chose above.
5. If you are using an IP address that previously assigned dynamically, then you will need to enter your routers configuration panel, and adjust the range of address allocated to DHCP, so your Pi\'s IP address falls outside of that range. Any other devices managed by DHCP, that now fall out of the dynamic pool, will get a new dynamic IP when they renew their lease.

An Entry Door is a Zone Type that you assign to the Front and Back doors or other doors that are used for entry and exit to the property
When leaving the property the occupant must exit through the Entry Door in order to Arm the system to Away Mode. (Leaving the house is not necessary in Night or Day Modes)
When the system is armed, opening the Entry Door will cause an Entry Alert to start - this is the delay to disarm the system by the keypad, before the Intruder Alarm is activated

An Entry Path is a property (checkbox) on a Zone, it is not a Zone Type. An Entry Path is normally a PIR (motion sensor) which is in the same area as the Entry door, which the user must cross while entering and exiting the property. The Entry Path is normally a PIR Away or PIR Away/Night zone Type or Alert Zone Type.

When entering the house, an entry Path zone will not cause an Alarm if the Entry door is opened first. If an Entry Path zone is detected without an Entry door open first, there will be an immediate alarm.

This new version has many useful improvements

Bugs Fixed

1.  Fixed Bug in Functions: If Blinds  or Thermostats are assigned to Outputs, the Outputs references are shown in Blue but the references are empty
2. Alternative phrases in Control Menu - Fixed bug when alternative phrase is added and deleted, it still remains as \"\" and cause problem wrong display in App
3. Fixed bug  new field GSM Module Type is getting the correct value by \"Read from EEPROM\" but is not saved with the file When the saved file is opened, the field is Unknown
4. Fixed bug in  IRIO -There is no \"None\" option available for the submodule type drop-down list If one of the types is chosen by mistake, the field  cannot be reverted to \"None\" (other than \"Reset to Default\"). 
   

1. In Write to Comfort, \"Write User Codes\" has been removed. This may cause accidental overwrite of user codes which had been changed by keypad. Write User Codes can be done in Security > Sign in Codes where there is \"Write User Codes\" and \"Read User Codes\"

1. [color=\"#ff0000\"]Counters, Flags, Sensors, Outputs - Show Status can show the current state of the registers. Now you can also write values to these registers. This is great for testing mapping to KNX, Cbus, Zwave, Modbus, RIO, HIO etc
   [/color]
2. Names of Zones, Outputs, Counters, Flags Sensors. The character \'_\" can be inserted before the name so that when the register is selected for mapping in eg IRIO, HIO, UCM/KNX and other UCMs, the underscored registers appear in the top of the list for easy selection. Otherwise selection is by alphabetic order. eg Counter Name _StudyLight would be at the top of the list ahead of Counter001, Counter002 etc

1. New Field Temperature Calibration Offset for the Thermistor temperature adjustment

1. New Field Temperature calibration offset in HIO
   
2. New  Property for source/sink current for LED to vater for different type of ELV switch
3. Added  mapping for some elements MUR, DND etc in channels

1. When TCP Interface is selected, the link to Comfort Server Manager is seen in Modbus Properties, so there is no need to go to Options > Settings to selecft the Universal UCM IP address and Port for Modbus/TCP
2. In Modbus Slave Mode, a new tab Modbus Server is seen. This gives ALL the modbus addresses assigned to Comfort registers in Decimal and Hexadecimal for easy reference - no need to calculation or lookup of the manual
3. Added Monitor Mode for Modbus communications. This shows transmitted and Received modbus messages, which is a great help when testing the connection and communication