Re: Re: Consensus on BSC temperature reporting?

[Lehane Kellett <lehane@xxxxxxxxxxxxxxxxxxx>]

OK - so how about new classes - sensor.report and sensor.cmd?

Devices could be simple (one wire) or complex (complete CH system).

Schema example (barebones):

Event
{
datetime=<datetime>
--mandatory
type=temperature  pressure  humidity  flow  illuminance  voltage
current  energy
--mandatory
unit=Celsius  Pascal  RH%  LitreSec  Lumen  Volt  Amp  Joule
--mandatory
(other acceptable units for temperature - Fahrenheit, Kelvin)
(other acceptable units for pressure - Bar, PSI, Arbritary)
(other acceptable units for humidity - Arbritary)
(other acceptable units for flow - CuInSec, CuFtSec, Arbritary)
(other acceptable units for illuminance - CustomPercent, Arbritary)
(other acceptable units for energy - KilowattHour, Arbritary)
unitexp=<ten to the power multiplier of unit - example for
kiloPascal(kPa) unitexp=3)
--optional
value=<signed numeric value of variable including optional decimal point
to any number of places>
--mandatory
setpoint=<signed numeric value of process target including optional
decimal point to any number of places and in same units as variable>
--optional
lolimit=<signed numeric value of process lower limit including optional
decimal point to any number of places and in same units as variable>
--optional
hilimit=<signed numeric value of  process upper limit including optional
decimal point to any number of places and in same units as variable>
--optional
text=<descriptive text>
--optional
}

You can then set the process values:

Command
{
type=temperature  pressure  humidity  flow  illuminance  voltage
current  energy
--mandatory
unit=Celsius  Pascal  RH%  LitreSec  Lumen  Volt  Amp  Joule
--mandatory
(other acceptable units for temperature - Fahrenheit, Kelvin)
(other acceptable units for pressure - Bar, PSI, Arbritary)
(other acceptable units for humidity - Arbritary)
(other acceptable units for flow - CuInSec, CuFtSec, Arbritary)
(other acceptable units for illuminance - CustomPercent, Arbritary)
(other acceptable units for energy - KilowattHour, Arbritary)
unitexp=<ten to the power multiplier of unit - example for
kiloPascal(kPa) unitexp=3)
--optional
setpoint=<signed numeric value of process target including optional
decimal point to any number of places and in same units as variable>
--optional
lolimit=<signed numeric value of process lower limit including optional
decimal point to any number of places and in same units as variable>
--optional
hilimit=<signed numeric value of  process upper limit including optional
decimal point to any number of places and in same units as variable>
--optional
text=<descriptive text>
--optional
reportinterval=<value in seconds before sending sensor.report unless
value changed by delta>
--optional
delta=<numeric value that sensor value must change before sending
sensor.report unless reportinterval expired>
--optional
}

Examples:

....
device=mmwave.roomstat.bathroom1
class=sensor.report
}
event
{
datetime=20060831161400
type=temperature
unit=celsius
value=18.4
setpoint=22
lowlimit=4
}
event
{
datetime=20060831161400
type=humidity
unit=rh%
value=95
setpoint=90
}

....
device=mmwave.sunsensor.northfacing
class=sensor.report
}
event
{
datetime=20060831161400
type=illuminance
unit=arbritary
value=167
}

....
target=mmwave.roomstat.bathroom1
class=sensor.cmd
}
command
{
type=temperature
unit=celsius
setpoint=23.5
lowlimit=-4
delta=0.5
}

Lots of rules not defined -  for example a device should irrespective of
reportinterval or delta send a report when a process variable is met or
crossed and if so change to Event.Setpoint, etc?
If a device reports in Celsius but is sent a (setpoint) command in
Fahrenheit should it perform the conversion?
Should it be broken down to event.temperature, command.setpoint, etc?

Dons flameproof suit.....

Lehane