HC3 (maybe HCx) and Nodered

[Guest kallecux]

When I call the HC3 api

http://192.168.3.116/api/customEvents/sunrise

to trigger the "sunrise" event, then this works via the SWAGGER console.

 

If I want to trigger the event via nodered, I can't do it.

 

Neither via the basic authentication built into, nor when I incorporate the user name and password in the URL.
I always get:

Error "405 not allowed".

 

What can be wrong here?
Best regards
Karl Heinz

[tcviper 20]

You probably need to call it with a user/pass?
Like http://admin:[email protected]/api/customEvents/sunrise

 

Does that work?

[jgab 1,954]

2 hours ago, kallecux said:

When I call the HC3 api

http://192.168.3.116/api/customEvents/sunrise

to trigger the "sunrise" event, then this works via the SWAGGER console.

 

If I want to trigger the event via nodered, I can't do it.

 

Neither via the basic authentication built into, nor when I incorporate the user name and password in the URL.
I always get:

Error "405 not allowed".

No problem posting from NR to HC2 (you do a POST do you?)

I would expect the problem being something in your NoderRed http node config...

[Guest kallecux]

Do you prefer Basicauthentication via the http Request node or inline authentication via URL?

[Guest kallecux]

Please login or register to see this spoiler.

 

[Guest kallecux]

GET works but not POST

 

I did it this way:

 

the URL is: http://admin:[email protected]/api/customEvents/sunrise

 

Please login or register to see this attachment.

Please login or register to see this attachment.

the NR response is: 

Please login or register to see this image.

/monthly_2020_02/image.png.8b64350bdadb3ab7c03d47b15568f034.png" />

 

Greetings!

 

Edited February 11, 2020 by kallecux

[A.Socha 112]

If get works that mean your PUT have something wrong maybe your payload?

[jgab 1,954]

On 2/11/2020 at 2:56 PM, kallecux said:

GET works but not POST

I did it this way:

the URL is: http://admin:[email protected]/api/customEvents/sunrise

Did you get it to work?

It turned out that I needed to add the header "X-Fibaro-Version:  2" or the HC3 got into a catalytic shock and showed 504. Usually needed a reboot.

[Guest kallecux]

Hello @jgab, no not yet - I put it aside. I will check the JSON content and follow your advice regarding the header.
Thanks for the hints!