Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
HTTP Receiver "Set point name"
-
I'm curious what the "Settable" and "Set point name" properties for a Data Point do. The help text does not even mention them, and I couldn't find any documentation on the site.
-
Where are you seeing "Set point name"? What type of data source are you looking at?
edit. ah right there in the title, listen to @phildunlap"Settable" controls whether the point can be written to.
-
Hi Aldo,
I'd encourage you to test with netcat, but when you set a settable HTTP Receiver point, it should send an HTTP GET to
[setPointUrl]?name=[setPointName]&value=[value] -
This is on the actual "Point Details" tab:
You can see HTTP parameter name is already set above it. So what do the other properties control?
Trying to better understand, mostly academic, but if it can be "settable" (i.e. user settable on that Mango instance) it would have practical uses for me.
-
What I'm wondering is if an HTTP Receiver Data Point can be “settable” in the sense that it can be manually overridden by user input.
Also what is the difference between HTTP parameter name and Set point name? Help text does not describe Set point name
-
You mean can you "set" a value to it and have that be the value without doing a regular set action?
About the only ways to programmatically insert values without going through the normal set action of a data source are
- The scripting data source if 'Saves historic' is checked. Then all set() calls will bypass logging type, the data source, and events (detectors, meta points, etc.)
- The data file data source if the new values are older than the existing values.
Other things, like the point data import, will also bypass the data source in creating a value history.
The HTTP parameter name is the incoming format. The GET request from the publisher will look like
http://yourip/httpds?parameterName=value@time&otherParameterName=value@timeThe Set Point Name is the outgoing format, as I described,
setPointUrl?name=setPointName&value=value@time
