slightly different dm/netremote issue

[mhwlng]

Girder remembers the last state of x10 devices when stopping/starting.

this causes problems for motion detectors, because

*the motion detector is triggered (not ready)
*girder is stopped
* after 1 minute, the motion detector is no longer triggered and sends the 'ready' condition
* girder is started (thinking it is still 'not ready')
* I move around, the motion detector sends 'not ready'
* the girder device manager does nothing, because it thinks that the state hasn't changed...

I tried to 'reset' the x10 motion detectors (like the lamps) at girder startup

but this doesn't work :



require 'DeviceManager.Devices'
require 'DeviceManager.Controls'
local ActionSource = 'Action'
for _,Device in ipairs(DeviceManager:GetDevices ('','','Security\\Sensor','') ) do
for _, Control in ipairs(Device:GetControls()) do
if Control:GetName () == 'Condition' then
Control:SetValue ('Ready',ActionSource)

print (Control:GetValue());

end
end
end
DeviceManager:NotifyAll(function(...) DeviceManager.ConnectionManager:HandleEvent(unpack (arg)) end)


so I assume that the Condition is a read-only property ?

any ideas ?

Marcel

[Rob H]

I'll have to leave this one for Mike

[Promixis]

added ability to select whether or not the device condition is persisted on the x10 device manager menu

[mhwlng]

that's 3 Promixis people helping me on new Year's eve :-)

Soooo.... what will happen if it's not persisted and you restart girder.

does it revert to a default value (e.g. 'Ready' ) or something ?



Marcel

[Promixis]

that's 3 Promixis people helping me on new Year's eve :-)

Soooo.... what will happen if it's not persisted and you restart girder.

does it revert to a default value (e.g. 'Ready' ) or something ?



Marcel


Its going to be 'unknown'

[mhwlng]

ok, thanks....

Marcel