Jump to content

Xathros

Members
  • Posts

    4589
  • Joined

  • Last visited

Everything posted by Xathros

  1. He upgraded from a 99 to a 994. ZWave is not available for the 99. -Xathros
  2. Simply setting a variable at the same time as I send a command to the relay. As far as I know, there is no way to query the relay state. You are welcome to quote me. -Xathros Sent from my iPhone using Tapatalk
  3. I printed my own as well. I don't think they look quite as nice as the custom etched buttons can but at least all of mine are the same color. And, yes, you can still do it this way. -Xathros Sent from my iPhone using Tapatalk
  4. Congrats! I thought I was there 4 years ago but these damn Black and Decker X10 weather proof relay modules keep finding their way back to my seasonal exterior lighting. Just can't bring myself to spend the $90+ to replace them with the outdoor appliance modules since they still work so well. -Xathros
  5. I don't know for sure but I bet thats it. -Xathros
  6. I should have caught that! -Xathros
  7. You are missing more than just setpoint up/dn, also missing schedule and options buttons. Are you sure they just aren't off the screen? you screen shot does not include the very bottom of the interface where the buttons appear for me. -Xathros
  8. If the button is a controller of a scene, you can't. Remove the button from the scene and use programs to activate the various scenes based on the type of button press instead. -Xathros
  9. Anytime. Happy to help. -Xathros
  10. Exactly What that does is any time the button is pushed, it checks the sensor state (variable value) and sets the button LED accordingly. Sensor on, LED on, sensor off, LED off. The program is triggers when the button is turned on or off and uses the value of the integer variable to decide the LED state. The variable is managed by the first program. NOTE: The variable in this case is an integer variable AND the button LED is also responder in a scene controlled by the sensor. Make sense? -Xathros
  11. Sounds to me like a mislabeled Switchlinc Relay. -Xathros
  12. I think EricK's point was that a KPL offers additional buttons for additional functions. -Xathros Sent from my iPhone using Tapatalk
  13. EricK- I see 2 programs for this using an integer rather than state variable: If Control 'Door Sensor' is Switched On Or Control 'Door Sensor' is Not Switched Off Then $i.DoorSensor = 1 Else $i.DoorSensor = 0 If ( Control 'KPL_Button' is switched On or Control 'KPL_Button' is switched Off ) And $i.DoorSensor = 1 Then Wait 2 seconds Set Scene 'KPL_Button' On Else Wait 2 Seconds Set Scene 'KPL_Button' Off -Xathros
  14. The only way I see to accomplish this would be to move the control of your load off of the dimmer and onto a micro module. Then use programs to monitor the dimmers various control messages and do whatever you want from there. -Xathros
  15. I've only done this once so far and don't feel fully comfortable with my memory, but I believe it was a total reset and I needed to delete the unit from the ISY and re exclude/include to get it going again. This was at a time that I was doing a fair amount of other ZWave testing so I may be mixing memories here. If I get a chance this weekend, I will reset one of my less critical unites and confirm. -Xathros
  16. You got it sir! -Xathros
  17. Solid advice. This is exactly how I got to where I am now. -Xathros
  18. In that line of thinking, one could place a normally closed reed switch in series with the IOLinc relay so that the circuit to the relay is broken when the door is closed. -Xathros
  19. Sorry, My bad! I just assumed that the sensor node could be queried under program control. It would appear not. I also have not been able to write updates via program despite various delays as described in another thread. In my case, all of my sensors are 5+ years old and I suspect some things have changed with newer sensors that might make this possible. -Xathros
  20. You can query the low batt node via program. Just need to make sure that the program knows you replaced the batt. The MS only notifies on low batt once so it won't continue to remind you after clearing if you haven't replaced the batt. Night only needs to be disabled. Try setting the sensitivity to 128. You will need to play with that value to get it where you need it. The MS needs to cross the light/dark threshold defined by that value for 3.5 minutes before it will change state for the dusk/dawn node. Hope this helps. -Xathros
  21. No - program is good. Once the node clears the program will eval false and stop. Query the low batt node to clear the On condition. There is a another setting in the MS for Night only mode that need to be disabled. -Xathros
  22. While this is not exactly what you asked for, this is what I do and contains what you need to do what you asked. In my case, I heat with a pellet stove. I use info from my Insteon stat (tied to my oil burner) to control the stove via a relay interface. I have my Stat set at 58 (minimum temp before the furnace comes on) and force the stat to stay there if manually changed. My ISY programs determine when to enable/disable the stove and I can change those set points and hours of operation in my programs. In fact, I have different set points and hours of operation automatically chosen based on outside temps. Thermostat - Autoset - [ID 01CA][Parent 0023] If Status 'Thermostats / LR Thermostat - Main' is not 58° (Heat Setpoint) Or Status 'Thermostats / LR Thermostat - Main' is not 82° (Cool Setpoint) Then Set 'Thermostats / LR Thermostat - Main' 58° (Heat Setpoint) Set 'Thermostats / LR Thermostat - Main' 82° (Cool Setpoint) Else - No Actions - (To add one, press 'Action') Hope this helps. -Xathros
  23. Heh, my Aotec ZWave smart energy switches require a factory reset to reset accumulated KWH. Firmware engineer must not have had his coffee that day... -Xathros
  24. What else is plugged in in your garage? Battery chargers for tools and things like that can have an adverse effect on comms. Unplug everything other than the IOLinc, test again. If comms improve, add back items till the problem returns. Anything that kills your comms should be put on a filter. -Xathros
  25. It's encoded Unicode I believe and that is what causes the odd symbols and rejection by the email to sms gateway. -Xathros
×
×
  • Create New...