Bug994

Thanks for the quick help everyone. It definitely knocks a couple things loose in the noggin. I do now remember how the two scenes is the key to get the keypad button to turn on and off. I think @oberkc has it correct on how the IOLinc didn't need a program to do that second scene. Even if a simple program for RatGDO is necessary, it shouldn't be too difficult. I'll play around with it this afternoon and update back here.

RatGDO and the plugin have been working well for me. I'm now trying to take the next step of setting it up to be part of a scene. I had this set up a long ago with the Insteon garage door opener kit (which sometimes worked, sometimes didn't) and I can't remember how I did it. Essentially I just want to do this: I have an Insteon KeypadLinc Dimmer 5 Buttons (2334) and I want to have Button A send the open/close command to the RatGDO. This part should be easy: add both the RatGDO plugin and the Button to the scene, let the Button be a Controller and the RatGDO be the Responder. However, I also want the button to be a Responder to the RatGDO based on the status of whether the garage door is open or closed: Backlight of the button should be on when the garage door is open, off when the garage door is closed. I can't for the life of me remember how I set this up before - and whether the RatGDO and plugin can also work this way. Trying to avoid doing it with programs if possible. Apologies if this is more of a basic IOX question, but thought I'd ask here first. Thanks.

I tried a number of things and still no luck. It's not a critical device for me, so I'm not too broken up about it. Would be nice to get it going some day though...

Thanks for the quick reply. eisy, 5.8.4 for both firmware and UI, Z-Wave module is 21100 I successfully removed the device and it re-adds OK when I do "Add a Z-Wave Device" - but it doesn't seem to do a "full" add. I did bring it down to the eisy device and added it just a foot or two from the antenna on the Z-Wave dongle. I'll let the device charge overnight and give it another shot in the morning.

I have an Aeotec Z-Wave Wallmote Quad (ZW130-A) that had been working well for quite some time with my 994 and the Z-wave board. It showed up as multiple nodes in ISY and I was able to use the four buttons in multiple programs. This device didn't migrate properly when I migrated to eisy - showed as Placeholder and no attempts at Synchronize > Update with Interview would bring it back (which worked for some of my Z-wave devices). I was able to do a Remove which worked fine. However, when I re-add it as a new Z-wave device, I'm not getting anything except a single node in my device tree: "ZY 088 Wall Controller" Any ideas why I'm not getting all my nodes when I re-add my device? I haven't tried re-booting my eisy yet, but that shouldn't be needed, right? Here are my logs: Tue 10/08/2024 06:13:11 PM : ---- Start Adding Devices - S2 Standard --- Tue 10/08/2024 06:13:11 PM : [ZWAVE-INCL-S2STD] Start Include with S0/S2 or non-secure Tue 10/08/2024 06:13:11 PM : [ZWAVE-INCL-S2STD] Added 'CommandAdded' callback 0xd6a8468 Tue 10/08/2024 06:13:11 PM : Z-Wave Listening for Z-Wave devices to add to the network Tue 10/08/2024 06:13:15 PM : Z-Wave Z-Wave device detected, start adding to network Tue 10/08/2024 06:13:15 PM : Z-Wave Z-Wave device detected, retrieving info Tue 10/08/2024 06:13:15 PM : [ZW-INTERVIEW-38 ] Add interview running entry for 88 Tue 10/08/2024 06:13:16 PM : [Device 88] Waiting on interview complete (timeout in 578) Tue 10/08/2024 06:13:18 PM : [Device 88] Waiting on interview complete (timeout in 538) Tue 10/08/2024 06:13:20 PM : [Device 88] Waiting on interview complete (timeout in 498) Tue 10/08/2024 06:13:22 PM : [Device 88] Waiting on interview complete (timeout in 458) Tue 10/08/2024 06:13:24 PM : [Device 88] Waiting on interview complete (timeout in 418) Tue 10/08/2024 06:13:26 PM : [Device 88] Waiting on interview complete (timeout in 378) Tue 10/08/2024 06:13:28 PM : [Device 88] Waiting on interview complete (timeout in 338) Tue 10/08/2024 06:13:30 PM : [Device 88] Waiting on interview complete (timeout in 298) Tue 10/08/2024 06:13:32 PM : [Device 88] Waiting on interview complete (timeout in 258) Tue 10/08/2024 06:13:34 PM : [Device 88] Waiting on interview complete (timeout in 218) Tue 10/08/2024 06:13:36 PM : [Device 88] Waiting on interview complete (timeout in 178) Tue 10/08/2024 06:13:38 PM : [Device 88] Waiting on interview complete (timeout in 138) Tue 10/08/2024 06:13:40 PM : [Device 88] Waiting on interview complete (timeout in 98) Tue 10/08/2024 06:13:42 PM : [Device 88] Waiting on interview complete (timeout in 58) Tue 10/08/2024 06:13:44 PM : [Device 88] Waiting on interview complete (timeout in 18) Tue 10/08/2024 06:13:46 PM : [Device 88] Waiting on interview complete (timeout in 0) Tue 10/08/2024 06:13:46 PM : [ZW-INTERVIEW-38 ] Device 88 : Interview Done with some non-conforming features : total=0 successful=0 attempted=0 Tue 10/08/2024 06:13:46 PM : ZWAVE-WORKQ-35 Queue sync device 88 (initialize) Tue 10/08/2024 06:13:46 PM : ZWAVE-WORKQ-35 Start sync device 88 Tue 10/08/2024 06:13:46 PM : [ZWAVE-SYNC 88] Rebuilding all existing ISY files/objects for Z-Wave device Tue 10/08/2024 06:13:46 PM : [SYNC-DEVICE 88.0] Root database 4.24.1 mfg=0.0.0 Tue 10/08/2024 06:13:46 PM : [SYNC-DEVICE 88.0] Set commands will now be accepted by the controller Tue 10/08/2024 06:13:46 PM : [ZWAVE-SYNC 88] Not multichannel Tue 10/08/2024 06:13:47 PM : [SYNC-DEVICE 88] Initializing associations to ISY Tue 10/08/2024 06:13:47 PM : ZWAVE-WORKQ-36 Queue write device updates for node 88, full=false Tue 10/08/2024 06:13:47 PM : ZWAVE-WORKQ-35 Finished sync device 88 Tue 10/08/2024 06:13:47 PM : ZWAVE-WORKQ-36 Start write device updates for node 88, full=false Tue 10/08/2024 06:13:47 PM : ZWAVE-WORKQ-36 Finished write device updates for node 88, full=false Tue 10/08/2024 06:14:37 PM : Z-Wave Z-Wave device added Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=32 (0x20) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=89 (0x59) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=90 (0x5A) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=91 (0x5B) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=94 (0x5E) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=96 (0x60) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=112 (0x70) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=113 (0x71) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=114 (0x72) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=115 (0x73) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=122 (0x7A) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=128 (0x80) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=132 (0x84) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=133 (0x85) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=134 (0x86) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=142 (0x8E) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=37 (0x25) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=38 (0x26) : uid=88.0 Tue 10/08/2024 06:14:37 PM : Z-Wave Idle Tue 10/08/2024 06:14:37 PM : Z-Wave Idle Tue 10/08/2024 06:14:37 PM : Z-Wave Idle Thanks...

It seems to be working with "Released" instead of "Pressed" - Control works now. I'm still seeing a few key drops here and there, but nothing too bad. My all-time favorite home automation thing I did: pause button on my Harmony sends a pause command to the player and sets the accent lights to 25% with an IR command to the (now eISY). That's working again now...

@lionheartkc - did you ever find a solution to this? It looks like I'm running into a similar issue...

I guess I'll keep answering my questions here (I need to learn patience before I post). It looks like "Released" is a good event to subscribe to instead of "Pressed". That seems to work better... Thanks for this solution... should be a good replacement for the old 944 IR (although I am also getting some keypresses not registering like noted in that other thread).

I was trying to clean up my devices in the tree and in doing so I thought I would delete a couple of them ("IR Button B" for example) and re-create them by pressing the button on my remote again. It seems the plugin might remember that it already added it to my devices and doesn't "send" it back to IOX again? Is there a way for me to re-add those that I've deleted? Thanks... [EDIT: Never mind. It looks like after rebooting my eisy and re-logging into the console it ended up re-adding them at some point in time. Leaving this here in case anyone else runs into this...]

OK - I have this set up and going and I see my Harmony remote button presses get picked up by the Polyglot plugin and I have the eISY event viewer picking them up as well. It created my nodes in my devices (eiSY IR Controller/n002_irbutton_104, etc.). All good so far. What I'm not understanding is the next step: how do I get one of those events to fire my program? I've tried "if Control > eISY IR Controller / IR Button K is pressed" (which shows up as "is switched pressed") which doesn't work. I've also tried "Status > State is Pressed" as well. What do I need to use as an If condition for this to work? Missing something obvious?

Stumbled around a bit and I may have found what I needed. It looks like the Hue node server was not actually installed - it may have just created a place holder for it during the migration to EISY? I went through the Node Store and installed it to Slot 1 and then I saw instructions to press the button on the Hue Bridge and restart the node. It went through and discovered my Hue devices. So I guess no "migration" but rather a fresh install/setup of that node server is what I needed to do. I'll turn off my old Raspberry Pi and start testing...

Migrating my ISY 944 to eisy and things seem to be going smoothly. I had set up Polyglot on an old Raspberry PI a long time ago and I barely remember how it works. All I know is that it still works - it has one node server (Hue) with only a couple Hue devices. I'm not sure what to do to get this moved over to my eisy. I can get to both of them in a web browser (port 3000) but I'm not sure what I should do to backup my node server on the old one and move it to the new one. Looks like most of the guides are targeted at moving 3.x to 3.x - not sure if anyone is even using an ancient 2.2x server these days. Any pointers would be helpful... Thanks.

So... it was the connection of the sensor wires at the ioLinc that was the problem... everything is working great now... Thanks for the replies on this...

Thanks for the tips so far. It appears that the sensor is flat out not working - I thought I had it tested, but those wires that go to the ioLinc are easily jostled and could have come loose when I rearranged things. I'll get the stepladder out and do some testing on it...

Unfortunately adding the second scene didn't work... Just to toss out the other settings: I have the button on the keypad set to "non-toggle [On]" and relay is set to "Momentary B" and just "LED on TX" and "Relay follows input" as the two checkboxes. I'm on 5.0.16c - I'm ready to upgrade, but I have to swap out the Z-wave module in the process (I have it, just not looking forward to the work and troubleshooting that side of things).

Thanks for the responses. The LED that I'm concerned about is the one on the keypad. What you're saying makes sense - I'll try the second scene as you describe. I was kind of confused about this "relay follows input" option - I'll have to do some research on that to see what it actually does...

Another garage door thread... I saw this note from a 2015 thread. I got the alternative magnetic sensor and wired it for Normally Open. Everything works for me except the LED lighting up. I did notice that there is no option for "relay response to sensor" - maybe it got renamed to "relay follows input?" Do I need to actually add the Sensor to the scene as well?

We have a "mystery" switch which we believe was used for an obsolete outdoor light at one point in time. I have confirmed that the line is dead. I believe I have a neutral on the switch next to it (I will confirm that). Can I tap the line and neutral from that switch and connect an Insteon 6 or 8 button wall keypad, even if I don't use its load for anything? Just use the 8 buttons for other programmed devices? I would obviously cap the existing wires that are leading to the dumb switch. Thanks...

Thanks, Gary - I'll look at one of those if I have trouble moving forward ...

Gzahar - It indeed looks like the trick for the relay was to provide the power to BOTH the VCC and INPUT channels (like you suggested) - making a small jumper wire between those two makes it work as expected: 12v trigger has power, LED lights up. 12v trigger goes away, LED turns off. So now it's on to the i/o Linc side of things and then figuring out how to integrate it into my ISY program. I'll report back...

Popping in with more questions - really feeling my lack of knowledge on circuitry and electronics here... So I got the 12v relay as suggested (https://amz.run/3djb) but I'm not really sure how to hook everything up. From my receiver/amp I have a 12vdc trigger output - I got a cable with mono 3.5mm jack on one end and two breakout wires on the other end. The input side of the board is four options: VCC (power supply +), GND (Power supply ground), GND (Control signal ground) and INPUT (Control signal input). Intuitively I thought that I would take one of the 12vdc ends and use it for VCC and the other for the Power Supply Ground - i.e., the 12vdc trigger itself would be powering the relay module. I was hoping that I would get the LED to light up, even without anything hooked up on the other side. Now I'm not so sure - do I need to have an actual (separate) DC power supply to the VCC/GND? And then hook my 12vdc trigger output into the Control signal side? I thought that the power from the trigger cable would take care of everything but now I'm not so sure. The other side then looks like this? COM1 to i/o Linc GND and then NO1 (or NC1) to SENSE? Thanks for looking at my remedial questions...

Cool - I'll start looking down that path. I assume that I would need to cut the 1/8" plug and separate it out into separate wires for the input side. Will do some further research (and probably pop in back here with more questions I'm sure...)

Is there a way for me to subscribe to 12VDC output trigger (as is found on A/V receivers, projectors)? For instance, my Russound has this functionality: 12VDC System Trigger Out Trigger Out 12VDC output is used for triggering an external amplifier or other component. The connections for the output are made using a two-conductor cable with 1/8” male mini-plug jacks at each end. The tip is positive (+) and sleeve is negative (-). The System Trigger Out supplies 12VDC when the first keypad is turned on. The 12 VDC is removed 5 minutes after the last keypad is turned off. I'm looking for a some way to detect when either of those things happens: when the first zone/keypad turns on, give me something that I can use to fire a program. Five minutes after all of the zones have been turned off, let me fire another program. It seems like everything I can find about 12V triggers are the opposite: using some devices to send an input trigger to another device to turn it on. I want to do the opposite: DETECT a trigger and do something with it. I found this older thread which discusses asks similar: But I don't want to turn a light on or off - I would like to call a Network resource in my program. Is there some way I could hack an open/close sensor or something like that? Russound is on, door is "open", Russound is off, door is "closed"? Thanks for any ideas... (preferably something that doesn't involve soldering...)

Upgraded to 5.x a couple months ago and I just had a PLM go belly-up (unrelated). So I'm trying to migrate to a new PLM and it's ... well, it's going. One thing that I'm having a problem with is adding a new TriggerLinc. I actually deleted it and did a Link Management > New Insteon Device. It appears to get created in my list of devices, but I'm getting some weirdness: - I only get two devices. I'm used to "Closed", "Heartbeat", and "Opened" - I'm not getting the "Closed" one. - When I went through the adding process, I chose a name "OpenerCloser" - but my two devices are named this: "OpenerCloser.4 - Heartbeat" "11.BB.C9.1 - Open" In the past I would have gotten this: "OpenerCloser - Heartbeat" (no ".4" in there) "OpenerCloser - Opened" (no ".1" in there and there is an "ed" at the end) "OpenerCloser - Closed" (this one is completely missing) Is this just some 5.x stuff that I'm not used to yet or do I have something going on? Thanks...

Thanks for the help on this - had to chuckle because I couldn't possibly drink beers that quickly. Very easy upgrade and everything seems to be working pretty well so far... Even got polyglot going in short order last evening as well!