HAI UPB Problems

I used Simply Automated UPB switches in a previous house and they worked great.  Because of HLC ease, I decided to go with HAI UPB switches this time, but I'm starting to think that was a bad idea. 
 
My wife especially is having lots of problems with these switches. Very often we will turn a dimmer switch ON, and the LED will change color indicating ON, but the light isn't ON.  This happens very often.  I've minimized this by using "Snap" for all the rocker fade rates. 
 
Does anyone else have any ideas how to minimize this "phantom ON" without using the Snap?  Simply Automated switches don't seem to have this problem that I can see.

If this is a locally controlled light (wired to the switch you are pressing), then likely it is being dimmed and/or set to go to last level.  You can change the options in Upstart to disable dimming and see if this fixed your problem.
 
I found when I had lights set to turn on with the ramp set at 3.3 seconds, people were sometimes pressing the button again because the lights weren't responding fast enough and/or they were trying to turn it off and then on again.  I've since changed most lights to either snap or 1.6 second ramp and it's solved the problems.

I know that Simply Automated switches have the option of changing the last level memory, but i haven't seen such a option on the HAI switches. The problem does seem to be related to that. Somehow the dim level is being changed to like 1% when they are turned on sometimes, and the LED indicates the switch is ON, but the light is not on. 
 
Using Snap for the rocker ON rate seems to help, but doesn't fully solve the problem.  If I also change the default dim rate to Snap, it seems to fully solve the problem, but then i can't dim the lights.  The best i can do is select from two dim levels, single-click and double-click.  Its such an annoyance otherwise I'm willing to do that if I have to. 
 
Here are my settings:
 
Rocker Settings
Single-Click On: 95% Snap
Double-Click On: 100% Snap
Single-Click Off: 0% Snap
Double-Click Off: 0% Snap
Report Light Level after Switched: Checked
 
 
Options
Dimming: Enabled
Default Fade Rate: 5 seconds
Minimum Dimming Level: 10%
 
Timer: Turned Off (Doesn't work anyway)
 
there is no option I see to enable/disable previous dim level memory like SA switches have.

What version of board firmware?
 
What do you mean by HLC ease?

Frederick C. Wilt said:

What version of board firmware?
 
What do you mean by HLC ease?

Click to expand...

 
What do you mean by "board firmware?"  The switch firmware is 1.09.  I don't have the Omni hooked up yet.
 
I'm planning to use HLC where the Omni tracks the status of your lights, and Leviton Room and Home controllers display this status.  Yes, I do realize that Simply Automated switches and other can be programmed with all the links and such to make this happen, but it is so much easier to have the panel program the switches, and just tweak that.
 
Also, in my last house I used Simply Automated switches, and it was always a battle to get the correct signal.  I used three couplers, and eventually a repeater, but the Simply Automated Gen 1 switches didn't work with the repeater.
 
In my new house I ONLY use the repeater with HAI Gen III switches, the signal is fantastic everywhere and in every direction. I DO have some new fan control switches from Simply Automated, since HAI does have ceiling fan switches, and i am having some problems with them, so I'm VERY VERY happy i went with Gen III. 
 
On the flip side, the HAI switches seems to have other problems like the timer doesn't work (talked about in another thread) and the problems that are the issue of this tread.

Yes I meant the firmware on the Omni.
 
I had a similar problem where switches seemed to be having their programmed light levels for different links re-programmed.
 
I never did track down the source of the problem but after a firmware upgrade the problem appears to be gone BUT it may just have been a coincidence.

I will get the Omni up and running soon, but it is not operational in this house yet.  Just using UpStart to program switches at this point.  The problem is when manually turning the switch on with the rocker.  I have installed "room controllers" in most rooms, and the Omni will do some of the light controlling as well, so I'll have less actual manual switch interaction eventually, but still will have some.
 
Another part that is annoying is that this problem, where pressing the top ON on the switch changes the LED color but doesn't actually light the light seems much more likely to occur when the switch hasn't been used for some time.  If I turn a switch on the off then on again, it never happens the next time.  Walk away a few hours then come back and turn on a switch and the problem happens again.

Frederick C. Wilt said:

I had a similar problem where switches seemed to be having their programmed light levels for different links re-programmed.

Click to expand...

So, are you saying you think the Omni programmed the switches without you telling it to?  I thought it only programs them with PC Access when you tell them to and put them in programming mode.  Maybe it does program them other times, because isn't there a way that you can set all the lights in a room each to a level, and then have the room controller "learn" those levels creating an ad-hoc scene?  So the Omni must read the light levels and program a link with those levels.

ano said:

So, are you saying you think the Omni programmed the switches without you telling it to?  I thought it only programs them with PC Access when you tell them to and put them in programming mode.  Maybe it does program them other times, because isn't there a way that you can set all the lights in a room each to a level, and then have the room controller "learn" those levels creating an ad-hoc scene?  So the Omni must read the light levels and program a link with those levels.

Click to expand...

 
I was never able to truly pin down the problem. But the programmed light levels for certain links were changing. Other then the PIM connected to the Omni what else could do that?
 
As I said upgrading the firmware and the lack of problems since then may just be coincidence.