The main switch is S1 and the child is S2.
You say that the one that doesn’t work is the main one, right?
Oh yes, of course you’re right, the physical switch on S2 should work correctly anyway, and the doubt is whether the physical switch on S1 works. I’ll perform a test tomorrow. Thank you
Can anyone explain how the Fibaro Smart Implant works with multiple temperature sensors connected? If you wire three, they all wire to the same connections, so is the reported temperature an average of the three? Thanks.
Not average. Each measurement is separate.
1 Like
Really? How does one see that in the app with this driver? I had initially connected it all up with two probes but could not find more than one temperature measurement in the device itself…
Hello Mariano. I was just posting a question on Daniele_Ratti’s [ST Edge] Driver for FIBARO Roller Shutter 3 (with energy monitoring and venetian blinds support) page, before I found this.
I think about to buy 9 used Fibaro Roller Shutter 2 FGR-222 for only 15€ and was wondering if this driver works with the venetian blinds feature. I saw this topic on this page multiple times but not a clear answer.
I’m also curious what the difference between your and Daniele’s driver is?
Thank you very much for your support! I don’t know what I would do to my smartthings hub if you wouldn’t release so many great drivers!
Hi @KochS
The Venetian blind functions are not implemented in my driver, because I saw in the manual that to operate in Venetian mode need set parameter 3 to value = 1 (commands are sent to the hun with Fibaro command class instead Zwave command class).
GENERAL SETTINGS:
3. Reports type
0 - Blind position reports sent to the main controller using Z-Wave Command Class.
1 - Blind position reports sent to the main controller using Fibaro Command Class.
Parameters value shoud be set to 1 if the module operates in Venetian Blind mode.
Default setting: 0
Parameter size: 1 [byte]
Since I don’t know what this entails, I only implemented it in the fibaro FGR-223
I don’t know, I haven’t seen Daniele’s driver code
And again! Thank you very much for your incredible fast response! I really appreciate your work in this community!
I will buy them anyway for my other non-venetian blinds.
Thanks again!
Hi @Mariano_Colmenarejo ,
First of all, congratulations for the great contribution you offer to the SmartThings community.
I intervene in this discussion because I need your support for a problem that I will now try to illustrate.
I used your DriverEdge “Z-Wave Window Treatment Mc” to manage the sectional garage door equipped with a Nice motor, to which I integrated its own Z-Wave module (mod. IBT4ZWAVE).
Yours is the only DriverEdge, among several tested, that allows me to obtain acceptable functionality, however some defects still persist.
The first discordant note is certainly the icon with which the device is represented in the APP, in fact SmartThings considers the device as if it were a motorized window blind rather than a garage door.
Furthermore, the device’s capabilities include the measurement of Power and Energy, values that the Nice device obviously does not detect. Due to this anomaly, every time I select the device from the APP, the note appears: “This device has not yet updated all of its settings of the states. Please try again later”.
Last note concerns the “Default position” function which is not configurable.
Given the above, I ask you if there is the possibility of updating your DriverEdge so that the Nice accessory is actually recognized as a “garage door” type device and so that it offers only its specific capabilities in the Tile.
I thank you in advance.
Greetings
Hi @dbHAxST
I need to know all the data, fingerprints, command class of the device.
Could you change to the zwave thing Mc driver and publish the data?
1 Like
1 Like
Hi @dbHAxST
Changed to profile nice-garage-door without power, energy and preset position
Try if works
───────────────────────────────────────────────────
Name Z-Wave Window Treatment Mc
Version 2023-09-28T20:08:30.327874442
───────────────────────────────────────────────────
- id: NICE/IBT4ZWAVE
deviceLabel: NICE Door IBT4ZWAVE
manufacturerId: 0x0441
productType: 0x2400
productId: 0x1000
deviceProfileName: nice-garage-door
1 Like
Hi @Mariano_Colmenarejo ,
I waited for the DriverEdge to update and I verified that it now works just as I expected: the tile icon represents a garage door; in the tile itself there are no Power and Energy parameters, and finally I don’t have the error warning “This device has not yet …”. Thank you, you were amazing.
I take this opportunity to offer you a suggestion for a possible further modification to DriverEdge. In my case the NICE IBT4ZWAVE Z-wave accessory is combined with a motor for a garage door, but in reality this accessory can be integrated with different models of NICE motors, both those for garage doors and those for gates or for other automations. In your opinion, is there the possibility of letting the end user choose what the actual use of the device is, therefore which icon to attribute to it? What do you think about it?
Thanks again for meeting my need.
Hi,
smartthings app defines which icons can be used as an option within the same category.
The GarageDoor category, I don’t know what options the app offers, if any.
The MultiFunctionalSensor category has these options, I don’t know if it will work.
1 Like
Hi @Mariano_Colmenarejo
Mariano i am struggling with the Fibaro 441 driver at the moment
Driver date 11-09-23 currently in use
I seem unable to create a smooth on to 100% and off to 0% white or rgb
I have read your instructions, tested by adjusting parameters for mode1 but no matter what i try i seem unable to get a smooth gentle on off transition without a network error or colour device control not switching off and then a second press of on off to finaly switch the colour off
Example white device tile
Switch on = on to 100% very quick
Switch off = physical device off to 0% very quick , device tile shows on with dimmer slider around 17%, another tap of the on off button finaly turns device tile off
Im looking to have a gentle on or off, perhaps with around 1.5 seconds to on and then when off is required 1.5 seconds to off so it appears a gentle state change
Can you advise on the best way to achieve this, the text provided for some of the settings is a little confusing
This confuses me
Hi @fido
This is the Fibro manual
This device has 2 modes for changing the state of the outputs, parameter 8
-
MODE1: Level changes are made in steps and adjusted with parameters 9 and 10.
I believe that the documentation has some error, since the example it gives does not say the value of the total time it took to make the state change.
According to the manual, the number of steps is chosen from 1 to 255 (parameter 9) and multiplied by the time in more than each step from 1 to 60,000 ms (parameter 10).
The example is 5 steps x 10 ms = 50 ms, but I see that it takes about 2 seconds. -
MODE2: It is the one I use and it works best, it is adjusted with parameter 11.
Time for changing from start to end value (0-immediate change, 1-63(20-126ms. [value] x 20ms), 65-127(1-63s. [value-64] x 1sec), 129-191( 10-630s [value-128] x 10sec),193-255(1-63min [value-192] x 1min).
The default value is 67 ( [67 - 64] x 1 sec = 3 sec ).
I recommend using this MODE1, it works well for me
I have changed the wording of parameter 11, so that it is more in line with the fibaro manual
───────────────────────────────────────────────────
Name Z-Wave Bulb Mc
Version 2023-10-09T09:55:14.762174908
───────────────────────────────────────────────────
When you have defined a transition time in the parameters, then the driver adds the default delay (2 sec) to read the states of each channel.
That is, if you define 3 sec, the driver will read the final state of the device 5 sec (3+2) later, the switch icon will spin until it receives the response from the device and therefore it is necessary to be patient when executing new commands taking into account the total delay as network errors may occur
What I have seen is that sometimes the app does not send the preference change and the driver does not send parameter new value to the device, but the app shows the value change.
This can cause a desynchronization between the displayed preference and the parameter value that the device has.
It has been a long time since I have seen this error, just as sometimes the state of the mosaic and the details view are desynchronized and events emitted by the driver are lost, let’s hope they fix it at some time soon
Thank you Mariano, i will take another look at this tonight, something i have found that gives better tile performance is using a virtual switch to change a colour or white
If i create seperate rgbw switches with your driver i have been getting network errors or failure for the tile to switch off even though the device is correctly off
If i use a virtual edge switch to switch off a driver created rgbw tile the rgbw tile performs quickly when on or off is actioned
Will have another play tonight
I’ve been testing this and it works perfectly now.
Keep in mind that the status update will always have a delay of 2 sec + the delay that you set in the parameters, since the device only reports when the RGBW colors are read with SwitchColor:Get(), after the delay of sending the command SwitchColor:Set().
If you want to establish a delay of 2 sec set parameter 8 to value = 1 (MODE2) and parameter 11 to value = 66
This is the last version published
───────────────────────────────────────────────────
Name Z-Wave Bulb Mc
Version 2023-10-09T16:17:08.060347816
───────────────────────────────────────────────────
For me everything works just fine! I tested now. No need to add again the devices. I just modified the setting for the devices that were wired wrong and now they work just fine. Thank you and congratulations for the work you are doing! 
1 Like