Posts: 1,255
Threads: 219
Joined: May 2007
Reputation:
0
Interesting.
I have had similar problems in the past (I\'m on the latest firmware) and as you say doing another learn again usually fixes. It sometimes takes a few attempts and my house isn\'t that big; certainly the 30m indoor typical range for ZWave is well inside that and only stud walls to go through. BTW would a bigger Zwave aerial on the UCM help?
I don\'t think your advice about re-positioning the device is correct though as they tell you explicitly NOT to do that as the device is part of the mesh and must maintain its position so cant be \"bench configured\" or moved after configuration. Would have thought that applies to UCM too as that\'s surely a node too?
Given that you say you test the device for multi-channel outside of the data coming back from the primary remote, is there any chance maybe that there is some conflict/timing issue here; as you doing (for a node) at the same time as the learn from the primary remote or once that has finished. Sounds like you could add a button to \"Recheck for Multichannel\" in Comfigurator then anyway?
Julian
Posts: 3,493
Threads: 476
Joined: Aug 2006
Reputation:
0
That advice is not quite correct
If the network has no problems then you should not reposition nodes
However if the network has such problems then you need to reposition the node that may have problems or do something else like adding repeater/nodes, otherwise the problem will still remain.
This was the problem actually encountered by another user with exactly the same problem, where the house was large extending to a few levels. It was due to blockage of the RF signal in the area where the UCM/Zwave was located. Moving the UCM/Zwave or the antenna fixed the problem, and the UCM/Zwave was able to detect all nodes as multichannel correctly
Posts: 1,255
Threads: 219
Joined: May 2007
Reputation:
0
OK but a switch normally HAS to be located in the back plate you\'ve embedded in the wall!
So do you mean to temporarily move it to configure or permanently somehow?
Posts: 3,493
Threads: 476
Joined: Aug 2006
Reputation:
0
The switch cannot be moved but you can move the UCM/Zwave if it is in an area of bad coverage or add another switch as a repeater
Posts: 221
Threads: 32
Joined: Oct 2011
Reputation:
0
Hi Ident (all)
I have just started again with my z-wave network and included the difficult fabiro node as the first device and it worked first time.
Again I have only just started to rebuild my network, but I have found that there is a slight delay in some devices, however, I have started to rebuild the code as well so it could be errors in what I have written.
Thanks for all your help, I am a member of many forums and this is one of the best in relation to support from the manufacture and members.
Best Regards
Lee
Posts: 221
Threads: 32
Joined: Oct 2011
Reputation:
0
Hi
Just an update.
I have just added a new fibaro 2 x 1.5kw to my network and Vera sees it right and controls it fine.
I have gone through all the usual inclusion routes for comfort and have even taken comfort out of the network and reset to default. However, I have the same problem as before that comfort only sees the new unit as a basic node.
This means I am back to the solution that worked before which was a complete reset of the network. This only takes half an hour but setting up and testing Vera and comfort will take 3 or 4 hours and I really don\'t want to do this every time I add a multichannel unit.
When I say I have gone through all possible inclusion I can assure you I am very proficient at this now and I am sure there is nothing more I can do around normal processes.
Does anyone have any ideas what else I can do? Chui mentioned a beta firmware that delt with the manufacture problem within Vera, but is there anything else this firmware include that might help here? Unfortunately I have not found the download so have not been able to try it.
Cheers
lee
Posts: 6,025
Threads: 880
Joined: Apr 2006
Reputation:
3
Can you try learning the network again using the UCMZwave?
Posts: 221
Threads: 32
Joined: Oct 2011
Reputation:
0
Hi
Sorry when I said include I have been doing the learn process in comfort. I have just updated to z-wave UCM firmware 7.061 and done the learn again with both switches of the new fibaro unit on.
It still comes out as a basic node.
What I I been doing is:
Included the new fibro in to Vera and run a learn on comfort. Outcome Comfort sees the new unit as basic node.
I then run a learn on comfort with the controller next to the new unit. Outcome Comfort sees the new unit as basic node.
I then removed the new fibaro unit from vera and ran a learn in comfort, obviously the fibaro was missing. I then included the new fibaro unit in to Vera and ran learn in comfort. The new fibaro unit was seen again in comfort (under a different ID) but still as basic node.
I then removed the comfort UCM from z-wave network and reset it to factory default. I also removed the new fibaro unit from vera and the included it again. I then included the UCM back into the network, but the new Fibaro unit still basic node in comfort.
Finally I have downloaded the new 7.061 firmware and run learn again. New Fibaro unit still basic node in comfort.
Cheers
Lee
