simplextech

The Phase Coupler link is great. I was looking at SmartHome but the hard wired one they used to carry is now discontinued? Or maybe just out of stock for a long time?

I have also thought about a NodeServer for Lutron. The Caseta Pro, RA2 Select and RA2 share the same integration interface which makes the development easier to support the primary systems. I've not worked with a QS system but I believe it still shares the same interface.

I see the same trouble with every system.... hmm...

Here are the programs. Why is this turning Off when people are in the Kitchen and moving around? Configuration: MSII - On-Only linked to a KPL 6 button Kitchen.Lights-State - [ID 002B][Parent 0018] If 'Kitchen / Motion Sensor / Kitchen.1 Motion' is switched On Then $Kitchen_Motion_State = 1 Wait 5 minutes $Kitchen_Motion_State = 0 Else - No Actions - (To add one, press 'Action') Kitchen Lights - Off - [ID 0011][Parent 0018] If $Kitchen_Motion_State is 0 Then Wait 5 minutes Set 'Kitchen / KPL6 / Kitchen.KPL6.1' Off Else - No Actions - (To add one, press 'Action') People can be in the Kitchen and moving around and the lights turn off.... ???

If you have the Z-Wave board there's the GE Heavy Duty relay and the Aeotec Heavy Duty relay: https://www.amazon.com/GE-Appliance-Required-Works-SmartThings-14285/dp/B00YTCZZF0/ref=asc_df_B00YTCZZF0/?tag=hyprod-20&linkCode=df0&hvadid=216539147262&hvpos=1o3&hvnetw=g&hvrand=4831132666293138423&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9009165&hvtargid=pla-351536326275&psc=1 https://www.amazon.com/Aeotec-Security-controller-electricity-consumption/dp/B00MBIRF5W I have no experience with either but I have thought of getting the Aeotec for a 240V wall heater... I still might.

I don't know. Let me go open one and find out. EDIT: No jumpers No Options either...

Thanks for the scene clarification. I think UDI needs to remove the "on level" adjustment when a "scene" is selected in the program. It leads to this type of topic Starting to get my head around the Insteon world now a little better. I get it that scenes are binary unless adjusted which I do with another scene actually. I was hoping that since there was that 'on option' in the program window it would maybe do something, but I guess not.

Thanks. That clarifies that. So in a program to adjust a scene I either have to adjust the scene 'on level' or adjust a single device member in the 3/4/5 way setup correct? The only annoyance with this is I then have to adjust each scene member for the LED's to reflect the correct level.

Please tell me what is wrong with this and why it does not work. Hallway.Lights-OverNight - [ID 003A][Parent 001E] If From 10:30:00PM To Sunrise (next day) Then Set 'Hallway / Scene / Hallway 3-Way' On 10% Else - No Actions - (To add one, press 'Action')

I should have clarified I sent the info to UDI support

I sent in a fairly decent diagnostic of the Fibaro to support. I hope support for it will improve. From what I gather UDI is doing some fairly large changes in how they are addressing/handling z-wave devices to make adding support easier/faster. I'm hoping that change comes soon but I expect it will be another firmware release to incorporate the changes.

I'm trying to figure this one out as well... anyone know? I've also submitted a request to SmartHome about the Luminance reading updates. On USB power I can query an MSII and it updates. On Battery it's a hit or miss as in sometimes it will query fine and then sometimes nothing or I get an error. Here's the current response I've received about teh Luminance reporting:

@kclenden thanks for this. It was very much what I was looking for. I do something similar with modifying the scene for a motion sensor. Thanks also for testing against a battery device as that saved me another trip to the forum (even though I sit here a lot) I was trying the scene modification methods and was seeing if I could just change something in the scene to modify the off node the open/close sensor creates in the ISY and no luck there either. It seems I'll have to continue with the use of a program and accept the delay. In timing it's not horrible as it's just to turn on the lights when going out on the deck. But when just stepping out to grab some wood for the fire it's nice for the lights to be on.

Based upon other reading from sites and poking around the open/close there's no option for "On-Only" like the motion sensors. So this leaves me with using a program. Any way to speed this up? I can open the doors and count almost to 2 before the switch is turned on.

I'm going to piggy back on this thread a bit.... I posted another thread about this but maybe @rccoleman you would have some ideas on this or perhaps @Michel Kohanim might have some thoughts. I have a program to turn on light switches when any of a group of doors are opened. Originally I had z-wave open/close sensors and z-wave switches in my previous system. I then changed out the open/close sensors to Insteon and things worked well and about the same speed I would say it was actually faster. Yesterday I changed out the switches to Insteon switches and I swear the speed of the program is now much slower in execution. Is this a speed issue of Insteon? I then created a scene with the door sensors as the controllers and that response is instant which is awesome. But it seems in a scene the lights also go off when the door is closed which is not what I want. So a program is what I have to use but the speed just seems very slow.... thoughts? Ideas?

I had a program that turns on the deck lights when any of the doors open and then turn off the light after 10 minutes. This was with Insteon door sensors and Z-Wave switches. Today I replaced the switches with Insteon switches and the same program seems "slower" at about 1-2 seconds before the lights turn on? Maybe there's a troubleshooting step I can take but I looked at the logs in level 3 and I don't see any retries or anything. So I had the idea of a scene with the door sensors. The On speed is instant which is great. However as soon as the door is closed the lights are out. I was toying around and looking for a way to change the off behavior but I'm not really sure if I can? The goal is to use a scene to turn on the lights when the doors are opened but I don't want the doors closing to turn off the lights. Can this be done with a scene?

In initial playing I saw the change to z-wave association and after update I get no options for what function to associate... hmm... I'll play around more later. I think you're probably right about UDI focusing on getting the basics completed before extending themselves too much into the more advanced z-wave capabilities.

Newer GE may... historically they did not and used a work around from the controller stand point. I would expect newer switches/dimmers to support it now that the patent is expired but there's still lots of other reports from other controllers that use work arounds for it. Of course those may be issues with older end devices being used... I dunno... I realized that I've not setup any z-wave associations with ISY... so I'm going to have to figure that out.. I've been spending my time learning about this new Insteon world and not mucking too much with the z-wave switches I've included.

Log data doesn't tell me which is which... so the controller is the HS switch? The responders are the Jasco/GE? That makes sense as the Jasco/GE DO NOT provide real instant status. There may be something else in play with the associated devices as well. I have some HS switches and a HS WD-200+ so I may play around with them and see what I get as well as pairing with a GE switch and see if they results are different. I may not get to that today though as I have a garage door to repair and weekend chores

That is the way associations work. Device -> Device without any controller involved. However I had thought at least for the HS switches they would still report back their status (on/off/level) even if from association.... interesting.

This is what you will find advertised as "Instant Status" from various z-wave switches/devices. HomeSeer switches have this as do some others. Lutron held a patent for years (expired now) that caused z-wave manufacturers to implement a "work around" that really never worked well. Most older z-wave switches do require polling to update the controller.

The Caseta lineup of products is very entry level. There's the Caseta Pro bridge which has the integration option but again the available devices is very limited. Stepping into the RA2 product family opens up a lot of possibilities but at a much higher entry cost. I think the appeal in general HA is around the Caseta Pro of having the fast lighting and Pico remotes. Lutron just announced a fan controller for the Caseta line which I have limited details on, however to me it's not worth changing out a Fanlinc + KPL for the same functionality. I think now is an interesting turning point with Insteon. With the MSII I think they are trying to evolve into more than just powered devices and remotes.

Yes associations is another topic. However the "gotcha" here is that not all devices support the full capability. All devices support the minimal of 1 association which is the controller. To benefit from this the end devices must also support multiple associations. This is device specific and not all devices support it which is really a downside that you have to be careful about devices and not just assume they are all implementing the full spectrum of z-wave capabilities. All Lutron systems use the same radio technology. So whether it be Caseta Standard (buy at stores, Best buy, Home Depot, Lowe's etc etc) or Caseta Pro which can be integrated with systems or up the spectrum to the RA2 or HomeWorks systems. They are great systems. As an individual you can get "certified" for install/setup of any of the systems. The RA2 classes I think are still free even. Getting up to the HomeWorks (high end) systems costs though. But if you can afford to deploy a system like HomeWorks then the cost of setup/integration would look like pennies on the final bill. I've actually been considering a Polyglot for RA2 compatible systems as I still have my Caseta Pro bridge and the Pico remotes are awesome and dirt cheap compared to Insteon remotes. I'm sure there are. I can say I'm mostly neutral but with a background in Z-Wave (Z-Wave Alliance member) and some exposure to Zigbee which is good but still not prime time for "general home automation" uses as it's still too fragmented even with the ZHA spec. Z-Wave really isn't much better in regards to the fragmentation but it has gotten better and controllers have gotten better at overcoming some of the problems that mostly originate with the devices and the lack of a "true" enforcement of the standards.

@rccoleman, there are benefits and draw backs with z-wave as with any of the protocols commonly used. The "ACK" is part of the protocol and used for validation. One of the z-wave specifications is ensured message delivery and re-transmission on failures. This makes the communications more "robust" but has it's drawbacks in speed. The nature of the communications being serial are also a drawback on speed as there is no "broadcast" mechanism. The "Central Scene" command class has actually been phased out and is not commonly used anymore and most newer devices don't even support it. I can go and double check the z-wave specifications but the last I checked and the talk on the z-wave alliance boards that was the case. Even HomeSeer has mostly phased out the "Central Scene" functionality which many people were using for this type of scenario. I've read of the draw backs of interference/noise with Insteon but at least it's known and there are mitigation steps. With Z-Wave it's unfortunately harder to figure out what the cause could be without expensive tools. A misbehaved z-wave device can wreak havoc on the entire mesh and trying to isolate and find it without the proper tools can be maddening!!! For lighting (personally) I have found Z-wave to be less than stellar for wanting the lights to respond quickly and dim/brighten or fade nicely. I've had Lutron, Z-Wave, Zigbee and now insteon in my home and test environment and as it stands now I'm still in the middle of rolling out more Insteon for comparison. However In my very early testing/comparison of things for lighting I would place Insteon and Lutron on the same playing field. May just be my opinion but I'm coming from a mostly Z-Wave background and I'm liking Insteon more and more each day for lighting and for motion sensors and contact (door/window) sensors. I just replaced all of my door sensors with Insteon because they respond much faster and more reliably than the Z-Wave sensors I had. All in all I think I will ultimately always have a mixed environment but for now I think Insteon will have my lighting and Z-Wave will be mostly plugin devices and energy monitoring devices and some exotic devices only available in z-wave. I think my switches/dimmers will all be converted to Insteon along with the motion sensors controlling the lighting.

Since getting my ISY the first thing I did was update to the 5.0.14Beta and start adding Z-Wave devices. I've had good success with only a few hiccups/issues. Some of my issues are self induced as I'm testing controller shifts and secondary controller functions which many would not be doing from different "other" controllers. With that... so far so good. There are still issues with some multi-sensor devices but so far I haven't noticed any major show stoppers just yet. Actually in my testing I'm finding that I like Insteon a lot more than I originally thought I would so I've bought a bunch of switches and dimmers to replace some of my z-wave stuff.