set_chargetargets gets message undefined

[cheick66]

set_chargetargets gets message undefined

[xerion3800]

Hi i gues you should use it like this:
msg.payload : Object { "fast": 80, "slow": 70 }

[PierreLevres]

Indeed. That is the way it is also documenten in the help for the node: {"fast": number, "slow": number}

…

Op 10 jul. 2022 om 22:07 heeft xerion3800 ***@***.***> het volgende geschreven:  Hi i gues you should use it like this: msg.payload : Object { "fast": 80, "slow": 70 } — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.

[cheick66]

I've sent it in that style { "fast": 80, "slow": 70 } by MQTT to the Node-Red workflow.
Copy and past from my first post is direktly out of Node-Red and there are my "" are cleared.

That is working for other payloads too:
{"defrost": true, "windscreenHeating": true, "temperature": 18, "unit": "C"}
This example will start the air conditioning.

As you can see a start_climate and set_chargetargets are both going a simular way through JSON to the Bluelinky function.

.

This is out of my logfile, to show, that it looks like same format

2022.07.11 11:00:03.167 3: MQTT2_DEVICE set Kia_connect setChargeTargetSoc {"fast": 100, "slow": 80}
2022.07.11 11:00:08.178 3: MQTT2_DEVICE set Kia_connect getAll
2022.07.11 11:01:37.652 3: MQTT2_DEVICE set Kia_connect startClimate {"defrost": false, "windscreenHeating": false, "temperature": 18 , "unit": "C"}

I'm not a programmer ;-)

EDIT: I did some more msg.payload

1. including "" is after receiving to Node-Red
2. after json
3. message from Bluelinky

If I sent a wrong json payload I receive a message from bluelinky
"ManagedBluelinkyError: Charge target values are limited to 50, 60, 70, 80, 90, 100"
So my resume is, that the blulinky request with {"fast": 100, "slow": 80} is maybe not the compleat right format, which results in an "undefined" on kia's server.

[PierreLevres]

Edit, the mail reply stripped of my attachments. To reconfirm, a small test <img width="1562" alt="Screenshot 2022-07-12 at 08 29 20" src="https://user-images.githubusercontent.com/62832923/178423756-3e335222-7b56-4497-9ac7-88072940f174.png"> So although the output from the ’set charge target nodes’ is ‘Undefined’, it does set the charge targets to the wanted targets.

…

On 11 Jul 2022, at 20:09, Peter Lips ***@***.***> wrote: Does it work, setting the targets? You can verify in your app. I have the same result (uunudefined) becouse the bluelinky function (public async setChargeTargets) does not return a value. That was adressed as something to be fixed but it got lost somewhere. > On 11 Jul 2022, at 10:39, cheick66 ***@***.*** ***@***.***>> wrote: > > > I've sent it in that style { "fast": 80, "slow": 70 } by MQTT to the Node-Red workflow. > That is working for other payloads too: > {"defrost": true, "windscreenHeating": true, "temperature": 18, "unit": "C"} > This example will start the air conditioning. > > — > Reply to this email directly, view it on GitHub <#219 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AO7MCG6TENNXCW56YTZ6A6DVTPMUPANCNFSM53EPYBBA>. > You are receiving this because you commented. >

[cheick66]

Hi all,
thanks for your support.
I can confirm, that it is working, as you accepted. It's maybe my fault, because I was to fast on checking the result :-)
If I give that process more time, I can see the result inside of the mobile App.

I will also try to add the "small test", to learn more about node-Red.
@PierreLevres could you send me the funktions, whiche you created to do the test? I already created the flow as a copy of yout picture. But I never did programming to node-Red :-(

Best regards
Christian

[PierreLevres]

Does it work, setting the targets? You can verify in your app. I have the same result (uunudefined) becouse the bluelinky function (public async setChargeTargets) does not return a value. That was adressed as something to be fixed but it got lost somewhere.

…

On 11 Jul 2022, at 10:39, cheick66 ***@***.***> wrote: I've sent it in that style { "fast": 80, "slow": 70 } by MQTT to the Node-Red workflow. That is working for other payloads too: {"defrost": true, "windscreenHeating": true, "temperature": 18, "unit": "C"} This example will start the air conditioning. — Reply to this email directly, view it on GitHub <#219 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AO7MCG6TENNXCW56YTZ6A6DVTPMUPANCNFSM53EPYBBA>. You are receiving this because you commented.

[cheick66]

Does it work, setting the targets? You can verify in your app. I have the same result (uunudefined) becouse the bluelinky function (public async setChargeTargets) does not return a value. That was adressed as something to be fixed but it got lost somewhere.
…
On 11 Jul 2022, at 10:39, cheick66 @.***> wrote: I've sent it in that style { "fast": 80, "slow": 70 } by MQTT to the Node-Red workflow. That is working for other payloads too: {"defrost": true, "windscreenHeating": true, "temperature": 18, "unit": "C"} This example will start the air conditioning. — Reply to this email directly, view it on GitHub <#219 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AO7MCG6TENNXCW56YTZ6A6DVTPMUPANCNFSM53EPYBBA. You are receiving this because you commented.

Hi Pierre,
for me it's working, I can see the changes in my Handy App and I can get a status by bluelinky with the changes values.

1. you send out the values
2. after a while you update the app and should see the changed values
3. also after short time you start a getall status inside your Node-Red workflow and it should also show the changes

Best regards
Christian