Fibaro Roller Shutter

[dantoine]

Hello, I have installed in my house 12 Fibaro Roller Shutter 2 (FGRM-222). Unfortunately, one of the devices does not seem to work correctly now. I can move the roller shutter up, down and also to any position, but the roller shutter no longer reports its current status to ZWay. However, the controller is listed correctly in the associations. Since all my attempts have brought nothing, I have now bought a new Roller Shutter 3 (FGRM-223). This one works and also reports its current status.

With the previous Roller Shutter I had programmed an association for the long hold of the S1 and S2 buttons, so that I could lower or raise all blinds in the house with one switch. Unfortunately, this no longer seems to work in Roller Shutter 3. In the description I found something about scenes (parameters 40 and 41). Here the Roller Shutter 3 should send a scene ID 1 for S1 and a scene ID2 for S2. Unfortunately, I do not know how I can process these scenes in ZWay, so that all roller blinds go up or down.

Can someone help me with this problem?

[seattleneil]

I do something similar (for a Zooz ZEN32 scene controller) that sends scene messages to Z-Way. Here's a high-level description of the approach:

1. Press scene buttons on the ZEN32 device and view the Z-Way log file (/var/log/z-way-serrver.log on a Raspberry Pi) to determine the various scene values being sent from the ZEN32 device to Z-Way
2. Use the Smarthome UI to add the EasyScripting app
3. Create an EasyScripting script that is triggered on scene messages for the ZEN32 device
4. Write JavaScript code to parse the scene ID and execute various Z-Way commands

For my ZEN32 device with Z-Wave device ID=24 controlling various lights, here's my EasyScripting JavaScript:

Code: Select all

### ZWayVDev_zway_24-0-91-DS // Zooz Control (24)

var scene = vdev("ZWayVDev_zway_24-0-91-DS").value();
console.log("In Zooz Control for ZEN32 Loft Controller Switch (24) - scene:", scene);

if (scene == "10") {
 if (vdev("ZWayVDev_zway_42-0-38").value() == "0") {
   vdev("ZWayVDev_zway_42-0-38").on();
  } else {
   vdev("ZWayVDev_zway_42-0-38").off();
  }
} else if (scene == "20") {
 if (vdev("ZWayVDev_zway_41-0-38").value() == "0") {
   vdev("ZWayVDev_zway_41-0-38").on();
  } else {
   vdev("ZWayVDev_zway_41-0-38").off();
  }
} else if (scene == "30") {
 if (vdev("ZWayVDev_zway_17-0-37").value() === "on") {
   vdev("ZWayVDev_zway_17-0-37").off();
   vdev("ZWayVDev_zway_10-0-37").off();
   vdev("ZWayVDev_zway_12-0-37").off();
  } else {
   vdev("ZWayVDev_zway_17-0-37").on();
   vdev("ZWayVDev_zway_10-0-37").on();
   vdev("ZWayVDev_zway_12-0-37").on();
  }
}

To control your roller shutters, you will need to determine the scene values and specify the Z-Way commands for controllings the shutters (e.g., replace the .on() and .off() with .up() and .down() or use other commands such as upMax(), increase(), decrease(), startUp(), startDown(), stop() and set(XX) (where XX is a specific level)). Note that the ZEN32 emits the same scene value when the same button is pressed (which makes sense - this is perfectly reasonable), but I wrote the script treat a button press as a toggle (i.e., press the button once: lights turn on if they were off, and vice-versa). If you want to force shades with device IDs 51 and 52 to move to position 50 when scene 10 is sent and position 75 when scene 20 is sent, I think the JavaScript code would include something like the following:

if (scene == "10") {
vdev("ZWayVDev_zway_51-0-38").set(50);
vdev("ZWayVDev_zway_52-0-38").set(50);
} else if (scene == "20") {
vdev("ZWayVDev_zway_51-0-38").set(75);
vdev("ZWayVDev_zway_52-0-38").set(75);
}

Good luck.

[dantoine]

Thank you very much for your answer. I am now also evaluating the scenes. But I did not work with EasyScripting, but with the if-then module from Zway. With a double click I can now raise or lower all blinds again.

The solution via associations I find in principle but still better, because here also times the controller can fail and still all blinds can be controlled. Too bad that Fibaro has removed this feature.