Existing Rule stopped working HTTP command fetching IP address from website
-
I can't work out why this existing rule now no longer works? It was a rule to get my current WAN IP address, store it in a variable and then send that value to the Multi-String device in Vera. The trigger was just a time based trigger to run every so often.
Set Reaction -
Temp Local Expression - This is empty and it shouldn't be.
The current IP value in the Global Expression "myIP" is also wrong and not up to date. If I press the Play button on the Set Reaction I get this error:
However the website https://ipv4.jsonip.com/ still seems to work fine and does show my correct current WAN IP address etc.
Thanks
-
I can't work out why this existing rule now no longer works? It was a rule to get my current WAN IP address, store it in a variable and then send that value to the Multi-String device in Vera. The trigger was just a time based trigger to run every so often.
Set Reaction -
Temp Local Expression - This is empty and it shouldn't be.
The current IP value in the Global Expression "myIP" is also wrong and not up to date. If I press the Play button on the Set Reaction I get this error:
However the website https://ipv4.jsonip.com/ still seems to work fine and does show my correct current WAN IP address etc.
Thanks
@cw-kid The capture variable having a null value is a pretty indication that there was an error. You have the "Suppress alerts on HTTP errors" box checked, so you're silencing your first option for notification of an error on the request. But then, there could be another location...

-
@cw-kid The capture variable having a null value is a pretty indication that there was an error. You have the "Suppress alerts on HTTP errors" box checked, so you're silencing your first option for notification of an error on the request. But then, there could be another location...

@toggledbits said in Existing Rule stopped working HTTP command fetching IP address from website:
"Suppress alerts on HTTP errors" box checked
Sorry I didn't notice that, I unchecked it and saved the rule, now when I reset the rule the popup error box just says "The request failed" and I still don't get an actual alert in the status area of MSR with anymore detail.
Or if instead I press the Play button on the Set Reaction it then says:
Error: Command timeout (1782 start_reaction)
at _ClientAPI._commandTimeout (http://192.168.0.4:8111/client/ClientAPI.js:546:201)But I can access the HTTP endpoint in my browser no problems on my laptop. I then SSH into the MSR box and tried to ping ipv4.jsonip.com at least and it does appear to reply from IP 34.160.111.145.
But it looks weird on the Debian MSR box, the ping reply it shows as:
from 145.111.160.34.bc.googleusercontent.com (34.160.111.145)
Where as if I just ping it from my Windows laptop it shows as:
from 34.160.111.145
I don't see the 145.111.160.34.bc.googleusercontent.com part what ever that is.
-
OK that's strange I just restarted MSR and the rule has started working again now. Its populated both the temp local expression and the "myIP" Global Expression and sent the correct current WAN IP address to Vera and the MultiString device. Maybe unchecking Suppress alerts on HTTP errors unblocked it. Dunno but its working now it seems.







