60000 means every minute. Should be possible. Anyway I changed the variable - nothing.
The only update in the db is after save the config (thing).
So for me it’s currently not working. Maybe someone should try a http config and test it.
Thanks Udo, this didn´t change it though I guess it was wrong anyway. However I found out that I missed the state transformation in the channel configuration and set it to JSONPATH:$.volumen. This works, I guess I´ll never understand the logic at all.
If looking at incomming data, there are some options to setup JSONPATH.
Data is received by a Binding (here http) through a channel. a) use a channel for each bit of information, so e.g. use a number channel and provide JSONPATH to extract one Number to the Channel b) use a string Channel to get the whole JSON Object.
Channel ist linked to an Item a) 1.a): As there is a simple Number, you can’t use JSONPATH anymore. b) 1.b): The String channel provides the whole JSON Object, so now you can extract Data in the link.
This is useful if there are many informations from the same JSON Object to be extracted. You will only need one Channel per JSON Object and just link as many Items to this Channel as you need.
Item Type is not limited to String but to the Type of data which is extracted. c) You can even use a String Item to get the whole JSON Object.
When not providing the whole JSON Object through a String Item 3.c), you simply can’t use JSONPATH.
If you are using a String Item with the whole JSON Object, you can use JSONPATH within the display Options and/or you can use transformation action within a rule.
So, there are three possible options to use JSONPATH, but you can only use it at one position.
To be honest, it would be nice to exclude transformation Services when it makes no sense to use them (e.g. channel is not of type string, so there can’t be a JSON Object), but it adds a lot more of complexity, so I guess the developers chose not to do so…