Hey all, first of all warm thanks to 3dg1luk43 for the awesome work!
And now a question: in my case detection of a wash program (short wash, 30min) takes around 15min (it is now the only program assigned to the existing cycles, so the detection is right) and even after that the total and remaining durations remain 'unknown' for another like 3-5min. Is there a way to accelerate detection and the interval of duration sensor updates?
BTW I have a working integration with the time bar, just in case you guys are interested:
And a tiny wrapper template sensor (used above) to return 0 as a duration instead of 'unknown' as the timer bar card does not like 'unknown', even if the active state is not yet reached:
- sensor:
- name: WashDryer Run Duration
unique_id: washdryer_run_duration
unit_of_measurement: min
device_class: duration
state: >-
{% set s = states('sensor.washdryer_total_duration') %}
{{ s | int(0) if s not in ['unknown', 'unavailable', 'none', None] else 0 }}
availability: >-
{{ has_value('sensor.washdryer_total_duration')
or is_state('sensor.washdryer_total_duration', 'unknown') }}
I'm really interested in giving this a try, can anyone suggest a decent UK smart plug - ideally zigbee? that is suitable for the loads (current etc) of a washing machine?
Love this integration, works great on my washer, but my dryer seems a bit finicky. What setting do I need to look for to keep these cycles from going on forever? The only one that I got right was the first one because I manually stopped it when it finished.
Ive been loving this since installing a few months ago and the new update is
However I seem to be unable to have any data for my Samsung heat pump dryer as it doesnt seem to utilise instantaneous power readings only overall consumption is there anything i can do for this please (other than putting it onto a smart plug)?
Ok so i,am using this addon for along time now and seen it evolve from a simple plugin to a very nice dashboard with lots of features. but i,am getting really annoyed and stuck with this new version.
I have data from about 200 wash cycles of my machine already stored and still the app does not have a clue what cycle we use most often.
i have 3 progams that we use the cotton program with 180+ cycles recorded the short program with about 10 cycles recorded and the clean machine progam with about 10 cycles on it.
But still the program never ever detects the cotton program correctly beacuse the time the cotton program takes is different for every cycle becasue it depents on the amount of stuff in the drum.
Also with the new updates the app advices me to put in a wait time after the cycle is finished of 6000 seconds!!! when i wash i want to wash multi cycles after each other and not wait 6000 secondes for the app to hopefully detect the cycle is done…
Anyway i put the time back to 60 seconds and the machine is off now for over 30 min and it is still detecting it as being in use… i have no clue what to do about this???
I don,t want to start over everytime a new update comes out of the app and i also dont want to force stop every cycle manually can some one point me in the right direction how i can setup my washdata so it will detect within minutes instead of hours that the cycle is done?
I as about to go and update to 0.5.3 after the fixes for slowness with 0.5.0/1/2, but I did see this about the extra wait time which I am not sure about. So +1 for understanding how/why this is needed on top of the usual settings for end of cycle.
I only discovered this add-on today, and I have a few questions:
Do I need to record each washing program five times for it to work reliably?
Is it possible to display a progress bar on my Home Assistant dashboard that shows the current progress of the washing cycle, along with the estimated time remaining? If so, could someone please explain how to set it up? @3dg1luk43
I have this integration up and running, 9 cycles for my dryer and 13 for my washing machine, but my dryer has a sensor so it doesn’t take the same time every cycle because it depends on load and moisture.
How can I let WashData still predict the remaining time?
The profile is labled as “poor quality” because the durations are so wildly different…
is there any changes or option within the integration for this integration have option to measure/detect Option/Modes only base on wattage only without time/lengmesurement for labeling cause i’m using this for Stupid Fan it’s mostly get success so far but i think it can label better or detect mode better without the length params of course not remove completly cause i mean it;s still need to run for a while to label the “cycles” / mode correctly
BTW love your work, i use your integration for Stupid Devices with cycles base it’s fantastic, currently using for my Washing machine, air-fryer, dryer, oven, microwave,dishwasher