Maytag Smart Washer/Dryer Integration

Third party integrations
41

Opps. Stupid mistake. I just fixed it. May want to download new sensor.py file manually if hacs doesn’t show the update.

I am curios if it will work on whirlpool. I was not able to use my Maytag with the Whirlpool app, so I think there are differences. If it does not work, edit the sensor.py. Look for:

"client_id": "maytag_ios",
"client_secret": "OfTy3A3rV4BHuhujkPThVDE9-SFgOymJyUrSbixjViATjCGviXucSKq2OxmPWm8DDj9D1IFno_mZezTYduP-Ig",

and replace with:

 "client_id": "whirlpool_android",
 "client_secret": "i-eQ8MD4jK4-9DUCbktfg-t_7gvU-SrRstPRGAYnfBPSrHHt5Mc0MFmYymU2E2qzif5cMaBYwFyFgSU6NTWjZg",
42

Man, that was quick! Thanks! Will give it another go in a bit!

Thanks again!!

43

Does this mean it’s working?

I am too lazy to put stuff in it to check! :slight_smile:

info
info343×666 12.4 KB

44

Yup. I think it is working. Surprised it worked!

45

Same! I didn’t change anything, I just updated with the changes you published. So it’s a Whirlpool washer and it’s working with your code! Very nice!

46

I’ve setup my washer with the project and I see my washer as a sensor, however the only thing that shows is “Ready”. How do I get it to show me the attributes in Home Assistant?

Edit: I see the attributes section i’m dumb lol :man_facepalming: but how do I display that as its own sensor or is it possible to set my washer up as device and have the details/attributes attached? I want to do that in order to setup an automation easier as I was struggling to setup an automation to notify my phone when the washer cycle is done.

Edit 2: I noticed the attributes section is missing the “status” attribute.
Sorry for all the edits i’m a bit of a newb when it comes to using the features of the forms.

47

Ok. I think I know what is going on. You should be able to show attributes in an entities card with

type: entities
entities:
  - entity: sensor.maytag_dryer_xxxx
    type: attribute
    attribute: temperature
 - entity: sensor.maytag_dryer_xxxx
   type: attribute
   attribute: applianceid

However, it looks like attributes in the code cannot use capital letters. I’ll try to make a code change now. Then you can build up a card of the entities you want.

I’ll check for status. But i map status to the state, 0->Ready 7->running. But I can make sure its an attribute too

edit: The notification setup is in the github read me. Shows you how to make an automation to notify when done for the dyer. Should be easy to change for washer (no wrinkle prevent)

edit: Updated code posted on github. All attributes should be available and I added status in washer, though it is mapped to the state.

48

Gonna give it shot and i’ll let you know if it worked. :slight_smile:

49

All done playing around with it I’ve come to suggest a few improvements :).
Would it be possible to get all the attributes as their own sensors that are all part of 1 device.
Doing this would allow for more customizations in a lot of different aspects.

Edit: would it also be possible to map all the values with their corresponding terms for the attributes?
So for example instead of displaying “Remoteenabled: 1” could it display “Remote Enable: Enabled”

50

Sorry just reading through and getting caught up. Its working for me too! Awesome work @jaaem!

@Jailbreaker58 you can add dedicated sensors from attributes in your config btw. It’s pretty common for integrations with tons of metadata (for example, essentially all weather integrations) to have a global status, and then attributes for the metadata and other details. Heres an example from my config:

sensor:
  - platform: template
    sensors:
      washer_temp_setting:
        friendly_name: "Washer Temperature"
        value_template: "{{ state_attr('sensor.maytag_dryer_xxxx', 'temperature') }}"

That will create a sensor that updates with the value of the chosen attribute whenever the parent changes.

1 Like
51

Glad it is working for everyone. I think templates is the way to go. It is possible to make separate sensors in the code, but it’s a ton of code since there are so many attributes (and most are not very useful). Some people have made custom lovelace cards (like phrz/lg-washer-dryer-card: Lovelace cards for use with the Home Assistant LG ThinQ Integration (github.com)), perhaps I or someone can adapt it to Maytag.

52

No one wants to help with the python module so we can get that integrated on HA officially? Then entities will be created automatically as with any other integration.

53

Wanted to contribute to this since it was instrumental in me getting this working with Alexa and Node-Red. Below are some of the settings i have discovered that may be helpful with the Home Assistant integration.

Washer Cycle Selections
Normal - 1
Heavy duty - 2
Whites - 10
Sanitize - 3
Towels - 11
Bulky items - 22
Custom Cycle - 11
Quick wash - 4
Delicates - 5
Wrinkle control - 16
Colors - 24
Drain & Spin - 8
Clean - 20

Dryer Cycle Selections
Regular - 1
Heavy Duty - 2
Whites - 16
Sanitize - 9
Towels - 15
Bulky Items - 6
Quick Dry - 7
Delicats - 4
Wrinkle Control - 5
Normal - 10
Timed Dry - 11

Dryer Temp Settings
Air Only - 0
Low - 2
Medium - 5
Medium High - 6
High - 8

Drum Light Setting
Off - 0
On - 1

Wrinkle Prevent
Off - 0
On - 1
On with Steam - 2

Dryness Levels (Used with preset cycles)
Less - 1
Normal - 4
More - 7

When sending a command to the dryer, the Cavity_opSetOperations has 3 settings (at least that i’m aware of)
Cavity_opSetOperations : 1 = cancel, 2 = execute, 3 = send and wait for input from end user

These are setting from my Maytag appliances.

1 Like
54

Here are the states i have discovered as well for both washer and dryer (Maytag):

Dryer States
Idle (Off) - 0
Idle (on but not running) - 1
cycled paused - 6
drying - 7
wrinkle prevent - 8
cycle cancelled - 19
cycle completed - 10

Washer States
Idle (on but not running) - 1
soaking - 1
cycle paused - 6
washing - 7
cycle completed - 10

55

Thanks. I’ll try to add the ones I missed next time I can. I don’t plan on adding the active control to this temporary integration. @abmantis I may try to work on the python lib when I get some time.

56

Feel free to PM me if you need want to get up to speed on the lib quicker.

57

@jaaem I forked your repo to do some development / testing – don’t have too much expectation out of me though, as I have a full plate already.

However, I set up Postman to do some testing and noticed one thing already – the appliance SAIDs are actually returned in the OAuth response in the SAID property.

If you want to poke around with the API in a simple(r) way, I’ve created a public Postman workspace (link below) for collaboration. Just set the user, pass, and washer/dryer SAIDs in the variables section of the collection.

Now you can get started tinkering with the various requests – make sure you select the token you grabbed under the “Authorization” tab for the request.

I’d appreciate any assistance here for adding additional REST resource requests (other than just “appliance”). Ideally, we would pull the SAIDs on initial setup and populate the appliance types automagically.

POSTMAN
Link: Postman

If it’s your first time using Postman, you’ll need an account. Then, head to the “Variables” tab of the collection and fill in the user name/pass current value fields (this will keep your credentials private). From there, go back to Authorization and hit the “Get New Access Token” at the bottom. It should save it in your session as “Appliance State” token.

58

Awesome, feel free to take it over or do a PR on new capability. Yes, I know the SAIDs are in the authorization message, but hardcoding the SAIDs was easier for me to map to either dryer or washer. The node.js version does a smart check if a field exists to determine this, but I was trying to be quick and just get it working.

59

Right on, thanks again for doing the hard work. :slight_smile:
I’m new to Python (and HA) but am an experienced developer… we’ll see where this takes me!

60

New to the boards, long time HA user. Installed the HACS integration successfully. Looks promising so far. I did notice the dryer looks like it got a unique_id, while the washer did not. May explain why Dryer is capitalized and washer is not. Anyway, I’m happy to do testing for both the washer and dryer as I have both, though my programming experience is limited to working in HA and NodeRed. Thanks for all your efforts!