Hi all,
I have been using Insteon dimmer switches and this plugin for many years and everything has worked perfectly.
I recently added some keypadlinc dimmer switches and I am noticing some odd behaviour and I am wondering if anyone else has experienced this or could offer an explanation as to why this is:
I should note that I am using the plugin to control the LED behind the individual keypadlinc buttons and I have the option "sync responder devices" off, for all my devices.
I am able to control an individual button LED by using the plugin to turn it on, however, if I use the plugin to send a series of "control a device" on commands, one after the other, with each command instructing the keypadlinc to turn on a button LED, then as each command arrives at the switch and the LED turns on, some of the previously lit LED's on other buttons turn off. This also seems to occur of any insteon command was just sent out (not just a command sent to the same keypadlinc).
I have also observed that this behaviour only occurs if the commands are sent one after the other. If I wait around one minute between each command, then the button LED's turn on as expected. It's almost as if the bit stream of commands coming in succession are confusing the switch.
I am a long term user of Homeseer and Insteon but I don't have programming or technical knowledge but I assume the Homeseer events add insteon commands to some kind of queue or buffer and then they are sent out via the hub. I am wondering if there could be some feature where we could get a user setting to allow us to control the pause between which insteon commands are sent?
Any comments would be appreciated as I find this behaviour quite puzzling. I currently have my system working the way I want, by using my workaround of inserting wait commands in my events, before trying to control a keypadlinc button LED
I have been using Insteon dimmer switches and this plugin for many years and everything has worked perfectly.
I recently added some keypadlinc dimmer switches and I am noticing some odd behaviour and I am wondering if anyone else has experienced this or could offer an explanation as to why this is:
I should note that I am using the plugin to control the LED behind the individual keypadlinc buttons and I have the option "sync responder devices" off, for all my devices.
I am able to control an individual button LED by using the plugin to turn it on, however, if I use the plugin to send a series of "control a device" on commands, one after the other, with each command instructing the keypadlinc to turn on a button LED, then as each command arrives at the switch and the LED turns on, some of the previously lit LED's on other buttons turn off. This also seems to occur of any insteon command was just sent out (not just a command sent to the same keypadlinc).
I have also observed that this behaviour only occurs if the commands are sent one after the other. If I wait around one minute between each command, then the button LED's turn on as expected. It's almost as if the bit stream of commands coming in succession are confusing the switch.
I am a long term user of Homeseer and Insteon but I don't have programming or technical knowledge but I assume the Homeseer events add insteon commands to some kind of queue or buffer and then they are sent out via the hub. I am wondering if there could be some feature where we could get a user setting to allow us to control the pause between which insteon commands are sent?
Any comments would be appreciated as I find this behaviour quite puzzling. I currently have my system working the way I want, by using my workaround of inserting wait commands in my events, before trying to control a keypadlinc button LED
Comment