I have set up a simple Z-Wave network with a Vera Edge controller. I have included the UCM/Z-Wave in the network. Comfigurator knows all the Z-Wave nodes and I can use Comfort responses to control the Z-Wave actuators and having associated flags with the nodes, Comfort knows the status of the actuators when they are changed by Comfort or by Z-Wave nodes.
In other words, everything seems to be working as expected except the Vera Edge has "Error: unable to get any information on node" against the UCM/Z-Wave node. Vera Edge seems to think the UCM/Z-Wave is a "SceneController1". Repeating the learn process for the UCM/Z-Wave doesn't make any difference.
I suppose as it all works I shouldn't worry but clearly something is not quite right with the setup which may cause problems in the future. Anybody any ideas?
Adrian has it correct; the Comfort Zwave UCM always is the secondary controller.
My first primary controller was an ACT Homepro, then i upgraded to a Remotec ZRC100 and now finally settled on the Fibaro Home Center 2 (did that as most of my units are Fibaro anyway)
I hear Vera is good too as well.
Yes I have a Popp Wall Controller included in the Z-Wave network and Vera is quite happy with that. I have also added a Comfort Virtual Node and again it all seems to be working fine (I can trigger Comfort responses with Z-Wave sensors) but have the same error message against the virtual node in Vera. Looking at the log, Vera is sending a "reconfigure" action which the UCM/Z-Wave ignores. (At least I think that's what's happening - the log is quite difficult to interpret without a detailed knowledge of Z-Wave protocols! )
lobby the major primary controller companies so that the Comfort/UCM is recognised as a "known" secondary controller; and thus maybe a bit better supported. I'm sure the list is longer but ones like Vera Edge and Fibaro Home Center 2 are two we all seem to use on this community as a start. For example I use Fibaro and they still haven't created a "template" for the UCM even though plenty of other templates for devices are getting created.
I know Cytech resources aren't infinite and I'm sure you want to interface to as many devices as possible so that you maximise your sales activities, I also think that maybe a few of these integrations like CBUS and ZWave should have "premium" developer status and maybe have features that go a tad further than some of the other "first gen" integrations.
Personally I want a reliable retrofit solution and hoped Zwave was it, but I'm sure others want a new build solution and if Comfort could "really..really" (that's technical for more features!) support these then life would be sweet!
In terms of my UCM/ZWave3 I sort of agree with Vangelis, I don't really use mine much either now.
I just added a Vera Edge, I selected generic device from the Vera Edge U17 screen. I also get the same message mentioned in this post and also Vera thinks the UCM/ZWave is a scene controller.
Is generic device the right device to select to add the UCM/ZWave
I have not tested yet but will try over weekend
As per my previous post, I have a Vera Edge setup with Fibaro Dimmer and Fibaro Motion sensor. I also have Philips Hue plug-in in Vera U17 software.
All this works fine on Vera U17, motion sensor detects motion and temp, The dimmer module can be controlled from Vera U17. I can switch on/off lights and dim the lights. I can setup scenes in Vera U17 and on detecting motion it can switch dimmer 2 module or the Philips Hue lights.
I am struggling with UCM Zwave. I have it installed in my comfort 2, no errors (See pictures of module properties and mapping). My Vera Edge U17 see's it a a scene controller but I get "unable to get information from node" in the Vera U17 software.
In comfort, the Fibaro sensor appears as a Slave_Garage_Door and the Fibaro dimmer as Slave_Multichannel.
When I try the "On" & "Off" function it does not work, the lights do not come on when executed from Comfort.