Color bulb no longer changing color based on temperature from weather station


#1

1) Give a description of the problem
My piston was working great until a few days ago. The color of a bulb no longer changes color because the dynamic info is “stuck” at 32 degrees and the associated hex color.

2) What is the expected behaviour?
The bulb color should change based on the temperature reported in the Get request. The data used has not seemed to change https://swd.weatherflow.com/swd/rest/observations/station/8616?token=5894bcfa-a5fc-4188-8637-77dff56426bb

3) What is happening/not happening?
It’s not using the reported temperature from the GET request and is reverting to only 32 degrees. Not sure if it’s a coincidence as I recently updated my webcore smart app.

**4) Post a Green Snapshot of the piston!
(upload://f03B65VPQ38BbkHS5zQijdJRiag.png)

**4) Post a Green Snapshot of the piston![image|45x37]

5) Attach logs after turning logging level to Full
2/8/2021, 1:33:01 PM +366ms
+0ms ╔Received event [Home].wc_async_reply = httpRequest with a delay of 1ms
+71ms ║RunTime Analysis CS > 16ms > PS > 6ms > PE > 49ms > CE
+74ms ║Runtime (46167 bytes) successfully initialized in 6ms (v0.3.113.20210203) (73ms)
+75ms ║╔Execution stage started
+89ms ║║Calculating (decimal) 32.0 , (decimal) 0.0 >> (decimal) 32.0
+93ms ║║Executed virtual command setVariable (2ms)
+137ms ║║Calculating (dynamic) 32.0 <= (integer) 110 >> (boolean) true
+143ms ║║Calculating (dynamic) 32.0 <= (integer) 100 >> (boolean) true
+148ms ║║Calculating (dynamic) 32.0 <= (integer) 95 >> (boolean) true
+153ms ║║Calculating (dynamic) 32.0 <= (integer) 90 >> (boolean) true
+159ms ║║Calculating (dynamic) 32.0 <= (integer) 85 >> (boolean) true
+164ms ║║Calculating (dynamic) 32.0 <= (integer) 80 >> (boolean) true
+169ms ║║Calculating (dynamic) 32.0 <= (integer) 75 >> (boolean) true
+174ms ║║Calculating (dynamic) 32.0 <= (integer) 70 >> (boolean) true
+179ms ║║Calculating (dynamic) 32.0 <= (integer) 65 >> (boolean) true
+184ms ║║Calculating (dynamic) 32.0 <= (integer) 60 >> (boolean) true
+188ms ║║Calculating (dynamic) 32.0 <= (integer) 55 >> (boolean) true
+193ms ║║Calculating (dynamic) 32.0 <= (integer) 50 >> (boolean) true
+197ms ║║Calculating (dynamic) 32.0 <= (integer) 45 >> (boolean) true
+202ms ║║Calculating (dynamic) 32.0 <= (decimal) 40.0 >> (boolean) true
+206ms ║║Calculating (dynamic) 32.0 <= (decimal) 32.0 >> (boolean) true
+210ms ║║Calculating (dynamic) 32.0 <= (decimal) 15.0 >> (boolean) false
+214ms ║║Calculating (dynamic) 32.0 <= (decimal) 0.0 >> (boolean) false
+217ms ║║Calculating (decimal) 0.0 - (decimal) 5.0 >> (decimal) -5.0
+220ms ║║Calculating (dynamic) 32.0 <= (decimal) -5.0 >> (boolean) false
+225ms ║║Executed virtual command setVariable (3ms)
+227ms ║║Cancelling statement #23’s schedules…
+238ms ║║Executed physical command [Weather Lamp].setColor([[hex: #4242ff, hue:67, saturation:100, level:63]]) (5ms)
+238ms ║║Executed [Weather Lamp].setColor (8ms)
+241ms ║╚Execution stage complete. (166ms)
+242ms ║Setting up scheduled job for Mon, Feb 8 2021 @ 1:38:02 PM CST (in 300s)
+252ms ╚Event processed successfully (252ms)


#2

To my eyes the expression used to set the Response variable doesn’t look right. Shouldn’t the ,0 at the end be inside the last )?

That said, I don’t think that is your problem. $response.obs.air_temperature must be evaluating as 0 regardless.

There have been some changes to web request handling in the latest webCoRE update, but I don’t know if that is a factor.


#3

I’m thinking the latest update in Webcore in which web request items were “fixed” may have done something to my previously working get request.