Hi, thanks for your work. Bus as said, no hurries
Today I got a todays forecast. I disabled the auto polling to prevent API usage. This seems to work.
Perhaps the issue was caused by 2 devices with the same API key polling too much.
Hello Pieter
thanks for this great app, but since the update this morning the manual calls no longer work, I have now set it to automatic and it does work. [2 sites (east west) 2 API keys and 50 calls => 25 per site]
OK, I have downloaded 3.2.2 and this happens. Card Unavailable. Error - "Network Request Failed. And if I try and replace it Solcast isn’t in the Apps list. Happened with 3.2.1 also. Because it crashed I couldn’t generate a diagnostic. Here is one after the App recovered.
There is a new test version 3.3.0 available.
It is still rough, but should work.
Test on own risk
New:
When you selected the new API (10 calls) or disabled polling and use flows to manual update:
The app will every half hour update the values with previous fetched data (historic), so without an API call.
The API calls are visible in the device itself. (As far as I know, it is not possible in homey to display date time in the device, that’ s the only way to easily see when the last update from Solcast was)
Hey, just a hint: You can use a string capability to show up in sensor view. You can fill it with the local time. I t dependes on the API data if ou can use the epoch time from the API (if provided) or use Homey time (that’s UTC, so yopu have to convert it to local time fur the user).
Example:
=> homey.openweathermap/drivers/owmOnecallCurrent/device.js at master · RonnyWinkler/homey.openweathermap · GitHub
=> Get timtezone: let tz = this.homey.clock.getTimezone();
To simplify the app, I suggest to remove the whole automatic polling thing and old and new api.
I guess it is easier to use flows to fetch updates, so you can choose yourself the amount of api updates.
If you have more than 1 installation, it will also be easier.
I will work on the intermediate updates, based on historic data.
Hi @Pieterv123 thanx for this app. I’m checking in as a new user. I created a solcast account, installed the app and solcast device and the example update flows. Everything is working as expected. Very easy to get up and running. In the coming day’s I will monitor the predictions and functionality and finetune my use case for this app and information. My main purpose will be to optimise the charging of my Sessy Homebattery on solar power.
Af few questions:
Am i right the midnight update time for the Netherlands is at 02:00 (like in your example)?
I observed the API calls counter was reset to 0 after the first 30 minute in-app update. I had 2 api call’s and now it is back on 0. Is this correct behaviour? I would suspect the reset would be round midnight update? Diagnostic report 33407f38-39f6-427a-942c-0674c77f6e7f