Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Arming and Control Menu stopped working via Cbus2
#1
Hi,

A few weeks ago, I could arm, disarm and switch Cbus lights on and off using the Control Menu on the iPhone APP. I had the following then...
  • Controller Fimware 7.047
  • Cbus1 Firmware 6.083 (beta test)
Since then I upgraded the following (including Comfigurator)
  • Controller  Firmware 7.050
  • Cbus2  Firmware  7.042 (Beta)
From the iPhone App, I am no longer able to arm to any mode, or control Cbus lights via the Control Menu. I can still disarm. 

I am using an iPhone 5s with iOS 7.1. I have emailed the new project and loaded that on the phone and I got the same results. 

I can however arm from the iPad App, but the Control Menu gives the same results there.
Reply
#2
Can you upgrade the UCM/Cbus2 to 7.045 as there were some bugs with the earlier version

Also remember that after upgrading from UCM/Cbus1 to UCM/Cbus2, you should do a write to Comfort because the Cbus1 actions were converted to Cbus2 actions in Comfigurator. It needs a write to comfort to write the changes into Comfort
Reply
#3
ident wrote:
Quote:Can you upgrade the UCM/Cbus2 to 7.045 as there were some bugs with the earlier version
I upgraded UCM/Cbus2 to 7.045, the Cbus Commands via the Control Menu on the iPhone App works. But arming still does not work.

Reply
#4
Further investigation reveals that I have issues with Scenes. On CBUS side I have Trigger Group 10 (in the Trigger Application) which has 5 action selectors.
In Comfort, pre UCM/Cbus2 I used to have Responses with command
Code:
Cbus RampInst CbusUCM 10 x 202  \'x being the action selectors.
 
Now with Cbus2 the commands are all the same, that is ...[color=\"#006600\"][font=\"Courier New, monospace\"]
[/font][/color]
Code:
Cbus2 CbusUCM 202 10 2
With no Action Selector.

I would like to continue using the Direct Method as far as Triggers are concerned and not use Counters.
Reply
#5
This is a problem with Comfigurator, the Action Selector field is not there for you to add a value.

Edit the Response manually and create it the same as a Lighting App string but use Application 202 instead.

Try the following:

197,UCMID,05,202,00,2,10,255

Ingo
Reply
#6
This should be fixed in the next version

It is actually easier to map the Trigger Group eg 10 to a counter and then set the counter to the value of the trigger selector
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)