1.8 Alpha2 Forecast.io - Widget Does Not Download

When trying to use the Scheduler to schedule Forecast.io the Displays fail to download the widget:

We did try the verify all link.

Log:

15729	1405e56	2016-02-07 21:27	XMDS	POST	ERROR	Bako-BigCountry-03	GetResource	Request failed for dataSet id=4. Widget=203. Due to Not Found
15728	1405e56	2016-02-07 21:27	XMDS	POST	NOTICE	Bako-BigCountry-03	GetResource	Matched column: bgImagePath|10
15727	1405e56	2016-02-07 21:27	XMDS	POST	NOTICE	Bako-BigCountry-03	GetResource	Then template for each row is: <p><img src="[bgImagePath|10]" style="width: 100%;" /></p>
15726	1405e56	2016-02-07 21:27	XMDS	POST	DEBUG		GetResource	Manage links to Display Group
15725	1405e56	2016-02-07 21:27	XMDS	POST	DEBUG		GetResource	Updating Display Group. Bako-BigCountry-03, 2

UPDATE: I should have noted that the layout has been imported from an export on 1.7.3

UPDATE 2: When trying to just create a basic layout with just the default region, only Forecasti.io set to run, and assigning it as the default layout we get this:

17080	2016-02-07 21:40	Unable to reach Forecast API: Client error: `GET https://api.forecast.io/forecast/<FORCAST.IO API KEY>/,?units=auto&amp;lang=en&amp;exclude=flags%2Cminutely%2Chourly` resulted in a `400 Bad Request` response: &lt;html&gt; &lt;head&gt;&lt

We double checked our Forecast.io API key, even changed it just in case. And we do see the weather in the layout builder, and preview of the new layout we created. (The old, imported layout fails to function, so I think, if I remember right that part just has not been completed yet.) So we are not sure why the 400 bad request. Even double checked my cacert.pem. And we have not hit the daily limit.

We figured out that the “Unable to reach Forecast API” error was because we did not fill out the longitude and latitude on the display itself. So I think that is a bug as I would think that the default set in setting would have applied. Also I would like to request an enhancement to the error message to indicate missing longitude and latitude.

So I the problem really seems to be that, currently, importing layouts containing Forecast.io … uh Widgets?.., is currently not supported.

Isn’t the problem that we should validate the long/lat are filled in correctly and if not present a better error message? I don’t see that there is anything wrong with importing a layout with forecast io in it.

Dan,

Yes on the error message that would work. I was thinking that the default long/lat would be applied if the display itself did not have the setting. But it looks like that is only used for previews.

You are correct that the problem with the missing widget was not caused by the import of the layout that included Forcast.io. It was that we also had used a dataset on the layout as well. It was the dataset that the layout was referencing, and it was not there. (We are hoping that 1.8 will be able to import these datasets when the final release happens)


:smile:

Thank You! (20 Characters)

Hahaha, awesome!! (123)

A post was split to a new topic: Importing Layouts Containing DataSets