This trigger no longer working - complaining about the operator needing changing

[tamorgen]

Good morning all,
I"m working on converting my luup Reactor scenes over to MSR, so I can eventually introduce an Ezlo plus into the mix and not loose all the work I've done with Reactor. If nothing else, this should free up some resources on my aging Vera Plus, and maybe speed up some functions. Maybe that's just wishful thinking.

In any case, I'm moving move my first Reactor set, which is a set of rules to control the blilnds/window coverings in my home. I have two types of blinds:

iBlinds retrofit motors (IB2.1-ZWx) version from late 2019.
Bali roman shades with factory installed Somfy CSZ1 Z-wave motors.

I'm setting up reactions for both types of window coverings. One of the problems I always had in Vera was with iBlinds, I had to do it by luup commands:

luup.call_action("urn:upnp-org:serviceId:Dimming1","SetLoadLevelTarget",{ newLoadlevelTarget="50" },316)

The reason for this, is that the open position was 100%, and the close position was 0%. In other words, the blinds were closed one way 100% an closed 100% the other way. I've been informed by iBlinds support that even in Ezlo, they still do it this way, which is different than most other Z-wave controller manufacturers. I'm not sure how the others do it, but some how "open" is right in the middle (50%).

So, in MSR, i can still set the Dimming1.SetLoadLevelTarget to 50, but I also noticed some other commands I haven't seen before in Reactor

Is there some way in MSR to set that middle value to 50% so I can use cover.open? The command cover.close works as expected, so I'm wondering how I might use that cover.set.

Thanks for any advise.

[toggledbits]

cover.set works the same as dimming.set — 0.0 to 1.0 for position.

[tamorgen]

@toggledbits said in MSR Reaction question:

cover.set works the same as dimming.set — 0.0 to 1.0 for position.

Okay, thanks. Wishfull thinking I guess

[gwp1]

@tamorgen if you need any help with iblinds and MSR let me know. I'm running five of them and have been for several months. Happy to fill you in on the ups and downs.

[tamorgen]

@gwp1 Thanks, are you doing it any different than setting the load level, like I am? It works, but it's ugly. I'm not sure why Vera chose to do it this way. iBlinds support has basically thrown Vera under the bus for the way they integrate it.

[toggledbits]

@gwp1 said in MSR Reaction question:

Happy to fill you in on the ups and downs.

I see what you did there.

[toggledbits]

@tamorgen I'm pretty tied up this morning, but later today I will send you a link to upload logs. I'd like to see your vera-status-initial.json and vera-user_data-initial.json files (logs directory). I can probably work around the Vera iBlinds wierdness and get them working the right way with the Reactor capabilities named (as a per-device/manufacturer exception).

Also, can you please improve the title of this post -- perhaps add " -- iBlinds support on Vera" or something like that. The title right now is too generic to be useful in future searches (and therefore doesn't meet the posting guidelines).

[tamorgen]

@toggledbits Thanks Patrick. I'll edit the post title.

[toggledbits]

Just to close the loop, per the release notes for 22257, a device exception was created for IBlinds 2.0, and @tamorgen confirmed via PM that it's working as expected.