Insteon on request not executed by module

Posted on
Fri Jan 18, 2019 6:49 am
DaveL17 offline
User avatar
Posts: 4889
Joined: Aug 20, 2013
Location: Chicago, IL, USA

Re: Insteon on request not executed by module

A PITA to setup a new device, to me, but maybe because I haven't done it enough...

I've found that can be device specific.

  • I've found network-wide inclusion to be hit or miss--so much so that I typically don't even try--I'll install the device and bring the Z-Stick to it in place.
  • I always exclude a new device first when I install it, in case it was paired with another controller at the factory.
  • After reinstalling the Z-Stick, I'll head back to the device with a laptop running the Indigo client and finish the install--in case I need to wake the device up for the initial sync.
  • I used to run an optimization on a routine schedule, but decided that was overkill. If I haven't installed or moved any devices, it seems unnecessary.
I don't have a ton of Z-Wave devices, but their installed fairly corner to corner so I get great coverage. The only troubles I have is that some devices will inexplicably lose a connection ("no ack") when they have been running perfectly fine for quite a while. In these cases, the fix has varied. Sometimes just sending an 'on' or 'off' command will re-establish communication. Sometimes I need to remove power to the device. In one extreme circumstance (an Everspring water sensor) I removed the batteries and let it sit for a couple weeks and then I excluded/included and it's been working since (I'm sure weeks wasn't necessary; that's just how long it took me to get back to it.)

It would be nice to know whether it's the device in a bad state, the Z-Stick getting confused or if Indigo is giving up after its retry limit. It would be even nicer if there were an automated way to kick a device in the pants when it's gone offline, but I don't know what that would look like.

I came here to drink milk and kick ass....and I've just finished my milk.

[My Plugins] - [My Forums]

Posted on
Fri Jan 18, 2019 10:25 am
peszko offline
Posts: 152
Joined: Mar 07, 2012

Re: Insteon on request not executed by module

RogueProeliator wrote:
FWIW, I have 82 INSTEON devices


RogueProeliator wrote:
I have followed best practices here for sending multiple commands (1-2s delay as appropriate). I don't have a ton of triggers on the devices that send other INSTEON commands, at least not relative to the number of devices.


In my case 1 to 2 s delay from signal to action is way too much. One of my examples: I have three setts of 4 kypadlinks that have most of the lights in the house and some scenes programmed to the buttons.. I want them to be in sync. So If I turn on a scene with sevenlights (one of my living areas, mood to 30% for most) one button sends a scene request to the lights. This triggers 7x4 button updates or 7 scene updates with with 4 modules in each to the buttons (I tried various ways). 28 insteon commands, or 7 scene commands (they were separate since turning any of the 7 had to be individually changed as well). From my perspective, (even more so from my wife's) this is a perfectly simple function. But.... What happens, is that the scene command generates 7 scene cleanup commands, 28 keypadlink commands for a total of 35. Now, If I space out the 28 keypad links by 2 sec, I get a minute delay until all the buttons sync. Now even worse, and quite common thing is that she decides that actually she doesn't want to turn them on so presses off after a second or so. Now, the lights don't react, so she presses it again, then again and calls me with a an annoying voice that the lights are broken again. And I can't do anything now for couple minutes because there are insteon messages running around and bumping in to each other. Even without the delays, but with clean up turned on, this was happening very often. Even worse with guests who expect the lights to go on or off when they press the button, And if they don't in a second or two, press it again and again and again. This is all happening while people are moving about the house triggering motion and door sensors, that turn lights on an off.

My solution is to remove all the keypad links, turn off clean up and just send two consecutive scene requests to the lights. And yes it works well. But I really liked the idea of the keypadlinks.

RogueProeliator wrote:
Interestingly, I could detect INSTEON communication via our baby monitor whenever my son was little -- it would show interference any time a switch was hit and you could tell the length of cleanup and "bouncing commands" until it settled down. It did seem excessive for what it was doing (e.g. turning off a light without any triggers). We had one device that must have been bad or had a band link or something as it would generate about 1 full minute of communication any time it was tapped. That doesn't seem very prudent from a reliability standpoint.


1 full minute of communication for a single switch is excessive.

RogueProeliator wrote:
I have no reason to move off INSTEON devices, but I do have all sensors and other quick-transmitting devices on Z-Wave


I plan to leave the insteon switches for lights only, and change most everything else to z-wave. From reading around, this seems to work well for people.

To me this means that making a complete Insteon automation system with sensors, switches and extended logic for a large system is difficult to impossible. I suspect that If all the sensing is done with z-wave and insteon only handles turning on/off switches I should have no issues.

Posted on
Fri Jan 18, 2019 11:13 am
RogueProeliator offline
User avatar
Posts: 2223
Joined: Nov 13, 2012
Location: Baton Rouge, LA

Re: Insteon on request not executed by module

My solution is to remove all the keypad links, turn off clean up and just send two consecutive scene requests to the lights. And yes it works well. But I really liked the idea of the keypadlinks.

I don't use the keypads except for one for ceiling fan control... I can't stand working with them from a programming / HA standpoint, so I do get where you are coming from with those. It has been a while, but when I looked a while back there wasn't a great Z-Wave equivalent and I believe it lacks scenes. Obstacles you can get around, of course, with a little effort. Others can chime in on any hardware that may be available now that is KeypadLinc-like.

1 full minute of communication for a single switch is excessive.

Agreed, but that is one particular / bad switch.

To me this means that making a complete Insteon automation system with sensors, switches and extended logic for a large system is difficult to impossible. I suspect that If all the sensing is done with z-wave and insteon only handles turning on/off switches I should have no issues.

Well, this is pretty much my situation and it has been rock solid, and probably the reason/difference with many that are having issues. INSTEON controls nearly every light switch in the house, some ceiling fans, and a couple of outlets. Motion sensors, climate systems, thermostats, etc. are NOT - they are a combination of Z-Wave, wireless, and WiFi protocols.

Who is online

Users browsing this forum: No registered users and 0 guests