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
nvalue vs. svalue
Moderators: leecollings, remb0
-
- Posts: 26
- Joined: Thursday 03 December 2015 13:58
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: nvalue vs. svalue
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
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
-
- Posts: 3
- Joined: Wednesday 24 May 2017 0:13
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: nvalue vs. svalue
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.)
In the JSON-API sometimes the nvalue is used (Air quality) and most times the svalue is used (Temperature, etc.)
Who is online
Users browsing this forum: No registered users and 0 guests