I've been using (and loving) Indigo for a couple years now, definitely enjoy all the new features in version 5.

Today I did discover a problem I'm hoping to get some help with. The following error is displayed in the log multiple times over the last 8 hours or so (sporadically, with several minutes between):

Code: Select all

dim/bright value out-of-range -- forcing to max

Can anyone shed some light on possible causes?

I believe that error is only thrown when a plugin attempts to adjust the brightness of a device too high - do you have any plugins installed?

Jay,

Yes, I have several plugins installed and enabled (Action Collection, Airfoil, Growl, Weather Conditions, WeatherSnoop), but I had not added any in the last couple weeks (or made any other changes for that matter). It isn't immediately obvious to me that any of these would mess with dim levels (except perhaps Action Collection). I'm still running 5.0.4 on a mac mini running 10.6.8 FYI.

Further troubleshooting has shown that the problem appears correlated to my w800usb. I noticed my motion sensors weren't working, and just on a hunch disabled my X10 RF interface in Indigo. A couple hours went by, and no error messages. I turned it back on and within minutes got another of those errors. Disabled overnight, no errors. Re-enabled, errors returned.

I then experimented with rebooting, unplugging etc. and couldn't get the thing to behave. I went in to the RF Interface Options dialog and turned on the "Report error on receiving corrupt commands" option. I immediately got tons of "undefined byte from w800rf interface" errors.

At this point my hypothesis is that my w800usb is defective, though I realize this error could be due to a new source of RF interference. I've ordered a new one (decided that either way given the small size of the company a cold spare was warranted) and will report back with my findings once it arrives.

Yep, that would do it. If some command comes in from the RF interface claiming that a dimmer was set to an out of bounds value then you may see that error as well.

Update: Replaced w800usb hardware, everything works as before. Just posting in case someone else encounters this problem in the future.