But why install an integration when the Appliance Notifications and Actions blueprint exists?
I think the only functional difference is that Washdata attempts to infer which cycle was run, but the blueprint doesn’t have to be configured via yaml.
But why install an integration when the Appliance Notifications and Actions blueprint exists?
I think the only functional difference is that Washdata attempts to infer which cycle was run, but the blueprint doesn’t have to be configured via yaml.