Jump to content

breischaft

Members
  • Posts

    62
  • Joined

  • Last visited

Everything posted by breischaft

  1. I saw that, but the next line has Zwave prereq's. this is where I read into it that I needed to switch, etc. I see now those critical words "if not," thank you for the clarification. Appreciate the fast response.
  2. I have 5.0.16B and thinking to go to C. am I reading this right that I need to shift my zwave stuff to another controller, upgrade ISY, and then shift back? so I need a second controller or I lose all zwave devices and programs?
  3. not the answer I wanted, but what I expected. Thanks for the quick reply.
  4. "Herein lies the problem... who is the OEM for these thermostat's. The LX205T is identical in looks and specs as the OJ and NuHeat." @simplextech you noted the OJ one looks the same - this is the one I have. Is there a way to make what you've done with the NuHeat one work for my OJ? the initial issue I see is that the node is looking to Nuheat.com or whatever to get into the unit. thanks
  5. Thank you for putting this information out. very helpful.
  6. Does it update automatically or is there something we need to do? Thanks for great compatibility
  7. FYI - I did exclude and then add one of them. behavior is still the same. it looked like the exclude and include processes worked properly.
  8. Thanks for the responses. The two smoke detectors both connected easily. They are both physically only a couple feet away from the ISY - I wanted to make sure all is working properly before I install and buy more. I try to do a network heal and watch the event viewer. Each node is updated for neighbors twice and fails all times. similarly if I sync nodes, there is a "can't get info" error from each. If I right click on one of them in the device list and then query, I get a communication error and all five nodes for the detector go to exclamation points. If I look at the test alarm node, it shows a status of off. when I press the test button on the smoke detector, status on admin console changes to on. but if I immediately query, no communication. These are my first z-wave devices, also first battery-only devices. feels like there's a connection, but then devices "sleep" and do not respond to queries. I was hoping to use several of these to help form the backbone of z-wave mesh network throughout house. are these working as you would expect and I'm missing something?
  9. I purchased a couple of these and paired with my isy994zw using z wave. almost immediately I get 'failed communicating with' errors. How do I get those to go away or what should I be expecting? also not understanding how to use the different connections (not sure term): smoke alarm, malfunction alarm, test alarm, low battery, heartbeat, CO alarm, end of life alarm I was expecting that each of these would have a state or status that I could incorporate into some scene or program logic. Thanks for your help
  10. anyone ever get this figured out?
×
×
  • Create New...