Below is a link to OneDrive Shared Excel spreadsheet of the full (ie "Filter Same Value Responses" off) dump of last night's Axle event (20-00 to 21-00):
- @admin: you are correct, the WW discharge message set is now visible and does not change values
-Axle is doing a number of reads that I did not see before. It looks like most of these are to confirm that parameter changes have worked, bu also some reading of "battery paused" during the event; I am not sure why this is?
-I cannot see the Axle parameter read before the 8pm start, but from previous events this looks like it takes place during the 30mins leading up to the Axle event.
@admin: I did not do any manual disabling and the WW disabling of schedules in the 2hrs ahead of the Axle event works brilliantly and shows in the log (screen shot attached) - this solves the only comms duplication issue where Axle reads from discharging state ahead of the Axle event and then resets to the discharging state after the Axle event.
However, depending on the time of the Axle event I need a longer period than 2hours ahead of the Axle event. In this case my battery was exhausted at 8-30pm, half way through the Axle event (see GE power graph image attached) - a 3hr disabling period would have done the trick last night, but this very much depends on time of the Axle event - any thoughts?
Great work WW team; I really appreciate the speed and interaction on making this integration work.
Dave
OneDrive link to comms history spreadsheet (please let me know if the link does not work)
https://1drv.ms/x/c/1fc508ba74055982/IQDywA-RzPOjQoAvm5fKzzSEATZYu1FA5tkC9fo1UKll1rg?e=pJhCMv
