fitzpatri8

How is this superior to changing the app and slider behavior to be consistent with normal Insteon operation? When you bring up a scene in your app, why not show the slider in the middle? If a user drags it toward the bright side, send a fade up until it is released, or send a sequence of brights to the group appropriate to the degree of movement from center. If the user drags to left, send fade down until released, or send a series of dims to the group appropriate to the degree of movement from center. That 1) avoids having to make repeated button taps, 2) acknowledges that you are adjusting the scene up or down, 3) recognizes that once devices hit maximum or minimum brightness, brightness of multiple devices with different start levels has changed relative to other members of the scene, and 4) remains true to the behavior you would see if you held a switch or keypad button. Alternatively, you could implement something similar to what Wes does in MobiLinc to indicate a 'scene brightness'--add up the levels of each member device, divide by number of modules, then show the average. Use the slider to send dims/brights/fades as described above relative to the degree of adjuster movement.

Use one of these to interface the alarm to an IOLinc: http://www.smarthome.com/1299/ELK-912B- ... olt/p.aspx

I use MobiLinc HD for that:

That's a different model. There are three different types of Micro Module: 2442-x22 is a Micro Dimmer; 2443-x22 is a Micro On/Off (relay); and 2444-x22 is a Micro Open/Close Motor Control. ( http://www.smarthome.com/2444-222/INSTE ... ule/p.aspx ) The most likely application of the last one is control of window coverings or projector screens, so the window covering category makes sense. The first two models work fine with 4.0.2. Since the third isn't yet supported, I was trying to add it using the Link Management, New Insteon device feature by manually assigning a different device type.

It's a 2444-222 Micro Open/Close module. I get a message that reads: New Device Errors The following devices could not be added: (device address) Unsupported Device: 14.1 - Cannot add Insteon Device

Can you use these outdoor dual-band units instead? http://www.smarthome.com/2634-222/INSTE ... ule/p.aspx

It looks like New Insteon Device feature and selecting a device type no longer operates as a work-around for new devices. When I try adding an as-yet unsupported Micro Module Open/Close unit by forcing a different device type under v. 4.0.2, I get the same error as I get using auto discover.

Apple disabled older versions of Java because of security issues. Check the Apple support forum for info on updating to the fixed version.

Performing a factory reset is sort of a 'nuclear flyswatter' option--it'll work, but it might be considered a little excessive. If you accidentally turn on Resume Bright again, the easiest thing to do is reset it. Simply adjust the switch back to the desired On level and single-tap the Set button. If you find you have to do it again in the future and you are reasonably certain no one is walking around your house tapping Set buttons on switches in the Off position, be sure to post back--that could mean that your particular set of circumstances (the four back-to-back commands to set local level, set ramp rate, set local level, set ramp rate without any pauses in between; the marginal signal environment; perhaps even the particular unit addresses involved) are setting up a storm of bits that are being misconstrued as a 'turn on Resume Bright' message and would merit further testing.

Lee, I'm glad you stuck with it to a successful conclusion. Ditto the other comments--your detailed knowledge of the technology and your willingness to share it are unparalleled and appreciated, and I learn new stuff from your posts all the time! Mike, thanks for your input, it really helped set the right direction for the rest of the conversation. It's been around for a bit and it's very easy to set (intentionally *or* accidentally), so I'm actually a little surprised that the Resume Dim feature (SmartLabs actually calls it 'resume bright' in the docs) doesn't get more attention. Operation is consistent with previous firmware versions that I've tried--you simply single-tap the Set button while the switch is Off to turn the feature on, then the level of the switch is saved each time you turn it off and it returns to that level the next time you press on. It's actually handy for folks who don't have an ISY to easily reset levels, since it means that you can easily reset the light to a dimmer level before turning the lights off when you put the baby to bed, then the light comes on at that lower level when you are bleary-eyed and called for a middle-of-the-night diaper change.

I agree, same here.

Still a problem in 3.3.10.

Perhaps a related issue: If I create a scene for multiple devices that include a thermostat in a Thermostat Mode other than Off, then go to one of the scene controllers and use the Copy scene attributes from... button, the controller's Thermostat Mode is changed to Off. It also appears to have swapped the heating and cooling setpoint.

When I create a thermostat scene using a 2441TH thermostat with 3.3.9, the Fan State won't stick on Automatic. I set it to automatic, leave the scene, then return to find it set to On. This appears to be a display issue only. The thermostat doesn't actually switch to fan always mode.

You do not want pressing the button to turn off the button's light, you only want the IOLinc to be able to turn it off. That's what you accomplish by putting the button into non-toggle ON mode.

As described, once you put the keypad button into non-toggle On mode, you should see the button light remain ON until the door closes.

With the MobiLinc Pro app for iOS or MobiLinc HD app for the iPad, you can add the camera plugin to see a camera display and control devices in the room through your ISY in the same page in the same app.

The bad news for you is, not only is there not a direct equivalent* unit in the Insteon family, there isn't even an equivalent in the x10 family. If you like it, hold on to the one you've got! The good news is, according to the manual I found online the unit responds to *both* x10 RF and x10 power line signals. That means you can plug the unit in near your ISY PLM, trigger an ISY program with an Insteon device, then have the ISY program control Rex with x10 power line signals. If your Rex10 should expire, the equivalent would be to use a mechanical tape recorder with an 'endless loop tape' (the kind they used to use for outgoing answering machine messages). Record your favorite ferocious canine, then use ISY programs and an Insteon appliance module to turn the player on and off as required.

The ISY does support the Insteon MorningLinc interface. It is the MorningLinc interface that actually talks with the Morning Industries remotely controllable locksets.

Also, with the TriggerLinc I believe you have to remove the battery for a few seconds then reinstall so it can recognize the jumper setting has been changed.

A ToggleLinc switch wouldn't have any way to monitor the state of a door. Do you mean an IOLinc only, or is an IOLinc linked to a ToggleLinc, or... Did you create all the links in the ISY, or did you manually link two devices using their Set buttons?

Negative, relay switches turn on or off. That approach would definitely reduce the lifespan of the bulb. The preferable option would be to use option 2 above: train the users to tap the On button when entering or leaving the room. Your programs could then watch for the second On signal and use that to trigger the 15 second timer and off command. You can do that. Cap off the red wire on the SwitchLinc, install an InLineLinc behind the fixture, then use the SwitchLinc to trigger programs which control the InLineLinc.

When you press the paddle on a switch, it uses what is called its 'local' ramp rate to turn on or off. There isn't an option onboard the switch itself to program different ramp rates for a local on and a local off, but having an ISY gives you a couple of options. Option 1: Set the 'local' ramp rate to 20 seconds. Create an ISY program to trigger only when the device control turns on. Have the program turn on a different scene, one with the same switch as a responder but with a quicker ramp rate. Option 2: Train the users to skip turning the bath light off. They can click On again to trigger a timer program, or they can skip pressing the control entirely and rely on other means to turn off the light. (Absence of motion, light from adjacent room turning on, or a timer triggered by the On signal expiring could all be used to turn the light back off.)

There's the problem, button D should not be a member of the mutually exclusive group. Button D should be non-toggle off and linked as a controller of the FanLinc (once the ISY is updated to support it) and buttons A, B and C.

HouseLinc does have one way to avoid HL doing any link management (at least any beyond the initial links it creates to the HL PLM). After you Add a device to HL, go to the Properties tab, verify the LED Blink on traffic is set correctly, then check the box marked Disable. That'll stop HL from querying the device or trying to make any changes to it.