From: John <jo...@to...> - 2012-03-28 23:34:24
|
Misterhouse is not tracking state based on xpl message like I expect. in items.mht: XPL_SENSOR, slotcar-sensors.water:1, WaterDetector_1, Sensors, current With debug=xpl, here is what is in the log when trigger message is sent by device on network: db1 xpl check: s=slotcar-sensors.water c=sensor.basic t=* d= xpl-trig { hop=1 source=slotcar-sensors.water target=* } sensor.basic { device=1 type=input current=1 } Device monitoring enabled: key=device, id=1, tested value=1 db1 xpl check: s=slotcar-sensors.water c=sensor.basic t=* d= xpl-trig { hop=1 source=slotcar-sensors.water target=* } sensor.basic { device=1 type=input current=0 } Device monitoring enabled: key=device, id=1, tested value=1 MH appears to be tracking to "device" key. Based on docs: http://misterhouse.wikispaces.com/xPL+-+Integrating+Common+Devices+and+Applications I expected that specifying "current" as <sensor_type> would have forced tracking to that key. Here is current user code but I based on above results I would not expect this to be triggered: if ($WaterDetector_1->state_now) { print_log "WaterDetector1: state=$state"; } What am I missing? Thanks, John |
From: John <jo...@to...> - 2012-03-29 23:33:07
|
On 03/28/12 18:34, John wrote: > Misterhouse is not tracking state based on xpl message like I expect. > > in items.mht: > > XPL_SENSOR, slotcar-sensors.water:1, WaterDetector_1, Sensors, current I needed to change the sensor_type field to "input": XPL_SENSOR, slotcar-sensors.water:1, WaterDetector_1, Sensors, input John |