I'm not getting the "cycle done" message in the logs. I've only been using it for a week so I'm on the latest version. When I initially tried it, it ran through the entire cycle and did the echo notifications. Now it just stops after 1st delay. Not sure what to do at this point, maybe just delete the app and start over.
If you don't get further Power Reports from your sensor, then it will wait there 'forever'.. or to the Max Cycle time (deadman).
I ran a test yesterday using a pseudo Power Sensor driver I created. It allows me to simply set values for Power manually. I have the Thresholds set to:
Using the latest driver, I got these Logs:
app:103 2020-01-17 09:46:52.209 am debug Cycle finished after delay. app:103 2020-01-17 09:46:52.187 am debug fixed: today at 9:46am app:103 2020-01-17 09:46:52.123 am debug send: BLM says Washer Cycle ended dev:151 2020-01-17 09:42:12.695 am trace pseudoWasher setPowerLevel 0 app:103 2020-01-17 09:41:51.992 am debug Ending duration is set, waiting app:103 2020-01-17 09:41:51.944 am debug Power: 0W, State: true, thresholds: 5.0 2.0 2 1500.0 dev:151 2020-01-17 09:41:51.825 am trace pseudoWasher setPowerLevel 0 app:103 2020-01-17 09:41:47.378 am debug We hit delay 1 times app:103 2020-01-17 09:41:47.336 am debug Power: 1W, State: true, thresholds: 5.0 2.0 2 1500.0 dev:151 2020-01-17 09:41:47.214 am trace pseudoWasher setPowerLevel 1 app:103 2020-01-17 09:41:40.022 am debug We hit the delay 1 times but cleared it app:103 2020-01-17 09:41:39.996 am debug Power: 5W, State: true, thresholds: 5.0 2.0 2 1500.0 dev:151 2020-01-17 09:41:39.879 am trace pseudoWasher setPowerLevel 5 app:103 2020-01-17 09:41:28.168 am debug We hit delay 1 times app:103 2020-01-17 09:41:28.139 am debug Power: 0W, State: true, thresholds: 5.0 2.0 2 1500.0 dev:151 2020-01-17 09:41:28.046 am trace pseudoWasher resetPower app:103 2020-01-17 09:41:21.916 am debug We hit the delay 1 times but cleared it app:103 2020-01-17 09:41:21.887 am debug Power: 5W, State: true, thresholds: 5.0 2.0 2 1500.0 dev:151 2020-01-17 09:41:21.769 am trace pseudoWasher setPowerLevel 5 app:103 2020-01-17 09:41:12.723 am debug We hit delay 1 times app:103 2020-01-17 09:41:12.685 am debug Power: 1W, State: true, thresholds: 5.0 2.0 2 1500.0 dev:151 2020-01-17 09:41:12.592 am trace pseudoWasher setPowerLevel 1 app:103 2020-01-17 09:41:05.255 am debug Power: 2W, State: true, thresholds: 5.0 2.0 2 1500.0 dev:151 2020-01-17 09:41:05.141 am trace pseudoWasher setPowerLevel 2 app:103 2020-01-17 09:40:56.459 am debug Power: 5W, State: true, thresholds: 5.0 2.0 2 1500.0 dev:151 2020-01-17 09:40:56.317 am trace pseudoWasher setPowerLevel 5 app:103 2020-01-17 09:40:46.229 am debug Cycle started. app:103 2020-01-17 09:40:46.218 am debug fixed: today at 9:40am app:103 2020-01-17 09:40:46.134 am debug send: BLM says Washer Cycle Started app:103 2020-01-17 09:40:46.113 am debug Power: 166W, State: false, thresholds: 5.0 2.0 2 1500.0 dev:151 2020-01-17 09:40:45.933 am trace pseudoWasher setPowerLevel 166 --- Live Log Started, waiting for events ---
What you can see is I set the power to validate the thresholds... Above 5 (166W) to start the cycle. Then a simulation of the dryer stopping for cool down, restarting (fluff?), and finally ending.
166W
5W
2W
1W
5W
0W (reset power)
5W
1W
0W
0W (second 'report' of a zero)
You can see two send: messages, a start and an end, the end is 5 mins after "Ending duration is set, waiting" -- everything is as expected.
@csteele What does your application state look like when the monitor isn't active? This is mine...
I'm assuming that CycleEnd is an integer date and it corresponds to the last time when the monitor thought that a cycle ended, which in this case would be last Monday 1/13 at 12:42pm. It's correct, a cycle did end then, but there were two cycles ran yesterday 1/17 that it never saw as ending. In the debug logs it shows both starting but no end.
cycleOn means that it thinks there is still an active cycle?
So my next question, is why would it not think that the cycle has ended? If the power monitor drops below 2W for 1 reporting, that should signal cycle end. The power monitor (it is a Wemo Insight using the Wemo connect app) is still showing power: 0 on the device page. So I'm still not getting how the monitor thinks there is an active cycle with 0 power being drawn.
Thanks for your help.
OK I get it now. I've got a different version of this app. I'm gonna delete it and take the one from the community github.
