I’m working with a piston which is supposed to generate a REST POST request containing the contents of weather alerts, but there seems to be an issue building the string for the request. If I replace the {Weather_Alert_Message} variable with a normal string, the POST goes out, but as it is, it’s not going out. Any ideas?
4/7/2018, 8:42:32 PM +361ms
+1ms ╔Received event [Home].time = 1523151753907 with a delay of -1546ms
+219ms ║RunTime Analysis CS > 20ms > PS > 76ms > PE > 122ms > CE
+222ms ║Runtime (41929 bytes) successfully initialized in 76ms (v0.3.104.20180323) (219ms)
+222ms ║╔Execution stage started
+489ms ║║Comparison (dynamic) [Freeze Warning] is_equal_to (string) [] = false (2ms)
+491ms ║║Condition #16 evaluated false (255ms)
+492ms ║║Condition group #13 evaluated false (state did not change) (257ms)
+499ms ║║Comparison (dynamic) [Freeze Warning] is_equal_to (dynamic) [] = false (1ms)
+501ms ║║Cancelling condition #8’s schedules…
+502ms ║║Condition #8 evaluated false (8ms)
+503ms ║║Cancelling condition #2’s schedules…
+504ms ║║Condition group #2 evaluated true (state changed) (10ms)
+506ms ║║Cancelling statement #18’s schedules…
+514ms ║║Calculating (string) http://192.168.1.121:3000/customBroadcast?text=" + (string)
+515ms ║║…Freeze warning now in effect from 8 PM this evening to 9 am
+515ms ║║CDT Sunday…
+515ms ║║* timing…late tonight into early Sunday morning.
+515ms ║║* Temperatures…in the low to mid 20s.
+515ms ║║* Impacts…sensitive plants and trees may be damaged or killed.
+515ms ║║Precautionary/preparedness actions…
+515ms ║║A freeze warning means sub-freezing temperatures are imminent or
+515ms ║║highly likely. These conditions will kill crops and other
+515ms ║║sensitive vegetation.
+515ms ║║Kd
+516ms ║║
+516ms ║║…Freeze warning now in effect from 8 PM this evening to 9 am
+516ms ║║CDT Sunday…
+516ms ║║* timing…late tonight into early Sunday morning.
+516ms ║║* Temperatures…in the low to mid 20s.
+516ms ║║* Impacts…sensitive plants and trees may be damaged or killed.
+516ms ║║Precautionary/preparedness actions…
+516ms ║║A freeze warning means sub-freezing temperatures are imminent or
+517ms ║║highly likely. These conditions will kill crops and other
+517ms ║║sensitive vegetation.
+517ms ║║Kd
+517ms ║║
+520ms ║║Calculating (string) http://192.168.1.121:3000/customBroadcast?text="
+520ms ║║…Freeze warning now in effect from 8 PM this evening to 9 am
+520ms ║║CDT Sunday…
+520ms ║║* timing…late tonight into early Sunday morning.
+520ms ║║* Temperatures…in the low to mid 20s.
+520ms ║║* Impacts…sensitive plants and trees may be damaged or killed.
+520ms ║║Precautionary/preparedness actions…
+521ms ║║A freeze warning means sub-freezing temperatures are imminent or
+521ms ║║highly likely. These conditions will kill crops and other
+521ms ║║sensitive vegetation.
+521ms ║║Kd
+521ms ║║
+521ms ║║…Freeze warning now in effect from 8 PM this evening to 9 am
+521ms ║║CDT Sunday…
+521ms ║║* timing…late tonight into early Sunday morning.
+521ms ║║* Temperatures…in the low to mid 20s.
+521ms ║║* Impacts…sensitive plants and trees may be damaged or killed.
+522ms ║║Precautionary/preparedness actions…
+522ms ║║A freeze warning means sub-freezing temperatures are imminent or
+522ms ║║highly likely. These conditions will kill crops and other
+522ms ║║sensitive vegetation.
+522ms ║║Kd
+522ms ║║
+532ms ║║Sending internal web request to: 192.168.1.121:3000/customBroadcast?text="
+533ms ║║…Freeze%20warning%20now%20in%20effect%20from%208%20PM%20this%20evening%20to%209%20am
+533ms ║║CDT%20Sunday…
+533ms ║║*%20timing…late%20tonight%20into%20early%20Sunday%20morning.
+533ms ║║*%20Temperatures…in%20the%20low%20to%20mid%2020s.
+533ms ║║*%20Impacts…sensitive%20plants%20and%20trees%20may%20be%20damaged%20or%20killed.
+533ms ║║Precautionary/preparedness%20actions…
+533ms ║║A%20freeze%20warning%20means%20sub-freezing%20temperatures%20are%20imminent%20or
+533ms ║║highly%20likely.%20These%20conditions%20will%20kill%20crops%20and%20other
+533ms ║║sensitive%20vegetation.
+533ms ║║Kd
+533ms ║║
+537ms ║║Executed virtual command httpRequest (9ms)
+538ms ║║Requesting a wake up for Sat, Apr 7 2018 @ 8:42:52 PM CDT (in 20.0s)
+545ms ║╚Execution stage complete. (323ms)
+547ms ║Setting up scheduled job for Sat, Apr 7 2018 @ 8:42:52 PM CDT (in 19.993s), with 1 more job pending
+566ms ╚Event processed successfully (566ms)
