Auto Mode no longer working in script - HP04

[xvlw]

I'm a bit of a new user for Home Assistant but I had managed to coble together some easy scripts to control my Dyson HP04

Up until recently and for most of the last year this very simple script was working :

Config : https://i.imgur.com/yoNpIJk.png
Visual Editor : https://i.imgur.com/ZXHFtQZ.png

For some reason it will no longer apply the auto setting once triggered, this is happening for all my scripts.

I then tried applying the switch directly (as I had seen closed issues from middle of 2021 about a move to switches from profiles

Config : https://i.imgur.com/cfAj7wv.png
Visual Editor : https://i.imgur.com/qCAHl9K.png

To me even though taking a different route through the visual editor the config is identical for both and both are using the recommendation ( switch.pure_hot_cool_auto_mode ) from this closed ticket : #49

Am I doing something wrong? Not sure what I broke in my script, it was working for most of the year.

Any help would be appreciated

[cmatte]

Experiencing the same here, and to be more specific both auto mode and front airflow are now showing as unavailable for Dyson Pure Cool.

[pbrunier]

I have exactly the same issue.
https://imgur.com/cAFSDu9

[Kakise]

Thank you for the report, it's clearly a regression from 0.15, I added it to the 0.17 roadmap

[xvlw]

Appreciate it.
Is there somewhere we can view the future roadmaps?

[qqaatw]

Exactly the same issue, looking forward to the fix. Thanks.

[Leonti]

Hi!
I've just installed the integration for TP04 and there are no controls to enable auto mode or front airflow:

Is it the same issue?

Also, when the TP04 is in AUTO mode and I switch it off and on again it starts with the fan setting set to 2 and not with the previous setting. Is it expected or is it a separate issue?

[Flameeyes]

Since this is mostly due to my changes that went into 0.16 — this is expected behaviour following Home Assistant best practices.

Auto mode and direction of fans is set on the control of the fan itself, rather than as separate toggle switches:

The fan.turn_on service provide access to the additional parameters:

For scenes this means that you'll have to remove and re-add the device for it to be started in the configuration you want.

[xvlw]

Using this I was able to fix my scripts.

[Leonti]

I can't believe I didn't try to click the Fan entity, I just thought it was a simple toggle ☺️
All good now, thanks for looking into this @Flameeyes!

[Kakise]

I'll add a section in the README regarding this issue.

[cvocvo]

Auto mode and direction of fans is set on the control of the fan itself, rather than as separate toggle switches:

@Flameeyes
Is it possible to get these toggles directly in a card? (avoiding the need to click into the entity to get them)

[Flameeyes]

You should be asking that upstream, I'm afraid.

I would generally be in favour of a "Fan" card view that would contain the settings, but I'm not sure if this is the right place to implement (particularly as we intend to merge the integration into core.)

[Kakise]

Auto mode and direction of fans is set on the control of the fan itself, rather than as separate toggle switches:

@Flameeyes Is it possible to get these toggles directly in a card? (avoiding the need to click into the entity to get them)

Now that the integration is to be merged in the HA core, the best thing would be to steer away this project from these kind of features as it should become a minimal working base on which you could build upon.

[xvlw]

Apologies about digging this back up, however I am still seeing a problem but now in Node Red when trying to recreate the above script.

After being able to sort out the Auto Mode I started building the automatons out in Node Red but I can't get it to trigger Auto Mode using switch.pure_hot_cool_auto_mode with fan.turn_on.

Am I missing something? It works fine using it in Home Assistant this way.

https://i.imgur.com/okZSg1v.png

[Flameeyes]

Your entity should be the fan entity, since the switch entity is no longer provided.

[xvlw]

Ok, I thought we moved Auto Mode to switches so that's my bad, however these are the options I get for entities using Fan. Using fan.pure_hot_cool, i get the error "Call-service error. The preset_mode auto is not a valid preset_mode: ['Auto']"

[Flameeyes]

I guess it needs to be capitalized.

[xvlw]

hahahaha I hate it here hahaha
Capital A worked on Auto

Thank you

[mundschenk-at]

@Flameeyes, what is the "canonical" way to disable Auto mode, other then setting a percentage speed? I wonder if modelling this as a preset is really the right way, or maybe it is, but there needs to be another preset manual (and Auto should really be auto).

[Flameeyes]

@mundschenk-at the Home Assistant canonical way to handle this is indeed having a single Auto preset_mode and switching it off by setting a percentage.

From the documentation:

Preset modes should not include named (manual) speed settings as these should be represented as percentages.

Manually setting a speed must disable any set preset mode. If it is possible to set a percentage speed manually without disabling the preset mode, create a switch or service to represent the mode.

"Auto Mode" is not orthogonal to the speeds: if auto mode is enabled, speed control is disabled, and vice-versa. You can't have "Speed 4 + Auto Mode."

[mundschenk-at]

It is, sort of, in that when you use the Dyson app or the IR remote control, the device remembers the last set speed percentage. If I switch on auto mode while speed is set to 10 (100 %), then auto will reduce speed if there are no particles etc. If you now switch off auto mode, the fan will return to full blast.

I'd like things to be consistent between HA usage and Dyson app/RC usage.

[Flameeyes]

Yes the Dyson app/firmware have a recall-last-speed — but that is not really exposed by Home Assistant. Since the plan for this component is to be merged upstream (or at least that's what @Kakise was hoping), I'd strongly suggest keeping it compliant with Home Assistant's semantics.

You can build your own helper switch, by saving the state of the fan entity before turning the preset to Auto, and recalling it after turning it off (this does require home-assistant/core#62794 to be merged though), but I don't think that breaking the HA model to match the Dyson app is the right answer here.

[mundschenk-at]

Sure, getting the integration merged upstream would be best. OK, I see, this is one architectural purity decisions. Well, can't be helped then.