This object is in archive!
rule E-Mail when dish-washer finished
Under Consideration
Hello Community!
I want to creat this rule. When dish-washer finished, a Mail was sent to my Mailadress.
It should work with a Fibaro Wall-Plug.
Some idea?..
Clemens
I like this idea 
No connection
Real-time notifications may not work
Do you have a curve of the consumption (A) AMPs.... ????
Then you can se the different stages of the washing and I can help you creat a rule from that. Best regards.
I need this:
Graf over konsumtion over time.
This is how it looks with my TV/ home cinema and a Fibaro wall plug:
Jacob!
Do you have a curve of the consumption (A) AMPs.... ????
Then you can se the different stages of the washing and I can help you creat a rule from that. Best regards.
I need this:
Graf over konsumtion over time.
This is how it looks with my TV/ home cinema and a Fibaro wall plug:
Jacob!
And set the Zoom to 1 day or 1 hour!
And set the Zoom to 1 day or 1 hour!
Hello Jacob!
Thx for help me. This is the curve.
Wall-p plug always on.
Hello Jacob!
Thx for help me. This is the curve.
Wall-p plug always on.
the lowest point of curve is 4,7
the lowest point of curve is 4,7
When the first peek in current aper how long tim until the last high current consumption. Why because the rule have to use the high current consumption in the end to determine when it ends. You could also put a wait block so you know exactly when it stops.
I can imagine two ways to do this. Current or time that tells you when it is finished, and combination of bothe. But the trigger I think have to be the high current, and the trigger for when its about to end is time plus when going from high current to low current. But this you can experiment with.
I am not that good at rules but please tell me if this works:
Maybe someone els have a rule for this.
When the first peek in current aper how long tim until the last high current consumption. Why because the rule have to use the high current consumption in the end to determine when it ends. You could also put a wait block so you know exactly when it stops.
I can imagine two ways to do this. Current or time that tells you when it is finished, and combination of bothe. But the trigger I think have to be the high current, and the trigger for when its about to end is time plus when going from high current to low current. But this you can experiment with.
I am not that good at rules but please tell me if this works:
Maybe someone els have a rule for this.
https://community.zipato.com/topic/useful-rules-post-your-rules-here
https://community.zipato.com/topic/useful-rules-post-your-rules-here
hey Jacob that look good, but what happens if your timer is out, say the cycle takes only 1 hour for a quick rinse?
I made this up, not sure if it works but would love for you to try it and let me know. Basically it starts when the dishwasher starts and will test after one hour, then repeat testing every 10 minutes another 10 times. Of course this can be modified to sync with your cycles better, but you get the idea. this way you could have a short wash cycle of less than 1 hour and it will keep checking up to 2 hours 40 minutes after it starts to see when it ends.
hey Jacob that look good, but what happens if your timer is out, say the cycle takes only 1 hour for a quick rinse?
I made this up, not sure if it works but would love for you to try it and let me know. Basically it starts when the dishwasher starts and will test after one hour, then repeat testing every 10 minutes another 10 times. Of course this can be modified to sync with your cycles better, but you get the idea. this way you could have a short wash cycle of less than 1 hour and it will keep checking up to 2 hours 40 minutes after it starts to see when it ends.
It is so nice to see all those intelligent people cocking up rules. I have decided to use the TV Plugin to the dishwasher instead, just to try this function. Wife will be happy. Man home with the Dishwasher. Perfect.
It is so nice to see all those intelligent people cocking up rules. I have decided to use the TV Plugin to the dishwasher instead, just to try this function. Wife will be happy. Man home with the Dishwasher. Perfect.
Hi tried to ad a message when the dishwasher started but that did not work that good. I keep getting messages now and then. Pleas help!
I also tried to add message when the dishwassher was completely turned of meaning < 0.5 A but the repeat element complained?
How can I add that to?
Best regards Jacob Wiqvist
Hi tried to ad a message when the dishwasher started but that did not work that good. I keep getting messages now and then. Pleas help!
I also tried to add message when the dishwassher was completely turned of meaning < 0.5 A but the repeat element complained?
How can I add that to?
Best regards Jacob Wiqvist
I can not see any power dip so I can't understand why the message Dishwasher started message keap coming?
I can not see any power dip so I can't understand why the message Dishwasher started message keap coming?
Jacob, the repeat puzzle does not work. At least it does not work for me.
Jacob, the repeat puzzle does not work. At least it does not work for me.
And I keep getting Push messages? And I have no ide why.
But I can't imagine that this can have with the repeat puzzle to do?
And I keep getting Push messages? And I have no ide why.
But I can't imagine that this can have with the repeat puzzle to do?
Pleas help me create the perfect rule for my dishwasher. The problems I have now is that the rule keps sending Push that the machine was on every third and tenth minut. And that it tok ten minuts until the push was sent that the machine was of.
What I want is this.
1) Send push when machine is started. Reliable. Not if you turn power on and the machine is in standby.
2) Send Push when machine is ended with in 2-5 minuts.
3) Repet send messages every 10 minuts, after the machine has ended that the "power is not turned off", to reduce risk of fire. Continue this for at least one hour.
This as god info abut the machine as possible. I use two wash programs, one with 60 C and one with 70.
18:17 = Dishwasher Started
19:34 = Dishwasher finished in reality
19:44 sent push about finished
7,6 Watts at pump start
2033 Watts at start
0.5-1 standby
0.0-0.1 turned of on power button
Very dirty Wash program 70 C = 150-170 minuts
Normal Wash program 70 C = 120-130 minuts
This was the hot and long wash program 70 degrees. I think this is all the info. Pleas help best regards!
Pleas help me create the perfect rule for my dishwasher. The problems I have now is that the rule keps sending Push that the machine was on every third and tenth minut. And that it tok ten minuts until the push was sent that the machine was of.
What I want is this.
1) Send push when machine is started. Reliable. Not if you turn power on and the machine is in standby.
2) Send Push when machine is ended with in 2-5 minuts.
3) Repet send messages every 10 minuts, after the machine has ended that the "power is not turned off", to reduce risk of fire. Continue this for at least one hour.
This as god info abut the machine as possible. I use two wash programs, one with 60 C and one with 70.
18:17 = Dishwasher Started
19:34 = Dishwasher finished in reality
19:44 sent push about finished
7,6 Watts at pump start
2033 Watts at start
0.5-1 standby
0.0-0.1 turned of on power button
Very dirty Wash program 70 C = 150-170 minuts
Normal Wash program 70 C = 120-130 minuts
This was the hot and long wash program 70 degrees. I think this is all the info. Pleas help best regards!
Looks like you need at least one variable or virtual switch here to memorize the machine has started, then you can trigger the message for ON and OFF (after a delay). The way I would probably first approach this is;
1. First rule will turn ON a virtual switch or variable set to 1 (lets say Dishwasher_InCycle) when the dishwasher consumes more than 7 Watts, to have a built in delay and if the consumption goes below this treshold then turn this switch off.
2. Same as above but for standby consumption and taking in consideration that if Dishwasher_InCycle is ON then this switch/variable cannot be ON (lets say Dishwasher_Standby). When both this switches are OFF then you know the dishwasher has been turned OFF.
3. A rule to manage the alerting part of this based on combination of switches.
4. As for the repetitive alerts you can probably get away with it using a Repeat puzzle and within an IF puzzle to check consumption on every iteration. DO NOT ADD A JOIN puzzle on this rule otherwise it will never work. Also it might not work the first time you enable this rule due a known bug on Zipato system.
I don't have a relay to connect my dishwasher to, but I would like to do it. Let me know how your tests go, when I get the relay I will give it a shot. Regards.
Looks like you need at least one variable or virtual switch here to memorize the machine has started, then you can trigger the message for ON and OFF (after a delay). The way I would probably first approach this is;
1. First rule will turn ON a virtual switch or variable set to 1 (lets say Dishwasher_InCycle) when the dishwasher consumes more than 7 Watts, to have a built in delay and if the consumption goes below this treshold then turn this switch off.
2. Same as above but for standby consumption and taking in consideration that if Dishwasher_InCycle is ON then this switch/variable cannot be ON (lets say Dishwasher_Standby). When both this switches are OFF then you know the dishwasher has been turned OFF.
3. A rule to manage the alerting part of this based on combination of switches.
4. As for the repetitive alerts you can probably get away with it using a Repeat puzzle and within an IF puzzle to check consumption on every iteration. DO NOT ADD A JOIN puzzle on this rule otherwise it will never work. Also it might not work the first time you enable this rule due a known bug on Zipato system.
I don't have a relay to connect my dishwasher to, but I would like to do it. Let me know how your tests go, when I get the relay I will give it a shot. Regards.
Will try during the day.
Will try during the day.
8-)
8-)
I thought I hade it but it does not seam to work...... The rule that should set the dishwasher finished does not work. (RULE NR. 94) on the picture above???????
Is there any conflict that you can se? Even when the current consumption is under 1.2 and the button "DM START" is on for more than 120 seconds the "DM FÄRDIG" does not get set.
Why have I used 120 seconds and a join element. Because I don't want the rule to get sent during the wash cycle because it briefly is under 1.2 W current.
One more thing is why is numbers reported in W but the text say current. Should the text not say WATT_CONSUMTION???? ZIpato???? A bug?
As I understand it if I remove the join block it would send the "DM FINISHED" command every time the current change as long as it under 1.2W and then I would get a lot om messages abut DM finished witch is not right? And the "<=" this means less then or equal to? Right?
If any one have a solution to rule number 94 I would be great full?!
I thought I hade it but it does not seam to work...... The rule that should set the dishwasher finished does not work. (RULE NR. 94) on the picture above???????
Is there any conflict that you can se? Even when the current consumption is under 1.2 and the button "DM START" is on for more than 120 seconds the "DM FÄRDIG" does not get set.
Why have I used 120 seconds and a join element. Because I don't want the rule to get sent during the wash cycle because it briefly is under 1.2 W current.
One more thing is why is numbers reported in W but the text say current. Should the text not say WATT_CONSUMTION???? ZIpato???? A bug?
As I understand it if I remove the join block it would send the "DM FINISHED" command every time the current change as long as it under 1.2W and then I would get a lot om messages abut DM finished witch is not right? And the "<=" this means less then or equal to? Right?
If any one have a solution to rule number 94 I would be great full?!
So close.....
Now I get the "DM_FINNISHED" Push, but I got it during the wash cycle. Cant understand why? Because it should only be sent if the current consumption is under 1.2W more then 120 seconds. And when I look at the graph it does not lock like that.
This is a short 30 min wash cycle.
This two curves is when I got the message "DM FÄRDIG" witch means dishwasher finished.
And what I can se the consumption is not under 1.2 for more than 120 seconds? What have I missed?
So close.....
Now I get the "DM_FINNISHED" Push, but I got it during the wash cycle. Cant understand why? Because it should only be sent if the current consumption is under 1.2W more then 120 seconds. And when I look at the graph it does not lock like that.
This is a short 30 min wash cycle.
This two curves is when I got the message "DM FÄRDIG" witch means dishwasher finished.
And what I can se the consumption is not under 1.2 for more than 120 seconds? What have I missed?
And no push sent DM OFF but the virtual switch went on 12:56 and now when writing, 13:00 still no push???
And no push sent DM OFF but the virtual switch went on 12:56 and now when writing, 13:00 still no push???
Well Jacob, seems to me that this is a timing issue. I will try a different approach using a bulb and a qubino flush relay. I will create a simulator for changing intensity on bulb based on your dishwasher behaviour and let you know my findings.
Well Jacob, seems to me that this is a timing issue. I will try a different approach using a bulb and a qubino flush relay. I will create a simulator for changing intensity on bulb based on your dishwasher behaviour and let you know my findings.
Defiantly something wrong with the rule.
I forgot some cups and opened the "DM" and put them in the cups, the power consumption was sinking and then I closed and it started again. After 2 minuts I gott message "DM" finished. Even tho the machine was consuming 2K Watt?
The strange thing is that I have copied a rule that works. And it does not send any message until the door have bin opened more than 2 minuts.
I will do some more tests with time, but so far it does not work.
Defiantly something wrong with the rule.
I forgot some cups and opened the "DM" and put them in the cups, the power consumption was sinking and then I closed and it started again. After 2 minuts I gott message "DM" finished. Even tho the machine was consuming 2K Watt?
The strange thing is that I have copied a rule that works. And it does not send any message until the door have bin opened more than 2 minuts.
I will do some more tests with time, but so far it does not work.
wow! Very difficult! I thought this rule was easier. But I went wrong!
And i have no idea. Is a description existing, which describes all Puzzleparts? Anywhere in the web, maybe?
wow! Very difficult! I thought this rule was easier. But I went wrong!
And i have no idea. Is a description existing, which describes all Puzzleparts? Anywhere in the web, maybe?
I really think this is a problem of timming (meaning that the update rate of the power meter may be too slow for the rule to work or using the right conditions within the WHEN block). In order achieve your objective I set 3 rules.
Rule 17 - It is only a simulator of a dishwasher cycle, I did it so it didn't have to take much time to test every time but still enough time in my opinion for the power meter to send updates to the controller (in this case is more of change percentage than update rate). You wont need this rule since you have the dishwasher.
Rule 18 - This is the rule that will detect when the dishwasher started it's cycle, and will set the virtual switch ON/OFF accordingly. ON - In Cycle, OFF - Not in Cycle.
Rule 19 - Sends message when done. The first problem I've found was to use the proper condition within the WHEN statement, then I got as far as this but for some reason the alerts takes way more time to be sent to my phone, and then for some reason it kept sending push notifications randomly even if my IN_CYCLE switch was already OFF. Not sure why but also may be the fact that my box has been experiencing reboots after I added a phillips hue bridge.
Also the two virtual switches you see, the first one was to "start the dishwasher" (first rule), second one to memorize the dishwasher is "IN CYCLE". I will keep making tests and I got more relays, maybe I will test with my dishwasher this time. I will keep you posted on my findings. Feel free to ask or comment.
I really think this is a problem of timming (meaning that the update rate of the power meter may be too slow for the rule to work or using the right conditions within the WHEN block). In order achieve your objective I set 3 rules.
Rule 17 - It is only a simulator of a dishwasher cycle, I did it so it didn't have to take much time to test every time but still enough time in my opinion for the power meter to send updates to the controller (in this case is more of change percentage than update rate). You wont need this rule since you have the dishwasher.
Rule 18 - This is the rule that will detect when the dishwasher started it's cycle, and will set the virtual switch ON/OFF accordingly. ON - In Cycle, OFF - Not in Cycle.
Rule 19 - Sends message when done. The first problem I've found was to use the proper condition within the WHEN statement, then I got as far as this but for some reason the alerts takes way more time to be sent to my phone, and then for some reason it kept sending push notifications randomly even if my IN_CYCLE switch was already OFF. Not sure why but also may be the fact that my box has been experiencing reboots after I added a phillips hue bridge.
Also the two virtual switches you see, the first one was to "start the dishwasher" (first rule), second one to memorize the dishwasher is "IN CYCLE". I will keep making tests and I got more relays, maybe I will test with my dishwasher this time. I will keep you posted on my findings. Feel free to ask or comment.
Jacob,
I have good news. As I mentioned before, I was having problems with my box restarting unexpectedly, this after I added a phillips hue bridge and a few phillips hue bulbs, this a the same time I was testing your dishwasher rule, which didn't work properly. Zipato support told me they were going to upgrade my box to the latest beta firmware which solves the rebooting issue and some "virtual states" issues. If you upgrade and do the rules as I did, they work fine. I noticed you weren't using any virtual switch so I will try something like your rule but it can be tricky rule.
Jacob,
I have good news. As I mentioned before, I was having problems with my box restarting unexpectedly, this after I added a phillips hue bridge and a few phillips hue bulbs, this a the same time I was testing your dishwasher rule, which didn't work properly. Zipato support told me they were going to upgrade my box to the latest beta firmware which solves the rebooting issue and some "virtual states" issues. If you upgrade and do the rules as I did, they work fine. I noticed you weren't using any virtual switch so I will try something like your rule but it can be tricky rule.
Thank you for your mature and helpful answer very kind of you!
I will try to understand the rules and test them. But what software do you use before updat? And now? I use ....9.8.8x4
I am very grateful for your help!
By the way I use some virtual switches: "DM AV", "DM START" and so on. But I have changed the propertis of them so it doesn't say HTTP on them! Dont know if that afects things?
Best regards Jacob W
Thank you for your mature and helpful answer very kind of you!
I will try to understand the rules and test them. But what software do you use before updat? And now? I use ....9.8.8x4
I am very grateful for your help!
By the way I use some virtual switches: "DM AV", "DM START" and so on. But I have changed the propertis of them so it doesn't say HTTP on them! Dont know if that afects things?
Best regards Jacob W
I use a slightly easier approach with only one rule. Basically I am setting a low and high limit for Watt consumption (eg. is it in "a cycle" or not) and a timer for how long the washer should be in the low consumtion state before triggering the message that it is ready. Watch the full cycle of your dishwasher to determain the low, high and timer...
I use a slightly easier approach with only one rule. Basically I am setting a low and high limit for Watt consumption (eg. is it in "a cycle" or not) and a timer for how long the washer should be in the low consumtion state before triggering the message that it is ready. Watch the full cycle of your dishwasher to determain the low, high and timer...
Fantastic @Alberto Macias!
Your rules seam to work after first try. I added some rules to be able to have some flexibility and do more things with the push messages. Maybe I ad a virtual switch so I can turn off Push messages. There is defiantly powerful things you can do with Zipato and flexibility.
I like simpel but powerful rules Henrik, but I want messages when DM is started, is finished and is turned OFF.
Once again big thank you Alberto.
The only thing is that I have to think why my rules did not work. Could it be the "REFRESH ALL" element you put in?
Her ar my rules:
Best regards!
Fantastic @Alberto Macias!
Your rules seam to work after first try. I added some rules to be able to have some flexibility and do more things with the push messages. Maybe I ad a virtual switch so I can turn off Push messages. There is defiantly powerful things you can do with Zipato and flexibility.
I like simpel but powerful rules Henrik, but I want messages when DM is started, is finished and is turned OFF.
Once again big thank you Alberto.
The only thing is that I have to think why my rules did not work. Could it be the "REFRESH ALL" element you put in?
Her ar my rules:
Best regards!
Replies have been locked on this page!