OmniPro II problem

[jmcgill]

I have an OmniPro II that I had professionally installed about 9 years ago. My firmware is version 3.4. It not flash upgradable. 
I have Dealer PC Access, snaplink and H@me iphone app.
 
About 2 weeks ago problems started. I have narrowed the problem down to the OPII is not executing the code that is programmed into it. 
 
I can turn on and off individual lights with the H@me iphone app or at the touchpanels.
H@me app shows that various motion detectors are working.
 
But I have several lighting scenes that are programmed as Buttons. Day mode, Goodnight mode are buttons. But when I press these, they do no execute.
 
Also, in my walk in master closet, the lights are supposed to turn on automatically for 5 minutes when triggered by the motion detector. We also have a motion detector on the front porch that is supposed to turn on due to motion.
 
I have tried resetting my OPII (by cutting power and disconnecting backup batteries). I have also exported and imported the programming out of and into the OP using PC Access.
 
Any suggestions?

 

[picta]

What lighting system are you using? Are the scenes programmed within lighting system or in PC access? Try to isolate the problem by adding Log message into the code, for example:
 
118.    WHEN Z10 NOT READY
            THEN LOG PORCH MOTION
            THEN Porch ON FOR 5 MINUTES
 
Do you see the log message and the lights do not turn on?

 

[jmcgill]

Lighting is UPB, by simply automated. Lighting scenes are in PC Access, using "Buttons". 
 
I tried your suggestion, by changing the following:
 
3. WHEN Mbed Closet MOT NOT READY
THEN MbedCloset ON FOR 3 MINUTES
 

3. WHEN Mbed Closet MOT NOT READY
THEN LOG master closet motion
THEN MbedCloset ON FOR 3 MINUTES
 
Then from the Comminications Tab, I clicked write to controller. 
 
Now everything is working again! Thank you for your help.
 
There seems to be 2 ways to upload a program to the OPII.
1. File --> Import
2. Communications --> Write to controller
Maybe someone could comment on the difference between these two methods.
 
 
 
 

 

[picta]

The File->Import does not upload program to the controller, it is uploading a file into PC access. Only "write to controller" updates the controller.

 

[sjht]

Lighting is UPB, by simply automated. Lighting scenes are in PC Access, using "Buttons". 
 
I tried your suggestion, by changing the following:
 
3. WHEN Mbed Closet MOT NOT READY
THEN MbedCloset ON FOR 3 MINUTES
 

3. WHEN Mbed Closet MOT NOT READY
THEN LOG master closet motion
THEN MbedCloset ON FOR 3 MINUTES
 
Then from the Comminications Tab, I clicked write to controller. 
 
Now everything is working again! Thank you for your help.
 
There seems to be 2 ways to upload a program to the OPII.
1. File --> Import
2. Communications --> Write to controller
Maybe someone could comment on the difference between these two methods.
 
 
 
 

I have an issue that started when I upgraded to the latest firmware and PC Access. My lights turn on, but don't turn off when the timer ends. They just stay on. No coding changes. Any suggestions? Thanks. SJ

 

[picta]

You can try to reload the firmware again. Do you have a software controller connected to the panel?

 

[sjht]

What do you mean? I'm running everything from the OP2. I do have a Mac mini running haiku but only use for notifications at this point. Everything else works fine. SJ

 

[picta]

What devices do you have connected to the serial ports? I've had similar problems with timers in the past when I had  a Homeseer plugin connected to the panel.

 

[sjht]

The only controlling devices are a global cache network device that integrates some of my home theater devices (and send serial commands) and iRule devices that connect via IP to control. All of these only do things when commanded via their devices. Not sure this would cause an issue as they are not doing anything if not activated from the device. SJ.

 

[JonW]

Watch the device in PCAccess under Status/Control and see if it initially starts with a timer and then the timer goes away.  I recently had this happening on a fan that I was activating from a keypad.  It would initially turn on for the specified time, but then when the HAI polling logic would check the device status, it would simply switch to "ON" and not go off.  I worked around it by changing the device to a UPB configured ID instead of an HLC one so it wouldn't get polled by the panel.  I think it is a bug and may be the same issue you are seeing.

 

[sjht]

I found the issue. I was using the set lighting level command vs. just on. In the past, it used to turn off after the timer ended, but now it seems to return to the previous lighting level even though the unit may have been turned off manually. I changed to just ON, and it works fine. Shuts off after the end of the timer. SJ