TWC Weather - Revision history

Ipaterson: Fixed weather icons that are no longer hosted by SmartThings

2022-11-17T14:41:13Z

Fixed weather icons that are no longer hosted by SmartThings

2022-01-09T01:56:14Z

‎Partial day forecast

2022-01-09T01:55:06Z

‎Partial day forecast

2022-01-09T01:53:16Z

‎Partial day forecast

2022-01-09T01:51:06Z

‎Forecast

2022-01-09T01:46:01Z

‎Forecast

2022-01-09T01:45:39Z

‎Forecast

2022-01-09T01:44:49Z

‎Forecast

2022-01-09T01:44:01Z

‎Forecast

2022-01-09T01:43:16Z

‎Forecast

@@ Line 396: / Line 396: @@
 [[WCmore's_Graphs#twcweather.forecast.daypart|Preliminary testing]] shows that today's morning/daytime data [0] turns null shortly after 3PM each day, and the next day's data shifts to [0] and [1] shortly after 3AM.  This means from approximately 3PM to 3AM, you will find [0] to be null, and [1] will show data from the evening/night in progress.  This also means that at about 3AM, the data for the night in progress vanishes, and is replaced with data for the following day/night.
-Edit: I have created a [https://community.webcore.co/t/twcweather-forecast-preserve-data-lost-at-3-oclock/20396?u=wcmore piston] to circumvent this craziness.
+Edit: I have created a [https://community.webcore.co/t/twcweather-forecast-preserve-data-lost-at-3-oclock/20396?u=wcmore piston] to out-smart this craziness.
 {| class="wikitable" style="margin: auto;"

@@ Line 395: / Line 395: @@
 [[WCmore's_Graphs#twcweather.forecast.daypart|Preliminary testing]] shows that today's morning/daytime data [0] turns null shortly after 3PM each day, and the next day's data shifts to [0] and [1] shortly after 3AM.  This means from approximately 3PM to 3AM, you will find [0] to be null, and [1] will show data from the evening/night in progress.  This also means that at about 3AM, the data for the night in progress vanishes, and is replaced with data for the following day/night.
 {| class="wikitable" style="margin: auto;"
@@ Line 402: / Line 404: @@
   *  8 changed between 3:20 and 3:36   (20% of the time)
 |}

← Older revision		Revision as of 01:53, 9 January 2022
Line 402:		Line 402:
	* 8 changed between 3:20 and 3:36 (20% of the time)		* 8 changed between 3:20 and 3:36 (20% of the time)
	\|}		\|}
		+
		+	2022 Edit: I have created a [https://community.webcore.co/t/twcweather-forecast-preserve-data-lost-at-3-oclock/20396?u=wcmore piston] to out-smart this craziness.

@@ Line 161: / Line 161: @@
 day forecast; append the index to get an individual day. For example, <code>$twcweather.forecast.temperatureMin[0]</code> is today's low temperature.
-Normally, [0] is today's data, and [1] is tomorrow's data... but initial observations indicate that the data shifts over to a new day at approximately 3:15am, not at midnight, as one would expect.  So from midnight to about 3:15am, the [0] data will likely be displaying '''yesterday's''' data, and [1] will be the '''current''' day.  Once the data shifts over, then [0] will go back to being today, and [1] being tomorrow.  <br>
+Normally, [0] is today's data, and [1] is tomorrow's data... but [[WCmore's_Graphs|initial observations]] indicate that the data shifts over to a new day at approximately 3:15am, not at midnight, as one would expect.  So from midnight to about 3:15am, the [0] data will likely be displaying '''yesterday's''' data, and [1] will be the '''current''' day.  Once the data shifts over, then [0] will go back to being today, and [1] being tomorrow.  <br>
 (IE: 20+ hours a day, [0] is today... 3+ hours a day, [1] is today... with events during the 3am hour potentially going in either direction)

@@ Line 161: / Line 161: @@
 day forecast; append the index to get an individual day. For example, <code>$twcweather.forecast.temperatureMin[0]</code> is today's low temperature.
-Normally, [0] is today's data, and [1] is tomorrow's data... but initial observations indicate that the data shifts over to a new day at approximately 3:15am, not at midnight, as one would expect.  So from midnight to about 3:15am, the [0] data will likely be displaying '''yesterday's''' data, and [1] will be the '''current''' day.  Once the data shifts over, then [0] will go back to being today, and [1] being tomorrow.  (IE: 20+ hours a day, [0] is today... 3+ hours a day, [1] is today... with events during the 3am hour potentially going in either direction)
+Normally, [0] is today's data, and [1] is tomorrow's data... but initial observations indicate that the data shifts over to a new day at approximately 3:15am, not at midnight, as one would expect.  So from midnight to about 3:15am, the [0] data will likely be displaying '''yesterday's''' data, and [1] will be the '''current''' day.  Once the data shifts over, then [0] will go back to being today, and [1] being tomorrow.  <br>
 To add to this confusion, some [0] dataPoints (for today) vanish shortly after 3pm.  <br>

@@ Line 163: / Line 163: @@
 Normally, [0] is today's data, and [1] is tomorrow's data... but initial observations indicate that the data shifts over to a new day at approximately 3:15am, not at midnight, as one would expect.  So from midnight to about 3:15am, the [0] data will likely be displaying '''yesterday's''' data, and [1] will be the '''current''' day.  Once the data shifts over, then [0] will go back to being today, and [1] being tomorrow.  (IE: 20+ hours a day, [0] is today... 3+ hours a day, [1] is today... with events during the 3am hour potentially going in either direction)
-To add to this confusion, some [0] dataPoints (for today) vanish shortly after 3pm.  (IE:$twcweather.forecast.temperatureMax[0] returns null all afternoon and into the early morning hours)
+To add to this confusion, some [0] dataPoints (for today) vanish shortly after 3pm.  <br>
-⃰ clears throat ⃰ ...  A special "Thank you" to TWC for forcing us to add extra code to work around this convoluted logic.
+⃰ clears throat ⃰ <br>  A special "Thank you" to TWC for forcing us to add extra code to work around this convoluted logic.
 To see a real life example, we can look at <code>$twcweather.forecast.dayOfWeek[0]</code>

@@ Line 165: / Line 165: @@
 To add to this confusion, some [0] dataPoints (for today) vanish shortly after 3pm.  (IE:$twcweather.forecast.temperatureMax[0] returns null all afternoon)
-⃰ clears throat⃰ ...  A special "Thank you" to TWC for forcing us to add extra code to work around this convoluted logic.
+⃰ clears throat ⃰ ...  A special "Thank you" to TWC for forcing us to add extra code to work around this convoluted logic.
 To see a real life example, we can look at <code>$twcweather.forecast.dayOfWeek[0]</code>