Just came across this topic and sort of new to this subject but it appears to solve the issue I have with missing the double click functionality on the dimmer 2.
I just installed the edge driver(s) and looking at the driver section (after excluding and including) I am on 2022-03-20.
Now, I see some ‘normal’ things like the dimming slider etc but also new ‘button 1’ and ‘button 2’, both stating ‘standy’.
I tried making a routine that is triggered by a double click but none of the options on both buttons seem te react.
Is this still non functional or am I missing something?
I don’t have dimmer2, maybe someone who has it in use could help you more, but basically as it is said in the different previous posts you have to do this:
For dimmer2 send scenes to buttons 1 and 2 you have to put in settings, parameter 28, Scene Activation → activated.
Button 1 receives the scene value sent by S1
Button 2 receives the scene value sent by S2
The actions shown by the buttons are those corresponding to the documentation table, according to the type of switch chosen with parameter 20.
The double click on S1 can be assigned to the action set level100% regardless of whether they send scenes or not. It is in parameter 23 of the preferences settings
Double click option - set the brightness level to MAX
Available settings:
0 - double click disabled
1 - double click enabled
Default setting: 1 Parameter size: 1 [byte]
Thanks for the response @Mariano_Colmenarejo. Turned out I had to use the scene activation indeed. Sorry for not understanding this reading through this topic at first. Another thing what was confusing is that the ‘button 1’ has multiple options for double click; ‘2 times pressed’ and ‘two time pressed’ of which, as it turned out, I needed to use the latter in order to get this to work.
I have published these versions of the drivers for Fibaro devices
Corrects an error that prevents correctly sending the values of the configuration parameters and preferences in unsigned values and that the default libraries interpret as signed.
Error affects these Fibaro devices:
Relay Switch FGS-212
Double Relay Switch FGS-222
Roller Shutter 2 (FGR-222)
Wall Plug – type E/F (FGWPE-102 | FGWPF-102) ProductType: 0600
The value will be sent with 2’s complement, with the correct size in bytes if the value of the parameter exceeds the maximum of the positive range of the parameter size in bytes.
The update will be done automatically in the next 12 hours
┌─────────────┬──────────────────────────────────────┐
│ Name │ Z-Wave Switch Mc │
│ Version │ 2022-04-26T16:54:29.919361 │
└─────────────┴──────────────────────────────────────┘
┌─────────────┬──────────────────────────────────────┐
│ Name │ Z-Wave Window Treatment Mc │
│ Version │ 2022-04-26T16:59:20.212615 │
└─────────────┴──────────────────────────────────────┘
┌─────────────┬──────────────────────────────────────┐
│ Name │ Z-Wave Bulb Mc │
│ Version │ 2022-04-26T17:17:23.54357 │
└─────────────┴──────────────────────────────────────┘
Hello.
My 2 blinds, using your Driver → Z-Wave Window Treatment Mc, are still using the version “2022-03-11T17:04:56.869848”.
And the strangest thing is, if I open your driver’s page, none of them have the “Uninstall” button… Only “Install”. Even though I have the driver installed, with the above mentioned version…
Should I press the install button for the “Z-Wave Window Treatment Mc”, to get the new version ??
Hi,
Can you please also add the FGRGBW-442 to your drivers. It is similar to 441 but probably different registers. If finger print is needed I can easily find and send
To include this device I have to make a new profile, the configuration parameters are totally different.
Surely it need a subdriver separate from the RGBW441, since it will surely use some different command class and I don’t have a device to do the debugging either.
I don’t know if there is DTH for this model?
On the other hand, it’s not that I have much motivation to do anything with the devices that are currently in Fibaro production, I did it mostly for devices that are no longer for sale and were going to become obsolete.
In my opinion, Fibaro is currently not doing the minimum that can be expected by users of fibaro products in smartthings, the stock controllers are with the minimum configurations and do not add anything new, as popular as smart Implant, RGBW442, FGR223, FGS224 … So if there are alternatives on the market to use in smartThings, we should buy those other products and not expect someone to do their job for them and continue selling us their products!
For you I would be delighted, but for Fibaro, whom I have not seen in the last 2 years help anyone to solve any problem raised in the forum, it annoys me a lot.
When I finish other things that I am doing and if you are willing to debug it by sending logs I will let you know
I totaly agree with what you wrote regarding Fibaro. In the past there where no ZigBee alternatives for shutter , light , dimmer and RGBW controllers modules. Today , as you wrote, there are many alternative in ZWAVE and Zigbee. I’m not going to buy anymore from Fibaro,
Yes, there is a DTH @jahrin just tested it and it works well
In the past, some people have used the DTH for the Zooz zen31 RGBW controller. Different company, somewhat different features, but it handled basic functionality OK. I believe @Diegocampy is one of the people who used this DTH for the Fibaro 442.
@krlaframboise , the author of the groovy DTH for the zen31 has said he will probably eventually get around to doing an Edge Driver for it, but it’s near the bottom of his priority list because he has a lot of other Zooz models to work on first. And it’s unclear if that eventual Edge driver for the zen31 will still work for the Fibaro 442.
As you know, you and I have agreed to disagree as to whether Fibaro should be blamed for not providing SmartThings-specific code for their zwave-certified devices. (Particularly since the devices work fine with other zwave certified hubs.)
But we both definitely agree that there are other brands of modules that work much better with SmartThings, and other manufacturers that have put much more effort into getting their devices to integrate with the SmartThings architecture.
On the basis that I think they are good devices, they work well with smartthings and when I think that it is Fibaro’s responsibility I am referring to this:
In several DTH’s and fibaro device stock drivers, which smartthings have migrated to edge, DTH they were and edge have been left with insufficient parameters configurable by users in preferences.
I think smartthings will have migrated to edge what Fibaro certified and paid to advertise “works with smartthings” in groovy DTHs.
I think this is fibaro’s responsibility since the certification was made with no 100% parameters for full use of its features. Putting 100% of the configuration parameters is just as difficult as putting 50% and Fibaro always preferred to put the minimum and leave the complete configuration with Fibaro Hubs.
For example dimmer2 does not even have settings for scene, double click for 100% level, reports intervals of power and energy, only ON-OFF for non-dimmable bulbs… and many other parameters.
I understand that there may be some function that only works in Fibaro HUbs, such as firmware update, but it is not the case of most parameters that determine how you will be able to use what you have paid for.
Why if you pay €50 or €60 for a very good device at the same price to use it with fibaro Hub and they tell you that it works with smartthings and when you install it you see that they offer you much less functionality, being able to give almost the same as other manufacturers do? ?
You remember well, but the level of my satisfaction was so low that I made the fibaro and not buy any more. With the rgbw led strips I replaced everything with hue, and for other devices only zigbee. Unfortunately this DH did not work well and I could not take advantage of the device as I wanted, the hated and abandoned.
Leaving aside the other Fibaro Devices for now, they do not say that the RGBW controllers work with smartthings. First or second generation. So at the very least, I think we have to assume that any edge driver would have to come from the community here.
I totally agree with you that in this case of RGBW Controller.
Fibaro don’t say it works with smartthings, but they will take advantage of any driver made in the community that works to continue selling more and more devices with the efforts of others in the community.
I’m not interested, I think fortunately, I’m in another stage of my life, but I’m sure there are developers in the community who would make the driver in a couple of hours if they put in a bit of their part and everyone would benefit.
If Fibaro don’t want to spend money on certifying it, don’t do it, but collaborate a little with the community like other manufacturers do and they will surely multiply what they invest, it’s a forum with many users and activity all over the world.
I don’t know if I’m talking nonsense, but I see a lot of work done by community developers for manufacturers who want to collaborate and take advantage of this great showcase.
Looking at the two manuals, it should work fine with that DTH.
Indeed the DTH does not have energyMeter.
In fact it looks like the same device with two different manufacturers,
With identical parameters and configuration values
The two are the productType: 0902
The zooz-zen31 is model (producId) 2000 (USA) and the Fibaro is model (productId) 1000(EU)
Thanks, I try it after our victory. Best regards!
