Getting Error: "Parse Error: Expected HTTP" - "HPE_INVALID_CONSTANT"

General
21

Dear Steve,

Sorry for not replying directly to your questions but I tried so many things that I forgot what I have tried and not.
For your questions:

  • No new firmware available
  • No other protocol available

By reading the documentation again I found some hope by reading that another web page (xml) was available which returns more details. But apparently that page does not exists. I tried to query it.

I have read your comment in another post about http 0.9

Sined

22

I will try with the proposed method with the TCP Node but not sure how to add the credentials in the payload.

23

I have also read a comment about using a command node with a curl command in it. This could also be a solution.

24

I found the answer in my response earlier.

25

Maybe a silly question, but what happens, if you just ignore the output? You want to open the door and it will open ... what else matters? :wink:

26

There is no possibility in the HTTP Request node to specify not to bother about the response. The flow does not continue if it encounters a error.

27

Hello @NoeudRouge,

ok, that would be bad, but is it like that? The debug flow also receive an output, so every other node after the http-node should get an output too?!

Cheers
Ranki

28

In fact, considering the fact that the very purpose of the flow is to open the front door I need to have some check to make sure whether the door is open or closed. That is a minimum. Don't you think? :slight_smile:

29

Hello @NoeudRouge,

I agree, the question is, if the device will tell you that or if you need to scrape this information from another page :slight_smile:
To be honest, I am lost now with ideas and as I cannot test it on my own system, I think I cannot try to help anymore. The only thing I would have tested (but w/o an idea, if it helps) is to set the headers
msg.headers["content-type"] = "application/x-wwww-form-urlencoded" to have the data transmitted as form.

Cheers and good luck!

Ranki

30

I will try some other combinations including your proposal.
Tbh at some time I will need to stop testing because each time I send the http request I need to jump, run and go to my front door to close it. Which is good for my health but not very productive in terms of time.
Again, thank you for your time and the one of Steve.
I really appreciated your support.
Cheers,

Sined

31

:upside_down_face: You cannot close it remotely?

32

First of all, I solved this once before about 2 years ago. I called WebRelay and they gave me a variation on the command. Instead of "state.xml" it was something like "superstate" or "advstate" but I can't remember any more. I tried both of these and its not quite right.

Anyway, if you just want to change the RelayState, the workaround is to use the "Catch" Node. This will trap the error and prevent the flow from crashing. You still get the error but you just throw it away. The WebRelay reacts correctly anyway.

If you want to Read the RelayState then you will need to check with WebRelay themselves.

33

UPDATE: Just got an email back from them and I remember now!!

Try "stateFull.xml" instead of "state.xml". Capital "F" essential.

Its because the WebRelay server code supports an old HTTP version.

34

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.