Hunter Douglas PowerView Gen 3 integration

Third party integrations
42

Perfect!! Many thanks @gotdibbs !

43

Hi! Am I correct from this thread that some of you are already working on updating the Powerview integration to work with the Gen 3 hubs? I recently got them installed at my home and I can adjust the blinds using the REST API, so that all works, just not through the integration right now (The integration actually won’t even connect to the hub?)

44

For HA I think that probably the answer is no, not yet. I believe that potential developers are quite busy…

By contrast I am almost finished in updating the OpenHAB binding to support Generation 3 hubs. So the good news is that HA developers will have an easier task because they can ‘steal the OH code with pride’ :wink:

45

Happy October everyone! :slight_smile: Just checking to see if there are any updates? As always, anything I can do to help, please let me know!

1 Like
46

I had some dialog with the tech expert at HD, and I have done the coding for OpenHAB for Gen 3 support, based on the current state of the API definition as kindly reported on this thread. However my understanding – reading between the lines – is that the Gen 3 API is still not fully finalised. Yes, they have released Gen 3 hubs, but I think they may be subject to firmware updates in the next months which would result in slight changes to the API Gen 3 specification / implementation. I think that platforms like Home Assistant and OpenHAB are not on the critical path here, but rather (again reading between the lines) the mass market platforms (i.e. Alexa and Google) are what will determine the final API and its release date.

47

@andrewfg
I just found this thread when hunting for a Gen3 HA integration. If you need anyone else to poke their system to get details or to beta test anything please feel free to ask. I’ve never done any HA integration development work but if you also have a repo you’re working out of for the Gen3 integration and I can be of assistance, again let me know.

It is amazingly cool they have a swagger server running on the gateway like this and you can poke at it for details and issuing commands. This is so much better than the old days of companies keeping APIs secret, yes to interoperability in integrations!

Thanks for your work on the integration.

48

Happy November everyone, hope you all had a safe and fun Halloween. Any news on getting Gen3 support in Home Assistant?

49

Add me to the list of those interested in this. Just got a gen 3 Hub with new shades and disappointed that there is no HA support.

50

I’m doing a house with a smart home system called Loxone. I know it’s not HA but I think the information that I’ve figured out might be of benefit to you guys as well. Through trial and error I figured out the syntax for the Gen 3 Gateway in order for it to return scene IDs, and send scene commands via HTTP. The URL that will return the JSON including the scene IDs is as follows:

“http://(Your Gateway IP)/home/scenes?”.

This will return the JSON with all the scene IDs, along with other information. From there the URL to command the gateway to implement a certain scene is as follows:

“http://(Your Gateway IP)/home/scenes?sceneId=(Your Scene ID)”.

Make sure that the “I” in “sceneId” is capitalized or else it won’t work. Hope this helps anyone else stuck on integrating the new Hunter Douglas gateway.

51

Well I mean - and no offense intended - at this point we pretty much know what the API is an what needs to be done. Personally I’ve already setup Node RED flows that do my shades.

We just need the maintainers to update things (right now I think the issue is in a used library)

52

Thanks for the feedback. I was unable to find much info online about the APIs for the gen 3 hubs. I’m sure most of you are more knowledgeable than me in this area but I thought I’d share what I found in case it helps anyone else.

53

I think from the HA point of view the main issue is that the underlying API has changed a LOT from v2 to v3 so all the supporting libraries and everything do need to both be updated but also in a way that keeps working for v2 as well, which basically means duplicating the whole system because it is so different.

FYI: I have an open Issue on GH for that: Hub v3 support? · Issue #23 · sander76/aio-powerview-api · GitHub

54

As an interim solution, I’m using Home Assistant to directly send RESTful commands. This gets me 95% of what I was looking for. For the benefit of others, here’s what I did:

  1. I configuring my desired scenes via the PowerView app. Then under More > Integration > Integration IDs > Scene IDs; I wrote down the IDs for each of the scenes I created.

  2. In my configuration.yaml, I created entries for each of my scenes. In this example “123” is the scene ID.

rest_command:
  powerview_scene123:
    url: http://192.168.0.82:80/home/scenes/123/activate
    method: PUT
    headers:
      accept: "application/json, text/html"
      user-agent: 'Mozilla/5.0 {{ useragent }}'
    content_type:  'application/json; charset=utf-8'
  1. Finally, I can create some automations based on that new entry. For example:
action:
  - service: rest_command.powerview_scene123
    data: {}
1 Like
55

This is basically what I am doing with NodeRED. I didn’t know HA could send http commands directly so I learned that today!

This works of course, the downside being you don’t get any pretty state recognition and UI to go along with it.

56

Hi,

I appreciate everyone’s efforts here to reverse engineer the Gen3 Hunter Douglas hub. I have been attempting to activate a scene. All of the GET commands return and function as you would expect. When I fetch all of the scenes with GET to http://powerview-g3.local/home/scenes - everything returns. As an example:

	{
		"id": 83,
		"name": "R29vZG5pZ2h0IFNjZW5l",
		"ptName": "Goodnight Scene",
		"networkNumber": 34514,
		"color": "11",
		"icon": "185",
		"roomIds": [
			8
		]
	},

The issue is I am unable to activate it with PUT to http://powerview-g3.local/home/scenes/83/activate. It returns with a 200 and the response even shows the ID numbers of the shades:

{
	"shadeIds": [
		35,
		77
	]
}

However, nothing actually happens. Am I missing something? Is there an authentication required to activate? Everything I am doing is just through unauthenticated HTTP calls on my local network. I would appreciate any help! Thanks!

1 Like
57

Trying using the actual IP address, instead of powerview-g3.local. Also, see if it works after rebooting the gateway. At least with mine, I’ve had to lockup several times, and the only solution was pulling the power cord.

58

Following this thread with interest!

Basic question: Since Gen 3 appears to use BLE, what are the possibilities of driving the shades directly via BLE, rather than the hub?

59

Thanks for the suggestion. Unfortunately those steps didn’t work. I’ll wait for another release to update the hub and see if there was a problem with it.

Once again thanks for the research you have done.

60

Has anybody heard anything from Hunter Douglass or made any headway into figuring out what can be done?

61

Subscribing to this thread :smiley:

I was able to get Swagger running on my hub, but I had to use the IP address rather than the “name” of the hub. These are blinds that were installed in August 2022. I have used the app on the my phone to update both the gateway and the blinds.

Using the commands above, I’m now able to get a full working swagger API for my blinds.

Enable Swagger on your hub: http://<hub-ip-address>/gateway/swagger?enable=true
Get the Swagger results: http://<hub-ip-address>:3002

I’m able to list blinds, jog them and correctly set their position.

I think @DocBrown’s solution are a reasonable intermediary. But I’m a semi-retired programmer with two sets of these blinds (home and cottage), so I’m happy to contribute here.