Buienalarm weather forecast not updating

Hi Guys, after 10 days no reaction on github...
Maybe you know the answer;

When inputting {"trigger": true} into the node, the node outputs data of Buienalarm and Buienradar.

The Buienradar output is up to date, but the Buienalarm output is dated the last time the flows where restarted.

After restarting the flows, the first trigger lists current info, but the buienalarm output is stale from that point on.
Please check the screenshot.

Version info:
Node-Red; 2.1.4
node-red-contrib-dutch-weather; 2.0.12
Issue and info on github; Buienalarm forecast not updating · Issue #11 · gvdhoven/node-red-contrib-dutch-weather · GitHub

It is possible that the weatherstation/buienalarm that provided the info no longer provides it for the location ?

Can you post a simple flow showing the problem?
I installed the nodes and can't make them do anything at all.

But I note that the entire "help" for the node is this

dutch-weather-rain-state

Provides information from the Dutch rain info provider Buienalarm at the interval defined in the configuration node.

The configuration node has Latitude & Longitude, but no Interval.

Hi Bakman2,
When the flows are restarted the information gets refreshed.
After that, the information is stale.


Hi Jbudd,
There needs to be an inject node to activate the node;

[
    {
        "id": "5aefb045822b9ec2",
        "type": "inject",
        "z": "54e928a42f811af3",
        "name": "1min",
        "props": [
            {
                "p": "payload"
            }
        ],
        "repeat": "60",
        "crontab": "",
        "once": false,
        "onceDelay": 0.1,
        "topic": "",
        "payload": "{\"trigger\": true}",
        "payloadType": "json",
        "x": 130,
        "y": 320,
        "wires": [
            [
                "c0f836a87e5f1f8d"
            ]
        ]
    }
]

I cannot reverse engineer his script but he is keeping track of the last time the data was fetched as the api refreshes the data every 4 minutes. Something might go wrong there.

Hmm to bad then. Thanks for you effort.
Hope that the owner of the node looks at Github then :wink: