Another get request not working

markbellkosel84 · February 4, 2023, 5:16pm

I have done some searching and found that others have struggle with this in the passed. Unfortunately none of those solutions work for me so I figured I see if anyone have any suggestions.

Here is my rule. When I copy and paste it into Chrome it works perfectly. When I run the actions of the rule, however, I get nothing. I have turned on logging and get no errors.

The rule is being run from my main hub and making a request to my secondary hub. They have hub mesh enabled and working fine so I don't think it's any kind of network issue.

Sebastien · February 4, 2023, 5:35pm

What if you use a Post instead of a Get?

markbellkosel84 · February 4, 2023, 5:38pm

Doesn't seem to work either

markbellkosel84 · February 4, 2023, 5:45pm

I had to add my own %20 in the device name! Apparently Chrome can handle that not being done

markbellkosel84 · February 4, 2023, 8:05pm

@bravenel it seems that the URL encode option was taken out in 5.1. I am told that the option is there in 4.1

bravenel · February 4, 2023, 8:55pm

Still there:

markbellkosel84 · February 4, 2023, 9:09pm

Oh I was under the impression that it was under the get action itself. So I need to set the address to a variable and then use the get with the variable?

bravenel · February 4, 2023, 9:12pm

Yeah, it came out of the HTTP Get action because it didn't know which portion to encode.