Ltek

I redid everything again... its clear there is a bug or something going on. Again. I've done this with 2 dimmers without issue, though have not tried it in a long time. Maybe I should test building a new 2 dimmer scene and see what happens. Here's the bugs I've found... 1. when changing the scene, I select 'Apply Changes to all devices' -- it does not copy any of the attributes to any device. If I select each device separately, then click 'Copy Scene Attributes' -- it will copy the presets correctly 2. Even when ALL devices are set as Responder and Controller (and I verified this on each individual device), controlling one dimmer does NOTHING on the other dimmers, nada, zilch.

They are all controllers.

I have several 2 Dimmer scenes where things work as expected. I manually change one dimmer, it changes the other to correspond. I've been struggling with a 4 Dimmer scene and have re-built is several times and tried manually setting presets, and using ISY... nothing works proper. When I look at the individual dimmers in the ISY menu (not inside the scene) they pre-sets were not set by the Scene, they wee default. So I manually set each one to the same settings 60/2.0sec. Even after that, changing one dimmer has no effect on the other dimmers. See attached screenshot where turning on one dimmer (any dimmer) using the On command does not obey the pre-set dim or ramp rate, but none of the other switches obey the switch that was used to turn it on. The only time it obeys the levels is when I use the Scene itself, to control all 4 dimmers. When I look at the ISY Error Log, I see the commands, but no errors. When I run a scene test I see 3 of the 4 dimmers show "Failed"? But no info why? Help please

Guys, I have an old 2413S v 1.B that doesn't power up. Which cap is most likely died on mine? At home I have 10uF 50v (enough to replace all the 10uF caps) and also have 100uF 25v but not any 6.8uF caps and no caps above 50v. What I gathered, here's the list of the existing caps... C3 6.8uF 250v C11 100uF 25v C13 10uF 35v C7 10uF 35v C8 10uF 16v C2 10uF 16v C5 10uF 16v thx!

Light fixtures are 2" Nicor Model # DGD211205KRDWH ... https://www.homedepot.com/p/NICOR-2-in-White-5000K-Remodel-IC-Rated-Recessed-Integrated-LED-Gimbal-Downlight-Kit-DGD211205KRDWH/308635390 The 6 fixture circuit works fine with the Insteon dimmers. I suspect Insteon dimmers require a min load and the Insteon support doesnt know. If others have gotten it to work on low-loads, it could be luck, or maybe the LED driver (control circuit) that is designed in a way to add more load. I'm going to add an incandescent light and then another LED or 2 to see when it starts to work.

Issue:Circuit with FOUR (4) Ceiling 5w LED Lights (all new, same brand) will not light up. BUT... Circuit with SIX (6) of the same all new lights, works fine.Tried 2 different Insteon Dimmers (77D & 76D) on both circuits, same results. Dimmer powers up, communicates with ISY just fine and shows the dim status on front as expectedCalled Insteon Support, they had no clue.Maybe the minimum draw is not being met?Would adding a dummy load resistor fix the issue?thx for your help!

A little bit offensive. Analogy: I want to marry someone with your head but not with your body. This was directed at PurdueGuy who uses Vera + ISY... just like I do. And your analogy is pretty accurate in this case. This is a fact of life... and it is normal. none of this makes UDI or ISY 'bad'. there is always room for improvement in any product and all products are better at some things then their competition, and vice versa. If ISY is perfect for 'you', fantastic. If ISY or any product is perfect (in comparison to competition) for most people, like iPhone in smartphone market - for a long time it had a commanding market share. Umm, Ltek, have you even looked at ISY's out of the box (i.e. native/free) HTML/AJAX UI? It's a little disconcerting to note that not enough research has been done before making assertions that are simply not true. For your reference: http://wiki.universal-devices.com/index ... ser_Screen ... under Programs. I looked at the HTML/AJAX UI... no admin is possible, only end-user functions. Clicking on Admin Console opens Java run time - thus, not mobile compatible. PC era is over, mobile devices (smartphone, tablet) now rule and as the market is showing, these devices easily out sell PCs. Take a look at the Maraschino Project (http://www.maraschinoproject.com). It is a module style architecture. I'd use this as an example of what would bring the ISY UI into a modern UI. Even if UDI did not do it all themselves but provided the framework, I'm sure others - including myself - would write modules for it. IDC device sales estimates for 2013... tablets ~ 227M PC/laptops ~310M smartphone ~1B 2013 Q4 tablets outsold desktop and laptop PCs combined. IDC predicts: 1- 87% Of ALL Connected Devices Sales By 2017 Will Be Tablets And Smartphones 2- tablet sales ALONE will surpass PCs on an annual basis by 2015, maybe in 2014. Writing is on the wall... why not convert to Java UI to a universal, HTML5, and be done with it? Support 1 interface across all platforms. This also opens up tons of opportunities for users to write modules for it. It is clear by the projects on the forum, users are not content with the native UI and are trying to roll-their-own. you misunderstand... I'm saying there is nothing wrong with 3rd party mobile apps... filing small 'gaps' in core ISY code/functionality is not "fixed" by purchasing a $20 full mobile app. Imagine your bicycle tire is flat. Will it still roll, yes kinda. Will it be difficult and tedious, yes definitely. Is it easy or a good leave it in that condition, definitely not. so you ask the bike store to fill it with air - but they, instead of simply filling the tube with air, tell you to buy a whole new tire for $20. You explain all it needs is air, but they tell you that the only fix is to buy something, they will provide no air. While it is true I could use the native web UI to navigate to the Program and use Run Then & Run Else - it does not solve the problem The issue is there is no easy & user-friendly way to accomplish this. While many may be content with one-off ways to do things and may never need anyone but themselves to use it... for myself, and my customers, this is not the case. We need to have non-technical user-friendly ways to do things that anyone in the family/guests/etc can use. This means we cannot put up instructions on how to navigate 3 levels and push some obscure button called "Run Else" UI needs to be simple like... Vacation mode ON / OFF Secure mode ON / OFF Stay mode ON / OFF ... this only one of the simple, but valuable, uses for Virtual Devices. AND this would translate directly into being usable in 3rd party Mobile apps. You could create a control panel for home guests, family, etc. It seems that maybe no one here does anything this complete & polished with but it is just the way I work and do things - both for myself and as a consultant. ... MOST home automation controllers include Virtual Devices to provide this, and other, functionality. never apologize for your opinion or your interpretation - everyone looks at things and uses differently. I hope everyone on this thread realizes this is not an attack on ISY or the people here. I see a ton of potential for my personal use and consulting business but I'm finding too many roadblocks right now to make it possible. Most (not the web UI thing) are small features that can be added to ISY's core while making a big difference in use cases, usage, and functionality/flexibility in ISY. Virtual Devices is only 1 of several things I see gaps in. Some look like they may be addressed in v5, others seems like they are not even on the roadmap - this is the concern.

Love to know if there are plans to add this in the near future... e.g. in the next few months when v5 comes out. This seems like a no-brainer to have and that a lot of people would use for complex 'Programs'?

Is this possible? I'd like to use this date/time to set timers for events. I saw a method posted in the Wiki using variables and such but that is overly complicated vs simply using a -+ based on the Last Changed value. Example: If Light is not OFF and NoMotion = 0 Then Wait NoMotion 'Last Changed' + 120 seconds Set Light to OFF This is simply one example using Lights & Motion -other more complicated ones include more devices. And, I do not want to link devices directly so I want to use the ISY's program logic for everything. thx

Larry, I don't have a ton of time to work on this with you but I can tell you Home Occupancy has 1M ways to do it no matter what system. I've done things like this and much more complex even with Homeseer, Vera, and other systems. For your case it actually look like 3 simple Programs ... Condition: house was occupied (e.g. Motion detected) -> Action: run the furnace fan more often Condition: When not home (no motion detected after # min AND temp < XYZ AND whatever OR whatnot ) -> Action: run it much less Condition: If the furnace fan runs from a thermostat heat call -> Action: reset the timer and, many examples are in VBscript, Jscript, java, C#, VB, etc since Homeseer can use almost any language that runs on Windows. there are tons of threads on Homeseer's forum over the years talking about home occupancy... happy reading

@PurdueGuy I'm with you, I'm tired of Vera's lack of conditionals. I dug into PLEG - it is very powerful and I have some complex security/occupancy based upon it but there are quirks I have spent hours working out - and frankly tired of it. Here's what we need: Vera hardware + ISY's conditional logic and general layout / methodology + and Vera's plugins/apps (AuthomationHD, dataMine, etc) I'll ping you offline and share some of my collected & documented thoughts on ISY. @oberkc I already listed two apps that have this and there are about 6-7 more a quick web search would provide you. If you were a power user and/or used other HA apps, or have mufti-faceted HA solutions, this would be pretty obvious. Buying devices or apps to fill a very basic gap like this is not desirable not is a 'solution' - for more complex things, like a Mobile UI, sure maybe but I don't like Mobilinc for a few reasons - and something this simple should not require a $20 "Fix" anyway. Bottom line - dead simple use case... using an ISY 'native method' ... try to turn on Vacation mode (to enable your Folder conditions) using ONLY a push of ONE BUTTON. Lets say, on a web page from any device and where in the world -- that SUPER SIMPLE thing is not possible. admin & dashboard requires Java... mobile devices do not use Java and I don'w want to install Java on every computer I might use. AND there is still no 'one button' way even with the Java apps. ... this is simple ON / OFF ... that is all. I'm moving off this topic for now at least. I have too much to do.

Most HA apps do not have ELSE. The flow of most HA apps is... Trigger / Conditions -> Actions aka IF -> THEN ... While it is a nice thing to have for the 10% of the time it will be used - the same exact thing can be accomplished using another If/Then. What kept me away from Homeseer, after my long time usage through 2.x, was the dropping of support for Insteon and the lackluster Zwave support - of course, this was like 4 years ago. I then moved to mControl - while the app as decent (though basic) and worked well with Insteon and Zwave - general support / bug fixes were non-existant. Homeseer only supports Zwave natively but the logic is robust and the plugins are numerous, and community is the most active I've ever seen. Homeseer users us ISY to provide Insteon support... but they seem to use Homeseer as the main logic hub.

Guys, I admire your enthusiasm for ISY but you both actually used non-ISY applications and/or a 3rd party devices (Vera) as a stop-gap / work-around for something that simply should already exist in ISY - and does in any other app/device priced in the range of the ISY. It should simply be there. Just because you don't personally see utility in having it or have developed complex or costly workarounds (buying MobiLinc or Vera or XYZ) does not mean that there is not a lot of value for users. If 70-80% of HA application/devices have a feature then there is a large user demand or adoption for that feature. If this user base is filled with either super-basic users and/or highly advanced coders then maybe there is not the need... but the mid-level power users, which frequent the Homeseer, Elves, etc of the world find this feature valuable. btw, this is only 1 of many gaps I see - others are much more important too. I emailed Michel, I hope he takes it as constructive and not that I dislike ISY. I think ISY is pretty good but in its current state I cannot use it as central to my system and I will need to look at other devices or move back to a PC app.

oberkc, I love that you are interested. I understand your logic. While I cannot spell out every use case, I actually did explain in my previous post the general use/concept. Here's one example I use myself in every system (~5 different ones used daily - not at the same time, usually - over the past 15 years)... Simple and common case, and multiple uses for the same concept... "house mode"... Vacation, Away, Home, Guests, etc. These can be a combination of lighting, security devices, Programs (aka Scenes in most of the HA world), etc. - How do you enable or disable these modes? - What if you don't want to need to be physically near your KPL (or don't use them like myself)? - What if you want to be able to easily turn on/off via your Android/iOS device or PC... are you going to log into your Admin UI & edit a variable? - What if a 3rd party solution (web UI, application, etc) needs an easy way to represent or track or set the mode? VirtDevice is dead simple, variable takes programming. They can also be used to track states (just like variables do) but much simpler, and easily visual ways to do so. In Vera we have a Virtual Device that is actually just like a KPL... multiple buttons in one device. You can configure 'sets' to be used like radio buttons... this is VERY cool and useful for setting modes. I have seen NOTHING even close to this in ISY.

And how is this different than using a variable, or another program, to respresent some "virtual" status? So, you are not arguing for a new capability, but, rather, easier use and better integration with the rest of the world. OK It is the same and also very different... Here's what I typed up for my email: Virtual Devices are a common analog in Home Automation - almost all robust HA apps I've used in the past 15 years has this concept. In the app they act like but are not linked to a physical device... so they are on/off, some % level, etc... just like a physical device would have. Useful for linking to Scenes/Programs/Scripts via a UI - for example, if you are going on / returning from Vacation, etc. Quick and easy way to hold values without needing to add the complexity of variables - they are much easier to set, use, see visually, etc. They are also easier to represent when integrating with 3rd party (non-ISY) apps and devices Tons of utility for even basic of users. I'm surprised the ISY is 5-6 years old and several revisions in and still does not have this.