admin The fix is to not run any custom schedule export start/stop/reset commands for any custom export schedule that partially covers an Axle event.
They won't be paused, but basically skipped because Axle will take priority.
WOW!!! That will be something when that is released. I would definitely want total hands off scheduling with Axle, as I have now, other than when the GE API has a parsing fit of course. I just ned to get over the double sets of commands issue (if that's the case).
I do think though it is so complex what WW is doing here, overriding all other schedule types etc, That you do need a few notes in the Axle section of WW to remind users what the consequences of Axle Activation are, what will not run and why, otherwise it will become a support nightmare. As I can't remember already what you stated it will overide. 😂
All in all it's a pretty slick integration that makes WW even more value for money.
Great work @admin and thanks for answering on a Weekend, Top Support as always. Thank You 😁
