Comfort Automation/ Security System Forums

Bugs Fixed

1. Reminder messages  fixed BUG from 5.173 -  reminders did not activate at correct time

New Features

1. DL command to write to EEPROM will write memory until event log. This reduces the time required to Copy UCM U2 EEPROM to Comfort
2. Erase U4 EEPROM operation during Write to EEPROM will not erase Event Log locations
3. Action 152 set and clear will return value 0 for Off, >0 for On
4. Disallow disarm by SMS (10) for security reasons
5. Improved vocabulary Upgrade allow retry for each programming line
6. Turn on Battery circuit immediately after reset  so that reset command  when AC is off, and battery is connected does not switch off the power to the system

Bugs

1. Assigning Output to Security > Status LED will cause KP Home/Armed LED to show the wrong status (from 5.220)
2. Reminder Enable function does not work for Reminder Numbers 9 to 16. Reminder Enables for 9 to 16 are the same as Reminder 1 to 8. This affects Scheduled Reminders only.
   

Note that products may not come with the latest firmware when bought from distributors. Please check the website or forum for the latest firmware and upgrades

Download firmware from https://www.cytech.biz/product_details.php?item_id=210

Just something I noticed, upgrading firmware doesn\'t give the option to Set Comfort Time. You have to set it again after the firmware upgrade.

Also, is there a newer Action Code document available describing the Action 152 command? I would like to know the changes made to it from previous release.

Ingo

The action codes latest document can be downloaded from https://www.cytech.biz/product_details.php?item_id=147

The date and time have to be updated manually, as Comfort is reset after the upgrade so needs time to wake up

[user=86]ident[/user] wrote:

Quote:The date and time have to be updated manually, as Comfort is reset after the upgrade so needs time to wake up

Found out the hard way, when critical time based responses failed to start.

We will add a warning message at the end of the upgrade

Re: Disallow disarm by SMS (10) for security reasons.
Is this an option which can be set in the configuration file, or mandatory? If so, why, as the command can only be accepted if the text comes from one of the programmed mobile numbers.

Thanks

There has been some debate about this issue
We may have to add an option or re-introduce the disarm feature
Any other comments from others?

[user=86]ident[/user] wrote:

Quote:There has been some debate about this issue
We may have to add an option or re-introduce the disarm feature
Any other comments from others?

I use SMS (10) a lot and I find it useful. One of the reasons I bought the GSM was to do arming/disarming via SMS.


Not sure what the security reasons would be to remove it. IT only works with programmed mobile numbers, so that is a bit of security. Unless if someone want to only send SMSes and not allow control from the programmed mobile numbers. In that case an additional flag or Action should be added to maybe dis-allow some of the programmed mobile numbers instead of taking the feature away.

I guess I will not be upgrading my firmware till then

Noted

Are you sure when you use (10) and there is an alarm, that it is safe to disarm?

[user=86]ident[/user] wrote:

Quote:Noted

Are you sure when you use (10) and there is an alarm, that it is safe to disarm?

True, one should not.

The only time that I did that, was when I was not in the house and I had an a visitor who caused an alarm, I only used (10) after confirming via the phone that all was well.

It will never be a good idea to disarm remotely while there is an alarm, not knowing what is happening on the premises. This includes via the phone/dial-in or any other way.