Hi, I installed version 0.2.9.
The error remains the same.
-
New plugin pimatic-home-connect
-
@bertreb Yes, a Raspberry Pi Zero W
-
@bertreb Great! Thanks for this rapid development cycle. The simulator now works. No errors.
-
@bertreb After the success yesterday I am trying the next step, to connect to the live dish washer.
Now I get the message:
19:48:37.582 [pimatic] info: New device “Home Connect Manager”…
19:48:37.631 [pimatic-home-connect] debug: Simulated device ‘siemens-hcs02dwh1-bc04cea85837’’ not started because of live mode
19:48:37.637 [pimatic] error: Error loading device “siemens-hcs02dwh1-bc04cea85837”: Cannot read property ‘status’ of undefined
19:49:21.432 [pimatic-home-connect] debug: No stored tokens
19:49:21.445 [pimatic-home-connect] info: Requesting Home Connect authorisation using the Device Flow
19:49:21.454 [pimatic-home-connect] debug: Home Connect request #1: POST https://api.home-connect.com/security/oauth/device_authorization
19:49:21.789 [pimatic-homeduino] info: Connected to homeduino device.19:49:23.856 [pimatic] info: Listening for HTTP-request on port 80…
19:49:24.993 [pimatic-hue-zll] info: Connected to bridge Philips hue, API version 1.37.0, software 1937113020
19:49:25.664 [pimatic-home-connect] debug: Home Connect request #1: OK +4205ms
19:49:25.669 [pimatic-home-connect] info: Authorise uri https://verify.home-connect.com?user_code=<<USERCODE>>
19:49:25.674 [pimatic-home-connect] info: Auth_uri: https://verify.home-connect.com?user_code=<<USERCODE>>
19:49:25.678 [pimatic-home-connect] debug: Waiting for completion of Home Connect authorisation (poll every 5 seconds, device code <<DEVICECODE>> expires after 300 seconds)…
19:49:30.687 [pimatic-home-connect] debug: Home Connect request #2: POST https://api.home-connect.com/security/oauth/token
19:49:31.946 [pimatic-home-connect] debug: Home Connect request #2: Authorisation pending +1251ms
19:49:36.953 [pimatic-home-connect] debug: Home Connect request #3: POST https://api.home-connect.com/security/oauth/token
19:49:38.237 [pimatic-home-connect] debug: Home Connect request #3: Authorisation pending +1276ms!!
Under this you see the application config
-
Hi, the live devices need the Device Flow authentication and tokens.
siemens-hcs02dwh1-bc04cea85837 looks like the simulated device?
In the plugin you need to fill in the ClientID and ClientSecret for the device flow app and switch the simulation off.
That the simulated devices still loads in live mode, i will fix.On the home-connect manager device you see a link (when you click on it)
Yo need to click on the Link and authorize the the control of your live equipment. -
@bertreb The siemens-hcs02dwh1-bc04cea85837 is indeed a virtual device. It was still present as a device, but I switched to live, so it is correct that it won’t start.
I had trouble finding the link. But now I did.
After authentication I get redirected to the success url (configured als http://localhost:3000/o2c), but it is a empty page.
Is it usefull to fill in another url, or does it have no function?
After this I was able to discover my live dishwasher.
So thanks again for your help, -
Ok, the result counts! The localhost:3000/o2c has not function in the device flow authentication. Its for the old way of Auth grant flow. But i did automate that. So its just a field that needs to be filled on the home-connect site.
-
Hi,
I am trying to use the startopts for devices, but I get an error:16:10:12.352 [pimatic] info: rule hc-program-cm: “” Rule not executed
I am using the simulated coffeemaker and have turned debug on in the plugin configuration.
The rule I use reads as follows in the config:
{ "id": "hc-program-cm", "name": "HC Program CM", "rule": "when CoffeeMaker Program is pressed then homeconnect CoffeeMaker Simulator startopts $coffeemaker-variable", "active": true, "logging": true },
The value for $coffeemaker-variable reads as follows in the config:
{ "name": "coffeemaker-variable", "value": "program: Cappuccino, BeanAmount: DoubleShot, CoffeeTemperature: 95C, FillQuantity: 100" }
The following rule does work allright:
{ "id": "hc-start-cm", "name": "HC Start CM", "rule": "when Coffeemaker Start is pressed then homeconnect CoffeeMaker Simulator start", "active": true, "logging": true }
],
-
Update 0.2.11 solves the problem. Thanks.
-
@pf said in New plugin pimatic-home-connect:
Hi,
I am trying to use the startopts for devices, but I get an error:16:10:12.352 [pimatic] info: rule hc-program-cm: “” Rule not executed
I am using the simulated coffeemaker and have turned debug on in the plugin configuration.
The rule I use reads as follows in the config:
{ "id": "hc-program-cm", "name": "HC Program CM", "rule": "when CoffeeMaker Program is pressed then homeconnect CoffeeMaker Simulator startopts $coffeemaker-variable", "active": true, "logging": true },
The value for $coffeemaker-variable reads as follows in the config:
{ "name": "coffeemaker-variable", "value": "program: Cappuccino, BeanAmount: DoubleShot, CoffeeTemperature: 95C, FillQuantity: 100" }
The following rule does work allright:
{ "id": "hc-start-cm", "name": "HC Start CM", "rule": "when Coffeemaker Start is pressed then homeconnect CoffeeMaker Simulator start", "active": true, "logging": true }
],
I have translated this to a demo dishwasher device and then the program options work.
When I go on and create and identical rules for my “live” dishwasher, the following happens.
A rule without program options works
A rule with program options does not work.info [pimatic]: rule hc-dishwasher-live-program: “” Rule not executed
18:41:04info [pimatic-home-connect]: command: startoptions, programAndOptions: undefinedB.t.w. the authentication to the live device works. I can see the live status and also monitor changes to live states.
-
@bertreb said in New plugin pimatic-home-connect:
hi, i think its fixed in version 0.2.12
I have tested 0.2.12, but the result is the same: rule not executed.
-
@pf said in New plugin pimatic-home-connect:
program: Cappuccino, BeanAmount: DoubleShot, CoffeeTemperature: 95C, FillQuantity: 100
Hi, do you also get the same error " … programAndOptions: undefined" ?
Or another debug message, that should be there just around “the rule not executed” message
I released version 0.2.13 with extra debug info, let me know the log results -
Somehow version 0.2.13 does not appear in my updates, not even after a restart.