fitzpatri8

In the Insteon world, a "scene" is a set of Insteon-compatible devices put into a particular, coordinated, programmed state at a ramp rate. Some devices might be on 100%, some 25%, some off, others somewhere in between, but the "scene" is all those devices at that particular level. Insteon achieves that by sending a "group on" message to a group devices previous linked as responders. Insteon protocol also allows you to adjust a "group" of Insteon devices--hold the top of a paddle down and the "group" will brighten; hold the bottom and the group will dim; tap the bottom of the paddle to turn off; fast double-tap the top or bottom to turn everything 100% on or 0% off instantly. Note that you aren't actually brightening or dimming the scene--the scene is those devices at their programmed level--you are brightening or dimming the "group". When you link devices to a controller, you are creating *both* a group and a scene. What the original poster is *really* asking for is a way to use Alexa to adjust an Insteon "group" proportionally to the values of a "scene". As has been already mentioned, you can currently use Alexa to brighten and dim a group of devices (at a preprogrammed 9% increment), that just requires the Portal to issue bright/dim commands to an existing group, and all responders can react simultaneously with a minimum of signal traffic. The OP's request requires something altogether different--that would require the ISY to accept a percentage command, compute and round to a new percentage based on the level set in a scene, then send individual direct commands to each member of the group to set each to a new level. Proportional control of a group certainly isn't impossible, but it isn't supported natively by Insteon hardware, so it would require substantially more computing and signal resources than any other operation. You have to weigh the cost/benefit of such a feature to decide its worth.

That's a feature, it had been part of the Insteon dimmer design from the beginning. Tapping on a switch that is already on will toggle the local load between the current dim setting and 100%, while sending a scene on message to linked responders. That makes it easy to distinguish which load is attached vs. one connected to another Insteon device without having to take the wall plate off to look at the wiring. If your intention is to move all the responders' loads to 100% at the same time, use a quick double-tap On to send a Fast On message to everything.

The bigger problem I see is with guests. "Turn on the lights" is a common phrase if you are asking for help from someone standing near the switch, but Alexa and Siri both seem to interpret that as "Turn on *all* the lights, throughout the house". That's disappointing if someone is trying to sleep!

Toggle mode is more powerful on the KeypadLinc, with each button supporting cross-linking as well as its own toggle setting. Set to toggle mode, each secondary KeypadLinc button press sends a signal opposite the current button state. If the button is currently on, tapping sends an Off; if the button is currently off, tapping sends an On. In non-toggle mode, each KeypadLinc button press sends the identical signal, regardless of the current button state. Because the KeypadLinc is a power line device, it can be linked as both a responder and as a controller. That way, it can stay synchronized with the state of the scene it controls.

Jg, it sounds like you understand. In toggle mode, each press/hold of each mini remote button alternates between sending on/bright and off/dim. In non-toggle, each button press/hold sends on/bright. Because the battery-operated mini remotes turn off their radios between uses, they cannot hear and respond to other controllers, thus the potential of them becoming out of sync with the rest of the scene and requiring two button presses to get the desired result. Your solution is the best choice, since the ISY does track the current state of the responder devices and can send the right signal with a single button press.

I urge caution. While that cereal may be cheap now, the price of the supplemental insulin it may cause you to need later is going through the roof!

In other words: yes, the ISY-99 is too old, it doesn't support newer Insteon keypads, and it is no longer being updated to support other new Insteon hardware. Universal Devices offers a discounted upgrade for owners of older ISY devices. See the Upgrade section on this page: https://www.universal-devices.com/sales/

Seems like the problem is that you have multiple, duplicate programs, one that you trigger with the keypad and a second that you trigger with MobiLinc. Combine those into a single program that can be triggered by both the keypad or MobiLinc, then you can use MobiLinc to look at either the true/false state of that single program or the status of that keypad button.

There isn't a direct command for turning a keypad secondary button on or off. Instead, create a new scene, add that button to the scene, then turn the scene on or off.

If the dimmer was programmed with an x10 address during factory testing, or if it heard one while you were linking another controller, it may be responding to power line noise that resembles a valid x10 signal. To rule out that possibility, I would perform a quick factory reset on the dimmer, then use the ISY's Restore Device feature to rewrite only valid links.

Are you using any x10 codes or motion sensors in this setup?

That sounds like the way the second version of the SmartLinc handled things. When you set up a scene, you could assign a scene a 'status' device, then the SmartLinc would show the status of the status device any time you refreshed the page. That works for 3-ways, but could easily mislead people about the status of more sophisticated scenes. It's that disagreement about scene status expectations on more sophisticated scenes that gets us in trouble. Some believe scene status should reflect the 'average' dim level of a scene (that's how the MobiLinc app works), some say it should only display as 'On' if all the devices match the on/off/dim levels defined in the scene exactly, some say it should display as 'On' if *any* included devices are on, some say it should display as 'On' only so long as *all* devices in the scene remain on, etc. Some people want to be able to choose between these choices for different scenes. So far, the best answer has been configuring the interface to reflect no scene status. Personally, I'd like the web interface to support display of a variable next to the scene name. That way I could set up my own ISY program to define the current 'status' of each scene as it suits me. For some scenes, that status might be On, Bright or Dim (for an ordinary scene of dimmers); for a basement scene that might be "In Use" or "Off"; for whole-house scenes, that might be On, All On, All Off, or Mixed.

The Control (device) trigger only operates if you tap the button on the module itself. The If Status (device) trigger detects an adjustment to the device via any method (including the module's buttons, remotely via another switch in a three-way setup, via a phone app, using a program, using the Administrative Console, via Echo, etc.). So long as your Echo scene turns on a keypad button, it sounds like you only need to use the status of that button as a secondary condition. And Status (button) is off, otherwise don't run the program.

Congratulations! I'm glad to see that there might be some light at the end of the tunnel for those of us willing to invest in automatic load shifting technology, but I'm also more than a little cautious. If the current system of incentives is convoluted, I'm concerned the proposed idea introduces even greater complexities and increased costs. If we make this too complicated, don't we risk even more utility market manipulation like we saw in Enron's heyday?

That's the expected behavior, as the ApplianceLinc (and LampLincs of the same vintage) was a single-band, responder-only device. Responder-only devices can't be linked or operated as a controller, so the only way the ISY knows its state has changed is if another, linked controller turns it on, or if the ISY intentionally queries it to find out its current state. Newer On/Off Modules and Lamp Dimmers (the ones with separate on and off buttons on the side) can be linked as controllers, so the ISY is notified when they change state.

Sounds like they are updating devices incrementally, perhaps based on serial number or some other sequence. This approach likely reduces the load on the update servers and puts Amazon in the position to stop updates if a serious bug crops up as the new firmware rolls out into the Wild West that is the real world. That's probably a good idea, considering the damage done by faulty push updates to Nest thermostats and the Wink Hubs.

No, device status is only transmitted to the scene controller in response to a status request message. Error correction is in response to a binary yes/no to the 'did you hear me' message from between controller and individual responders only. Under normal usage, when you control a scene with a switch, as the scene responders are adjusting their load settings, the switch will then send clean-up messages, asking each responder if it heard the scene message. The responder provides only a short ACKnowledgement to the controller that the message was received and processed, no load information is exchanged. The process is quick and efficient to support large, house-wide scenes. The ISY displays its understanding of a device status based on its copy of the controller and responder link tables. (It is linked to the switch, so it'll see the switch turn on; and it knows modules a and c are linked as responders to the switch. When the switch says 'on', the ISY logically computes that modules a and c are now in whatever state they were linked.). That's why it is necessary to use the ISY's Asministrative Console for all scene building and link table maintenance. If you start linking or adjusting devices manually, the ISY has no way to discern their correct state until the 3 A.M. maintenance program runs and the ISY specifically queries each device for its current status.

Three things to note: A model 2474 will not work with no load attached, since it itself is powered by splitting power with the load and running a small current through it even when off. If you disconnect or unscrew the bulb, you create an open circuit where the switch receives no power; CFLs and LEDs may not pass enough electricity through for the switch to work, or in doing so that may cause the bulb to flicker when 'off'. They recommend an incandescent bulb of over 25 watts, IIRC; and The 2474 is a single-band device that transmits over the RF band, since it doesn't have the necessary 120 volt wiring to supply a power line signal. That means it needs to be within RF range of a dual-band device that can get messages to and from the ISY. If you haven't yet installed your dual-band equipment, you may want to plug or wire it in first, before attempting to add any single-band equipment like the 2474.

The only missing piece is, remember to remove the fan from the light switch scene, that way you won't turn the fan off momentarily when the light goes off. If you'd like the fan to be fully automatic, add a program to detect the light turning on to turn on the fan.

When used with a motion sensor connected to the Sense line, be sure to also disable the 3-way mode (enabled by default). Otherwise, activating the module remotely can create a situation where the trigger is reversed and the light starts to turn off with motion/on after timeout.

It's blue in the device tree because of the device type. Responder-only devices, like the ApplianceLinc or the older LampLinc, appear in blue, while devices that can act as Controllers (like the On/Off Module, the newer LampLincs with bright/dim buttons on the side, SwitchLincs, etc.) show in that reddish hue. You can intentionally hide and un-hide devices in MobiLinc. Go to Settings, Lighting Controller, Hidden Items to see the list.

See the developer's explanation here: http://mobilinc.com/features/mobilincconnect/ There's also a MobiLinc section in the Third Party Products section of this forum: http://forum.universal-devices.com/forum/35-mobilinc/

You can use the app to check status and control devices, scenes and programs without the service, though a couple of features that require the connect service will be disabled. You can set up a static LAN IP address on your router, then pay your Internet provider the extra fee to get a static WAN IP address from them; or you can set up a dynamic DNS forwarding service that your router automatically updates, if your router supports that feature; or you can get another device on your LAN to email you any time it detects that your ISP changed your modem's IP address; or you can use MobiLinc only from phones/tablets connected directly to your router and not worry about remote access.

Did you feel a tingle when you touched it, something suggesting you might have had a static electricity discharge?

Quick fix--add the OutletLinc as a responder to the Kids Bedroom Light scene. Let the ISY write all the links. When it is all done, delete the OutletLinc from the scene, then let the ISY erase all the now-unnecessary links. That should fix it.