Omni Pro II & Omnistat RC80

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?
 
I'm afraid I don't know much about the RC80, but...

1. Does it maybe have some occupancy mode setpoints that need to be disabled? Possibly it changed when you disarmed your alarm this morning?

2. Do you have more than one? If so, make sure they are set to different addresses.

3. Make sure the thermostat has a name in the OPII setup. If it doesn't, then the OPII may not have zone 16 properly configured to communicate with it. Also make sure the thermostat type is set properly in the setup.
 
Its been connected to the HAI Omni II Pro panel now for about 6 years. Never scripted anything in panel regarding schedules or turning it on or off until now. (no occupancy modes/setpoints). I only told it to change the set point at night and again in the morning. I've deleted the lines in the script for now. I only have one. Zone 16 is set up as Thermostat - Auxillary. Its set up as Auto Heat/Cool in setup. Hold is working and buying me WAF for the present.

Thank you for your suggestions Cornutt.
 
Another couple of wierd things happened last night.

Currently have left thermostat in HOLD mode.

I took it off hold last night and all was fine for about 1 hour then again the heat setpoint went to 74F with nothing telling it to do so - back to hold.

Getting ready to enable auto schedule on thermostat and disconnect it from HAI panel. Did I upset the balance of things by introducing some code to control my thermostat?
Here is a snippet of what I did after I shut off the internal scheduling. A bit extreme on the temps but it should have worked.

TIMED 12:01 AM MTWTFSS
THEN Thermostat HEAT SETPOINT 60
TIMED 6:01 AM MTWTFSS
THEN Thermostat HEAT SETPOINT 68
TIMED 10:01 AM MTWTFSS
THEN Thermostat HEAT SETPOINT 58


While deciding to automate thermostat settings (now code has been removed) "neated" up my lighting scripts bundling groups of lights in single statements instead of having one line per light.

All my outdoor lights indoor lights that I didn't manually shut off stayed on last night.

I know there is no communications problems in that I can manually shut off and turn on lights from PCA and the consoles.

Today will reset HAI panel from scratch and upload current config to see if that changes anything.

Very frustrating in that I haven't done anything but update the programming lines to consolidate some automatic panel actions. (snippet attached - lights are going on but last night none of them went off)

TIMED SUNSET MTWTFSS
THEN Chandelier BRIGHT 3
THEN Front Hallwa BRIGHT 2
THEN Dining Room BRIGHT 4
THEN Dining Outlt BRIGHT 7
THEN Living Room BRIGHT 6
THEN Family Room DIM 6
THEN Sink Light BRIGHT 3
THEN Kitch Table BRIGHT 6
THEN Master BR ON
THEN Study Lamp ON
THEN Meagans BR BRIGHT 3
THEN Edwards BR BRIGHT 3
THEN Edwards BR C BRIGHT 2
THEN Curio BRIGHT 2
THEN Curio-2 BRIGHT 4

TIMED 10:45 PM MTWTFSS
THEN Meagans BR OFF
THEN Edwards BR OFF
THEN Edwards BR C OFF
THEN Curio OFF
THEN Curio-2 OFF

I've reset the panel once or twice in the last 5 or so years. Will look in the installation manual for directions.
 
Hmm. If you OPII is that old, it probably has firmware in ROM. What version are you running? Maybe this is an old firmware bug.

BTW, one thing I have in mine is a rule that logs a "mark time" message every four hours. That way, if the controller firmware were to stop running for some reason, I could look in the log and determine roughly when it happened.
 
Yes my OmniPro II is old (5-6 years old) with the ability to upgrade FW ROM.

I updated from FW Rev 2.14 (many years) to FW Rev 3.2D about beginning of DEC, 09.


I updated FW to take advantage of the new protocol and enchancements reading that new rev was pretty stable. (what made me do it)

The mark time code to log sounds interesting - can you please post it.

I am sending a time sync to the HAI panel via HS about once a day. Other than the time sync I have only a few events in HS which talk to the panel (just mostly reading status type stuff).

All of the lighting today (including supplimental security lighting events) is done on the HAI panel. I'm wondering if thats even working since I consolidated my lines of code.

The only changes to my panel relate to a consolidation of code and introduction of migrating the Omnistat built in scheduling over to the panel. I don't believe this would overwhelm what the panel is doing and is pretty non invasive.

I was hoping to do the same with a second panel in a very similar setup but now thinking "not yet" for the time being.

WHEN Ext Deck IR NOT READY
AND IF TIME CLOCK 1 ENABLED
THEN Deck Coach ON FOR 10 MINUTES
THEN Rear Coach ON FOR 10 MINUTES
THEN Deck Lights ON FOR 10 MINUTES

It used to be like this:

WHEN Ext Deck IR NOT READY
AND IF TIME CLOCK 1 ENABLED
THEN Deck Coach ON FOR 10 MINUTES

WHEN Ext Deck IR NOT READY
AND IF TIME CLOCK 1 ENABLED
THEN Rear Coach ON FOR 10 MINUTES

WHEN Ext Deck IR NOT READY
AND IF TIME CLOCK 1 ENABLED
THEN Deck Lights ON FOR 10 MINUTES

Can someone detail the process for the warm / cold reboot? (I've done both but forgot and working on my gig network stuff today primarily)
 
Pete, unfortunately I'm about out of ideas. Hopefully someone from HAI can chime in here on Monday.

Is your version of PC Access up to date? You need at least 3.2.0.543 to run with the 3.2D firmware. Otherwise it won't generate correct code.

IIRC, you access the clear-memory functions from the console: Go into setup with the installer code, hit # to get to the installer settings, and then thumb through with the arrows -- it's near the end of the list. You might just want to try a power cycle first. Disconnect the battery, pull the power for about a minute, re-connect the battery, and then plug it back in. You'll have to fix the time afterwards.

My "mark time" code is pretty simple actually:

EVERY 4 HOURS
THEN LOG Mark Time
 
Thermostat went back to 74 on its own again while setback is at 72.

Re-installed set backs into scripting (just three for now).

Enabled "hold" locally (concurrently dealing with WAF on this one)

Will try a cold reset today.

Noticed an update to FW on OmniProII panel to 3.3 from 3.2D last night.

Didn't do a cold reset yet but wondering if I can so a reset of sorts to the RC80 thermostat. I remember a few years back doing something to reset it when I had the power problems with it.

I re-enabled the internal automatic thermostat programming and all is back to where it was before I disabled internal programming.

Next test is to disconnect HS from panel and try same again. Wierd thing is that I have had HS plugged into the HAI panel for "years". I've always left the automatic control locally and not seen this problem that won't go away.
 
Pete, I'm out of ideas. What's weird about this is that it sounds just like the symptom that some of the RC1000s/2000s were having -- but only when they were configured to display Celsius.
 
... just like the symptom that some of the RC1000s/2000s were having -- but only when they were configured to display Celsius.
Can you elaborate on that?

I have an RC-2000 configured to display in Celsius (but is not connected to an OmniPro panel) and it hasn't misbehaved like Pete's thermostat.
 
The misbehaving stopped inexplicably.

I can't figure it out and its my fault as I introduced too many variables at one time so I do don't really know which one caused the RC-80B (or communications to RC-80B) to work right. Yes mine is set up only in Fahrenheit mode.

Yesterday disconnected my HS from my HAI panel. Enabled the thermostat events on the HAI OmniPro II. Updated PC Access. Disabled RC-80B local automatic events. Enabled "heat" mode only.

Scripting on Omni Pro II worked. Ran event Lowering setpoint - it worked. Ran event raising setpoint and it worked. Manually sent commands from Omni Pro II panel to thermostat and they all worked. All of these events worked where as before they didn't.

Re-enabled HS HAI plugin. Watched OmniPro II events. Continue to work. (from yesterday afternoon). Just in watching mode right now.

I've always had the OmniStat RC-80B connected to my OmniProII but never tried to run events from Panel to Thermostat (or even from HS to thermostat) leaving it alone and only monitoring temps and other HAI temperature and humidity sensors plugged into panel.

WAF was at an all time low during these troubling times.
 
... just like the symptom that some of the RC1000s/2000s were having -- but only when they were configured to display Celsius.
Can you elaborate on that?

I have an RC-2000 configured to display in Celsius (but is not connected to an OmniPro panel) and it hasn't misbehaved like Pete's thermostat.

On early production RC1000s and 2000s, if you configure them to display Celsius, the setpoints may change randomly. It's a firmware thing. There was a thread about it here a few weeks ago. HAI will exchange ones that have the problem.
 
Last night my problem came back. Worked for 1 day.

The thermostat "wants" to go to a setpoint of 74F. No real change with that issue. Its always wants 74F no matter what I set it to with the OmniProII. If I use the OmniPro II and tell the thermostat to go to 65 it will go there. 1 hour later will have a look see and it will have a setpoint of 74F.

So last night added a line to my setback telling it to hold after I tell it to change the setpoint. I think this is working. This is kind of a "Mickey Mouse" circumvention thing.

I was thinking of manually adjusting the upper limit of the setpoint to 72 and see what it does.

Reading some older HS threads indicate that the beta HAI plugin did some interesting "stuff" with an Omnistat plugged into the panel. So today downgrading plugin to standard HS version versus beta. I believe it will still provide what I need for HS events without affecting the Omnistat thermostat.

This was kind of a ding because I was thinking of connecting another Omnistat to OmniPro II installed in FL.

Downgraded HS plugin to standard instead of beta. Manually changed heat setpoint via HAI PC Access and it "looks" like its staying. With this working right then I can still remote in via HAI and HS and make a change if needed.

The next test will be to disable event on HAI panel and enable an event in HS to do the same thing (set heat point).

Thermostat appears to be OK now with the downgrade of the HS OmniProII plugin to the pre-beta standard version. The setbacks that I wrote into the OmniPro II appear to be working per scheduled time.

I haven't tried shutting off the schedules on the OmniProII and enabling the schedules on the HS server yet.

Question?

Trying to write a couple of lines in the HAI panel using the "or" command and looking at examples but not totally figuring it out. IE:

IF X sensor is on
or
IF Y sensor is on
or
If Z sensor is on
Then
do this
and
that
 
Back
Top