Something else to look into

[spknapp]

As if my other post wasn't enough to worry about, I have been looking at Wadenut's Thermostat Scheduler script package. Working with Greg it's to the point now that his script isn't throwing out errors. But my CT-80 and BeakerStat don't seem to act on what his script sends to it.

For example, I just had a test event fire to change the setpoint to 72. The log shows that his script thinks it sent the command:

BeakerStat Unit #1 Setpoint set to 72

but yet my thermostat doesn't reflect this new setpoint and the BeakerStat debug file does not seem to have any related activity at that time.

So, now to you, Reid, should Greg's Thermostat Scheduler script work with BeakerStat?

(Lower priority than my other thread.)

Thanks

[Wadenut]

To add...

The specific script line would have been

hs.plugin("BeakerStat").CmdSetHeat(1,72,1)

[The script does work 100% with both 'ZWave Thermostats' and 'DooStat' (X10) using the same cmds]

[reidfo]

Something else to look into

I haven't used Greg's script so I don't know how it controls the thermostats. If it uses the thermostat API then it should work. I will have a look this weekend.

[reidfo]

Something else to look into

To add...

The specific script line would have been

hs.plugin("BeakerStat").CmdSetHeat(1,72,1)

Ok so it uses the thermostat API. I will do some testing this weekend to see what's going on.