Adding Tilt to the Hunter Douglas PowerView Cover integration (Luxaflex)

[Kingy444]

Thanks for that mate - the type 54/55 is one of the last things i need to include. Dont worry too much about slider ‘bounce’ atm - this release has a big but we have fixed it in core.

Based on your advice above i have just updated the google drive to make these tilt anywhere. You shouldnt have a seperate entity for the tilt though - it is part of the main blind entity - Could you please test the 54 / 55 again

We want to make sure the commands for both acts the same - ie setting one them both to 0 or 100 would both tilt and shade result in the positioning being the same. We are unsure if HD inverted the value for left shades so just need to test that part

Open and close for shades should be pretty straight forward I expect these to work as intended
Close for tilt will set to zero, open for tilt will set to 50 now - the old code was setting it to 100 which was just closing the other way.
With that in mind do some testing with the slider too and make sure the shades are tilting the same way

EDIT: I guess what we are trying to determine here is should 30% on the 54 wilt the same way as 30% on the 55 - a good comparison would be checking the powerview app and reporting back how they report there.

[ApriliaEdd (Edd)]

OK brace yourself for picture overload! I’ve updated to the version you posted this morning.

I have set the blinds to the same position using the powerview app
Righthand Stack

powerview app

HA

Actual

Left Stack

powerview app

HA

Actual

from the powerview app there is no way to send a “close command” you have to close the shade with the upper part of the screen slider and then tilt them closed either way with the lower slider. if you use the “pebble” controller to close them the actual blinds do this (left blind is left stack/bifold and right is right stack/sliding door)

HA reports this

Powerview shows this

so it seems that when you send a close it tilts the blinds the same way regardless of stack side.

Sending an open command from the pebble results in this

looks like open is 100% shade and 100% tilt for both types.

[Kingy444]

So important question - we happy with how they operate from HA interface ?

[ApriliaEdd (Edd)]

for me they operate the same as the powerview app, which is what we want right? continuity

as they are 0% tilt is vanes fully anti clockwise for all of my blinds 100% tilt is fully clockwise, 0% blind position is fully closed for all and 100% is fully open

i can certainly work with that.

[andrewfg (Andrew Fiddian-Green)]

@Kingy444

So important question - we happy with how they operate from HA interface ?

@ApriliaEdd

i can certainly work with that.

@Kingy444 could you please summarise your findings on type 54 & 55 for me to eventually update the OH code to track your HA code?

… also any thoughts concerning type 56 split stack vertical shades?

[andrewfg (Andrew Fiddian-Green)]

@pessorrusso

My shades api output:

{"shadeIds":[10956,44040,11895,228,45451,49704,1978,49953,30911,4731,55855,10680,64816,29156,11946],"shadeData":[{"id":10956,"type":18,"capabilities":1,"batteryKind":2,"smartPowerSupply":{"status":0,"id":0,"port":0},"batteryStatus":3,"batteryStrength":161,"roomId":50436,"firmware":{"revision":2,"subRevision":2,"build":2767,"index":9},"name":"RGluaW5nIDI=","groupId":57347,"positions":{"posKind1":3,"position1":32767},"signalStrength":4},{"id":44040,"type":18,"capabilities":1,"batteryKind":2,"smartPowerSupply":{"status":0,"id":0,"port":0},"batteryStatus":3,"batteryStrength":153,"roomId":45685,"name":"T2ZmaWNlIDM=","firmware":{"revision":2,"subRevision":2,"build":2767,"index":9},"groupId":45777,"signalStrength":0,"positions":{"posKind1":3,"position1":32767}},{"id":11895,"type":18,"capabilities":1,"batteryKind":2,"smartPowerSupply":{"status":0,"id":0,"port":0},"batteryStatus":3,"batteryStrength":155,"roomId":18036,"firmware":{"revision":2,"subRevision":2,"build":2767,"index":9},"name":"TWFzdGVyIDE=","groupId":9889,"positions":{"posKind1":3,"position1":32767}},{"id":228,"type":18,"capabilities":1,"batteryKind":2,"smartPowerSupply":{"status":0,"id":0,"port":0},"batteryStatus":3,"batteryStrength":155,"roomId":45685,"firmware":{"revision":2,"subRevision":2,"build":2767,"index":9},"name":"T2ZmaWNlIDE=","groupId":45777,"signalStrength":0,"positions":{"posKind1":3,"position1":30826}},{"id":45451,"type":18,"capabilities":1,"batteryKind":2,"smartPowerSupply":{"status":0,"id":0,"port":0},"batteryStatus":3,"batteryStrength":160,"roomId":65367,"firmware":{"revision":2,"subRevision":2,"build":2767,"index":9},"name":"TGl2aW5nIDI=","groupId":38297,"positions":{"posKind1":1,"position1":259},"signalStrength":4},{"id":49704,"type":18,"capabilities":1,"batteryKind":2,"smartPowerSupply":{"status":0,"id":0,"port":0},"batteryStatus":3,"batteryStrength":152,"roomId":45685,"firmware":{"revision":2,"subRevision":2,"build":2767,"index":9},"name":"T2ZmaWNlIDI=","groupId":45777,"signalStrength":4,"positions":{"position1":0,"posKind1":1}},{"id":1978,"type":18,"capabilities":1,"batteryKind":2,"smartPowerSupply":{"status":0,"id":0,"port":0},"batteryStatus":3,"batteryStrength":161,"roomId":50436,"firmware":{"revision":2,"subRevision":2,"build":2767,"index":9},"name":"RGluaW5nIDE=","groupId":57347,"positions":{"posKind1":3,"position1":30895},"signalStrength":4},{"id":49953,"type":18,"capabilities":1,"batteryKind":2,"smartPowerSupply":{"status":0,"id":0,"port":0},"batteryStatus":3,"batteryStrength":161,"roomId":65367,"firmware":{"revision":2,"subRevision":2,"build":2767,"index":9},"name":"TGl2aW5nIDE=","groupId":38297,"positions":{"posKind1":3,"position1":32767}},{"id":30911,"type":1,"capabilities":0,"batteryKind":2,"smartPowerSupply":{"status":0,"id":0,"port":0},"batteryStatus":3,"batteryStrength":156,"roomId":18036,"firmware":{"revision":2,"subRevision":2,"build":2754,"index":32},"name":"TWFzdGVyIDM=","groupId":63214,"positions":{"posKind1":1,"position1":65535}},{"id":4731,"type":18,"capabilities":1,"batteryKind":2,"smartPowerSupply":{"status":0,"id":0,"port":0},"batteryStatus":3,"batteryStrength":160,"roomId":21086,"name":"QmVkcm9vbSAx","firmware":{"revision":2,"subRevision":2,"build":2767,"index":9},"groupId":13862,"signalStrength":4,"positions":{"posKind1":3,"position1":32767}},{"id":55855,"type":18,"capabilities":1,"batteryKind":2,"smartPowerSupply":{"status":0,"id":0,"port":0},"batteryStatus":3,"batteryStrength":162,"roomId":19934,"firmware":{"revision":2,"subRevision":2,"build":2767,"index":9},"name":"VHY=","groupId":17638,"signalStrength":4,"positions":{"posKind1":3,"position1":30980}},{"id":10680,"type":18,"capabilities":1,"batteryKind":2,"smartPowerSupply":{"status":0,"id":0,"port":0},"batteryStatus":3,"batteryStrength":160,"roomId":65367,"firmware":{"revision":2,"subRevision":2,"build":2767,"index":9},"name":"TGl2aW5nIDM=","groupId":38297,"positions":{"posKind1":3,"position1":32599},"signalStrength":4},{"id":64816,"type":18,"capabilities":1,"batteryKind":2,"smartPowerSupply":{"status":0,"id":0,"port":0},"batteryStatus":3,"batteryStrength":155,"roomId":9344,"firmware":{"revision":2,"subRevision":2,"build":2767,"index":9},"name":"QmVkcm9vbSBHdWVzdA==","groupId":57376,"signalStrength":0,"positions":{"posKind1":1,"position1":0}},{"id":29156,"type":18,"capabilities":1,"batteryKind":2,"smartPowerSupply":{"status":0,"id":0,"port":0},"batteryStatus":3,"batteryStrength":162,"roomId":18036,"firmware":{"revision":2,"subRevision":2,"build":2767,"index":9},"name":"TWFzdGVyIDI=","groupId":9889,"positions":{"position1":65535,"posKind1":1}},{"id":11946,"type":18,"capabilities":1,"batteryKind":2,"smartPowerSupply":{"status":0,"id":0,"port":0},"batteryStatus":3,"batteryStrength":161,"roomId":55960,"name":"QmVkcm9vbSAy","groupId":44302,"positions":{"posKind1":1,"position1":309},"firmware":{"revision":2,"subRevision":2,"build":2767,"index":9}}]}

@pessorrusso I see from your shades api output that you have fourteen type 18 shades and one type 1 shade => can you please tell me the model name / description for this type 1 shade?

[Kingy444]

54 / 55 act as any other tilt anywhere 180 do so that simplifies your implementation. And neither is inverted, both using the same 0/65k results

I’m thinking all type 3 capabilities are tiltanywhere ? do you have reason to think otherwise ?

So we originally had type 1+3 linked as horizontal+vertical partners but i actually think it is 2+3 are the partners with capability 4 being the TiltOnClosed partner (which we have none identified)

[Kingy444]

@andrewfg

@pessorrusso I see from your shades api output that you have fourteen type 18 shades and one type 1 shade => can you please tell me the model name / description for this type 1 shade?

Good Pick up @andrewfg

@pessorrusso this would be the shade you called ‘Master 3’ - but additionally for Andrews request could you confirm this is just an up/down shade or if it has tilt. Capability 0 is the only one that isnt clear on that
While your json indicates its up/down only i figure its possible we posted bad data to the shade if you were currently using HA to move them (dont worry if that is the case, it wont break anything except state information and a force refresh fixes that)

[andrewfg (Andrew Fiddian-Green)]

@Kingy444

do you have reason to think otherwise ?

No. Because in OH I have no users reporting that type of shade.

@Kingy444

i actually think it is 2+3 are the partners with capability 4 being the TiltOnClosed partner (which we have none identified)

I also have none identified.

So in summary, I would change my code to support your two hypotheses above. (And eventually change it again if an actual user reports an actual complaint…)

@Kingy444

but appreciate retesting of type 21

I also do not have this type yet in my data base, so could you please let me know its respective capabilities and model name / description?

[Kingy444]

@andrewfg

I also do not have this type yet in my data base, so could you please let me know its respective capabilities and model name / description?

think that was a typo for 51 - i have no type 21 either

[andrewfg (Andrew Fiddian-Green)]

@Kingy444 so (pending the model name from @pessorrusso my “final” database looks like this below => any comments?

[andrewfg (Andrew Fiddian-Green)]

@Kingy444 PS I am guessing from their descriptions, therefore, that types 69 … 71 might probably not have capabilities 3. Perhaps capabilities 4. And therefore as curtains can’t tilt, perhaps caps 4 is the vertical analogue of caps 0. Or something like that??

[Kingy444]

@andrewfg

types 69 … 71 might probably not have capabilities 3. Perhaps capabilities 4

I think that is a fair assumption - i was curious how curtains would tilt

I will implement the same assumption and then if anyone advised otherwise at least we are on the same page and can let the other know

Other comments on your capabilities definition
Capability 9 is not tiltAnywhere - it requires the rear shade to be open and the front to be closed

[Kingy444]

@andrewfg do you have any reports of shade_type(44, “Twist”) ?

I’m curious if it is actually a tilt shade with capability 0 or if it was incorrectly reported too now as it is the only type 0 capability reported that has a tilt capability

EDIT 1: Looking at this they may be capability 0 but no tilt too Twist® Roller Blinds with PowerView® Automation from Luxaflex® - YouTube

EDIT 2: Strike that - definitiely tilt capability - see point 5 here programming manual
But still curious if the capability is truly 0 or it should be capability 1

[Kingy444]

That site i just posted has some interesting info - would be good to get someone with split stack involved based on the image here programming manual

I can see them needing special code potentially

[ApriliaEdd (Edd)]

I have one window which a split stack would work on…open to donations

couple of things I noticed overnight:

firstly, this one is probably personal for everyone but for me, the blind should only be considered closed if it is completely closed and tilted closed. my blinds have been showing closed since I finished testing for you yesterday but the blinds were what we consider open (tilted 50%) as in they let light in. we only really fully open the blinds if we are opening the doors.

Secondly my blinds are on mains power can you tell this during discovery and disable the battery entity for these as it always reads 0% except for one that is reading 90% randomly…

is the intention for this to replace the official integration in due course or will it remain a custom component?

[andrewfg (Andrew Fiddian-Green)]

@Kingy444

definitiely tilt capability - see point 5 here programming manual
But still curious if the capability is truly 0 or it should be capability 1

I myself have these shades so I can confirm type 44 and capabilities 0. They are obviously an oddity because the ‘tilt’ really relates to the degree of overlap between the bands on the front and back parts of the shade loop. And so you can ‘tilt’ them by changing position1 @ posKind1 = 1 and/or by changing position1 @ posKind1 = 3. In other words the required code functionality is the same as for ‘normal’ tiltOnClosed shades. So I am wondering if perhaps I need (like you) to allow exceptions to the normal type <=> capabilities mapping??

[andrewfg (Andrew Fiddian-Green)]

@Kingy444

I will implement the same assumption

@Kingy444

Capability 9 is not tiltAnywhere - it requires the rear shade to be open and the front to be closed

Ok to both.

[andrewfg (Andrew Fiddian-Green)]

@Kingy444

Capability 9 is not tiltAnywhere - it requires the rear shade to be open and the front to be closed

Ah. Interesting. So in other words it has yet another interlocking scheme…

EDIT: @Kingy444 can you please let me know if Capability 9 has 90 degree or 180 degree tilt?

[Kingy444]

@andrewfg

EDIT: @Kingy444 can you please let me know if Capability 9 has 90 degree or 180 degree tilt?

No worries. They are Tilt 90