paulbates

John I'm personally ok with that. I keep the app open, and have unique sounds for key alerts and prefer for the notifications to tell me about new events. Paul

Brian Its sounds like in this case the XPNR would be better recommendation because they kill high voltage spikes? That has been my experience with them, they prevented PLMs from being killed by motor noise. Paul

You can have them both running simultaneously, provided you have duplicate ISYs, Zwave Card and PLMs. I would treat it as a slow migration from ISY1, which is V4, to ISY2 which is V5. This how I migrated from HS to ISY. Have ISY1 be V4, set all devices and programs up on it. Set up ISY2 as a bare V5 system, no devices or programs. Slowly, over time, migrate groups of things over to ISY2 V5... lets say all of the switches and programs associated with yard lights.. move them at one time as a group to ISY2. Make sure the yard lights and programs work properly on ISY2. Give it time to validate, then do another group. One day, ISY1 has nothing on it and becomes backup gear, and the ISY2 V5 box actually becomes the new PROD. Paul

Probably that's the problem, the iolinc and GDO noise source are too close to each other, if possible plug the iolinc elsewhere. - You could put an insteon noise filter between the GDO and outlet. - I used these XPNRs for the old furnace motors and low voltage lighting transformers: https://www.amazon.com/X10-Line-Noise-Reducer-XPNR/dp/B0002M5OIY They wire straight across hot and neutral, as close to the noise source as possible... if the GDO has wire nuts in the housing, right there, or inside of the outlet they plug into. I've seen other devices here in the forum called snubbers which I believe are functionally the same thing, but a little smaller. I can vouch for the XPNRs, have a number of them deployed. Its very likely that a lightning strike was the culprit, these filters won't help that. Paul

The path out of V4 to V5 will be "organic" and not necessarily an X on the calendar.. Its about risk appetite, and which functions/devices you have that could be legitimately deployed under 5 now? For instance, I moved to 5 and kept everything as is. Then, I set up a node server and moved 1 of 2 thermostats to it. I ran that for for a while till I was comfortable, and then moved the other thermostat. I then changed programs to use new functionality, a little at at time. Break it into pieces, come up with a plan... Lots of backups. My experience for V4 to V5 was nothing like the HS 2 to 3 upgrade, meaning fairly straight forward with a plan. When your other half questions it, you can blame me Paul

Line noise on the circuit from motors in things like GDOs or power tools used in the garage can cause insteon devices to fail. I've had a similar experience with a PLM that was too close to my furnace's fan motor, I had to put filters on the furnace fans, which stopped it from happening. Paul

I would plan on some testing. I'm pretty sure the EZflora is a triac design for AC. I pretty sure that if it would work, it needs to be AC. I would assume it would work 24VAC or lower, not sure though. Paul

Hi Its less about viability and more about what's important to you. My take is that UDI does not budge on quality, versions take whatever they take to get right, given the price point. FWIW, I was a 10 year user of all 3 versions of HomeSeer and switched fully to the ISY 2 years ago, for the positive reasons of the product, this forum and last but not least, UDIs direct involvement. I've been on V5 for 10 months. Using io_guy's Automation Shack software, I'm getting direct benefit of Node Server technology. There are additional Node Servers I'm looking to take advantage of. Also, UDI has healthy commercial consulting and power industry projects to keep them not only stable, but growing. How many "flash in the pan" HA hub like solutions have come and gone in the last 2 years... or are very shallow from a capability standpoint? Since new builds generally have some financial "wiggle room", I would get 2 ISY 994is, and make production, and the other one the backup and V5 test box. Chances are you can move some functionality to 5 now. Paul

It could be a couple of things. 1) Insteon devices can "lose their way" sometimes after being installed. Right click on the keypad in the admin console and select "Restore device" 2) It could be the keypad is going bad... if you put your ear close is it buzzing loudly, any other anomalous behavior 3) It could be communication problems. I would suggest trying 1) and report on 2) because its quick easy to do. See if 1) addresses it Paul

The topic is fascinating...... in a "let others try it first" kind of way

John Here is a sample of adding substitution to resources: http://forum.universal-devices.com/topic/19499-pushover-syntax/?p=183270 ${var.2.27} -- this means substitute a variable at that point in the network resource. .2. means its one of the state variables in the admin console. .27 means it is state variable ID 27 on the list of state variables. Unfortunately you can't use the variable's name. ${mod.weather.temp.hi.24h} -- this means substitute something from an ISY module. In this case, I have the ISY climate module, and I want the 24 hour hi temp to be displayed at this point. See my sprinkler picture in my post above to see how it looks in the delivered message. Here are the variable substitution docs in the wiki. You should be able to get started with what's posted above. Paul

Scott- easier to show it as an example with the Pushover mobile app/service. Pushover is an alternative to email/text services. The Pushover app/service gives me a report of my house, organized in different views: Pushover main view for my house: Pushover list of all activities in time order: Pushover view of my garage door messages only: Each pushover grouping (they call it an "app") can have multiple message types in it, this is my sprinkler list The downside is that there is a little bit of a learning curve to get it going. Paul

John, here is one. Pick 'Networking' for the action, then "Resource", then the name of the resource you created that you want to use in the program. That will execute the resource at that point... if it has variable or module substitutions, they will have the values they are when you execute the resource. Sprinkler - 4 - Notify on Dry Area Program Complete - [ID 0038][Parent 0012] If 'Yard / Sprinklers / Hot Zones - Manual ISY' Status is Not Running Then Resource 'Pushover Sprinkler Log - Completed dry areas schedule' Else - No Actions - (To add one, press 'Action') Paul

The advantage of Insteon and Zwave thermostats is that they can be integrated directly into the ISY. I had similar experience with the insteon thermostat that Smokegrub did, but I acknowledge that many, like Stu, have great luck with them. I have the Venstar colortouch series (T7900) which can have commands sent to them from the ISY if you have the network module. To read the temp and status you need an external server to run software to poll the thermostat and "push" the status back into the ISY. I use Nodelink for that. I have 2 thermostats in 2 parts of the house that are very different. One is on the first floor in the kitchen, the other is between the first and second floors in the stairwell. I also have an attic fan and insulated dampers whose actions are coordinated with outside temp and HVAC. Finally, humidity control is big factor for me. We have very dry winters and the venstar t7900 can run the humidifier via the fan and keep the house at an even humidity level regardless of when the furnace runs. It also can use the AC lower the humidity when the temp is ok but the humidity is high. That's been used a lot this year as the out door humidity is high. The features of the T7900 and the amount of control I get using nodelink made it more than worth the extra effort to set up a server to run nodelink. Paul

Hi, I would try removing this statement: And Status 'Porch Light' is not on Also, how does the iphone geofece get set? Is that another program, if so please show it as well Paul

Because my LAN has become more complicated over time and has more management requirements, I run my own router for wifi and local services like DHCP, DNS. I install it behind the ISPs modem or router. I shut off wifi and services in the ISPs router, or have them do it, if it exists. That way the ISP's modem / router can be changed with little, if any, local changes. There have been times when I switch ISPs, or times when the ISP forces a technology change of their equipment. Historically the ISPs equipment has had limited features or they don't work well, I like shopping for my own router from a firewall and LAN/WLAN features perspective. This is a good time to consider this approach. Paul

No, thinking scientifically, about the Lunar Effect... as an explanation for what's happened across this forum in the past week or so.

A public service reminder that its not a full moon for another 7 days

This post shows some of the 'how to do it" Also this wiki article with instructions on several messaging platforms I looked at all of them and decided to try pushover first and have stuck with it. I'm very happy with it. I use a combination of ISY alerts, and direct email alerts from things like my alarm system... all in one spot. Paul

To deal with them both getting turned on: write a program to check the status of both being on, and then decide what to do... turn one or both off, send an alert,etc. That works well in testing for me, it never happened on its own, For the day to day operation, tightly control the fan with a handful of scenes and programs. Scenes that turn one switch on can be set to turn the other off. I have one scene tied to keypadlincs buttons, another to a program that turns the scene on, counts 45 mins and turns back off. The low speed is tied to a temp sensor on an inolinc. But you could repeat the first process for high / low speed keypad linc buttons Paul Paul

You're welcome. There is also a program that checks for the status of both of them being on at the same time, which would be a mistake. The program shuts down the high speed and sends an alert. Its a paranoid ALL ON safeguard that's fortunately never run unless being forced tested... (He said, making incantations to the insteon gods) I also would get a closing cover for the switches' electrical box, attics are muy dusty, dirty places. Paul

This post covers the background and links to some specific programming practices that could help http://forum.universal-devices.com/topic/19333-all-my-insteon-lights-and-devices-came-on-what-should-i-do/

I have 2 inline lincs in box, one wired to each hot of the fan. In hindsight, I would go for an on/off switchlincs as it makes for easier testing at the fan. I have a Windland templinc thermometer on an iolinc in the attic for low speed. However since reinsulating the attic, I have it set to read when it hits freezing or less and then have the fan run 10 minutes a day low speed to make sure the attic stays dry. The fan and dampers to the house are controlled by scenes and programs. The scenes turn one switch on and the other off. Its also controlled by keypadlincs around the house and a remotelinc in the bedroom. One button is on / off, the other it on, and then turn itself back off after 45 mins. Paul

The 24vac 20va is a North American irrigation system standard as Brian pointed out. If those 2 wires contacted when the one pulled out, it could have blown the transformer. It seems odd that its light was still on if that was the case.

To keep riding the OCD express , one issue might be the transformers and sprinkler system wires hanging down from the bottom pulled the leads out of the ezflora. I mount each bundled wire package with a strap and put a little bit of a bend in each individual wire so there is a slight pressure into the ezflora, so jostling of the box doesn't cause what appears to have happened here Paul