paulbates

My recollection is that the little triangle option for variables showed up in V5... been a while though. Definitely do not attempt remotely. I would suggest waiting till the first part of the weekend or when you have a couple of day period free to make sure nothing breaks (even though that's unlikely). My system has become "production" over the years and I can't risk the phone calls at work if something were to happen. Paul

Eric Its been good, I've been on it almost 4 years (I started on an original alpha). Some if it depends on your technology mix. I was insteon only and don't do a lot of direct control with scenes. I've observed that programs that control scenes and some z-wave devices can take a little more effort to migrate. The biggest thing is backups... start with a clean backup of your current V4 setup before you attempt to migrate. Then once you migrate, don't start new programs (like the above) even though its tempting. Give everything at least a few days to make sure its working and all programs have run. Then once it looks like you migrated what you had successfully, move on to updating programs. The reason is, any changes you make to your ISY on V5 can not be backwards migrated to V4, if you were to decide you didn't like V5. However most people who have migrated to V5 have been good with it and moved on. Paul

Eric Which version of ISY Firmware family do you have, V5 or V4? I think some of the features that the other members are mentioning may be limited to to V5 Paul

There's a little bit of a learning curve, but another option is a notification service like pushover. The assoicated apps let you file notifications in folders you define ... security, hvac, irrigation, etc. Normally notifications are almost instant, the longest is <10 seconds that I can observe. It saves clogging up your email and texts as well. Once you have the basic Network Resource setup, its a copy/paste + new text to make a new one, and replace a line in the ISY program. Others here got me started on pushover and I'm very happy with it. Paul

Ok. The device looks ok and it doesn't make sense that the program would switch query back and forth with status. The only other option I can think of is disabling the program, and completely recreating it, eg... it sounds like something is wrong with the content of the program within the ISY. If that works, delete the original, disabled program. I see what you're doing with the device status, by running a separate program, it will ensure that the delay and off are run.

Is the device Insteon, Z-wave or ? Does the switch seem to function correctly when you turn it on and off from the admin console? What happens if you query t a few times from the admin console (leaving 3 - 5 seconds between retries)? It could be a device or communications problem. Edit: Turn on the event viewer when trying the on/off and query above (Tools/Diagnostics/Event viewer... set to level 3 device communications)... any errors? Post results here. Also, while you should figure out what's going on, you can probably get rid of that statement. Since the sensor and program could retrigger while the light is on already from a previous run of the program, its not clear that the statement is affecting how the program performs.

Yes, but historically its known for reliability problems like you are seeing. That's why the suggestion is to move to forward through your gmail account. One of the things you have to do with your gmail is go to the account and set it for "allow less secure apps" or it won't allow the ISY to proxy through it. I don't know if this was suggested above or not, but this is how I used notifications through my gmail account and I had to set it Paul

Ok great. Another thing is making sure that the "Use Default" box on the SMTP settings dialouge got unchecked. Paul

After you deleted the line, do you press "Save Changes" on the left before re-adding it? I would try that.... and press "Save Changes" again after re-adding it. Paul

The launcher matches the UI to the firmware version. I agree that it seems odd that if you are 4.7.0 the ac is a different version. But my suggestion is to follow Michel's directions as written... one of the goals should be to getting to the latest FW. Paul

Ok. One of Michel's steps was to update the firmware to the latest 4.7.3 after installing the launcher (with the UD icon) and making a backup of the ISY. Paul

Your firmware is 4.7.3 and admin console is 4.6.2? I would close the admin console, clear java cache and run the launcher again Paul

When you see your ISY come up in the finder, are you getting a choice between launching the admin console or dashboard? Paul

My suggestion is to open a ticket with this information and UDI will work something out with you that you'll be happy with Paul

Hi My suggestion is that you post this in the mobilinc section of the forum so that Wes (InsteonNut) will see it. There are some additional questions to answer too: which version of moblinc (X), and how you are using your geofence: which portal (ISY or mobilinc) you're using (if any), was it working previously and then stopped? is the ISY varable a state variable?

My house came with that old rainbird work box. Amazingly big... you could stuff a body in there once you get rid of the old controller parts.

Mark Same on time of day. I've been doing 3am as well for perennial rye for 10 or more years. Same on water cost as well... ours is insanely expensive. HA irrigation paid for itself, now its paying for the rest. I think when you say weather module, did you add the irrigation module on top of that as well? The irrigation module does the evapotranspiration calcs to say if watering is needed. Paul

Insteon devices can handle outside temps typically mine see -20 to +105. Find a decent work box like @bleepblorp suggests, that you can get an outlet inside of while maintaining electrical code for the outlex. I would suggest buying terminal strips too for the zone wire. Wire from the ez to the terminals on one side, and out to the yard on the other. Here's an example of the terminal part, but I had 3 13wire bundles (on the right side). You'd only have 1 bundle of 8, but would need to add an outlet and with room to plug in the ez. Its a carlon box from home depot.

Great Ken, nice job on the programs. I had 2 ezfloras I wrote programs for a few years and they were more complicated than yours without being more effective, I like these. I get what you mean by "fail safing". I've experimented with my current controller and "over did" my water savings approach... I've saved water, but a few brown spots this summer because I was too agressive this year... and the city replaced sidewalk and destroyed a few zones for a month I've not looked at weather controllers or their nodeservers but they are interesting. I have a hydreon rain sensor connected to an iolinc that I've used for 5 years, and I can pick up actual outdoor temp from a sensor for my ventstar thermostat. All other weather / light for my ISY programs comes from the climate module like you're doing Paul

Nice / simple / logical. Accounting for climate can save a lot of water and that's where automation comes into its own vs older standard sprinkler controllers that don't always get replaced. Those are typically set for worst case summer heat. A couple of small things to think about: I'm pretty sure that 'Climate 24 hour rain' is a look ahead, not behind. But You could encorprate both history and forecast..in your If: 'total rain today' (since you run @ 10pm), or '24 h rain' forecast (maybe more than .2... like maybe .5 or higher). That way you don't water when it did rain, or when its likely to rain.. but beyond your run time. If you are using an ezrain/flora controller: only one zone at a time will run. If zone 1 is running, and you start zone 2, ... Zone 1 will automatically shut off, you don't have to turn it off. Obviosly the last one you do. IIRC, I think shutting any one valve off shuts them all off simultaneously. Easy to test. Thanks for sharing. Paul

Thanks for sharing. A suggestion to make it easier to view for forum members is to do either one of the following: right click on each program name in the list, and pick 'copy to clipboard' on the bottom of the presented list... then paste the copied text for each program in a forum message window here.. one at a time.... or... .. use the windows snipping tool or <windows key> <shift> <S> to capture an image of each one and paste in a window here. Then write about the purpose of each program on top of each one. The format provided is ISY xml format, requireing the forum members to load your program in to their ISYs to see them. Thanks Paul

Let's start with what you mean by data, I assume its tracking device , variable and program actions? If yes, there is ISY Logger in the Nodelink Nodeserver. Its a separate Nodeserver App, eg not Polyglot, and the ISY Logger can be installed as part if it. With ISY Logger, you can define the devices, variables and programs you want tracked and it can Show them on its web page log window Save to a file Send to a unix syslog facility (along with other Nodelink messages) Its been a while since I used it, at one point programs were logged by their number not name. You'll need to set it up, experiment and see if it meets what you are trying to accomplish This is information on setting up nodelink which has 20 different devices in it including ISY Logger. Its pretty simple to use. You can select programs, variables and devices to track. You don't want to have more than you need as its subcribing to the ISY and could affect performance. Below is the setup page with a Program, Device and Variable example. Paul

So, I'll add one more to my list. The page for the GE AC units I found said it works with IFTTT. I believe moblinc X works with IFTTT, as does the ISY portal. @InsteonNut - I've wandered outside of what I know. Can you respond with what the possibilities are in this case? Paul

No/Maybe. Mobilinc can control devices and programs that are defined in the ISY. Here are exceptions If there are public definitions of an API (application programming interface) for the AC, and ISY Network Resources could control it, then you could define network resources and write ISY programs to call the network resouces and mobilinc could control those programs AFAIK, Mobilinc (as well as the other ISY mobile apps) can not control devices defined as Nodeserver Node ... yet Paul

Is it a new scene? if so, did you "discover devices" after setting it up? If neither of the above is the case, try removing it from alexa, readding / discovering Paul