Page 1 of 1

nvalue vs. svalue

Posted: Tuesday 18 April 2017 15:55
by rickvanakkeren
Hi all,

Can someone explain to me what the difference is between a nvalue and a svalue?

The reason I'm asking is when i'm looking in the API-URL's, most off the time 'nvalue=0' is in the URL and svalue is used. But not for all. For example, why does the Air Quality require a nvalue instead of a svalue?

Rick

Re: nvalue vs. svalue

Posted: Tuesday 18 April 2017 19:26
by SweetPants
I think it has to do with 'n'umerical and 's'tring values??

Re: nvalue vs. svalue

Posted: Tuesday 25 April 2017 23:08
by axello2
Sounds plausible, but why are all the *numeric values* on the domoticz/out channel with the svalue# keyword?

Is this whole nvalue, stype, svalue1, svalue2 etc. documented somewhere? As I run into a snafu creating my own service.

It's mentioned on the http://www.domoticz.com/wiki/MQTT page, but not explained.
It is shown, but not explained in http://www.domoticz.com/wiki/Domoticz_API/JSON_URL

Re: nvalue vs. svalue

Posted: Wednesday 24 May 2017 0:16
by maho2nd
I have the same question.

In the JSON-API sometimes the nvalue is used (Air quality) and most times the svalue is used (Temperature, etc.)