Insteon 8 Button Dimmer Keypad to control Z-Wave Dimmers

[matt (support)]

And your Trigger is defined as Device State Changed on the Light 1 device?

What would be very helpful is to see what occurs in the Event Log. Copy/paste what is shown both when it does work correctly, and when it doesn't work correctly and explain in detail what you are doing in both cases and how the Trigger is defined that is executing (in the working case).

Okay so here is my test:

14:46 I pressed the ON button on 202.S1 and button "4" on keypad 202.S2 turned on in sync
14:47 I pressed the off button on 202.S1 and button "4" on keypad 202.S2 stayed lit.

14:48 I pressed button "4" on keypad 204.S1 and button "5" on 202.S2 turned on in sync as well
14:49:30 I pressed button "4" on keypad 204.S1 again and button "5" on 202.S2 turned off in sync as well
14:49:48 I pressed button "4" on keypad 204.S1 again and button "5" on 202.S2 did NOT turned on in sync

Sometimes it works when I press physical button and sometimes it doesn't. But it always seems to work when I turn on the lights directly from within Indigodomo. The buttons stay in sync as I turn on and off the lights.

Here is the log:

Code: Select all

Oct 22, 2019 at 12:48:33 PM
   Starting Indigo Server version 7.3.1 (Mac OS X 10.13.6)
   Loading attachments
   "iTunes attachment.scpt" script loaded
   "device target attachment.scpt" script loaded
   "time stamp attachment.scpt" script loaded
   "growl attachment.scpt" script loaded
   "scenes attachment.scpt" script loaded
   "group target attachment.scpt" script loaded
   Loading database "/Users/philipp/Documents/3769Greenwood.indiDb"
   Loading plugin "Masquerade 0.1.4"
   Starting plugin "Masquerade 0.1.4" (pid 416)
   Loading interface "Z-Wave 2.0.124"
   Starting interface "Z-Wave 2.0.124" (pid 419)
   Loading interface "Virtual Devices 2.0.5"
   Starting interface "Virtual Devices 2.0.5" (pid 422)
   Loading plugin "NEST Home 2.0.52"
   Starting plugin "NEST Home 2.0.52" (pid 423)
   Loading interface "INSTEON Commands 2.2.2"
   Starting interface "INSTEON Commands 2.2.2" (pid 424)
   Loading plugin "Action Collection 2.1.5"
   Starting plugin "Action Collection 2.1.5" (pid 425)
   Loading plugin "HomeKit Bridge 1.0.2"
   Starting plugin "HomeKit Bridge 1.0.2" (pid 426)
   Found disabled plugin "Lutron RRA2/Caséta 7.2.7"
   Found disabled plugin "Growl 2.0.2"
   Found disabled plugin "Global Property Manager 2.0"
   Found disabled plugin "Timers and Pesters 2.0.2"
   Found disabled plugin "Airfoil Pro 1.0.9"
   Found disabled plugin "NOAA Weather 2.0.1"
   Found disabled plugin "SQL Logger 2.1.0"
   Found disabled plugin "EasyDAQ Relay Card 2.0.3"
   Found disabled plugin "Ring Doorbell 0.1.30"
   Found disabled plugin "iTunes 2.0.4"
   Found disabled plugin "iCal Alarm Processor 2.0.1"
   Bonjour registered "Indigo - 3769Greenwood"
   Started interface "Virtual Devices 2.0.5"
   Started plugin "Action Collection 2.1.5"
   Started interface "INSTEON Commands 2.2.2"
   Started plugin "Masquerade 0.1.4"
   Masquerade                      Starting Masquerade
   Masquerade                      Checking for updates...
   Started plugin "NEST Home 2.0.52"
   NEST Home                       ** Data Tracking Online **
   WebServer client connected
   WebServer                       started on port 8176 -- digest authentication enabled
   Masquerade Warning              A new version is available: https://github.com/FlyingDiver/Indigo-Masquerade/releases/tag/0.1.6
   HomeKit Bridge                  Caching all HomeKit Bridge devices...
   Started interface "Z-Wave 2.0.124"
   Z-Wave Error                    "Z-Wave Controller" serial port open error: [Errno 2] could not open port /dev/cu.usbmodem1461: [Errno 2] No such file or directory: '/dev/cu.usbmodem1461'
   Z-Wave Error                    make sure the USB virtual serial port driver (ex: FTDI driver) is installed and correct port is selected
   Z-Wave Error                    Z-Wave Controller might be disconnected
   Z-Wave Error                    silently retrying serial connection every 5.0 seconds
   Started plugin "HomeKit Bridge 1.0.2"
   HomeKit Bridge                  Attempting to start 'ADU Loft'
   HomeKit Bridge                  Attempting to start 'Indigo HK'
   HomeKit Bridge                  Attempting to start 'Indigo SpotBot'
   HomeKit Bridge                  HomeKit Bridge is running the latest version, no update needed

Oct 22, 2019 at 12:48:42 PM
   Connected to PowerLinc 2413U interface on port usbserial-A906XMAY
   PowerLinc address 49.F8.80, firmware version 9.14
   Interface Failure               lost connection with interface
   HomeKit Bridge                  HomeKit Bridge is loaded and ready to use
   HomeKit Bridge                  Server 'ADU Loft' has successfully started, you can use your HomeKit apps or Siri for this accessory
   HomeKit Bridge                  Server 'Indigo HK' has successfully started, you can use your HomeKit apps or Siri for this accessory
   HomeKit Bridge                  Server 'Indigo SpotBot' has successfully started, you can use your HomeKit apps or Siri for this accessory

Oct 22, 2019 at 1:05:05 PM
   Received INSTEON                "205.S1" on to 100% (instant)

Oct 22, 2019 at 1:51:38 PM
   Received INSTEON                "205.S1" off

Oct 22, 2019 at 1:55:44 PM
   Indigo Cocoa client connected

Oct 22, 2019 at 1:56:03 PM
   Sent INSTEON                    "306.S1" keypad set brightness to 10
   Sent INSTEON                    "306.S2" keypad set brightness to 10

Oct 22, 2019 at 1:57:46 PM
   Sent INSTEON                    "306.S1" raw insteon command (20 08   00 00 00 00 00 00 00 00 00 00 00 00 00 00; ack: 08)

Oct 22, 2019 at 1:58:11 PM
   Sent INSTEON                    "306.S2" raw insteon command (20 08   00 00 00 00 00 00 00 00 00 00 00 00 00 00; ack: 08)

Oct 22, 2019 at 2:01:15 PM
   Sent INSTEON                    "204.S1" off
   Trigger                         204.S1 OFF
   Sent INSTEON                    "PowerLinc Interface" off (instant) (scene 43 - 204.S1)

Oct 22, 2019 at 2:46:17 PM
   Received INSTEON                "202.S2" off (button 4)
   Received INSTEON                "202.S1" on (button 1)
   Trigger                         202.S1 ON
   Sent INSTEON                    "PowerLinc Interface" on to 100% (instant) (scene 35 - 202.S1)
   Received INSTEON                "202.S1" on (button 1)

Oct 22, 2019 at 2:47:02 PM
   Received INSTEON                "202.S1" off (button 1)
   Trigger                         202.S1 OFF
   Sent INSTEON                    "PowerLinc Interface" off (instant) (scene 35 - 202.S1)

Oct 22, 2019 at 2:47:34 PM
   Received INSTEON                "202.S1" on (button 1)
   Trigger                         202.S1 ON
   Sent INSTEON                    "PowerLinc Interface" on to 100% (instant) (scene 35 - 202.S1)
   Received INSTEON                "202.S1" off (button 1)
   Trigger                         202.S1 OFF
   Sent INSTEON                    "PowerLinc Interface" off (instant) (scene 35 - 202.S1)
   Received INSTEON                "202.S1" on (button 1)
   Trigger                         202.S1 ON
   Sent INSTEON                    "PowerLinc Interface" on to 100% (instant) (scene 35 - 202.S1)
   Received INSTEON                "202.S1" off (button 1)
   Trigger                         202.S1 OFF
   Sent INSTEON                    "PowerLinc Interface" off (instant) (scene 35 - 202.S1)
   Received INSTEON                "202.S1" on (button 1)
   Trigger                         202.S1 ON
   Sent INSTEON                    "PowerLinc Interface" on to 100% (instant) (scene 35 - 202.S1)
   Received INSTEON                "202.S1" off (button 1)
   Trigger                         202.S1 OFF
   Sent INSTEON                    "PowerLinc Interface" off (instant) (scene 35 - 202.S1)
   Received INSTEON                "202.S1" on (button 1)
   Trigger                         202.S1 ON
   Sent INSTEON                    "PowerLinc Interface" on to 100% (instant) (scene 35 - 202.S1)
   Received INSTEON                "202.S1" off (button 1)
   Trigger                         202.S1 OFF
   Sent INSTEON                    "PowerLinc Interface" off (instant) (scene 35 - 202.S1)
   Received INSTEON                "202.S2" off (button 4)

Oct 22, 2019 at 2:48:16 PM
   Received INSTEON                "204.S1" on (button 4)
   Trigger                         204.S3 ON
   Sent INSTEON                    "PowerLinc Interface" on to 100% (instant) (scene 38 - 204.S3)

Oct 22, 2019 at 2:48:31 PM
   Received INSTEON                "204.S1" off (button 4)
   Trigger                         204.S3 OFF
   Sent INSTEON                    "PowerLinc Interface" off (instant) (scene 38 - 204.S3)

Oct 22, 2019 at 2:48:48 PM
   Received INSTEON                "204.S1" on (button 4)
   Trigger                         204.S3 ON
   Sent INSTEON                    "PowerLinc Interface" on to 100% (instant) (scene 38 - 204.S3)


Hoping we can find a solution since this always works well in my other place where I am running everything off of an ISY. Let me know if you need anything else!

[matt (support)]

Okay, so based on that you are saying this:

Code: Select all

Oct 22, 2019 at 2:48:16 PM
   Received INSTEON                "204.S1" on (button 4)
   Trigger                         204.S3 ON
   Sent INSTEON                    "PowerLinc Interface" on to 100% (instant) (scene 38 - 204.S3)

worked correctly, but this same Trigger later did not:

Code: Select all

Oct 22, 2019 at 2:48:48 PM
   Received INSTEON                "204.S1" on (button 4)
   Trigger                         204.S3 ON
   Sent INSTEON                    "PowerLinc Interface" on to 100% (instant) (scene 38 - 204.S3)

In both cases Indigo is sending the exact same command, and the PowerLinc is not reporting any problems receiving the command which means it attempted to send it out. The problem with group/scene commands like this is they are not acknowledged. So if there is a signal problem (including a possible collision from clean-up commands that might still be coming in from the original 204.S1 button press), then it will silently fail. The PowerLinc won't report it as an error since there is never an acknowledgment back from group/scene commands.

Here are some possible solutions:

1) Add an action level delay of a couple of seconds (there is a delay option in the actions panel) before you send out the group command. That will help prevent a collision if it is occurring from a cleanup command coming in from 204.S1 button press at the same time the PowerLinc is sending out a command.
2) Duplicate the action to have it send the PowerLinc scene command a couple (2 or 3) times.
3) Troubleshoot possible signal problems. If adding a delay (suggestion #1) helps, then there probably isn't a signal problem but instead a collision. So if #1 works then don't bother with #3.
4) Turn on the Always send group/scene cleanup messages checkbox in the Interface Options dialog (choose Interfaces->INSTEON->Configure... menu item)

I'm not real fond of #4 personally, although that is probably what the ISY does. The problem is that sends out cleanup commands to every module in the scene. If you have a scene that does something like "All Lights Off" for the entire house, then that is a ton of commands. It would be as reliable and much faster to just send the group/scene command a few additional times. I'm not fond of sending duplicate commands to increase reliability, but I'm even less fond of clean-up commands sent to all of the modules (especially if you have scenes with lots of modules). Ideally, Indigo would allow you to set the clean-up command preference on a per scene level instead of globally, but currently that isn't an option.