Xathros

Larry- I think he was planning on putting the converter at the basement end of the wire so heat wouldn't be an issue there. -Xathros

Sure, Pi is full linux. But I run a VM for linux network services that is much better than a limited system on a chip and without any additional hardware purchase. In context of sensor data for HA with ISY, can you share your thoughts on CAI vs Pi? For strictly sensors, the CAI is likely the easiest route as apostolakisl stated above. The Pi is just capable of much more albeit more complex. Cost wise, they are roughly the same and both require external power supplies. The Pi would also require an add-on board to connect the one wire sensors whereas the CAI is ready to accept then sensors right out of the box. A full VM may be more capable than the Pi but the Pi only draws a few watts and runs off a cell charger. One of my goals was to eliminate the cost of a full PC 24/7 and not lose the basic services that it provided. The Pi was a perfect fit for that. -Xathros

What was the reason you switched? Would you mind sharing a few pros and cons for CAI vs Pi? I have both a CAI and a Pi. The CAI is a good solid stable interface for these sensors and other I/O needs. The Pi can do this and so much more being a full linux based computer. I use the Pi as a webserver, ftp server, syslog server and as an interface to other things that cannot talk directly to the ISY. -Xathros

Hi Oberkc- I just went back and re-read the OP. I do believe my solution is what balla4eva33 was asking for. His problem was that with multiple sensors timing out at different times, the lights were not behaving in a usable manor. My solution simply moved the timer from inside the 3 MS to my program and keeps the lights on while there is continued motion detected by any of the 3 sensors. Thank you for adding the info RE: jumper 5 and using the ISY for configuring the sensors. I probably should have pointed that out as well. -Xathros

Excellent! Glad I could help. Just noticed that I failed to answer one of your questions Re: Beep Duration. Some newer Insteon devices can beep. Not very loud and its just a short beep (maybe 1/10 second) regardless of the duration selected. I use this on some of my light timers to warn that a light is about to turn off in 30 Seconds and at a few key locations when a door opens - sort of like a chime. I would not rely on this as a doorbell as if there is even any moderate noise in the room you may not hear these beeps. -Xathros

Looks like it works for me on my T1800. Look at options on the main node and make sure repoort Humidity is checked. Then in a program you can: If Status 'Thermostats / LR Thermostat - Main' < 40% (Humidity) Then Whatever... -Xathros EDIT: Re-read your post and I think I missed your point. I don't believe the Stat itself is designed to control a humidity system. You could however use the info from the stat to build your own as I posted above.

It gives the system the ability to know that the furnace or AC is running (or at least should be) and do something based on that knowledge. I use the HeatCtl node in a routine that tracks my furnace runtime for daily/monthly reporting. If you happen to have door and/or window sensors, you could fire off a notification if your furnace is calling for heat and a door(s) or window(s) are open. Maybe turn on/off fans to help distribute the heat/cool. -Xathros

For the second example, it is fewer programs for a good set of features. Easy to maintain or modify. This would work best with the sensor in On only, Sensing mode (checked). It looks to me like franklyn7895's programs would accomplish the same as mine but using 4 programs instead of 2. These would also work best with the sensor configured for On Only, Sensing mode (checked) -Xathros

Here in New England, sprinkler systems are air pressurized with a foot valve that opens when the air pressure in the system drops. This way, exposed pipes normally have no water in them until a head pops and lets the air pressure drop. I'm not sure what the standards/codes call for in other areas but a system that could be subject to freezing doesn't sound like a good idea to me. -Xathros

Looks to me like any of those would work. Like Larry said, any USB wallwart would suffice and likely be much cheaper. -Xathros

I use one of these to power a number of my 5v devices (including the ISY). It's overkill for just a Stat but will provide a nice stable 5V. http://www.amazon.com/Amico-Regulated-Switching-Converter-Display/dp/B008SO6MIO/ref=sr_1_2?ie=UTF8&qid=1391019963&sr=8-2&keywords=5v+switching+power+supply I also have a 12V version for my router, switch and DIN relay. -Xathros

That is because the program is re-triggered by the changing status of the lamp. In my programs: Program: MotionMonitor If Control MotionDetector is Switched On Then Run Program Blink (If Path) Program Blink: (Disabled) If Status Light is On Then Repeat 2 times Set light Off Wait 1 Set light On Wait 1 Else Repeat 2 times Set light On Wait 1 Set light Off Wait 1 We check for the motion sensor sending a Control On message (Not status) then call a disabled program that makes a decision based on the status of the lamp. This second program is essentially what you did but since it is DISABLED, it does not self trigger when the lamp status changes. It will still operate when called by the first program. -Xathros

Blender, Vacuum, anything that makes noise - or - Trigger an IOLinc attached to a Doorbell? -Xathros

Run the event viewer at level 3 and repeat that last button add. Post the log. Maybe Lee will see something. -Xathros

Take the 2411T and the remote you are trying to learn to the PLM and plug it into the same circuit. Try again. -Xathros

In this scenario, I like the first solution better. Low temp detected, adjust the Stat, notify and then delay further action. The goal is to prevent the pipes from freezing. The second solution waits for however long it takes for the sensor bounce to stop + 30 minutes + however long it takes for the attic temp to recover from the increased heating. I think it would be best to act first then wait. Just my personal preference. -Xathros

Probably an Avast update along the way changed the way it was handling the ISY. Glad you got it working. -Xathros

Here is how I would do it: Program: BasementMotion If Control Motion1 is Switched On or Control Motion2 is Switched On or Control Motion3 is Switched On Then Set BasementLight On Wait 5 minutes Set basement Light Off Else This way, the lights will com on with any motion and stay on for 5 minutes after the last motion was detected. Adjust the 5 minute delay to suit your needs. You could add a second program to disable the motion detect program when the lights are manually operated as follows: Program: BasementMotionDisable If ( Control BasementSwitchlinc1 is Switched On or Control Basement Switchlinc2 is Switched On ) And ( Control BasementSwitchlinc1 is Not Switched Off and Control BasementSwitchlinc2 is Not Switched Off ) Then Disable Program BasementMotion Else Enable Program BasementMotion Hope this helps -Xathros

This is certainly not normal. What are you using for Antivirus and Firewall solutions? When you turn on or off lights (at the light) does the status of the light change in the admin console? If not, try disabling your AV/firewall and test. -Xathros

Hi mbrossart- I am assuming this is a V.43 firmware KPL. These newer KPLs are coming with a multicolor LED behind the set button. From the User manual: Error Blink Default = on This setting is adjustable via software or a central controller only. Keypad Dimmer LED blinks red for a few seconds if one or more responders do not acknowledge a message. LED Behavior Keypad has a dual-color green and red LED which momentarily indicates if a button press was successfully communicated to all scene members. LED State Meaning Blinks green once - One or more scene members acknowledge the button press. Blinks red once - One or more scene members did not acknowledge the button press (note: scene members may still have heard the scene command and adjusted their settings) This doesn't explain a constant steady red condition. If this wasn't happening on 2 different KPL's I would have said device failure. Do they operate properly aside from the red glow? I have one of these newer KPL's and don't notice any red glow even when the room is dark. -Xathros

Anytime! Happy to help. -Xathros

Hi Mike- As long as you don't want to track levels of dim, you could use two programs to accomplish this. If Control MotionDetector is Switched On Then Run Blink (If Path) Program Blink: (Disabled) If Status Light is On Then Repeat 2 times Set light Off Wait 1 Set light On Wait 1 Else Repeat 2 times Set light On Wait 1 Set light Off Wait 1 -Xathros EDITED: To reduce the number of programs and provide proper operation. EDITED Again for same reason.

I suspect the problem is switch bounce from the reed switch door sensor causing multiple On commands as the magnet moves past the switch. I bet your event viewer shows multiple DON messages from the sensor when the door opens. Adding a wait should help. Try this: If Control 'Garage Door Sensor' is switched On Then Wait 3 seconds Send Notification to 'Default' content 'Garage Door Opened' Else - No Actions - (To add one, press 'Action') This will filter out the bounces and you should only receive one notification. If you still get multiple, try increasing the wait to 6 seconds but I bet the 3 will resolve it. -Xathros

The 2411T is an IRLinc TX. I just added one of these over the weekend on FW 4.1.3 I don't believe there is any reason for this to fail on 4.1.1 I suspect that you have a comm issue where you are trying to link the 2411T. As mentioned above - reset the 2411T again and move closer to the PLM and try again. If needed, you can use an extension cord to plus the 2411T in closer to the PLM while keeping the device located near the equipment you are trying to control with it. If that works, then you will need to figure out the comm problem in the desired location. You didn't plug it into a surge suppressor did you? If so, you might try plugging the 2411T directly into the wall and try again. Your AV equipment and any surge suppressors should be behind a filterlinc to prevent them from interfering with insteon signals. -Xathros

The Ubi- Welcome to the UDI forums! The ability to operate on the local network is most likely the most important feature to this community. I would test the http request from the Ubi but dont want to send my credentials in the clear outside of my LAN. The ability to have Ubi speak on command is a close second on the priority scale for me. Once again, welcome. I look forward to working with the the Ubi team and getting things working with out automation projects. -Xathros Sent from my iPhone using Tapatalk