Send HTTP-Request via Scene in HC3

[missenberger 6]

Hey everybody,

 

i just upgraded from HC2 to HC3 "the hard way"... so I excluded all devices from my HC2 and added them manually to HC3.

All devices are now available again and my next step is to re-build all my virtual devices and scenes. 

 

I had a Scene on my old HC2 that - once it was started manually - sends a simple HTTP request. The old HC2 code - that worked properly - was :

Please login or register to see this code.

 

I tried to copy it into a HC3 scene, but it does not really work.

The "Action" part of my HC3-scene now looks like this:

Please login or register to see this code.

 

The first line is just for test reasons. The scene is running. Device 187 goes from on to off and from off to on when you run the scene.

I also do not get any error messages when the scene is running. But the HTTP request does not work. It should start a AC unit in my sleeping room. But it does not start.

When i copy the URL and open it manuall via browser, the AC unit does react... so the URL itself is correct.

 

Any idea how to make this run the very very very easy way... (It´s to complex for me to put the IP, the Port, the URL in seperate variables and use them later to build this HTTP request using those variables.... I like to have everything in a minimum number of lines

 

Thanks and greetings

Michael

Edited March 7, 2023 by missenberger
specified "HC3"

[Joep 197]

Try this Lua code, it's very basic for a scene

 

Please login or register to see this code.

 

More information about HTTP request with the HC3

Please login or register to see this link.

about it.

[missenberger 6]

Thank you Joep,

 

I will try this later when my son is sleeping.

I will let you know if it works (i am sure it does :-))

 

But I checked your block and its phenomenal.

I will for sure read this the next days. Its very good.. very impressive.

You surely invested a lot of time for it and its worth every minute!

 

[Joep 197]

24 minutes ago, missenberger said:

I will let you know if it works (i am sure it does :-))

 

If there are any problems just ask here, me or someone else from the community will help you.

 

24 minutes ago, missenberger said:

But I checked your block and its phenomenal.

I will for sure read this the next days. Its very good.. very impressive.

 

Thank you very much for you big compliment. 😎

[missenberger 6]

Hello Joep (and of course others reading this),

 

I just tried the LUA code from above and it´s kind of strange. 

It does run. I do get status 200 back, so there is something going out reaching my Daikin device.

But the Daikin device does not react. --> [SCENE205]: {"status":200,"data":"ret=PARAM NG","headers":{"Content-Type":"text/plain","Content-Length":"12"}}

 

The PARAM NG probably means, that the GET-parameters are somehow wrong. But if I take the URL and cope it to my browsers adress line, it works fine. So the URL with the same parameters work when used from outside my HC3.

 

Any ideas how to analyse / fix this problem?

[Joep 197]

Try with an encoded url: http://192.168.178.75:80/aircon/set_control_info?pow%3D1%26mode%3D3%26stemp%3D22%26shum%3D0%26f_rate%3DA%26f_dir%3D3

[missenberger 6]

This does not work either...  but funny thing: When i start the scene 4 times, I get different responses:
[08.03.2023] [15:45:33] [DEBUG] [SCENE205]: {"status":200,"data":"ret=PARAM NG","headers":{"Content-Type":"text/plain","Content-Length":"12"}}

[08.03.2023] [15:45:42] [DEBUG] [SCENE205]: {"status":200,"data":"ret=PARAM NG","headers":{"Content-Type":"text/plain","Content-Length":"12"}}

[08.03.2023] [15:45:45] [DEBUG] [SCENE205]: {"data":"ret=PARAM NG","status":200,"headers":{"Content-Length":"12","Content-Type":"text/plain"}}

[08.03.2023] [15:45:50] [DEBUG] [SCENE205]: {"status":200,"headers":{"Content-Type":"text/plain","Content-Length":"12"},"data":"ret=PARAM NG"}

 

Same thing if I go back to the unencoded URL:
[08.03.2023] [15:48:16] [DEBUG] [SCENE205]: {"data":"ret=PARAM NG","status":200,"headers":{"Content-Length":"12","Content-Type":"text/plain"}}

[08.03.2023] [15:48:20] [DEBUG] [SCENE205]: {"headers":{"Content-Type":"text/plain","Content-Length":"12"},"data":"ret=PARAM NG","status":200}

[08.03.2023] [15:48:33] [DEBUG] [SCENE205]: {"headers":{"Content-Type":"text/plain","Content-Length":"12"},"data":"ret=PARAM NG","status":200}

[08.03.2023] [15:48:42] [DEBUG] [SCENE205]: {"data":"ret=PARAM NG","headers":{"Content-Length":"12","Content-Type":"text/plain"},"status":200}

 

Very confusing....

(at least I still have my HC2 / LOL)

[Joep 197]

It's the same response, the headers parameters are not sorted. 😉

 

I think you have to fiddle with http headers, like:

1. headers = { Accept = "text/plain" } or
2. headers = { Accept = "application/json" }

Like:

 

Please login or register to see this code.

 

[missenberger 6]

I think I found a solution for it... it seems to work now (will have to test it later in detail). 

 

The header was not the problem. The problem indeed was the encoding of the URL. I only encoded the GET-Parameters at the end of the URL with a function (i found here on the forum). Once I encode the whole URL with the same function (with http://...) it does not work anymore.

 

Honestly... I do not really understand what´s happening here... and why. I am not really a programmer. I can read most code and with a good portion of trial and error I can also write code. But who cares I am happy it works now and I can set up the needed scenes for my home automation.

I will clean up the code tonight or the next 2-3 days, remove my test variables and comments and post the final result here. Maybe somebody else is having the same problem some day.

 

Thank you Joep for directing me to the encoding topic.
I would not have made it without your help.

 

 

[Joep 197]

The browser does the encoding for you. Therefore it works in the browser url bar. In my example above I also only the parameters where encoded. I learned that the hard way too. 😀

[missenberger 6]

As promised I will post the working solution here... which is 99% your solution, Joep.

I have seen, that you only encoded the second part of the URL as well. That´s why i said, I do not understand what is happening and why.

So... to give poetential searchers some more keywords. The following code is the complete action part of a scene, that sends one request to a Daikin Emura Aircondition with WIFI-Module (some people say, it only works for older models and newer ones do not support a RestAPI, but I do not have newer models and cannot test and confirm it. Mine are from 2018 or 2019.)

 

The parameters at the end of the URL tell the AC-unit what to do (pow=0 means switch off, pow=1 means switch on. Mode=3 is Heating, Mode=4 means cooling. Temp is self explaining I guess. Just search for "set_control_info daikin" at Google.... there is a good, but unofficial documentation on github.

 

Joep, again thank you very much.

 

Please login or register to see this code.

 

[VENTO 0]

On 7/3/2023 at 20:31, Joep said:

 

Si tienes algún problema, pregunta aquí y yo o alguien más de la comunidad te ayudaremos.

 

 

Muchas gracias por tu gran cumplido.  😎

 

 

Buenos dias ,alguien sabria como hacer un dispositivo virtual para encender apagar detector moviento camaras dahua, lo consigo haciendo camaras con url modificadas ejemplo 

http://admin:[email protected]:443/cgi-bin/configManager.cgi?action=setConfig&MotionDetect[0].Enable=true.MUCHAS GRACIAS