Any chance that this could also include support for their layered shades?
What I'm missing is the ability to send the "Home" button press on the remote which splits the layered shades. I can't seem to set any level or position that can split the shades the same way the "Home" button on the remote can. Setting Level 1 doesnt open the shade enough, setting level 2 opens the shade too much.
If I set the shades up as dimmers and then set the dimmer switch "on", as long as the shades were fully closed to start, the shades will split the proper way. Whatever command is sent by dimmer on seems to mimic the home button on the physical remote
I have two of their layered shades myself. I agree, setting a level 1 or 2 is not the same as the HOME button but it's as close as I can get it.
There is no function that I've found in the library to programmatically call that position. I would love to be able to add that to the driver.
I did try sending the open command (0xFF) but that didn't send the shades to home, it fully opened them, just as the 100% (0x64) command does.
I'll keep doing some research in to the available commands. If anyone here knows what command to call to have the Somfy motors move to home I'd love to hear it.
Just wanted to say thanks for the driver. The standard Z Wave one would not stop the shades unless I used Set Position -1. Which was good until I realized that the Advanced Button Controller would not support negative numbers. So anyway ended up adding the stop command for shades on the Advanced Button controller (Child) for the Somfy held event on the remote. So full parity (and more) with what came out of the box with the ZebraBlind shades.
Great to hear, thanks! Glad I could put something together that helps.
So chatting with the dev of ABC and he has suggested that it would be good to implement the stopPositionChange() method as indicated in this thread. Advanced Button Controller (ABC) - #340 by stephack
If you are open to doing that and posting it I am happy to test both ABC and the updated driver.
Essentially would need this in your driver, so not to break any other uses of stop();
def stopPositionChange() {
logDebug "StopO=PositionCHnage command issued."
stop()
}
I added the stopPositionChange() per your request.
Thanks for that, loaded that up and on its own no issues. I also dont expect any issues from ABC as well. Thanks for supporting this change request
I have a total of 6 blinds using the roller shade driver now. On my dash board 3 of the shade tiles stay lit yellow when the shade reports closed, and 3 go back to being gray when the shade reports closed. All shades are reporting level 0 and position 0 in their individual device page. Any idea what would cause this behavior? Thanks!
Can you send a copy of the logs for one that stays yellow and one that goes back to gray as well as a screenshot of the settings for each?
Hi. Hope I'm providing the correct log:
Shade that stays yellow no matter the position:
Shade setting screen shot
I just realized that with the Springs Window Driver that all the icons stay the color they are regardless of the shade position. The ones that are gray stay gray if they are closed, open, partially open and the ones that are yellow, stay yellow if they are closed, open, partially open. I think it depends on their state when I switched from Generic Driver to Spring Window driver, if they were yellow when switched they stay yellow etc...
Log from a shade I reverted to Generic Driver where the icon color behaves correctly:
Settings from shade:
Thanks. Which template are you using for the tile in the dashboard?
I don't use the dashboards as much as I use WebCoRE. The tiles I see in my dashboard do show the proper state name (as it changes) and the sliders work fine. Mine don't change color though.
It's all grey all the time.
I'll try and duplicate what you're seeing.
Im using the shade template.
The state changes fine, the icon changes fine, however the tile color is always stuck, unlike the generic driver which is dynamic. Thank you for looking into this.
Fixed! 
Well, not really a fix so much as a change to accommodate how the dashboards work. It took a little reverse engineering to figure out what triggered the background color change.
I still don't quite understand why the two drivers behaved differently in the dashboard, considering they both use the same "shade" tile template. The sheer tiles stayed gray all the time and the roller shade tiles remained yellow all the time. 
In any case, both drivers have been updated along with the HPM manifest, so you can just pull the update via HPM at it will update both drivers.
The tiles will be gray when closed and yellow for the other states (open, sheer, partial open). Now that the tiles will change color based on state, you can change the colors to whatever you'd like.
I had partial success. I updated the driver and installed it.
LR1 was partially open and it was still gray. I closed the shade and reopened to partial open and it was yellow. Success!
LR2 was partially open and it was still gray. I closed the shade and reopened to partial open and it stayed gray. Fail
Here are the logs showing both a close and partial open for LR1 and LR2 along with the settings of each device.
I also rebooted the hub to see if that had any effect and it didnt.
Thanks
Adding on to my previous post...
I watched 3 of my shades (not the ones mentioned above) go to full close, report close, then I opened them completely, and all 3 reported open and turned yellow. I exited the dashboard and came back and only two were still yellow even though all 3 were reporting open. Strange
Not sure there's anything else I can do here. The issue is in the dashboard, not the driver.
The roller shade driver is setting the switch value to off when the level is set at zero. Any other level sets the switch value to on. When the value is on, the tile is yellow. When the value is off, the tile should be gray.
I have seen the shade position move to a specific value (position 1) and can see the shade move, but then the hub reports back that it's in position 0 (closed).
If anyone here can shed some additional light on the dashboard templates, I'm happy to dig deeper but at this point, I'm at a loss as to why the dashboard tile changes colors simply be leaving and returning.
This driver worked well for for my ZebraBlinds Graber Z-wave Roller Shades for six months and then last week the shades stopped responding. I thought it might be related to the 2.2.8 update, but if no one else is having issues it must be something else.
I've not seen any change since updated to 2.2.8 (2.2.8.133 through 2.2.8.152). No changes to the driver and it's still working the same.
New HE user here, working on setting up my Bali (Spring Window Fashions) motorized roller shades. I have one shade setup as a device along with its remote. I'm trying to add it to my Google Home to control with voice--the Generic Z-Wave drivers associate the device as a light and I'm unable to separate the actual Lutron light switch with the Bali shade.
The SWF Driver is fantastic--first, let me thank you for your work on the driver! I can add it to a HE Dashboard and the device works correctly. However when I use the driver with the Bali device and try to add that to GH, the device is not found by GH. Is this a known behavior, or should the SWF Driver allow addition to GH for voice control?
