Fibraro Universal

[juwi_uk]

Chaps,

I\'ve been messing with the Fibraro universal module which has different inputs on board; 2 x inputs and a 1-wire temp bus.

http://www.amazon.co.uk/Fibaro-FGBS-001-...B0093K2D1C

In the ZWave mappings for the UCM we can only set the register type for all registers assuming they are the same.  Could this be changed in future so you can set per register. 

I\'d like to be able to map inputs to inputs/flags or counters and the temperature to a sensor.  At the moment everything needs to be a counter (or flag, the latter of which is pretty useless for temp measurement !).

Julian

 

[slychiu]

according to your image, the channel 3 sensor can be mapped to a Comfort sensor?

[juwi_uk]

Nope, only Counter and flag are available as options for register type.

 

 

[slychiu]

can yiou send the cclx file to support@cytech.biz with the learned module?
we are curious to see the properties of the fibaro device

[juwi_uk]

Any thoughts on this now I\'ve sent my CCLX to support?

Ju

[slychiu]

we just wanted to see the device in the list. But as you say you can only select one mapping, unless you create a virtual node

[juwi_uk]

OK but I\'m now confused.

Why is it that the physical device only shows Counter or Flag  but a virtual device shows lots more register types. Where is the limitation;  device, firmware, comfigurator?

If I was to use a virtual node I have no idea how to map that to a particular sensor on the 1-wire bus connected to the Fibaro Universal.

The \"universal \"supports 2 x inputs and up to 4 x Dallas temp sensors.

Julian

 

 

 

 

[Ingo]

I am going to jump on this bandwagon. I purchased a UCM/Z-Wave, a Remote, one Switch and a Fibaro Universal device.

Has any progress been made to map a Z-Wave temperature sensor to Comfort Sensor?

[juwi_uk]

Yep I\'m \"officially confused\".  :0)
If I can map a counter then why cant I map a sensor too; surely a comfigurator limitation as they both store a 16 bit value.
Ju

[slychiu]

Zwave has evolved over time becoming more complicated
Originally there were no multi-channel nodes. Then they added multichannel nodes but each channel is supposed to be the same class, or that is what we thought

A multichannel device can only be mapped to one type of Comfort Register ie Counter, Flag or Sensor
 
The Fibaro universal sensor module has 2 channels of binary switches and optional channels which may be connected to various sensors, manual link http://www.fibaro.com/manuals/en/FGBS321...en-1.2.pdf

When the UCM/Zwave checks each node it will look for the classes supported by the channels in the device. if it supports multilevel sensor class then it allows mapping to a Comfort sensor. If it does not support tye multilevel sensor class, then it allows mapping to Counter or Flag. The Fibaro Universal device did not support the mulitlevel sensor class according to the UCM/Zwave query reply, that is why it was not mapped to sensor, but to Counter or Flag. This device does not seem to be a certified Z-Wave device, so perhaps it there is some problem with it. see http://products.z-wavealliance.org/


Zwave Multilevel sensor class is always mapped to sensors not flag or counter because our sensors are meant to be used for sensor data, so there is no confusion between the use of sensors and counters

A Virtual Node is created  inside the UCM/Zwave to mimic a Zwave node. The virtual node is meant to allow zwave devices to associate to it so that commands or status can be sent to comfort. Hence it can be maped to Counters, Sensors, Flags, Response, Outputs etc

Some of the limitations of mapping are due to the original design of the UCM/Zwave firmware. When new features were introduced by Zwave like the multichannnel class, Virtual nodes and Bridge controller, we had to maintain backward compatibility with the  older firmware implementations.