Tom Carmody

I came online to update my post and found your reply. Thanks for your response. I'm not using batteries with my thermostat and the purpose for the I/O module is to turn on an additional wall heater when the main heater is on. The I/O module was working beautifully with the old Insteon thermostat, so I gave it a try. The update I came online to make was that I found the culprit. I assumed there was something in the thermostat that was causing the premature command to off. Among other features, what the Go Control thermostat does that the Insteon thermostat doesn't do, is report a change in temperature measurement with each degree. I had a secondary program that used an else statement and in the if statement, I had, If temperature >75 degrees and the wall heater was on to turn off the I/O module. Since the Z-wave sends a temperature our with each change, the else statement picked it up, since it was under 75 degrees and shut off the I/O Module. The Insteon Thermostat wouldn't trigger it for being under 75 degrees. It was a bad program and I have deleted it and found a better way to prevent using the wall heater when it's above 75 degrees. Thanks, again.

I have a Go Control Model Model #GC-TBZ48 that I installed on my eisy network and it works beautifully. I have a simple program to turn on an Insteon I/O Module when the Heat/Cool State changes from Idle to Heating. Here's the If/then statement: If Thermostat Heat/Cool State is "Heating", then Set I/O Relay "On" I have another program that turns off the I/O Module. After the thermostat reaches it's set point the state changes to "Pending Heat" and then a few minutes later the state is switches over to "Idle". Here's the If/then statement: If Thermostat Heat/Cool State is "Idle" or "Pending Heat", the Set I/O Relay "Off". It works great unless the time it takes for the thermostat takes longer than 10 to 20 minutes. If it takes longer than just going up a degree or two, out of the blue, the I/O Module receives a command to turn "Off". I can't figure out why. The amount of time is somewhat random. Sometimes it's 10 minutes and other times, it's different. I have a second thermostat that has a similar program and it's controlling an Insteon ON/Off Module. It doesn't have the same problem. I have attached two screen-shots of my Event Viewer on one PNG file. The top shot is the second thermostat. It was a successful operation when the setpoint was reached. The bottom shot shows the error. The ZY037 was not yet up to set point and 2:13:07PM, something happened to trigger the I/O Module (Insteon: 15.BC,3F). Is there a better way to write the program? If so, why do I not get an error on the "On/Off" Module?. I'm not a Z-wave expert and I have no idea what 80& of it means. Thanks for any input.

When it gets stalled in the writing mode, am I hurting things by clicking on write changes? When I do this, it acts like it has finished writing about 5 seconds later. Should I be more patient? How long should it take for a ZSE29 to be included and written into Admin Console?

Thanks. I could use the Aeotec Extender for the second motion sensor but the first one is less than two feet away from the eISY on the other side of a wall. I'll double check the linking/inclusion mode. The motion sensors are powered by a USB cord so there's no battery so the close one will act nicely to help the second sensor (also USB powered).

Thanks for your quick reply. What's your eisy firmware and UI versions? IoX v.5.6.3 Are you using the Zwave Zmatter dongle? Yes If you bring the sensor close to the eisy and link it do all the nodes show up? I started at about 20 feet away (one story up and moved to 1 foot away. At 20 feet, I only saw a couple of nodes show up. At 1 foot sometimes I'd get the same two nodes and other times I'd get all of them. After I took it out of test mode and it experienced an immediate freeze, I would exclude/remove the device and try it again. I did notice that pressing the tamper button three times every 20 seconds or so (which wakes up or keeps awake the sensor) gave me a much greater possibility of loading all of the nodes. With or without the pressing of the tamper button 3 times, if all of the nodes appeared, it would say writing and stay on writing until I right clicked the device name in the left-hand column and then left clicked write changes. It's possible that you may have marginal communications between the sensor and the eisy. How many other a/c powered Zwave devices do you have installed? Besides the two sensors I tried to load, all I have on this network is a door lock.

I am having a heck of a time getting the subject sensors up and running on my eISY network. The UDI Mobile only will not fully load all of the features and won't show the motion status. When I use Admin Console, it takes a number of tries to get it to seemingly fully load. When it partially loads, I have to exclude the previous inclusion. When I get it to load fully (or at least that what is seems because all of the features become available (power level, luminance reading, motion, etc.) it works perfectly in test mode but once it's mounted and the tamper switch is depressed, it freezes up and will not detect motion. I contacted Zooz and although they responded quickly, they haven't been able to help because they are not familiar with UDI and don't have an eISY in their lab. I have reset, reloaded, tried lower level of security, tried no security, and answered lot's of their questions. Because I'm having problems with all three of my sensors, they don't believe the problem is with the sensors. I have a little Zooz ZSE18 indoor sensor that is working well with my eISY. Has anybody had success with the ZSE29 on an eISY network? Thanks.