Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Mostly light sources. House code A & B. M-F with some dawn/dusk combos along with firm times. Nothing fancy. Could I have a faulty WM100? It has been on the shelf for a few years.

I have used X10 for the last 30 years and my trusty CM15A had no issues, just a pita to plug in and adjust. The Android app is a breeze, compared.

That's a wierd one. Were these lights, what address were they? What was the schedual?

In that case you can open the unit and it'll be obvious as to how to bend the contacts attached to the buttons to correct that.
I PM'd you with another suggestion and a link to it.

First thing I would do is operate those sliders back and forth a few times to see if that helps by removing oxidation.  Those sliders have contacts that bridge copper traces on the circuit board which can oxidize or wear out.  Cleaning can help but if worn out just replace. 

Thanks Brobin
The slider for 1-4 or 5-8 slides waaaaay too easily.
If I tilt the timer, that slider usually moves.

First thing I would do is operate those sliders back and forth a few times to see if that helps by removing oxidation.  Those sliders have contacts that bridge copper traces on the circuit board which can oxidize or wear out.  Cleaning can help but if worn out just replace. 

For some reason, without any pattern, my WM100 loses the M-F schedule on some devices and changes them to "once" with M-F unchecked.  Other devices (same type) remain unchanged. This has happened 2 or 3 times since replacing my CM15A with this device. Firmware is current and so is the Android App. I have the app on multiple Android devices but use one for WM100 maintenance.

Good morning to all
My trusted and reliable MT14A little box works well I shall say, 95% of the time, with a sliding scale...
At times, things come on that shouldn't, but I've learned to accept it.

When I go to the timer to look at what's programmed and to correct one of those phantom turn-on's, I get more irrational behavior.
With the slider button on PROG, I will, for example, press the 4 button ON to see that time(s) are programmed.
As I press that ON button for 4, the display will show me the times for other number codes. So pressing 4 ON, I'll see:
4 09:15AM
8 07:00 PM
6 05:30 PM
etc

That happens with the number 4 code or any other, and I make sure to keep the 1-4 or 5-8 button on the right position for the number code that I'm checking.

Could this be causing the random on's
Is it time to replace my timer? Is there a way to reset it kind of thing?

Thank you

Thank you for the information.
One thing that may effect the WM100 is the UPS used and the design of the WM100's power supply.
Many UPS units have a stepped or modified AC output on battery backup. You can find true sine wave UPS units but many still are modified output.
Depending on the exact model UPS output. The WM100 may not handle that signal well and act strange.
I an glad your was fine on the UPS and all seems to be fine with the setup.

As I'm sure just about everyone who uses the WM100 Wi-Fi module knows, it does not include a battery backup for its internal clock.
You can overcome this flaw if you put the WM100 on a UPS that will permit the WM100's signals to cross back into the outlet into which the UPS is plugged.
I have numerous X10 modules that I use in my home's automation system, and I discovered this vexing problem only after a power disruption.
I decided to try using an old UPS that I brought back online for use with the WM100 specifically. While this is not the best solution, since this is CLEARLY a design flaw in the WM100, I have been testing it for a week and it has resolved the issue with the time-loss. I have not tested to determine whether the frequency of the power supplied OUT of the UPS affects the timer in the WM100 over the long term. I have repeatedly cut/restored power to the UPS and the WM100's LED remains steadily illuminated, the WM100 functions normally afterward, and it appears to be keeping the time synced as set from my cell phone. I have repeatedly checked the WM100's "History and settings," and the timing of the ON/OFF signals to the other X10 modules remains as I set it.

Problem #1 with the lights is one that's a real head scratcher.  I got nuthin' except maybe bored poltergeists. 
Could #2 with the fan be caused by whatever you're using to determine the heat level failing open or closed to always indicate a high heat condition?  That would explain the fan turning back on all the time since the Ocelot would always see high heat as true.
For #3 you might try replacing or swapping the solenoids for zones 2 & 3 with others as I've had those fail in the past or maybe the 24VAC power supply for the solenoids is failing or there's a shorted wire to the solenoids.

Thanks for the suggestions.

All I can think of on problem 1 is some sort of intermittent noise source or powerline glitches.  The XTBM-Pro only gives the current noise level, which is zero.  But several weeks ago I did detect a high noise level that disappeared as breakers were tripped, but it didn't resume when that breaker was switched back on.

My idea on problem 2 is similar to yours.  There is a thermister in the garage that the Ocelot uses to calculate temperature.  I have to pick through the code to see what might be causing the problem.  I wrote that code two decades ago, and it has worked fine until just a few days ago.  Maybe all it needs is a refresh.

I've had solenoids go bad before, but they are working fine.  I can manually switch them on and off through the Rain8 with a 4-button X10 wall controller.  If it was a stuck valve, the next zone would have come on, but it didn't.  Similarly, the 24VAC is fine.

I can understand one unit acting up after a couple of decades due to a soft programmed bit, but why are three different controllers misbehaving the same way?  (Zone 3 stuck on again this morning.)  The only idea I have is that somehow random X10 traffic is confusing the Rain8 while it is proceeding through its sequence.  But it had worked fine for almost 2 decades.  Why now?

As a test I'm going to modify a XTB-523 to only accept the housecode that controls the Rain8.  If that fails, I guess I'll have to move the timer function into the Ocelot, and only use the Rain8 as a multi-channel X10 relay.

I considered a commercial smart irrigation controller, but we have the unique situation that there are just a couple of inches of soil on top of a lava flow for our 20' x 40' "lawn".  So that dries out very quickly in the summer when days are often over 110F.  The Ocelot runs periodic short cycles depending on the temperature to keep everything alive.  And of course we have to be compliant with water restrictions during the summer months.

Jeff