rolling shutters issue (pause button)

[rlegrand]

Hi all,

I'm complete newbie with tasmota and domotic.

I just flashed tasmota on my new switch and tried to configure it by using provided templates.

It globally works but I miss one functionality.

To summarize, the swith has 3 buttons:

* One to raise the shutter

* One to lower the shutter

* One to stop the current action

This is the kind of switch I've got:

https://templates.blakadder.com/assets/images/etersky_WF-CS01.jpg

And these are the two templates I tried (I think they are are globally the sames with buttons position which changes ):

https://templates.blakadder.com/etersky_WF-CS01.html

https://templates.blakadder.com/WF-CS01_EU.html

The problem is with the "pause" button which should stop to raising or lowering the roller shutter, and which does nothing.

I can stop raising by setting the raise button off, and same for lowering, but I just can't use the pause one, which doesn't work.

Leds are perfectly working for all buttons.

I can also confirm that the button worked with the origin firmware.

That's it, my knowledge in this domain is too limited so that I don't know where to go and I came here just to get your advice ;)

ps:

May it be a good idea to find a programmatic way to say:

-> button3 (pause) = turn lowering/raising button off if lowering/raising button is on

?

[Philip Knowles]

Have you put the rules in and enabled them as explained on the blakadder pages?

 

Regards

 

Phil K

 

Sent from Mail for Windows 10

--
You received this message because you are subscribed to the Google Groups "TasmotaUsers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonoffusers...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/sonoffusers/34403b60-9ab4-4d4c-87aa-31e4956ac231o%40googlegroups.com.

 

[treinenwimke]

Hi,

Just put in the rules as explained here. The STOP button doesn't do anything without the rules. I know because I have several of those switches and created one of the mentioned templates.

BR//Willem.

[rlegrand]

Thanks guys,

Yes it works.

Note that instructions are here https://templates.blakadder.com/WF-CS01_EU.html but not here

https://templates.blakadder.com/etersky_WF-CS01.html.

Thanks again.

[rlegrand]

To be more specific, it works fine while I don't use the shutter mode.

When I don't activate it, everything works fine (except that the motor still tries to raise the shutter when it's at top, but I can live with that if I don't find the solution ).

When I activate it, I just don't understant what's happening while I have a lot of unexpected behaviours (I activate it before adding your rule).

The worst one is that, once I close the shutter, it's "definitively closed", I can't open it anymore. I guess this may be due to calibaration issues, but I can't figure out what is wrong...

If this sounds familiar to you, please let me know ! :)

Thanks!

Le lundi 13 juillet 2020 09:37:57 UTC+2, treinenwimke a écrit :

[treinenwimke]

Yes, on the GitHub page is says: 'Requires enabled shutter support in Tasmota' but it should read 'Requires disabled shutter support in Tasmota'.

The shutters I use have an end-stop, so the motor stops when the shutter is open or closed. My rules use timers (PulseTime1, 2 and 3) for security reasons but I don't really need them. 

You should time how long it takes the shutter to completely open (from completely closed) and completely close (from completely open). Then add one second (or two) and put these values in PulseTime1 and PulseTime3. Then the motor will stop at the end of the travels. You could change the rules and put in some more PulseTime# statements, if needed.

Hope this helps,

Willem.

[rlegrand]

Hello,

It's a little bit what I thought ( about Requires enabled shutter ).

I have an other issue so I can't test now but I'll give you results as soon as my priority issue is fixed (hope it will fixed some day).

Impossible to acceed anymore to tasmota. I open a nex discusion for that.

Remark:

Using open/close durations seems logic but I guess it implies to specify the start/end positions ?

If yes, I'm not sure which command may be used for that, I wonder if I should open the shutter, then run "ShutterCalibration 100", close it, then run ShutterCalibration 0 ?

Thanks anyway for your help!

[treinenwimke]

Hi,

 ShutterCalibration is part of the shutter support. Don't use it if you're using these rules, or use it and delete the rules. Imho you can't use both at the same time, it gets messy.

I'm only using my rules with the PulseTime set as explained before. As my shutters have end-stops, the PulseTime is only used (in my case) to reset the up- and down-buttons within a set time.

I have some other rules in place (to set the shutters in a given position f.i.) but they all rely on timer functions (Timer#) in collaboration with variables (Var# and Mem#). And it's working great.

Hope you get it fixed!

[rlegrand]

Ok,thanks taking the time to answer !

Shutter support or not, I think I did a mistake and my idea was impossible to implement, this is what I had in mind:

* raise the shutter and tell tasmota that this is the starting point

* then tell it the durations to raise and lower the shutter

=> From that, it could have been totally independant even if the shutter doesn't stop automatically

But anyway, I think it's not possible to do it that way (or I haven't understood how).

Let me ask you another thing which is maybe not relative to tasmota ( because I see you have some knowledge about shutters).

At first (before your answer), I didn't even know that the motor would stop on its own ( I have never installed electric shutters by myself ).

And now I'm confused, because before I changed my shutter switch, with the previous one, the shutter was stopping correctly on top/bottom positions.

Actually it's only working fine at bottom, and I don't understant why that behaviour changed when I changed the switch.

The only idea I've got is that it could be related to that: https://tasmota.github.io/docs/Commands/#power-monitoring

I'm curious to have your opinion.

Yep the other point is fixed thanks ;)

[treinenwimke]

Hi,

First about the power monitoring: I think it has nothing to do with the shutters, but if you want to be sure, just switch it off.

Then the stops at the top and bottom: I don't know what type of switch you were using before, but maybe you can post the make and model and we can have a look at that. I myself used some simple X10 switches before I switched to Tuya with Tasmota.

Below I'll give you an example of what I'm using now but first some explanation.

Basically my shutters have 5 standard positions:

• fully open - event 'HOOG' - 0% closed
• anti-theft - event 'DIEF' - 25% closed
• half open - event 'HALF' - 50% closed
• night state - event 'KIER' - 75% closed
• fully closed - event 'LAAG' - 100% closed

To use these settings in my system I defined several rules. These rules can be used by the built-in timers and with MQTT.

Now for the rules. 

I live in the Netherlands so my rules contain some words you might not recognise, but don't worry those are only names I use for the events I created. You can replace them with your own names.

Rule1

on EVENT#DIEF do backlog var1 %mem1%; event HOOG; event WAIT=DNTI endon 

on EVENT#HALF do backlog var1 %mem3%; event HOOG; event WAIT=DNTI endon 

on EVENT#KIER do backlog var1 %mem2%; event LAAG; event WAIT=UPTI endon 

on EVENT#GAAT do backlog var1 %mem4%; event LAAG; event WAIT=UPTI endon 

on EVENT#HOOG do backlog Power2 1; delay 3; Power1 1 endon 

on EVENT#LAAG do backlog Power2 1; delay 3; Power3 1 endon 

on EVENT#STOP do backlog Power2 1; delay 3 endon

 

Rule2

on CLOCK#Timer=1  do event DIEF endon 

on CLOCK#Timer=2  do event KIER endon 

on CLOCK#Timer=3  do event LAAG endon 

on CLOCK#Timer=4  do event HOOG endon 

on CLOCK#Timer=5  do event DIEF endon 

on CLOCK#Timer=6  do event KIER endon 

on CLOCK#Timer=7  do event LAAG endon 

on CLOCK#Timer=8  do event HOOG endon 

on CLOCK#Timer=9  do event GAAT endon 

on CLOCK#Timer=10 do event HALF endon

Rule3

on EVENT#DNTI do backlog Power3 1; delay %var1%; Power3 0 endon 

on EVENT#UPTI do backlog Power1 1; delay %var1%; Power1 0 endon 

on EVENT#WAIT do backlog delay %mem5%; event %value% endon 

 These are the values I use for the counters in Mem:

Backlog MEM1 30; MEM2 60; MEM3 60; MEM4 33; MEM5 222

 

And finally the timer setting (one of them):

Timer1 {"Arm":1,"Mode":0,"Time":"07:45","Window":00,"Days":"1111111","Output":2,"Repeat":1,"Action":3}

Now, the above timer fires at 7.45, every day, and fires the event named 'DIEF' (see Rule2). In event 'DIEF' the value of 'Mem1' (30) is loaded into 'Var1', event 'HOOG' is fired (w/o a value) and event 'WAIT' is fired with the value 'DNTI' (see Rule1).

In event 'HOOG' the Power2 relay is switched to 1 and by doing this the Up and Down relays will be switched Off (due to setting InterLock 1,2,3; InterLock on); then there is a small delay and Power1 is set to 1 (so the shutter goes up, in my case, as the <> button is setting Power1).

Event 'WAIT' is fired with value 'DNTI' and first there is a delay with the value in 'Mem5' (222 which means 22.2 seconds). These 22.2 seconds is the time my shutter needs to travel from completely closed to completely open + 1 extra second for safety. After the delay, the event 'DNTI' is fired ('DNTI' is the value we supplied to 'WAIT', see Rule1).

Event 'DNTI' first switches on Power3 (shutter goes down) and then waits for the delay in 'Var1' to finish; At last it switches off Power3 and the shutter stops in the required position.

These rules work very well for me because due to the excellent workings of the timers in Tasmota my shutters stop within only a few (1 or 2) millimeters every time.

 

i hope this gives you an idea and feel free to ask if something isn't clear. It's possible there are other (better) ways to do this, but this was designed about 2 years ago and since then it's working great, so no need for me to change it.

BR//Willem.

[rlegrand]

Ok,

Thank you.

For the shutter which doesn't stop, I will let it for some time. I doubt this was due to the switch because it was an old somfy switch ( don't have the model anymore ). It's inexplicable at this point :)

For your rules details, thanks a lot, I'm sure it will help ;)