Somfy ZWave Blinds (Dimmer)

[DeveloperDavidB]

@EdwardN

Could you edit your post with the error codes, select it all and press the </> button?

Thanks for the suggestion. Fixed.

[mike.maxwell]

@DeveloperDavidB

These blinds are battery powered. I wonder if the battery reporting is causing error.

that wouldn't do it as any battery report will be ignored, but in any event given the above I should be able to find the null issue.

[bravenel]

@DeveloperDavidB

Another thought. With them showing up as dimmers, it gives us the option to use apps like simple lighting to control the blinds. I think I would prefer both options, and don’t mind the blinds showing up in list’s of dimmers and switches.

@mike.maxwell

yeah, it will break any ported apps where users aren’t aware of the driver requirements…

I think for now I’ll leave well enough alone and leave them in there.

It seems to me that a good compromise is to leave capability "switchLevel" in the drivers for shades, and add to them capability "windowShade". The upside of this is that apps that treat shades as dimmers will still work, while apps that offer open/close will also work. The downside is that shades will show up in selectors for dimmers, although not vice versa. Personally, that doesn't bother me as I always give devices a meaningful name, and I won't mistake "Dining Room Shade" for "Dining Room Lights".

We can extend RM to include operating shades as an action, using the windowShade capability. But, if you already had rules setup that used dimmers, they would still work as well.

[EdwardN]

I think the biggest reason for people wanting shade control is not having to stupidly say “Alexa, turn off my bedroom shades” and spoiling the mood by having to explain why a smart house can’t figure out the difference between a switch and a window covering. XD

[ogiewon]

You can use an Alexa Routine today to incorporate more natural language into your voice commands. For example, create an Alexa Routine named “Open Bedroom Shades” and another called “Close Bedroom Shades”. Within the routines, simply turn on or off the correct set of devices. To activate, simply say “Alexa, Open Bedroom Shades” and your done. We use a “Good Morning” and a “Good Night” routine which are very natural to say. These routines then help to sequence multiple lights (via Alexa to Hubitat integration) and Logitech Harmony Activities (via Alexa to Harmony integration), and also provides a quick weather report as well.

I agree that ideally it would be nice to simply say “Alexa, open the bedroom shades” without the extra layer of complexity/configuration. However, it was very nice during my transition from ST to Hubitat to be able to simply tweak a few Alexa Routines as I moved devices over and the family was non the wiser that anything had changed in the house (except, that it works quickly and reliably now with Hubitat’s local processing! )

[EdwardN]

Yes yes, I’m aware of the workarounds. I meant it as a joke. “When technology is a impediment to bedtimefuntime”

[mike.maxwell]

@DeveloperDavidB, a driver using your provided fingerprint is available in build 1.0.5.707.
Generic zwave shade.
Give it a spin and let me know how it works!

[JDogg016]

It works which is nice BUT because you have attributes for open/close on/off I only see the ability to use this as a dimmer in Homekit. The device is listed as Generic zwave shade, but can only be seen as a dimmer.

Consequently “turn off the lights in my bedroom” closes the curtains.

PS - same with Alexa.

[mike.maxwell]

@JDogg016

It works which is nice BUT because you have attributes for open/close on/off I only see the ability to use this as a dimmer in Homekit. The device is listed as Generic zwave shade, but can only be seen as a dimmer.

I don't think that has anything to do with us, that sounds like a Homekit limitation, same with Echo currently...

[DeveloperDavidB]

@mike.maxwell Hi Mike. My blinds are not responding at all to this new Device handler. Not when using the new Open or Close, and not when using On or Off. For now I have switched back to the default dimmer. Here are the logs that were produced.

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 14:58:59.390:errorFor input string: "" on line null

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 14:58:59.365:infoLiving Room Left Shade is closing

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 14:58:57.389:errorFor input string: "" on line null

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 14:58:57.366:infoLiving Room Left Shade is opening

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 14:58:53.977:errorFor input string: "" on line null

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 14:58:53.954:infoLiving Room Left Shade is opening

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 14:58:44.751:errorFor input string: "" on line null

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 14:58:44.689:infoLiving Room Left Shade is closing

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 14:58:07.654:warndescription logging is: true

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 14:58:07.652:warndebug logging is: true

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 14:58:07.642:infoupdated...

[mike.maxwell]

interesting, well all I had to test with was a dimmer…
Did you remember if you saved any preference settings in the driver before testing it?
If you didn’t, could you load the driver again, then hit the save button for preferences, then try it?
If you did that, cant get much from those logs.

[DeveloperDavidB]

I saved the Maximum travel time to the default 30 Sec. Hit Configure, then refresh, then tried open, close, and set level. All no go. Here are some fresh logs that start with Configure then refresh

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:50.941:infoLiving Room Left Shade battery level is 100%

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:50.939:debugBatteryReport: BatteryReport(batteryLevel:100)

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:50.937:debugparse description: zw device: 34, command: 8003, payload: 64 34 04 FF FF FF A9 00 00 1A 95 FF FF FF A8 00 00 0D 1F AA 63 00 00 00

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:50.826:infoLiving Room Left Shade is open

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:50.825:debugshadeEvents value: 99

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:50.823:debugBasicReport value: 99

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:50.821:debugparse description: zw device: 34, command: 2003, payload: 63

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:49.976:debugrefresh

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:45.000:errorFor input string: "" on line null

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:44.973:infoLiving Room Left Shade is opening

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:42.459:errorFor input string: "" on line null

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:42.437:infoLiving Room Left Shade is closing

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:39.716:errorFor input string: "" on line null

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:39.693:infoLiving Room Left Shade is opening

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:32.893:errorFor input string: "" on line null

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:32.867:infoLiving Room Left Shade is closing

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:20.282:infoLiving Room Left Shade battery level is 100%

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:20.280:debugBatteryReport: BatteryReport(batteryLevel:100)

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:20.270:debugparse description: zw device: 34, command: 8003, payload: 64 34 04 FF FF FF A9 00 00 1A 95 FF FF FF A8 00 00 0D 1F AA 63 00 00 00

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:20.178:infoLiving Room Left Shade is open

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:20.177:debugshadeEvents value: 99

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:20.172:debugBasicReport value: 99

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:20.166:debugparse description: zw device: 34, command: 2003, payload: 63

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:19.357:debugrefresh

[dev:92](http://192.168.1.38/logs#dev92)2018-04-10 15:16:19.328:warnconfigure...

[mike.maxwell]

this doesn’t look like your normal programming error, this looks more like a really stupid one…
I’ll have a look at it before the next build goes out.

[DeveloperDavidB]

@mike.maxwell

I’ll have a look at it before the next build goes out.

Thanks man!

[DeveloperDavidB]

Incase anyone is interested in Blinds, here is a link to the exact ZWave blind product we are talking about.

ZWave Blinds

[JDogg016]

I take it back. Mine do not work either reverted back to z wave dimmer

[mike.maxwell]

@JDogg016

Mine do not work either

The main reason I don't like building drivers for a device class I don't have, all my shades are Serena.

[DeveloperDavidB]

@mike.maxwell

The main reason I don’t like building drivers for a device class I don’t have, all my shades are Serena.

No problem Mike. I don't mind being patient with stuff like this. If it would help we could always do a GoToMeeting or similar if you would be interested. I also wouldn't mind testing if it would be helpful.

[JDogg016]

Then why don’t you publish the driver code and let the developers develope and test it.

Just release the z wave dimmer!

[JDogg016]

This is not true. This worked perfectly fine with ST.