Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Fibaro Relays
#61
Vera Node 60


Attached Files Thumbnail(s)
   
Reply

#62
Vera Node 60 1


Attached Files Thumbnail(s)
   
Reply

#63
Vera Node 60 2


Attached Files Thumbnail(s)
   
Reply

#64
Vera Node 60 3


Attached Files Thumbnail(s)
   
Reply

#65
Vera Node 60 3


Attached Files Thumbnail(s)
   
Reply

#66
Vera Node 60 4


Attached Files Thumbnail(s)
   
Reply

#67
We are still puzzled over this, we cannot figure why this would happen

Can we ask you to do the following;

  1. remove the fibaro (id 60) from the network using Vera
  2. remove the UCM/Zwave from the network usingVera
  3. Click  Reset to Default on UCM/Zwave - do not forget this
  4. add the fibaro again on Vera
  5. lastly learn by UCM/Zwave again to add us back
see if that works


If not please capture the IO Monitor and send to support@cytech.biz with the cclx file


Thanks for your help

Reply

#68
Hi,
This is what I have been doing, however, I am happy to give it another go might not be until tomorrow.
Cheers
Lee
Reply

#69
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
Reply

#70
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;

  1. upgrade to the latest Zwave firmware
  2. do a learn again with UCM/Zwave. There is no harm in this and it does not erase information.
  3. Reposition the UCM/Zwave or the device that cannot be detected as Multichannel
  4. Add another Z-Wave node in the network where the coverage is weak
Unfortunately these are typical of RF problems and Z-Wave in particular


Reply



Forum Jump:


Users browsing this thread:
4 Guest(s)

Powered By MyBB, © 2002-2026 Melroy van den Berg.