Finally tested it, the smartapp just hangs up on “Fetching hub info” and never finishes. It’s possible a device on my network is interfering but I won’t be able to test that out for a while.
I’m having trouble changing the names of the linked shades and scenes. For the shades, if I change the name, I have to click on the icon to change that in order for the “save” to appear. For changing the scene name, I can’t get the “save” to appear. Any ideas?
The config screen for the scenes should be identical to those for the shades, where there is a “Save” action in the top right.
Can you post a screenshot of your scene config screen?
For some reason, it’s now there. Not sure what happened. Thanks.
@johnvey - Thanks for putting this together. I have the following configuration
v2 Hub
5x roller shades
4x Duolights
1 A deux
The Duolights and the A Deux up and down for the front shade (as well as the valence) works great. Are you planning on supporting the blackout shade? Also how about the roller shade?
@amesh you are the first to ask about the Duolights. From the API docs, it would appear relatively straightforward but I don’t have any so I wouldn’t be able to test anything that I did.
For the single silhouette shade, it was already kind of a stretch to fit it into the SmartThings model of on/off (vanes) and brightness (shade). Adding a third control for the blackout shade would most likely happen as an entirely separate device. Would that make sense to your automation setup?
i’m happy to test it. I’m ok with a operate shade type as I’ll be using Core to automate the solution. It will just mean adding another device to the task sequence. the preference would be to keep it together for manual interactions but I understand if that isn’t the case. Let me know how I can help.
Thanks,
Amesh
@johnvey, thanks for the PowerView integration. I am able to control individual shade from ST to Alexa. However, I notice Alexa can not set the % of how high or low the shade will be. It will open and close fully by saying “Turn on and off” with Alexa. However, saying “Set shades to 40%” will have no result. Is there something else I need to do for Alexa to control the % of opening and closing of the shades?
Hi, I thought I’d ask if you had any suggestions to my problem. I’m hoping you use Google Home. For months I had PV Gen 1, I set it up with IFTTT and used Google Home, worked well with the delay. I got the Gen 2 hub a few days ago, setting it up went well, migrated data from Gen 1 hub, in PV app everything works like always. Opened Google Home and all scenes were there, under Powerview category, each scene had “in ******” (room name) added behind it ex: Top Down Den in Den." When I said “Hey Google Top Down Den” it replied “Lowering Den Blind” but nothing happened (always works in PV app), I tried “H. G. Top Down Den in Den” same response but no action.I deleted all my IFTTT reciepes. Even made a new room , put 1 Blind in it, it works in PV app, showed up in Google Home also doesn’t work. Unlinked, relinked PV account, rebooted everything, now G H says " My apologies I don’t understand." Hunterdouglas support was no help. Also I got the Gen 2 because I thought it was Smartthings compatible, is it? FYI, I have 27 ST/ Zwave devices setup working well. Lol, I really miss voice control for my 14 PV blinds. If you can recommend anything I’d greatly appreciate it, if not no worries. Take care.
Not sure why it wouldn’t be working for you, really.
Yes, I have Google Home working to control my blinds with a Gen 2 PV Hub without IFTTT.
But all I had to do was use the updated version of this device, and it worked.
One tip: “Ok Google, Sync my Devices” causes it to re-check-in with smartthings to update the device list.
Might help? Not sure. It did solve a problem for me once…
Hey thanks for the reply. 1 more question; did you upgrade from the Gen 1, or did you go from zero to the Gen 2? I’m thinking about unlinking PV account, factory resetting the Gen 2 hub, kinda starting from scratch. Lol
@samjjp2009 added a fix, tracked here:
Update your device handler from the repo and let me know if that resolves your issue.
The only way I could get it to work is to say “Run” or “Activate” before the Scene name. HEY GOOGLE RUN OPEN BLINDS in DEN." Is that how yours works? After months of using the Gen 1 Hub, and IFTTT and just being able to say OPEN DEN BLINDS (OR OPEN DEN OR DEN OPEN ) I’ll have to get use to it.
I upgraded from 1 to 2.
And yeah, I need to say “activate”.
You can get around that by setting custom routines in the google home app.
Then you can use whatever trigger you want. (With or without “activate”).
@johmvey, it works greats!! Thanks for the hard work.
@johnvey, I notice that all the shades (no matter they are open or close with the ST) will show V. Closed. The way I know it is opened or closed is by looking at the %. It will show 100% (the main screen still show V. Closed) when it is opened and 0% when it is closed, is it the way it supposed to work?
@samjjp2009 yeah that seems like a bug. Could you file that in the Github issue tracker? Honestly, I’m not sure when I can get around to fixing that but at least it’ll be a known issue.
@johnvey I submitted the issue to the tracker. I am just glad I can control each shades individually thru your integration. Thanks again!
Hello,
I recently integrated Hunter Douglas PowerView Hub Gen. 2 to Smartthings Version 2 hub. I got all 3 of my shades to show up, but would like to find out if there is any way to get the primary button on the top to reflect “Shades” instead of “Vanes” please? It seems every action button reflects “vanes” option in the “Things” selection of “My Home” of Smartthings. I apologize if this has been asked before and maybe I missed it in my search. Thanks in advance for any input of suggestion.
@spillins, this is currently hard-coded to treat the vane control as the primary action and can’t be remedied without writing more code.
I believe that the fix would be to write an alternate tile configuration and then assign it as the “main()” tile. One could just write this as a one-off handler, or get fancier and add a configuration option to allow users to select their preferred primary action.