Serial Commands for Hunter Douglas Hub!

[Deane Johnson]

I tried it this morning in a browser and got past the Google Search. It returned URL Not Found. I was checking the URL using Fing on my iPad to confirm it was there. I looked around and this was on the PC screen, I assume from the Hub:

{"scene":{"shadeIds":[]}}

I then took the "1" off the end and got this, which is clearly Hub data:

[{"id":64108,"networkNumber":0,"name":"Tm9vbiBQb3dlclZpZXcgT3Blbg==","roomId":1683,"order":0,"colorId":0,"iconId":0},{"id":24565,"networkNumber":1,"name":"UG93ZXJWaWV3IFN1blJpc2U=","roomId":1683,"order":1,"colorId":3,"iconId":0}]}

I read it to mean the scenes are 0 and 1 (as suspected), the long entry is the shade #, and the room ID is 1683

I now feel I'm in the same position as the proverbial image of a monkey sitting holding a human skull, looking at it in wonderment.

[Dean Roddey]

OK, so do the URL I indicated above again, but use those "id: number returned in the data above, so 64108 and 24565. Those are probably what you are supposed to be using.

[Deane Johnson]

OK, so do the URL I indicated above again, but use those "id: number returned in the data above, so 64108 and 24565. Those are probably what you are supposed to be using.

The shade operates as it should.

[Deane Johnson]

I then used the same numbers in a serial test Event and the shade operated properly from the Test screen.

Then, I created a widget and put the same instruction in the widget. The shade operated from my iPad properly.

I think I'll toss the skull aside and go dancing through the jungle.

BTW, this seems a long way from their documentation that says to use the single number (0 or 1).

[Deane Johnson]

My friend at Hunter Douglas has confirmed that what the API is instructing is that we would use the longer number (as we did), rather than the single digit. The single digit is merely referring to the longer number for that Scene.

I suggested they might want to make that a little clearer.

[Dean Roddey]

My friend at Hunter Douglas has confirmed that what the API is instructing is that we would use the longer number (as we did), rather than the single digit. The single digit is merely referring to the longer number for that Scene.

I suggested they might want to make that a little clearer.

To be fair, they do show that in the example:

GET /api/scenesceneid=40369/ HTTP/1.1