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
Unfortunately these are typical of RF problems and Z-Wave in particular