Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Fibaro Dimmer 2 FGD-212 learned as a Multilevel Sensor
#21
Yes you make point regarding this matter.  But on the other hand when i chose comfort one of the reason because knowing it has ucm zwave as hub to zwave network .. i expect there is no issue about incompatibility.. all my lamps in my under construction house using the latest led module of philips ( very effecient in energy compare with led lamp in the market recently ) with new dimming driver that use trailing edge... so i need dimming controlled to communicate with comfort and i  chose zwave .... all the lamps,  comfort with 6 SEM and its local expansion, GSM ucm, 25 dimmer controllers including 15 fibaro FGD 212, all sensor alarm, IR beam etc just installed... no point of return ...

But last night i read the link given above and manual of FGD 212 ... seem that FGD 212 has inclusion option to disable secure mode to enable other device communicate  by unsecure methode.. if i am not misunderstood ...i havent had time to test it ... i hope this can solve the issue with comfort
Reply

#22
Chiu,
From what I\'m reading is does say that you cant control the device in non-secure mode from what I read. ie
\"... If you want to control Dimmer 2 in non-secure mode you should re-include it in HC2 and this time do not use Security Mode....\"
So to me it supports both but driven by how you include it in the first place.
Surely to be able to support either scenario the UCM just needs to support one more class;  the \"secure\" class doesn\'t it?
Ju
Reply

#23
Quote:\"... If you want to control Dimmer 2 in non-secure mode you should re-include it in HC2 and this time do not use Security Mode....\"
This is what someone on their forum says (not sure if it is a fibaro guy or a user)
However the test lab report says (see Leons screenshot) this device works only in Secure mode so it is a contradiction. Hence only someone who has the device can verify it by including in non-secure mode.
If it is really true that it can work only in secure mode that will be a problem for many other devices as they will not be able to associate with this in secure mode
Reply

#24
Quote:This is what someone on their forum says (not sure if it is a fibaro guy or a user) However the test lab report says (see Leons screenshot) this device works only in Secure mode so it is a contradiction. Hence only someone who has the device can verify it by including in non-secure mode. If it is really true that it can work only in secure mode that will be a problem for many other devices as they will not be able to associate with this in secure mode
So I asked this question on the Fibaro Forum and the reply came back as

Quote:Security is mandatory for new Z-Wave+ devices. So device which uses ZW+ Chip must implement this feature.
Quote:But, it is up to user how device will be included. In HC2/HCL before inclusion process you can decide - secure or non-secure inclusion.
Quote:Also it is possible to include new Dimmer in secure mode and control directly other devices in network (non-secure ones) via associations but it is necessary to change one of advanced parameters in device\'s configuration.

Reply

#25
Chiu,
Your system is very powerfull as integrator system ( instead of great and security one ) as your customer  i hope comfort willing to accommodate as much as possible in zwave world development, especially if this issues related with Zwave+ .... in order to make your market position also powerfull for integration with the zwave network
Reply

#26
Hi juwi_uk,

You should also ask \"If FGD-212 is done in non-secure inclusion, can other non-secure devices control FGD-212 directly, via association too?\".

This is to confirm it is not a one way control only.
Reply

#27
juwi_uk wrote:
Quote:
Quote:Security is mandatory for new Z-Wave+ devices. So device which uses ZW+ Chip must implement this feature.
Point to note that the above statement is misleading.  
Security is only mandatory for new Z-Wave+ Controllers.  Other Z-Wave+ devices will depend on their own specifications or applications. Wink
Reply

#28
Hi 
I just want to clarify regarding ZWave plus standard modules.
ZWave UCM should work with any ZWave plus module as long as the module does not encrypt its messages.
So Fibaro ZWave plus Dimmer will not work at it encrypts its messages 
whereas
Qubino Flush Dimmer ZWave Plus should work as it does not encrypt. please see http://www.pepper1.net/zwavedb/device/866.
More over, its dimming abilities for LEDs is better than the fibaro. For the UK it does require a neutral wire so wall mounted switches  with only switched live it will not work.
HOWEVER, this module can be placed in the ceiling rose where there is neutral so can still be used with a momentary switch.
I think is the case and make clear.
Reply

#29
Its not clear support trailing edge dimming protocol as i need
Reply

#30
UCM/Zwave will work with any zwave plus device except for the new zwave plus features including encryption.  It imay not just be encryption that is different
Zwave should have made it a requirement that all zwave plus devices must have a mode that supports older devices, for the sake of compatibility
Reply



Forum Jump:


Users browsing this thread:
1 Guest(s)

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