New plugin pimatic-home-connect

---

@mwittig thanks for your response and the support offer.
The proof of concept for the CoffeeMaker was made using the simulator. A very nice tool for testing.

Cool! That is now getting here as I read in IO-Broker

To start the build of the plugin we need to design the way we want to map the home-connect functions to pimatic with specifics per appliance (Washing machine, CoffeeMaker, etc)

The following pictures are from the Home-Connect simulator and its a simulation of a CoffeeMaker

Feel free to post your thoughts on how these features should be available in Pimatic.

To help the thought process two Pimatic Gui images from the proof of concept CoffeeMaker

There some progress on the pimatic-home-connect plugin and a version for testing is available.
The plugin can be installed via the Pimatic plugins page.

The plugin is supporting the CoffeeMaker, Washer, DishWasher, Oven, Dryer and FridgeFreezer
and can work in Simulator or Live mode.

More info on readme.

If you got feature requests or bugs please report on features&bugs

I released version 0.1.2 of the home-connect plugin

Its now possible to use a programOption variable in the execution part of rules.

homeconnect <device id or name> [start, startopts $<programOptionsVariable>, pause, resume, stop]

The format for the $<programOptionsVariable> is:

program: <programId>, <optionname>: <optionValue>, <optionname>: <optionValue>, ...

Example for CoffeeMaker

homeconnect <CoffeeMakerId> startopts $options

Value of the variable $options is

program: Cappuccino, BeanAmount: DoubleShot, CoffeeTemperature: 95C, FillQuantity: 100

Cool! Maybe I find the time to look into this. I have a home-connect dishwasher and an oven.

It is nice to the development of this plugin. Thanks for the good work.
My usecase for the plugin would be the following.
I allways use the same program for my siemens dishwasher (same program, same start time). Now I have to enter the starttime with a lot of presses on a touch screen.
It would be nice to be able to program the dishwasher via a rule to start it either daily automatic or with only one touch on a button in the pimatic web interace.

@pf you can already start the dishwasher with a rule.
The execution part of the rule is

homeconnect <dishwasher-id> startopts $dishwasher-variable

To start for example the Eco50 program the $dishwasher-variable is:

program: Eco50

or if you want a delayed start add the option StartInRelative (value in seconds)

program: Eco50, StartInRelative: 7200

The StartInRelative is somewhat useless because with the rule you can time the start of the program.
With this you can build a rule to start a program at a certain time.

The latest version is 0.1.8

Looks great!

Finally I have succeeded in creating a developer account for Home-Connect.
So now I wil take the next step in testing the plugin.
When I do an update to 0.0.34 to 0.0.38 I get the following warning. I do not know if it is important, but perhaps it helps:

npm WARN deprecated mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)

pimatic-home-connect@0.2.7 node_modules/pimatic-home-connect
├── querystring@0.2.0
├── url@0.11.0 (punycode@1.3.2)
├── request-promise-native@1.0.8 (stealthy-require@1.1.1, request-promise-core@1.1.3)
└── node-persist@3.0.5 (mkdirp@0.5.4)

Hi, thanks for the feedback. These are warnings and coming from the library’s i used. To get rid of them i need to rewrite those libs. For now not a priority.
Are you using the simulator or directly an own device?

@bertreb I would first like to try the simulator and then I want to connect to my dishwasher.
But for the moment I get an error after activating the plugin:
(node:9863) UnhandledPromiseRejectionWarning: TypeError: Cannot read property ‘<<My apps Client ID>>’ of undefined
at /home/pi/pimatic-app/node_modules/pimatic-home-connect/pimatic-home-connect.coffee:35:27
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:9863) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:9863) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
After this I am able to create a home-connect-manager, but I cannot discover devices.
The Home Connect Manager device status remains at: Initializing

Hi, did you fill in the clientIdSim and clientSecretSim in the plugin config and switched simulation on? Both are long strings with only chars and numbers. They are generated when you create the app in the Home-connect website.
It seems that ‘<<My apps Client ID>>’ is used, and that is not a valid ClientId

Thanks for your reply. In the plugin config I filled in:
clientID: (empty)
clientSecret: (empty)
Checkbox simulated: Checked
CliendIdSIm: <the client ID I got from my developer portal>
ClientSecretSim: <the client secret I got from my developer portal>
In the logfile I deleted my clientSimId with the replacement text <<My apps Client ID>> as I did not want to publish my own Client ID in this form

Ok, thats clear
I added extra error handling and published version 0.2.8. And I assume you switch on the debug?
It think i know what the problem is, but wait for your feedback

@bertreb I installed version 0.2.8 and turned on debug.
The log shows:
21:59:18.919 [pimatic-home-connect] debug: Error savedTokens handled TypeError: Cannot read property ‘<<here was my clientIDSim>>’ of undefined

Ok, the error is now catched. I added an extra check on the tokens in version 0.2.9

Hi, I installed version 0.2.9.
The error remains the same.

Are you using a rpi?