Hey,
> That's the caching. You configured it as follows:
>
>> "cache": {"schedule": "m.02"}
*That's* the caching feature, ok… shouldn't it be updated every 2
minutes with our setting?
Seems to be broken, I've removed it entirely now - at least in our json.
Thanks for the tip!
Bye,
jomat