Xioami cooker integration

Feature Requests
121

Cool! I will give it a try

122

Awesome. We have a first step to integration.
@syssi Any chance we might see a service to control the cooker as well?
P.S The git instruction for services calling service says air purifier. :slight_smile:

123

It’s just a typo. There a two service calls: start & stop.

124

Hmm. Can’t find service not xiaomi_cooker.start nor xiaomi_cooker.stop among populated services.
All the cooker sensors are working though.

Screenshot%20from%202018-11-09%2018-28-11
Screenshot%20from%202018-11-09%2018-28-11699×698 31.3 KB

125

Ups. May be the service isn’t implemented yet. I will fix it!

126

Thanks @syssi waiting for update!

127

Please update the custom component. Start a cooking profile and stop cooking is working fine now.

Service: xiaomi_cooker.start
Service data: {"profile": "0001E101000000000000800200A00069030103730000085A020000EB006B040103740000095A0400012D006E0501037400000A5A0401FFFF00700601047600000C5A0401052D0A0F3C0A1E91FF820E01FF05FF78826EFF10FF786E02690F0DFF826EFF691000FF826EFF69100069FF5AFF00000000000081E9"}

Some cooking profiles: https://raw.githubusercontent.com/rytilahti/python-miio/master/miio/data/cooker_profiles.json

1 Like
128

Thanks @syssi seems to be working now. Will continue to test :+1: This is enough for automation all we are missing now is sensible UI for users.

129

Hi @syssi.

After some testing came up with couple of fidings and suggestions:

  1. Temperature sensor returns “Unknown” in any operational mode except “Waiting”
  2. Could Mode sensor return actual operational mode except “Running” since it is fairly hard to determine which operational mode currently cooker is since in any requested mode returns “Running” status.

Will continue testing.

Thanks @syssi.

130
  1. I’ve improved/fixed the temperature sensor.
  2. Which values would be useful here?
131
  1. Awesome. Will check that bit later.
  2. Something which cold help to destinct current operational mode. Perhapse title of currently running profile?

Thanks

132

Hi again,

  1. Temperature sensor seems to work really well in all modes, but except “AutoKeepWarm” mode.
  2. I think I have came with other solution how to determine in which operational mode is the cooker. Perhaps we can keep as it is.

Thanks

133

The current profile cannot be identified while cooking. I will keep the mode as it is.

134

Fair enough. Thanks @syssi. Any thoughts on temperature sensor?

135

Could you try the latest version of the component? It should be fixed now. Please report additional operation modes with temperature issues.

136

Just got one of these cookers, would be nice to get this as part of the standard components :smiley:

Btw its not working, i Placed the files into the custom component folder structure, as the files are in git…but its failing to load the config. Seems to be the API key. You link to the Aquara gateway key in the docs, but that is not the key being used here.

137

Not that big a difference if it is a standard or custom component, to frank .The componen is definitely working. All you got to do is to copy custom_component from git to your setup, retrieve key from mihome app, and setup yaml file.

138

Right. But the key (password) from the docs here https://www.domoticz.com/wiki/Xiaomi_Gateway_(Aqara)#Adding_the_Xiaomi_Gateway_to_Domoticz

is not the key the component wants.

139

The “Xiaomi Aqara” encryption key and the Xiaomi MiIO token are two different things.

This is the documentation you are looking for: https://www.home-assistant.io/components/vacuum.xiaomi_miio/#retrieving-the-access-token

140

Yeah… thanks. The documentation should be updated to point to the right one :smiley:

(or is it possible to get this working via the gateway…?) Which i do have…