Hi All


It has come to our attention that the www.alphawerk.co.uk server is currently unavailable and as a result this is triggering an uncaught exception in the alarm code. This is a known issue which will be resolved in the next release when we overhaul the telemetry code.


You may find your UHAI is unresponsive until this is resolved, we are working on it and I will update this ticket once I have an update.


Thanks,


Matt

On 22nd December I noticed that the time on a door station was correct but the day was shown as 23rd. I reloaded the schedule and ticked the option for \'set Comfort date and time\'. This put D&T correct, but 11 minutes later it reverted to the incorrect time, and has stayed there. For all I know this has been like this for a long time. Where do I start looking for the cause of this error?

It is n Ultra 2 system file system 34, Comfort 7.099

Sorry if this is a daft question, I think it is but as its being discussed on another forum thought I\'d best check here.
1) is there any issue with wiring up shock sensors to comfort, and can standard sensors be used ? What settings do you use ?

Hello,
I\'d like to know how to see if [size=\"1\"]the lights are on or off[/size] in the Comfort app for android applied to Velbus System.
I don\'t know what is wrong with my programming. Is there any possibility to work with colours and, for example, when the words turn green, lights are on and when they turn red they are off? Or is there any other possibility of programming so I can distinguish if the lights are on or off? Can you help me?

Many thanks,
Rui Oliveira

Attached Files

  Screenshot.zip (Size: 670.19 KB / Downloads: 1)

Hello,

Can you provide me which protocols/ports need to be opened on my home router so that I can access with Comfort app on my phone from internet?

I can connect with Comfort app if connected inside my home network, but can\'t from internet.

Thanks in advance,
Luis Santos

UCM/GSM4 v7.106 beta firmware has the following changes from  7.100;

1. The Status value in the bottom left of the UCM/GSM screen will show the current GSM signal strength 0 to 4. In previous firmware, the GSM signal strength is displayed only for 1 second after which is followed by Normal/No Error. The status \"Normal/No Error\" has been removed as it provides no information and prevents the GSM signal strength from being displayed.
   
2. The signal strength 0 to 4 is followed by text describing the level number, eg 0 - No Network, 1 - Weak, 2 - Fair, 3- Good, 4 - Strong. This is not done by firmware, it is in Comfigurair defaults. To update the defaults, go to file > Update Defaults in Comfigurator. This updates the defaults. Close and restart comfigurator to activate the new defaults

This video  shows how to access the Setup menu in KP04A or KP06A


https://www.youtube.com/watch?v=gk0Dk0K_XSs

Press F0 to enable engineer menu before pressing and Holding * for 4 seconds
If engineer menu is not enabled, the keypad will ask you to press F0

Changing the ID of KP04A and KP06A is not by DIP switch or shunts
It is done by entering the setup mode of the keypad
The short video shows how it is done

https://www.youtube.com/watch?v=gP9ZZvp4iko

when the ID conflicts with another keypad it is not necessary to engineer mode or sign in

UCM/Cbus2 7.054

1. Fixed Bug - Enable and Trigger Group addresses did not update the mapped Comfort Counters
2. Fixed Bug - sending commands to Trigger and Enable groups by Response wizard did not update the mapped Counters
3. Fixed Bug - changing counters in Comfort mapped to Enable group addresses did not send the change to the Enable group. Now this allows commands to be sent to an Enable group by changing the value in the mapped counter

1. Sending Flag value mapped to cbus group address will take effect even if the flag state is not changed.
2. Improved firmware upgrade so boot sector may not be updated if there is no change
3. Improved firmware upgrade so it may work even if UCM/Cbus is reset during upgrade
4. If counter change originates from ucm/cbus, comfort broadcast counter change will be ignored by ucm/cbus to avoid the endless feedback and change when slow dimming by cbus2. This improves slider on app

1. Fixed occasional problem initial zone state transmitted to C-Bus Security application zone status may not be updated
2. Improved Monitor Mode for cbus soo that messages  Received from Cbus and  Transmitted to Cbus are displayed. Previously, only message from Cbus are displayed. This requires Comfigurator 3.12.2 (not available yet)
3. Work-around for rare problems for some C-Bus networks where the C-Bus serial interface was not able to receive a full status reply for the Lighting Application and hence was not able to initialise resulting in the ERROR led remaining on. Cbus2 firmware will not go into Smart Mode even if the Status Reply is not received from Cbus Lighting application
   

Hi.
I am not quite sure how to categorise this, because to be honest I\'m not quite sure what is going on.

Our topology is not very complex:
- comfort 2 main, outputs driving relay boards
- A remotely located RIO (connected via main panel) for controlling some lights and inputs from sensors in the drive and front of house
- A Slave module for outbuildings
- An IRIO (connected via the SEM) for controlling lights and inputs from sensors in the garden

For all things on control menu I have flags associated with them for the status to be shown on the app (IRIO requires flags to control it too, and I just did the menu the same way for the RIO, the differences are in the responses).

I am using timers in some responses to turn the lights on in sequence when a sensor is triggered. I have disabled these sensors by disconnecting them from RIO, so they shouldnt happen at present.


The problem (if it is one):
I notice the following when I use the comfort app (doesnt matter if its on iphone, samsung phone, or samsung tablet)

When I select Control, and then the specific section, the on/off status of the things controlled by the RIO initially say \'Wait\', and after a number of seconds appear.
This doesnt happen for any of the other things. I am unclear why there would be a delay in getting status for some flags over others.

Second problem:
when I switch one of them on/off it seems to take ages to action sometimes. For example, if I switch on 1 output via the app for the first time today, it might happen straight away, or it might take a couple of minutes.
Its not simply the app not updating, as I can see the light doesnt come on until roughly the same time the app status updates.

When I use the control menu it uses different responses to turn the lights on/off in one go by setting/clearing the flag, turn the outputs on/off, and stop the timers.

Have I somehow created a dependancy on the timers ?
I have set a bunch of \'Do response after x seconds using timery\' in the responses that sequence the lights. In the others they do \'stop timery\' for all the timers used.

When I run a response (say to turn lights on), if I trigger another response does it get queued up on the stack, or done in parallel ?
Just wondering if I have one response waiting on a timer and another stops the timer...

Is there any way to see what response comfort is currently doing, or what is in its stack of responses ?

I also see this same behaviour if I monitor the output using comfigurator, and action responses from it.

Any thoughts ?

Cheers,
   John.
p.s. slychiu, I uploaded the config file recently to put on my phone, so if you keep a record of these you have the file already