cover type, channel ?

[uzelac]

Need bit more explanation on cover subtype, not sure what factor and max/min means.

My covers take two switches, one for up and other for down. Nothing smart.
I just take care that DDRC units don't ask up and down in the same time, since that can happen because Dynalite doesn't understand covers.

At least, that is what i know.

Is there any better way to do covers in Dynalite ?
Because of this limitations, i use timedcover which is also here on github.
Would be much better if Dynalite have something on its own.

Thanks

[ziv1234]

Can you show me your config with timedcover? From: Saša Uzelac <notifications@github.com> Sent: Thursday, January 9, 2020 2:30 AM To: ziv1234/hass_dynalite_component <hass_dynalite_component@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: [ziv1234/hass_dynalite_component] cover type, channel ? (#5) Need bit more explanation on cover subtype, not sure what factor and max/min means. My covers take two switches, one for up and other for down. Nothing smart. I just take care that DDRC units don't ask up and down in the same time, since that can happen because Dynalite doesn't understand covers. At least, that is what i know. Is there any better way to do covers in Dynalite ? Because of this limitations, i use timedcover which is also here on github. Would be much better if Dynalite have something on its own. Thanks — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#5?email_source=notifications&email_token=AD5UNS77KQGYJC4PYLKJTBDQ4ZVZXA5CNFSM4KEQS4W2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IE5JZ2A>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AD5UNS6EOQKV673ODCB67XTQ4ZVZXANCNFSM4KEQS4WQ>.

[uzelac]

Sure, there it is as new fail in your component :)
Delete it ASAP, hope you don't mind, couldnt think of better way after i've 'tried (and failed) to format it proprely here in issues.

[ziv1234]

Where did you put the file? I cannot see it anywhere on Github From: Saša Uzelac <notifications@github.com> Sent: Thursday, January 9, 2020 12:27 PM To: ziv1234/hass_dynalite_component <hass_dynalite_component@noreply.github.com> Cc: Ziv <zivk@hotmail.com>; Comment <comment@noreply.github.com> Subject: Re: [ziv1234/hass_dynalite_component] cover type, channel ? (#5) Sure, there it is as new fail in your component :) Delete it ASAP, hope you don't mind, couldnt think of better way after i've 'tried (and failed) to format it proprely here in issues. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#5?email_source=notifications&email_token=AD5UNS7A2GOS32H4QMJOXQDQ433WVA5CNFSM4KEQS4W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIPZMWQ#issuecomment-572495450>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AD5UNSZ6RCMO6DBAPB7GDETQ433WVANCNFSM4KEQS4WQ>.

[uzelac]

I pressed create new file, and it went... somewhere.
Did this again, hope this link is ok:

https://github.com/uzelac/hass_dynalite_component/blob/687092f99f0e4754496b15d6f417c793c3cb0b6f/timedcover%20example.yaml

[uzelac]

As you can see, I have three presets per cover, one for cover to go up, one to go down and third to stop.
That is also how this timedcover works.
Now, with channels, maybe it can be done better, earlier with presets... couldn't find better way.

[ziv1234]

Thanks. It works now From: Saša Uzelac <notifications@github.com> Sent: Thursday, January 9, 2020 8:29 PM To: ziv1234/hass_dynalite_component <hass_dynalite_component@noreply.github.com> Cc: Ziv <zivk@hotmail.com>; Comment <comment@noreply.github.com> Subject: Re: [ziv1234/hass_dynalite_component] cover type, channel ? (#5) I pressed create new file, and it went... somewhere. Did this again, hope this link is ok: https://github.com/uzelac/hass_dynalite_component/blob/687092f99f0e4754496b15d6f417c793c3cb0b6f/timedcover%20example.yaml — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#5?email_source=notifications&email_token=AD5UNS4P6IMKNLS3K6WYQSLQ45UF3A5CNFSM4KEQS4W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIRJE4I#issuecomment-572691057>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AD5UNS4327X4DNECLPTSYX3Q45UF3ANCNFSM4KEQS4WQ>.

[ziv1234]

I wrote something today. Mine is the same setup but there is also a channel that can move it up and down. The problem I see with timedcover is that it works if all the action is from HomeAssistant, but I also have wall switches and a Control4 system that may send command. Hopefully will be able to upload something today or tomorrow From: Saša Uzelac <notifications@github.com> Sent: Thursday, January 9, 2020 8:31 PM To: ziv1234/hass_dynalite_component <hass_dynalite_component@noreply.github.com> Cc: Ziv <zivk@hotmail.com>; Comment <comment@noreply.github.com> Subject: Re: [ziv1234/hass_dynalite_component] cover type, channel ? (#5) As you can see, I have three presets per cover, one for cover to go up, one to go down and third to stop. That is also how this timedcover works. Now, with channels, maybe it can be done better, earlier with presets... couldn't find better way. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#5?email_source=notifications&email_token=AD5UNS3AM74XAWHNJ4TA773Q45UNBA5CNFSM4KEQS4W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIRJKZQ#issuecomment-572691814>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AD5UNS46SPKC4UJ7R462WZTQ45UNBANCNFSM4KEQS4WQ>.

[uzelac]

You are right, timedcover wont count time if one instructs cover outside of HA.
It can be done, it can time from channel/preset change to change... Well, it can but it doesn't :).
Dynalite isnt capable to know position, but HA can.

[ziv1234]

I uploaded a new version with an additional template, “timecover”. When you define the templates (or the overrides), you specify: 'timecover': channel: 2 # this is optional. I also have a control 4 system that controls the same blind via a channel. If not relevant, use 0 open: 1 # preset to open close: 2 # preset to close stop: 4 # preset to stop duration: 75 # time to fully open / close class: blind # device class. Only affects the visual in HA I will also add the ability to tilt. My system open tilts when opening the blind briefly and closes them when you close it, so uses the same presets, just for a shorter time. From: Saša Uzelac <notifications@github.com> Sent: Thursday, January 9, 2020 11:34 PM To: ziv1234/hass_dynalite_component <hass_dynalite_component@noreply.github.com> Cc: Ziv <zivk@hotmail.com>; Comment <comment@noreply.github.com> Subject: Re: [ziv1234/hass_dynalite_component] cover type, channel ? (#5) You are right, timedcover wont count time if one instructs cover outside of HA. It can be done, it can time from channel/preset change to change... Well, it can but it doesn't :). Dynalite isnt capable to know position, but HA can. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#5?email_source=notifications&email_token=AD5UNS2QPWOIKZLOJI4SK7DQ46J37A5CNFSM4KEQS4W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIR3TNQ#issuecomment-572766646>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AD5UNS36NEEG4GCQBXC5EU3Q46J37ANCNFSM4KEQS4WQ>.

[uzelac]

Great, will give it a try on monday when i return home! :)

[uzelac]

Btw maybe even better would be to make:

'timecover':
channel: 2 # this is optional. I also have a control 4 system that controls the same blind via a channel. If not relevant, use 0
open: 1 # channel to open
close: 2 # channel to close
duration: 75 # time to fully open / close
class: blind # device class. Only affects the visual in HA

And so script takes care that up and down are nevert ON at the same time. This way one doesnt need preset for stop.
I believe for me personally it is better with presets, they are already working, but maybe it is more "correct" to use channels

[ziv1234]

My mistake: open, close, and stop should be presets, not channels. You need the stop one, since as far as I know, Dynalite doesn’t track the specific preset, but activating a preset causes the action. The channel one is optional as I need it for my setup but it is not mandatory. Set it to 0 to ignore. The dynalite component already takes care of the fact that they are not up and down at the same time, as an area’s preset is the latest that was selected in that area. I assume that for your blinds, “open”, “close”, and “stop” are all in the same area for a specific blind, right? From: Saša Uzelac <notifications@github.com> Sent: Saturday, January 11, 2020 4:27 PM To: ziv1234/hass_dynalite_component <hass_dynalite_component@noreply.github.com> Cc: Ziv <zivk@hotmail.com>; Comment <comment@noreply.github.com> Subject: Re: [ziv1234/hass_dynalite_component] cover type, channel ? (#5) Btw maybe even better would be to make: 'timecover': channel: 2 # this is optional. I also have a control 4 system that controls the same blind via a channel. If not relevant, use 0 open: 1 # channel to open close: 2 # channel to close duration: 75 # time to fully open / close class: blind # device class. Only affects the visual in HA And so script takes care that up and down are nevert ON at the same time. This way one doesnt need preset for stop. I believe for me personally it is better with presets, they are already working, but maybe it is more "correct" to use channels — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#5?email_source=notifications&email_token=AD5UNS2KGZIXFRSJGJT2HH3Q5HJMVA5CNFSM4KEQS4W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIWDCIQ#issuecomment-573321506>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AD5UNS4L3BOQC64JOMQEFYDQ5HJMVANCNFSM4KEQS4WQ>.

[uzelac]

Same area, of course.
But I did not mean that.

I meant that component can be made that it needs channels, not presets to work.
In that case:

timecover':
open: 1 # channel to open
close: 2 # channel to close
duration: 75 # time to fully open / close
class: blind # device class. Only affects the visual in HA

As i said, maybe it is more correct.
In that case your script would need to:

Automation OPEN

• close_channel OFF # just in case
• open_channel ON
• time delay
• open_channel OFF

Automation CLOSE

• open_channel OFF # just in case
• close_channel ON
• time delay # count seconds, whatever
• close_channel OFF

[uzelac]

What is more important, does your timedcover script reacts to direct dynalite keypad commands ?
If i use presets on keypad, will it get that and show precise position ?

[ziv1234]

my dynalite keypad send the presets so the timecover template monitors these presets and updates the level accordingly. It works in my setup so interested to see whether it works for you.
mine isn't configured with channels this way, as i dont have a direct control (or at least not aware of one) for the open and close channels of the cover itself, so i have to use the presets.
Let me know if the current one works for your setup. If not, i can try and program it, but since my setup works differently, will be very difficult to test...

[uzelac]

Is this OK, to write in .yaml file ? (i use dynalite.yaml with !include in configuration.yaml)

'201':
name: Guest Room Cover
template: timecover
channel: 0
open: 1
close: 3
stop: 2
duration: 17
class: blind

[uzelac]

Ok, got it, spent some time trying and reading your default configuration.yaml:
And yes, it is a bingo once more :).

Btw, I've put my dynalite.yaml here so someone can learn:
https://github.com/uzelac/hass-dynalite-component-support/blob/master/dynalite.yaml

[ziv1234]

thanks From: Saša Uzelac <notifications@github.com> Sent: Monday, January 13, 2020 9:54 PM To: ziv1234/hass_dynalite_component <hass_dynalite_component@noreply.github.com> Cc: Ziv <zivk@hotmail.com>; Comment <comment@noreply.github.com> Subject: Re: [ziv1234/hass_dynalite_component] cover type, channel ? (#5) Ok, got it, spent some time trying and reading your default configuration.yaml: And yes, it is a bingo once more :). Btw, I've put my dynalite.yaml here so someone can learn: https://github.com/uzelac/hass-dynalite-component-support/blob/master/dynalite.yaml — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#5?email_source=notifications&email_token=AD5UNSYL2AE3O2KQMY2VB6DQ5TBF7A5CNFSM4KEQS4W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI2B5HQ#issuecomment-573841054>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AD5UNS5FDP37DKIGPNX7WLDQ5TBF7ANCNFSM4KEQS4WQ>.

[ziv1234]

It should be with the latest version of the library. However, I didn’t update the component From: Saša Uzelac <notifications@github.com> Sent: Monday, January 13, 2020 3:34 AM To: ziv1234/hass_dynalite_component <hass_dynalite_component@noreply.github.com> Cc: Ziv <zivk@hotmail.com>; Comment <comment@noreply.github.com> Subject: Re: [ziv1234/hass_dynalite_component] cover type, channel ? (#5) Is this OK, to write in .yaml file ? (i use dynalite.yaml with !include in configuration.yaml) '201': name: Guest Room Cover template: timecover open: 1 close: 3 stop: 2 ? — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#5?email_source=notifications&email_token=AD5UNSZ4U5B2MVMVCOKZTKDQ5PAG3A5CNFSM4KEQS4W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIXKLLI#issuecomment-573482413>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AD5UNS3QY2DZCXV7BM7MMVDQ5PAG3ANCNFSM4KEQS4WQ>.