Hunter Douglas Gen3 also Honeywell Home ProSeries

[nadler]

I just moved into a new condo.  My wife wants Hunter Douglas cellular shades.  They have a new Gen3 protocol which uses wifi, a hub, and BTE.  It seems very proprietary and not DIY friendly at all.  Also, it's new and there is not much information on it.

Does anyone have any experience with Gen3 for Hunter Douglas?  Any advice in general about these (like stay away)?

On another note, the condo came with the Honeywell Home ProSeries security.  Also not very DIY friendly.  I wanted to add some window sensors but the integrator wouldn't let me do it myself.  So I wound up paying $80 each for 3 window sensors when I could have bought the sensors for $25 each and installed them myself in 10 minutes.  I noticed there is a Total Connect NS.  Would this work with the ProSeries and z-wave through the panel and/or Polisy?

Thanks.

Noel

[sjenkins]

Don't know much about it but my wife has a bunch of the Gen3 on the way ; we'll see when they arrive.  Of course my plan is to figure them out with a software & maybe hardware solution ; then of course get integration to the Polisy through NS or Network or MQTT.

[nadler]

That sounds like what I would like to do as well. Let's keep in touch.

[dakall]

I have Gen2. The API is readily available online. There was a lot of carryover from Gen1 to Gen2. I don't see why Gen3 would be different. It works with all of the same home-automation systems.

I use the network resources of the ISY for all the controls. I don't use the HD app for any scheduling. I just  set up scenes and then call those scenes with the ISY.

[nadler]

Thank you @dakall and @sjenkins.  I thought perhaps the api would be different since the Gen3 hub seems to be different.  HD touts the GEN3 as a new way to communicate with their shades.  I hope the rest commands work with GEN3.  That would work well for me.

 

[sjenkins]

On 6/14/2022 at 5:39 PM, dakall said:

I have Gen2. The API is readily available online. There was a lot of carryover from Gen1 to Gen2. I don't see why Gen3 would be different. It works with all of the same home-automation systems.

I use the network resources of the ISY for all the controls. I don't use the HD app for any scheduling. I just  set up scenes and then call those scenes with the ISY.

@dakallcould you share an example or webpage resource for gen2. I don’t have my new blinds yet but may get going on my research. 

[dakall]

On 6/18/2022 at 7:16 PM, sjenkins said:

@dakallcould you share an example or webpage resource for gen2. I don’t have my new blinds yet but may get going on my research. 

There is a thread here already that got me going. No sense for me to duplicate everything that is in here. Yes, it's older and for Gen 1, but the logic is the same for Gen 2. There were a few syntax changes between 1 & 2 but nothing major. I don't know if the Gen 3 API has been released yet.

Here is a link to the API documentation. It's somewhere in the thread as well.

https://mynzws.co.nz/wp-content/uploads/2021/05/Powerview-Third-Party-API.pdf

I do not consider my self to be a programmer in any way, shape , or form. Thanks to the above thread and lots of experimentation, I now know enough to be very dangerous. You will need to use the H-D app in order set up all the shades and scenes you wish to use. I found it easiest at first to just control the scenes with the ISY. Here's a few quick and dirty instructions and tips.

Once the hub is set up to your liking, you can now enter this into your browser:

http://hub_ip_address/api/scenes

You should get something similar to this:

{"sceneIds":[9075,63105,43541,49729,27775,61525,22154,15570,45956,62971,31558],"sceneData":
[{"roomId":39030,"name":"T3BlbiBCYWNrIDkwNzU=","colorId":9,"iconId":0,"networkNumber":199,"id":9075,"order":0,"hkAssist":false},
{"roomId":19362,"name":"RnJvbnQgRG9vciBNaWQgNjMxMDU=","colorId":12,"iconId":0,"networkNumber":182,"id":63105,"order":6,"hkAssist":false},
{"roomId":26247,"name":"R3JlYXQgUm9vbSBPcGVuIDQzNTQx","colorId":13,"iconId":0,"networkNumber":181,"id":43541,"order":8,"hkAssist":false},
{"roomId":39030,"name":"U3Vuc2V0IE9wZW4gNDk3Mjk=","colorId":5,"iconId":97,"networkNumber":74,"id":49729,"order":4,"hkAssist":false},
{"roomId":26247,"name":"R3JlYXQgUm9vbSBDbG9zZSAyNzc3NQ==","colorId":13,"iconId":0,"networkNumber":171,"id":27775,"order":7,"hkAssist":false},
{"roomId":39030,"name":"QmVkdGltZSA2MTUyNQ==","colorId":15,"iconId":12,"networkNumber":16,"id":61525,"order":2,"hkAssist":false},
{"roomId":39030,"name":"Q2xvc2UgRnJvbnQgMjIxNTQ=","colorId":14,"iconId":95,"networkNumber":70,"id":22154,"order":3,"hkAssist":false},
{"roomId":39030,"name":"T3BlbiBGcm9udCAxNTU3MA==","colorId":1,"iconId":96,"networkNumber":188,"id":15570,"order":1,"hkAssist":false},
{"roomId":39030,"name":"TGF0ZSBOb29uIENsb3NlIDQ5NTk1Ng==","colorId":7,"iconId":95,"networkNumber":76,"id":45956,"order":10,"hkAssist":false},
{"roomId":19362,"name":"RnJvbnQgRG9vciBMb3cgNjI5NzE=","colorId":12,"iconId":0,"networkNumber":2,"id":62971,"order":5,"hkAssist":false},
{"roomId":2590,"name":"U3VuZGF5IDMxNTU4","colorId":5,"iconId":0,"networkNumber":222,"id":31558,"order":9,"hkAssist":false}]}

These are my 11 scenes that I have set up in my Powerview Hub. The hub assigns a "sceneIds" number to each scene. As you can see, they are all listed in the first line, and then individually in the subsequent lines as just "id." The "name" field is encoded in base64. There are plenty of online base64 decoders. I simply cut & pasted the "name" field into one of these decoder and it would return the name in English. I made a spreadsheet for quick and easier reference. Here's a portion of it:

SCENES		NAME (base 64)
Open Back	9075	T3BlbiBCYWNrIDkwNzU=
Open Front	15570	T3BlbiBGcm9udCAxNTU3MA==
Close Front	22154	Q2xvc2UgRnJvbnQgMjIxNTQ=
Bedtime	61525	QmVkdGltZSA2MTUyNQ==

Once you know the "id" for the scene, the next step is to make a Network Resource to call it. Here's what I use for my "Open Back" scene:

  Obviously, your hub IP address and "sceneId" will be different, but this is how you would make a network resource for this scene. 

I know this seems much to take in at first, especially without access to a hub. Once you get one and begin to experiment with it, this will all make much more sense. 

I am also able to control individual shades, which the original post doesn't really get into much. That is a bit more involved, but I can help you out when the time comes.

 

[nadler]

That's a wealth of information and very helpful.

 

Thank you.

[sjenkins]

For others I have received my gen 3 blinds and gateway.  I am at the very beginning of figuring this out but the api is slightly different.

To get you going replace /api with /home , so....

http://{ip of your gateway}/home  will give you a dump of current parameters in JSON

http://{ip of your gateway}/home/scenes 

http://{ip of your gateway}/home/automations

http://{ip of your gateway}/home/shades

http://{ip of your gateway}/home/shades/{id of shade you want}

You now know as much as I do so far.  Have not found a document like the beautiful version 2 document as per above but using that as a beginning point.  They seem to have changed a number of things subtilely....  

[sjenkins]

The gen 2 api is pretty useful.  

Can activate a scene with...

http://10.0.1.82/home/scenes?sceneId=40

obviously insert your ip for mine and sceneId (capitol eye) for your number which you can get the list with http://10.0.1.82/home/scenes

[nadler]

@sjenkins, thanks again.  My shades should be installed next week.  Looking forward to trying your tips.