- This topic is empty.
-
Posts
-
Have a look at http://rayshobby.net/?p=8422, and the comments about JSON output. The queries most likely to help are /jo (controller option settings) and /jc (controller variables).
Mark
is there a general movement towards json over the http get commands? or are they both going to be supported going forward?
The JSON replies still occur over HTTP GET. The difference is a trusted syntax over parsing random HTML (that changes from build to build). This way apps/services built on top of OpenSprinkler can reliably get controller data.
I second Samer. The JSON data is still retrieved with a HTTP GET command, but it’s in a nice form that many programming languages (Javascript, Python, PHP…) can directly parse.
sounds good, I have been looking through the values returned from the different options, and am not noticing one that shows the status of the rain device…is the json options for each command documented somewhere?
The JSON options are not documented in the user manual yet (I should add it soon). Here is the list of available commands:
http://x.x.x.x/jo: returns options.
http://x.x.x.x/jc: returns controller variables.
http://x.x.x.x/jp: returns program data.
http://x.x.x.x/jn: returns station names and data.
http://x.x.x.x/js: returns station status bits.
from the variable name you should be able to figure out the meaning of each variable.
- You must be logged in to reply to this topic.