lilyoyo1

This has already been talked about countless times on this thread and many others

Firmware and UI of your isy?

You'd want to do that even with 700 series as zwave doesn't handle multi scenes as well

S2 was designed for perimeter protection devices which is why you'll see Alarm systems widely supporting S2 but other controllers slowly adding it. Since the Isy isn't an alarm system, I can see them not rushing to implement it for that reason alone. For lights- the speed of it (or lack there of) makes S2 a bigger pain than actually using it. By default the Isy does support SO security. If/when support comes for s2, only UDI knows. They have stated the 994 WILL NOT receive an upgrade to the 700 series chip. Polisy will have it so I suspect at that point it will have S2. Due to how zwave works by default, the weakness isn't with installed and configured devices. It's while you're adding a device to your system. This is where S2 comes into play as far as preventing stuff. Sure reading all the details behind it makes it seem like S2 is great but in the field, reality is much different

No bug. In addition to what @MrBillsaid, different insteon devices also have different counts. A lol for example would count for 8 devices just like a dual outlet would be 2.

Unless it's your own personal house that you are selling, nothing should come out of your profit unless you're under charging. The clients should be paying for everything. If your flipping houses then that's a different story. To a certain degree, it will come out of your profit but if you factor that into your material costs from the beginning, that's mitigated as well. For example, when I did standard homes for a local builder, he set aside 10k to include insteon and a couple of other things into every home he built. The customer could add on custom programming during/after the sale should they choose. Because it was part of the plans and build, the sell of the house reflected that without cutting into profit. There's more that goes into it but this is the general gist. By using caseta and insteon as you do, you're actually costing yourself money unknowingly. Time is money. If you're running around manually linking things you've just made less per unit than if you sat at a computer doing everything. The same with insteon. Margin is already thin when it comes to low end consumer devices, so upsell is paramount. We'd install on/off switches and non dimmable bulbs. However the customer could opt for dimmable. In doing so, they'd be paying the switch and bulb cost. Pure profit for minimal effort. Down the road, should they find out the cost of an insteon dimmer, they aren't upset at a huge markup which means they're more likely to refer you to friends as well as continue to use you for more services in the future.

Factory reset the switch and test it. If it does not control other lights, restore it in the Isy and test again. If it controls other lights then it's either part of a scene or program thats causing this to happen

To each their own. Casetas built in device limitations makes it a non starter for me (and other high end installers) as those types of homes typically exceed it's capacity. I also prefer all in one solutions as that means I don't have to worry about new devices not being supported or firmware updates from 1 thing causing an issue with another. RA2 is more than an overpriced Caseta. That's like saying a Maybach is the same as the S600. While close, there are subtle details that makes it a step above. Besides, it doesn't matter. It's a business. It's not your money, it's the clients. You're there to maximize what you make without taking advantage of customers. The markup on Ra2 gives you much greater profit margin than Caseta- unless you're adding a ridiculous markup which only serves to piss off customers and lessen the chance of repeat business and/or referrals. By using Caseta, you're costing yourself money by minimizing what you can earn

High end homes deserve high end systems

Did you update the scene when you made it or just the controllers in the scene? My suspicion is that the scene itself hasn't been updated

The ISY pretty much works with anything now.... Much more than Smartthings. The only products with potential issues are devices that do not follow the protocol

That is true. However if you notice, Smartthings out the box actually only lists specific devices as being supported and you are limited in your configuration options. Unlisted "generic" devices can be added but all (including supported devices) have limited configurable options without slot of work on the back end. The Isy is a controller that shows everything to give full control over your system while Smartthings is basically an app that purposely limits you for the sake of simplicity. There are trade offs to both approaches

Whenever, you update, you should read the directions to avoid potential headaches. One thing that stands out is your Java cache needs to be cleared and you should be using the launcher on the update page

Details about your system such as firmware and UI. Did you recently update your isy

I get what your saying and it would be nice. However, they have no control over zwave at the protocol level. It would take OEMs either supporting what the device class is capable of or removing the unnecessary code. It may potentially be possible if they only supported a few devices. Then they could program around the code limitations however, that would leave users with minimal choices in devices they wish to use.

That's because all of that information is in the zwave device at the firmware level. The mfg of the device just codes not to add support for it

What do you mean look more like insteon does?

Yes. Zwave is a different protocol and has its own board.

Depends on ones perspective. There are lots of companies still in business that UDI doesn't support. One could argue that by focusing on building their own brand outside of the Isy by focusing on new customers, they give themselves the best chance to grow. At one point, the Isy was dependant on insteon. By branching out and supporting zwave and other stuff, the isy has been able to grow and stand on its own. The new line allows insteon to do the same. Grow their own name without the Isy. That way, should UDI choose to not support them, they'll still be ok. They can always come back later. Let's be real for a minute. Half hates insteon and the other half are already entrenched in their systems. While some may try a few devices, you won't find many ripping out their whole system that's been working for them.

The new version will not be out for quite some time. The new line will be built out before that's released

It wouldn't work with insteon but would for zwave if you got the zwave version

The USB plm has always been around. It is not compatible with the Isy. Polisy is able to make use of the USB plm

Looks like you're having issues communicating with that kpl. I'd troubleshoot first to ensure communication is good. Next, I'd add a few seconds delay between each line to give time for the commands to process

Overheating may cause devices to fail but would not cause any signal degradation. Especially since each module would still be repeating the signal. With X10 they would degrade since they do not repeat but the insteon signal itself gets repeated so any potential degradation would be a wash. In addition to that, he said plugged into the same outlet not necessarily stacked on top of each other. I used a plug in module stacked on top of an iolinc as an example of Insteon being in close proximity to one another not causing issues (in addition to switches in the same box). Insteons own test stations often have setups on their carts where modules were either stacked or combined in some way. While anything is possible, I highly doubt proximity would case an issue.

It wouldn't . If that was the case, people would have issues when they put range extenders on top of iolincs or switches side by side in the box