+- Comfort Automation/ Security System Forums (https://www.comfortforums.com)
+-- Forum: Third Party (interfacing to Comfort) (https://www.comfortforums.com/forum-5.html)
+--- Forum: Zwave (https://www.comfortforums.com/forum-62.html)
+--- Thread: Fibaro Relays (/thread-3125.html)
- lwillerton - 02-06-2014
Vera Node 60
- lwillerton - 02-06-2014
Vera Node 60 1
- lwillerton - 02-06-2014
Vera Node 60 2
- lwillerton - 02-06-2014
Vera Node 60 3
- lwillerton - 02-06-2014
Vera Node 60 3
- lwillerton - 02-06-2014
Vera Node 60 4
- ident - 02-06-2014
We are still puzzled over this, we cannot figure why this would happen
Can we ask you to do the following;
- remove the fibaro (id 60) from the network using Vera
- remove the UCM/Zwave from the network usingVera
- Click Reset to Default on UCM/Zwave - do not forget this
- add the fibaro again on Vera
- lastly learn by UCM/Zwave again to add us back
If not please capture the IO Monitor and send to support@cytech.biz with the cclx file
Thanks for your help
- lwillerton - 02-06-2014
Hi,
This is what I have been doing, however, I am happy to give it another go might not be until tomorrow.
Cheers
Lee
- slychiu - 02-07-2014
If this does not fix the problem, can you buy another of the same
We will buy the nonworking one from you so we can test it in our lab
- ident - 04-30-2014
Hi Lee
Have you made any progress on the Fibaro issue?
We have since looked at other users issues on Zwave not being able able to detect nodes as multichannel.
This is very likely due to network problems
When UCM/Zwave does a learn, it receives the network information from Z-wave primary controller, but not whether the nodes are basic or multichannel
The UCM/Zwave then queries each node individually one after the other to check if the node is multichannel. If the node replies that it is multichannel, then UCM knows it is multichannel and is recorded as such in Zwave Mapping. However if there is no reply within the time-out of 8 seconds or so, then it is considered as a basic node, and you will not be able to send multichannel commands to the node.
This is likely due to the UCM/Zwave not able to reach the particular node. There is also a 4 hop limit to the Zwave network.
You can try the following if you have this problem;
- upgrade to the latest Zwave firmware
- do a learn again with UCM/Zwave. There is no harm in this and it does not erase information.
- Reposition the UCM/Zwave or the device that cannot be detected as Multichannel
- Add another Z-Wave node in the network where the coverage is weak