pete_c
Guru
I've had my Omnistat connected to my OmniPro II now for a few years but only monitored temps, humidity, remote temps and humidity.
Historically I have only used the built in scheduling and never attempted any remote scheduling.
I decided this past week to give it a try writing the turn ups and turn downs onto my OmniProII.
1 - I've disabled the automatic scheduling on the OmniStat.
2 - I created a simple schedule. Turn down at night and turn up in the morning.
3 - I watched my script work this morning. Wierd things happened.
The script changed the setpoint to 70F this morning like it was supposed to. I saw the change on the Omnistat.
One hour later or so the setpoint went to 74F apparently by itself. This event never even programmed or existing.
This is causing me some WAF grief this morning.
Any ideas?
Historically I have only used the built in scheduling and never attempted any remote scheduling.
I decided this past week to give it a try writing the turn ups and turn downs onto my OmniProII.
1 - I've disabled the automatic scheduling on the OmniStat.
2 - I created a simple schedule. Turn down at night and turn up in the morning.
3 - I watched my script work this morning. Wierd things happened.
The script changed the setpoint to 70F this morning like it was supposed to. I saw the change on the Omnistat.
One hour later or so the setpoint went to 74F apparently by itself. This event never even programmed or existing.
This is causing me some WAF grief this morning.
Any ideas?