Andy P

Wibar - welcome to ISY! Before everyone jumps in, can you say whether you have discovered the UDI Wiki which has lots of examples, or any of the other resources for learning about ISY? ISY-99i/ISY-26 INSTEON:Create a Program - Universal Devices, Inc. Wiki (universal-devices.com) Andy

Oh Thanks for clarifying, I never had one of those dual relay outlets.

I got a couple of the newer I3 outlets. I3 do not work with the 994 but I had just upgraded to EISY (mine are at 5.7.0), so no issue for me. There are several key differences between the I3 outlets and the older dual band dimmer outlet (which I also have installed - 2472D v44). First and foremost, the I3 is not a dimmer - only on/off. The good news is that this means you don't need that magnet thing on the plug to use the outlet. The bad news might be that it isn't a dimmer - but I am using it for a fan so didn't matter to me. Second, Both the top and bottom outlets are controllable - not just the top one. Third, the I3 load sensing, is supposed to be able to trigger an event to control other devices when you manually turn on/off the device that is plugged into the outlet, but I have not figured out how to use that yet. Programming wise, it is the same other than not being a dimmer and having two devices in one. I have one outlet set to turn on when I turn on a wall switch for a bathroom fan. Also use a programmed timer to turn it off. I'm keeping the old dimmer outlet because it works well in the nightstand to dim the light and the other outlet is used for charging a smartphone so doesn't need to be switched. Andy

OK, so I know this node server is not being actively developed, but I thought I would make a suggestion and see what happens. On the physical panel for the Honeywell Vista, there is a green light that is on when no zones are faulted. I looked through the TC2 API alarm node status enumeration and it does not look like the API returns a 'not ready to arm' state unfortunately. So, I can write a program with 22 IF statements, one for each node, to check if all nodes are OK, but that seems like a lot of work. So, my feature request is that at each polling interval, the top node which represents the alarm panel has a new property 'All Nodes OK' that would be set to True or False depending on whether the scan of all the nodes returned OK for every node. Or in other words, if that property was false, it means that at least one zone is not OK. This would allow me to do some automation, like turn on a light, if any of my zones are faulted without having to put all 22 zones in the IF statement. I looked through the source code for the node server, but I am not familiar enough with how the node servers are coded to tell how hard that change would be. Meanwhile, I guess I will bite the bullet and create a boolean variable that gets set by those 22 IF statements. Andy

After reading this post, I decided to try the TotalConnect plugin with my EISY (v5.7.0) Installed the node server and waited for it to populate the nodes. No problem. A couple minutes later I had 23 nodes corresponding to the wired and wireless zones on my Honeywell panel. However, all the nodes showed status of 'off'. I correctly guessed that I had to restart the admin console for the status to look right. After a restart I am seeing all the zones 'ok', or 'faulted' as expected and the high level node as 'disarmed'. I wonder if the OP just needs to restart the admin console to get the status to change from 'locked' to the correct status. I decided to write a simple program to turn on a light when the window in my office was opened. Well, it worked, but of course since the polling interval is set to 120 seconds, it took almost 2 minutes before the light turned on. I don't expect to use the connection for any real time events so I don't plan to change the polling interval. I will probably use it to turn on the random away lights program when the alarm is armed. Bob, thanks for porting this and seems to be working right, at least for me. Andy

Any chance that there is a direct link between FRONT.DOOR and Entry Front Door Light or they are linked together in a scene? Try disabling the program entirely and opening the door and see if the light goes on.

Fixed it! Thanks, @Goose66 My automations are working again! I use the MyQ nodeserver nodes in a program to turn on lights in an 8 button KPL whenever a garage door is open. Appreciate your quick update. Andy

Yes, same problem here - same message, not working at all. Should probably close this thread and stick with that other one.

Thanks for the info. If you have it set to Momentary C, do you also have a sensor with set of contacts wired to the 2450? I'm pretty sure I was using Momentary B before switching to myQ openers but I can't be 100% sure. You could potentially try switching it to Momentary C and see if that works then go back to debugging mode C. Momentary C Use the I/O Linc sensor input to determine whether the I/O Linc relay will trigger. An ON command’s desired state can be programmed to either open or closed. I/O Linc will use the opposite for the OFF command’s desired sensor state. For example, if an ON command is programmed to trigger only when the sensor is closed, an OFF command will trigger only when the sensor is open

Hi, probably need a bit more info to help. Can you describe a little more about what is working and what is not. 1. So you have the 2450 attached to the garage door using the COM and NO terminals? 2. You have the 2450 set to Momentary B mode? 3. When you say the remotes are working, is that the remote that came with the garage door or an Insteon remote paired to the 2450? 4. Have you been able to discover the device using the ISY and how does it show up? 5. What is not working with the ISY? You can screenshot any info that could help the readers here provide advice. Andy

I used to directly link the MS to the lights as well, but wanted a way to override the motion if I used the switch. So I have a program that sets the dim level to 59% if turned on by motion. The default brightness of the manual switch scene is 50%. And opening the door also triggers the light to 59% similar to motion. Adjusting the brightness to anything other than 59% also disables the motion off. Mud or Hall Motion - [ID 0011][Parent 0010] If ( 'Motion Mudroom.1 Motion' is switched On Or 'Motion Hallway.1 Motion' is switched On ) And 'Main Hallway' Status is Off Then Set 'Main Hallway' On 59% Set 'Main Hallway Remote' On 59% Hallway Motion End - [ID 0033][Parent 0010] If 'Motion Hallway.1 Motion' is switched Off And 'Motion Mudroom.1 Motion' Status is Off And 'Main Hallway' Status is 59% Then Set 'Main Hallway' Off Set 'Main Hallway Remote' Off Mudroom Motion End - [ID 0013][Parent 0010] If 'Motion Mudroom.1 Motion' is switched Off And 'Motion Hallway.1 Motion' Status is Off And 'Main Hallway' Status is 59% Then Set 'Main Hallway' Off Set 'Main Hallway Remote' Off Side Door Opens - [ID 0046][Parent 0010] If 'Breezeway Door' is switched On And 'Main Hallway' Status is Off Then Set 'Main Hallway' On 59% Set 'Main Hallway Remote' On 59% Andy

Every once in a while launching the finder does not find either of my EISYs, so when it did find them, I did a SAVE file. Now when it doesn't find the EISY, I just do a LOAD and it allows me to get to the admin consoles without any problem. Never figured out the pattern for when they don't show up in the finder. Andy

This is what the log entry should look like: Tue 07/25/2023 06:36:46 AM : [55 A9 F 1 ] DON 1 Tue 07/25/2023 06:36:46 AM : [55 A9 F 1 ] ST 255 (uom=100 prec=0) Tue 07/25/2023 06:36:46 AM : [55 A9 F 1 ] DON 1 Tue 07/25/2023 06:37:22 AM : [55 A9 F 1 ] DOF 1 Tue 07/25/2023 06:37:22 AM : [55 A9 F 1 ] ST 0 (uom=100 prec=0) Tue 07/25/2023 06:37:23 AM : [55 A9 F 1 ] DOF 1 Here are my settings: Andy

This is the MELE Quieter3 document - it labels the hole CMOS Reset/BIOS Reset

Pul all of the away programs in a folder. I use the name Random because the lights have a random pattern. Create a State (boolean) variable $State_Random. Set the folder condition to IF $State_Random is 1 Put a scene controller by the door that you exit - use that to turn the random mode on and off. Very easy as you leave the house! Assign one of the buttons of the scene controller to a scene called Switch Random. Create these programs SC Random On Switch If 'SC / Mudroom Scene.B' is switched On Then Run Program 'Turn Random On' (Then Path) Resource 'Notify Random On' SC Random Off Switch If 'SC / Mudroom Scene.B' is switched Off Then Run Program 'Turn Random Off' (Then Path) Resource 'Notify Random Off' Turn Random On If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then $State_Random = 1 $State_Random Init To 1 Set 'Switch Random' On Else - No Actions - (To add one, press 'Action') And Turn Random Off If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then $State_Random = 0 $State_Random Init To 0 Set 'Switch Random' Off

OK, Thanks, very helpful to confirm that the scene buttons only turn on and I didn't mess anything up. Based on this, I have changed my usage as follows. created a scene with the loft light switch added shop stairs button 2 as a scene controller to turn the scene ON. added shop stairs button 4 as a scene controller to turn the scene OFF. set the color of button 2 LED to green (parm 8=2) set the color of button 4 LED to red (parm 10=3) created a program that runs when the loft light status changes to turn the button leds on and off So now, I can turn on the loft light with button 2. Turn off the loft light with button 4 and when the program runs, it either turns on the green light on button 2 or the red light on button 4 and turns the other light off. Here is the program - had to add the waits to get it to work correctly Loft light status - [ID 0009][Parent 0007] If 'Shop Loft-Binary' Status is On Then Wait 1 second Set 'Shop Stairs-Binary' Set Configuration Parameter 3 = 3 Wait 1 second Set 'Shop Stairs-Binary' Set Configuration Parameter 5 = 2 Else Wait 1 second Set 'Shop Stairs-Binary' Set Configuration Parameter 5 = 3 Wait 1 second Set 'Shop Stairs-Binary' Set Configuration Parameter 3 = 2 Doing the same for the attic light so this effectively gives me a switch that can turn the stairs light on or off with the big button and turn the loft and attic lights on and off with each using a pair of small buttons and including indicators of being on or off on those buttons. Thanks for your help! Andy

I am in the process of moving my z-wave devices from Hubitat to the z dongle on EISY (5.6.0, 5226, 21100), and have a lot working but some strange behaviors. I followed the process of exclusion, factory reset then inclusion to get the best results. The ZEN32 has one button (called the relay and also called button 5) and 4 smaller buttons are called 1 through 4. Adding the device creates 11 nodes: 1 node for the relay called _1 Binary Switch 5 nodes for the small buttons plus the relay called 201N001 through 201N005 Central Scene Control Button 5 nodes for the small buttons plus the relay called 252N002, 4, 6, 8 and 10 Basic Association So, the normal operation of the big button does cause the Binary Switch node to change from On to Off and back again, and I can also control it through programs - all good. Pressing small button 3 generates a log entry. Sun 06/25/2023 08:27:09 AM : [D2D EVENT ] Event [ZY017_201N003] [DON] [0] uom=115 prec=0 Sun 06/25/2023 08:27:09 AM : [ZY017_201N003 ] DON 0 (uom=115 prec=0) Sun 06/25/2023 08:27:09 AM : [ZWAVE-CTL-EVENT ] Basic Set from 17.0 unmapped (ignored) So, it says unmapped ignored (although it will trigger program execution). First questions - when I turn on zwave -> detect button presses I can get the dialog box to pop up, but there is no node than allows me to 'right click on an association only node' and map the button - so does that actually work? Second question - when I press button 3 again, it again generates a DON event. No matter which button I press, or how many times, they only generate DON events, never DOF. I reviewed the advanced settings for the device and there is no setting that would appear to cause this behavior. SO, how do I get this device to generate both DON and DOF events? One side effect of this behavior is that when I assign a button to a SCENE as a controller and add another switch to that scene, I can turn that Scene ON but cannot turn the scene back off using the ZEN32 buttons. I also tried using the Basic Association nodes, but they don't seem to generate any events at all in the log (at level 3). My work around right now was to create a program that basically uses the DON events to toggle the other switch - here using button 1 which toggles the loft lights when the stairs button is pressed repeatedly. I am using 'switched on' instead of 'status on' because if you use 'status on' the program just goes into a loop turning itself on and off. Zen32 - [ID 0018][Parent 0007] If 'Shop Stairs-S1' is switched On And 'Shop Loft-Binary' Status is Off Then Set 'Shop Loft-Binary' On Else Set 'Shop Loft-Binary' Off I can live with the work around, but it means that the LED indicator is out of sync sometimes with the on/off status so I would really like to get the buttons to generate off events and get the scenes working. Any ideas? I am reaching out to ZOOZ as well for firmware updates. Andy

I just received my dongle as well - no instructions in the box, but found the answer in this post - nice to have an active user community!

I have to agree with that - I always use 'add device and remove existing links' to avoid unexpected consequences

I walked away from Indigo three years ago and started over with a 994. Now running on the EISY. The UD hardware and software is rock solid. I miss two things from Indigo, though. The admin console equivalent was a bit easier to use and navigate and the ability to create web portals with device control and status was amazing. There were some issues with compatibility with new MacOS releases at the time which was annoying. During the transition, I bought a new PLM and set up everything in parallel with Indigo before shutting it down. Also tried using the ISY bridge software to sync status to indigo for a while after removing the PLM from indigo, but decided that was not responsive or reliable enough to continue. I ended up using Hubitat for the zwave stuff, but once the zwave/matter usb device is in stock again, I plan to get one of those for the EISY. Good luck with the transition! Andy

Just tried this node server. Installed ok and created two nodes - one for the connection and one for the spa. Yes, I set the host parameter to the IP address. But all the values are zero. In the log, there is a message :AttributeError: module 'pybalboa' has no attribute 'BalboaSpaWifi' when I try to set any value I looked at the package on github and there is no pybalboa.py in the package. So then I searched github for pybalboa and found that in a separate project. It looks like that module has had extensive changes including deleting pybalboa.py and replacing it with client.py So the question is - is there any active development on this node server and does the nodeserver need to be updated to use the new version of pybalboa or to have an old version of pybalboa included in the 3.0.0 version? Or am I doing something wrong? Thanks, Andy

It works!!! Thanks, Bob - perfect fix. Now I am getting all the button events in the polyglot console and the admin console and the programs are triggering properly. I went ahead and bought the production version - but, oops, on the wrong EISY. So bought another for my House EISY. Now I just have to buy a Lutron hub for my barn so I can use the Pico remotes over there. Thanks again, Andy

Thanks! i will give it a try as soon as i have a chance and let you know. Andy

Just to add that. when I use the PJ2-3BRL remote, I see these entries as expected 2023-05-25 12:43:40,489 Thread-2 udi_interface DEBUG picos:btn_off_callback: Button off was Press 2023-05-25 12:43:40,489 Thread-2 udi_interface.interface DEBUG interface:send: PUBLISHING {'command': [{'address': 'device11_1', 'cmd': 'DOF'}]} 2023-05-25 12:43:40,507 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2023-05-25 12:43:40,507 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2023-05-25 12:43:40,801 Thread-2 udi_interface DEBUG picos:btn_off_callback: Button off was Release

Yes to everything about the node created for each button. And exactly how I set up the programs. The problem is, no event is generated at all for any of the buttons and so no programs run. I turned on debug logging in the polyglot console and there is no log entry when I press a button and no action in the EISY admin console either for that remote. If I set that exact remote through the lutron app to control a light, I do get events for the light in both the log and in the admin console as I mentioned. This is the PICO remote model that has no Favorite button in the middle, but other than that seems to be the same. Andy