Shelly Plus 2PM (Wifi) or Shelly Qubino Wave Shutter (Z-wave) for roller shutters?

Hello,

I would like to buy about 10 switches for roller shutters. Which one would you recommend, Shelly Plus 2PM (Wifi) or Shelly Qubino Wave Shutter (Z-wave)? Which one would be more stable? If Z-wave, which Z-wave stick would you recommend to control them? Thanks

It’s not one of your options but I am running 6 of these which have been great, no issues at all. They are Z-Wave and I use a now pretty old Aeotec Z-Stick 5 which has been great. Now you would get a 7.

1 Like

I have 6 Shelly’s 2.5PM (wifi), FW is changed to ESPHome and they all work flawlessly from the beginning.
Whatever you buy it’s a good idea to have power measurement, since with that you can monitor real state of cover - whether it’s moving or not, if it’s stuck, you know when it reached endpoint… without PM you can only guess all these states…

1 Like

I know that Wave module from Shelly does support tilt for venetian blinds (so does fibaro). AFAIK shelly 2pm (wifi) does not support it out of the box. I have seen Tasmota FW can do it, but it is not as straightforward as one would think. So if you have venetian blinds, I would go for shelly wave. I use aeotec z-stick and Zwave JS UI - works without issues

1 Like

Thank you for answers. So I will order Z-wave Shellys.

One thing to know - i have recently installed shelly wave 2pm and noticed unpleasant delay when relay is operated by physical switch. Turns out it is a feature and it is common for wave shutter as well.

You can update firmware on relay if you want to resolve it.

Hi,
can anyone share the full list of parameters used (for Venetian). I have just started with them and documentation is not so much fun.

Shelly Knowledge Base | Shelly Qubino Wave devices shows less than Z-Wave JS Config DB Browser - 0x0082 which even not complete.
Moreover, the Shutter is not listed in Z-Wave Product Catalog - Search for shelly

How do you do this once your shelly are enrolled into Zwave JS UI?

You can do that directly from device. It happened to me on all that after few moments, it throws error. But if you look into Zwave JS UI, update is still progressing

If you’re going with Z-wave, I would recommend Fibaro over Qubino. They’re way more reliable and easy to work with.
If you’re going with WiFi, Shelly is definitely the way to go (but no venetian blind support)

1 Like

I was asking for firmware update

You download that from their website and update via device options. Ehat else do you need to know?

I bought a couple Wave Shutters and have them deployed.
I went with them because a needed a bunch of them for every window in my house and wanted the lower idle power consumption of the Z-Wave version vs. normal Shellys on wifi. Sadly I don’t own good enough test equipment to figure out the real world power draw of them.

I went ahead and adopted them to HA with the included QR-Codes which worked just fine. But then I had the issues that some parameter changes did’t work correctly (flipping outputs/inputs for up/down). So I wen’t ahead and updated them with the latest firmware. I’m running version 12.23 currently.

Here are my current pro’s and cons:

Pros:

  • Basic functionality works, physical switch input controls shutters just fine
  • Control via Home Assistant works (manual up/down) and percentage
  • Shelly 1st level support is decent and is is providing good support
  • Config options are decently labeled in Z-Wave UI and Home Assistant
  • Z-Wave Associations are possible, you can send the inputs from one wave shutter to another one and control two blinds with one switch without having a controller running (needs Z-Wave JS UI Addon, not supported by built in Home Assistant Z-Wave stack currently)

Cons:

  • Inputs are currently tied to outputs. If you push SW1/SW2 the blind always moves
  • Inputs are not reflected into Z-Wave network, Home Assistant doesn’t know you pressed the down/up button, it only knows you moved the blind after you stop it or it reaches the top/bottom
  • Position/status only updates when the blind has reached the set position, there is no state which updates the current position etc.
  • The input delay that has been fixed for the other Shelly Wave products is still present here, support told me it’s going to be fixed in a future update
  • Associations don’t work correctly if you set the input switch type to Momentary switch, if you choose follow switch it works. Not a big deal, because the other behavior is identical
  • It’s not possible to select macros like double tap to close/open on the physical switch
  • It’s not trivially possible to manually adjust the position percentage (other than by changing time parameters maybe). For me 50% closed is not in the middle of of the window.

I am in contact with them over email and hope they can improve the firmware a little.

@Tschuuuls i will track your progress here we share the same shoes. 14 windows…

@Tschuuuls do you made any progress? how you performed the calibration?

Following this as well.
I had my mind set on going Z-wave and Shelly, but this makes me doubt.
While I’m at it, might ask the question.
Does this thing have built in safeguards?
I assume you connect them to pushbuttons instead of flip switches?
What happens when you push both? doe the Shelly allow it and it blows up your motor? Or does it know to only keep one signal active.
I assume you’ll NEED HA if you wan’t it to go up/down with a single pushbutton (instead of 1 for up and 1 for down)?
Thanks

Are you aware that they are waiting for a fix in Silicos Lab’s SDK before releasing any updates?
See https://community.shelly.cloud/topic/2093-comparison-to-similar-products-will-there-be-similar-features/#findComment-26211