Why global value triggering can't be fired via outside global value changing?

[10der 830]

subj.

 

example:

 

Please login or register to see this code.

 

pi@home:/home/pi# curl -v -H "Content-Type: application/json" --user "[email protected]:Micro$oft" -X PUT http://192.168.1.36/api/globalVariables/Test -d '{"name": "Test", "value": "777"}'

 

nothing....

 

 

 

[Dave_H 52]

Hi @10der

 

You may well have figured this out by now, as your question was posted some time ago.  However for the benefit of others, pass in a payload in the body as follows:

 

Please login or register to see this code.

 

Dave

[Dave_H 52]

And I'm sure there are plenty more undocumented features out there for us to find.  Happy hunting!

[10der 830]

Hi Dave!

 

it's workaround :)

Yes. I can call scene, more than! I can pass parameters to scene... but question was about global params

do not hijack thread  

 

[Dave_H 52]

Hi @10der

 

I wouldn't dream of hijacking your thread .  But my answer was in relation to updating global variables and triggering scenes, as I thought that was what the question was about, and not about passing parameters to scenes .

 

Dave

[10der 830]

Sir!

 

when u update a global param u shouldn't pass any params for run scene.

any proofs?

 

ok here is

 

Please login or register to see this image.

 

(c) 

Please login or register to see this link.

 

where did you get?

 

Please login or register to see this code.

 

 

just "googled" by the forum.  Aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa!!!!!!

 

<irony> Thank you Fibaro for updated docs </rony>.

 

crazy. +1 Dave

Edited February 5, 2018 by 10der