Weird behavior for/on notification with delay

Moderator: leecollings

Post Reply
jotheman
Posts: 4
Joined: Sunday 23 May 2021 22:41
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Weird behavior for/on notification with delay

Post by jotheman »

Version: 2021.1 (build 13256), beta
Platform: Raspbian (RPi 4)
Hardware: Quite some, not sure it's relevant, can provide info if useful of course
Description:
I use blockly for a couple of timers with which I validate whether my dryer, washing machine and dishwasher have finished.
This works fine for both the washing machine and the dishwasher. I check whether the smartplugs use less than ~5W or something of power. If so for a few minutes and the device was active (>100W of usage) before that time, I let them send me a message. This works perfectly/flawlessly for both the washing machine as well as the dryer. Both are done after the power is lower than like 5W for around 5 minutes.

Here comes the weird part: I use the exact same events/setup for the dishwasher, but it doesn't work and I cannot figure out why.
I have a smartplug and check whether power usage is below 5W for 35 minutes (2100 seconds) before sending a signal (after it's done it has a literal "cooldown" before of 35 minutes for the dishes to cool down, after which it starts beeping). I can see this is in the powerusage of the smartplug and I think it should be fine. The weird thing is, after those 35 minutes it does not send a message. Here's where it gets really weird: If I change the timeout to send a message to like ~30 seconds it does send the signal. And additionally: If I completely turn of the dishwasher (so I push the power button of the dishwasher itself, like I normally would once it starts beeping its done) then ~35 minutes later the message does seem to go out!
Initially I thought it was probably due to the fact that it was still drawing more power sometimes, but if it does work if I change the timer/wait to those 30 seconds it does work, soI cannot, for the life of me, correlate the two! Can this be a bug or am I missing something?

The three blockly events are shown here:
Image
If the image doesn't work straight from OneDrive, see this link:https://1drv.ms/u/s!AiGVwbbzCHrZirE7eQC ... Q?e=mDTOjs

Again, this exact same setup works perfectly for washer and dryer where the only thing different is the timeout being under 350 for both of them.
Help is very much appreciated!
User avatar
waaren
Posts: 6028
Joined: Tuesday 03 January 2017 14:18
Target OS: Linux
Domoticz version: Beta
Location: Netherlands
Contact:

Re: Weird behavior for/on notification with delay

Post by waaren »

jotheman wrote: Sunday 23 May 2021 23:04 Help is very much appreciated!
First step would be to add some extra log statements in the Vaatwasser check klaar do areas. This will help identifying what happens.
Have you tried to add Var S-Z [Vaatwasser aan] = 0, directly after Var S-Z [Vaatwasser klaar] = 1 after 2100 seconds ?
That will make sure Vaatwasser check klaar will not do any action until Vaatwasser aan detectie see a value > 100 Watt
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest