Is there any news about this?
Not testing it forces me to update any changes in two different drivers, with the risk of errors that this may produce in one of them.
Is there any news about this?
Not testing it forces me to update any changes in two different drivers, with the risk of errors that this may produce in one of them.
Sorry @Mariano_Colmenarejo, my friend @dubi_dekel, still didnβt receive his modules. Can you please us 2 more weeks, hopefully, the modules will be receivedβ¦
Hello
Lately the shutter opening percentages (FIBARO FGR-223) no longer work correctly The driver version is: 2024-09-19T16:05:26.710412525 what can I do? (NB I donβt have physical keys connected to the fibaro but only voice command) @Mariano_Colmenarejo
Grazie!
Hi,
What exactly do you mean by they no longer work properly?
The driver has not changed for the FGR-223 for a long time
@Mariano_Colmenarejo For example, for a few months now, the old shutter opening percentages have been different, for example 80% corresponds to 30%, while opening and closing are ok. This is on all 5 roller shutters.
I wanted to try to recalibrate but not having physical keys but only voice command with Alexa Iβm not capable!
Thanks again
Your shutter is probably not properly calibrated. No need to change the driver. In ST app go into settings and initiate calibration. Your shutter should automatically move up and down. When the calibration process is done the percentage commands should work
Thank you! I did it this way and now it works. I had to keep switching the flag from βstart calibrationβ to βcalibration not startβ several times, but eventually it started and now it works.
Hi Mariano, first of all I wanted to thank you for your work, Iβm using many of your drivers and Iβm very satisfied with how they work.
Iβm using your fantastic driver to control the roller shutters with Vimar actuator.
It works very well, only that I have difficulty correctly setting the percentage levels of opening of the roller shutters.
For example if I set opening to 50% it doesnβt open at half but much lessβ¦
Is it possible to add an offset to the percentage given by the driver to correct the measurement?
Hi,
This solution is not possible.
It seems to be a calibration problem of the device and I donβt know how to calibrate it.
The driver only shows the % that the device sends to the hub.
Iβm also using @Mariano_Colmenarejo driverβs and find that around 73% is half window opening. Iβm fine with thatβ¦
Hi @Mariano_Colmenarejo - hope this is the right place to post, itβs the only topic I could find that mentions βZ-Wave Switch and Child Mcβ plus βSecure SSR302β.
I have just replaced my Secure SSR302 and have found that the productId has changed and it is not supported by your driver.
Would you be able to add the following fingerprint to the βZ-Wave Switch and Child Mcβ driver, please:
Manufacturer: 0x0059
Product Type: 0x0003
Product ID: 0x0006
The previous productId was 0x0002.
Many thanks for all your work on Smartthings drivers.
Hi,
Added to this driver version
I wish you a Merry Christmas
βββββββββββββββββββββββββββββββββββββββββββββββββββ
Name Z-Wave Switch and Child Mc
Version 2024-12-24T15:31:49.670533464
βββββββββββββββββββββββββββββββββββββββββββββββββββ
- id: 0059/0003/0006
deviceLabel: Double Switch SSR302
manufacturerId: 0x0059
productType: 0x0003
productId: 0x0006
deviceProfileName: dual-switch
Hi,
Fantastic! Thank you so much for the very quick response.
A Merry Christmas to you too and best wishes for the New Year.
Thank you Very much for creating this driver Mariano. I am using this driver with a Fibaro RGBW 2 (442) and after some playing around it is mostly working as I expected.
2 questions though I am hoping someone can assist with.
Thank you very much for your response.
Iβm also using this device with this driver. Regarding:
Thank you for the helpful response. When creating the virtual switch, will it also allow me to set the color for all 3 at once or is it only on/off functionality?
Whatever you decide to do when the virtual switch will be triggered will happen. On/off, dimmed, color and even build in sequence.
If you need you can create more virtual switches for more actions.
Hi,
I think it may be related to the transition times, parameters 151 and 152 in preferences
The driver reads the status some second after sending the off value (level value= 0 for all channels) and if the device has not yet finished making the transition, then the status read will not be Off.
Try testing with parameter 152 at a value of 0 sec and if it works well I will try to find a solution
Thank you very much for the information.
Setting parameter 152=0 seems to have no impact on the behavior.
Clicking the main power button in the app still turns off the light but does not change the status to off. It does show 0W power draw and it does change the RGB and White power switches to off, but leaves the Main switch in On status.
Clicking it again will immediately make it display as Off as expected.
One other issue Iβve noticed, when turning the LED strip off/on via the Main power button, it will always turn BOTH the RGB and White buttons on, even if only 1 was on when it was turned off. Can this be changed?
Thanks again.