1) Give a description of the problem
The case of the hyperactive laundry monitor, alerts too soon during a wash and alerts when the washer isn’t even on.
2) What is the expected behavior?
I have one of the AEON Labs Home Energy Monitor HEM v. 1. I’m using the dual clamps DH, one for the washer and one for the dryer. The washer wattage is all over the map, the Fuel Stream shows standby power between 8w-14w. Operational wattage is generally above 50w, with occasional spikes down to as low as 14w. Spikes rarely last more than 1 30 second measurement, never seen 3 in a row. Most pistons for this setup are able to work when the power goes on, the HEM button gets pushed and when it’s done, that button is held. However, given the random spikes and dips I need to control for those in the piston.
This Piston monitors the HEM. Ideally it only flashes the lights and sends a text only after the wattage is high for 3 30 second readings and then dips down below the threshold for 4 30 second readings – when it’s been on for a while then done.
3) What is happening/not happening?
Seems to be ignoring the need to start the counting over if the button is held (because it’s ostensibly done) before it’s had at least 3 high readings. Seems to be alerting me before it’s had 4 low readings.
Been really fun to figure out the logic how to get this to work correctly, but I’m clearly missing the right commands to get it to do what it needs to.
4) Post a Green Snapshot of the piston
5) Attach any logs (From ST IDE and by turning logging level to Full)
1/16/2018, 8:47:00 PM +299ms +1ms ╔Received event [Home].time = 1516153621466 with a delay of -1168ms +270ms ╚Event processed successfully (269ms) 1/16/2018, 8:46:54 PM +448ms +1ms ╔Received event [Home].time = 1516153615978 with a delay of -1530ms +2023ms ║Setting up scheduled job for Tue, Jan 16 2018 @ 8:47:01 PM EST (in 4.996s) +2031ms ╚Event processed successfully (2030ms) 1/16/2018, 8:46:44 PM +522ms +1ms ╔Received event [Laundry Monitor].button = held with a delay of 353ms +6460ms ║Setting up scheduled job for Tue, Jan 16 2018 @ 8:46:55 PM EST (in 4.997s) +6467ms ╚Event processed successfully (6468ms) 1/16/2018, 8:46:04 PM +125ms +1ms ╔Received event [Home].time = 1516153565808 with a delay of -1684ms +294ms ╚Event processed successfully (293ms) 1/16/2018, 8:45:54 PM +367ms +0ms ╔Received event [Home].time = 1516153555566 with a delay of -1200ms +6572ms ║Setting up scheduled job for Tue, Jan 16 2018 @ 8:46:05 PM EST (in 4.869s) +6581ms ╚Event processed successfully (6581ms) 1/16/2018, 8:45:44 PM +164ms +1ms ╔Received event [Laundry Monitor].button = pushed with a delay of 115ms +6406ms ║Setting up scheduled job for Tue, Jan 16 2018 @ 8:45:55 PM EST (in 4.997s) +6413ms ╚Event processed successfully (6413ms) 1/16/2018, 7:48:04 PM +173ms +1ms ╔Received event [Home].time = 1516150085218 with a delay of -1047ms +258ms ╚Event processed successfully (259ms) 1/16/2018, 7:47:54 PM +352ms +1ms ╔Received event [Home].time = 1516150075321 with a delay of -970ms +5873ms ║Setting up scheduled job for Tue, Jan 16 2018 @ 7:48:05 PM EST (in 4.994s) +5929ms ╚Event processed successfully (5928ms) 1/16/2018, 7:47:43 PM +952ms +0ms ╔Received event [Laundry Monitor].button = held with a delay of 306ms +6373ms ║Setting up scheduled job for Tue, Jan 16 2018 @ 7:47:55 PM EST (in 4.997s) +6382ms ╚Event processed successfully (6382ms) 1/16/2018, 7:47:35 PM +430ms +0ms ╔Received event [Home].time = 1516150056236 with a delay of -807ms +457ms ╚Event processed successfully (457ms) 1/16/2018, 7:47:24 PM +421ms +1ms ╔Received event [Home].time = 1516150045331 with a delay of -910ms +6834ms ║Setting up scheduled job for Tue, Jan 16 2018 @ 7:47:36 PM EST (in 4.982s) +6843ms ╚Event processed successfully (6843ms) 1/16/2018, 7:47:13 PM +924ms +1ms ╔Received event [Laundry Monitor].button = pushed with a delay of 288ms +6411ms ║Setting up scheduled job for Tue, Jan 16 2018 @ 7:47:25 PM EST (in 4.997s) +6418ms ╚Event processed successfully (6418ms)