lilyoyo1

Ever since they sub contacted their support it's gone downhill tremendously. I feel bad for anyone that has to talk to them.

They make simple devices without slot of options which is why it's like that. They aren't trying to do anything fancy like fibaro or aeotech which also shows in their price point.

You said it's disco'd in their store. Meaning, they are no longer going to be carrying it. They are no longer making anymore plms for the time being but they are not disco'd. There will also be a new version released along with new products but i do not have a date for those at this time. I've attached a list of products they will continue to make and those that are currently on hold until further notice

For the 1000th time, smarthome is not abandoning anyone. We are currently In a situation worldwide where it's hard for many companies to get the silicon chips needed to run their devices (partly why cars lots are low to empty when it comes to new cars). Insteon has decided to focus on specific core devices at this time vs making their full product line and having nothing to sell. If you're going to need a Plm right now, then it wouldn't be wise to split your system as you will be left without one for a while. Either until the new PLM is released or they start making more of the old. I don't have any information on dates so I suspect it'll be a while.

You should post them here just in case someone else falls victim to this device....oops I meant; decides to use this device.

Not everything that shows up in the console is used by your device. That's why I said to test the device and see what changes. Zwave as a protocol supports different command classes and device type. Mfg. will program their devices based off the parameters for a device type. That way, when added to a controller, the controller knows whether it's a dimmer, relay, thermostat etc. That's the extra information that you are seeing. It has nothing to do with the specific device you are using. What the mfg. decides to implement is on them and whether or not they decide to take advantage of what (and how) that device type is capable of. Had Ge decided to take full advantage of the device type, then all the extra stuff would come into play and you would have a more detailed manual for it.

Insteon and zwave is like comparing apples to oranges. The only thing similar is that they're fruit (in this case automation protocols) what it takes to program insteon is not the same as it is for zwave. I don't use that device so I can't give you any details on it. I've seen a couple of people try to use it on here but they weren't too happy with it for multiple reasons If memory serves correct, they had to set dimmer values for the different speeds. Some people on other forums (as well as this one) complained that the status wouldn't update but that could be for an older version. If no one chimes in and Ge's manual doesn't provide anything, you'll probably have to mess around with it to see what different things do. @asbril may have some information for you as he uses a lot of zwave products. If you have to be the trailblazer here, I'd manually control the switch to see what the Isy shows. What happens when you hit the button and the fan is low. Your second tap to make it medium, third tap to turn on high, etc. I suspect you'll need variables and programs to capture those taps in order for the isy to keep proper status of the fan speed when controlled manually. You'll also probably need programs in order to have the ISY control the device the way you would like. Good luck and let us know how it turns out

What steps have you taken to add it? What is the other controller? What's your UI?

While the Isy will be discontinued at some point in the future, that future is not for some time. UDI has already stated (on multiple occasions) that it will continue to be sold once the console is ported to Polisy for those who do not desire all that polisy offers. If you want to hear it directly from the company, a forum post isn't the way to go. For best results reaching out to UDI directly via their support channels would be the proper channels. While they do chime in from time to time, the forums are really about other users providing a helping hand to questions

RTI is dealer only though you may be able to find one on eBay or something. Cooper (Eaton) has been around forever. They make quality devices. I've never used their keypad so I cannot comment on how well it works.

If this is simply a program for Alexa then you do not have to worry about the if statement. If you want the program to pull double duty (ie: also being controlled by a keypad button), them your if statement would include that. Alexa would only run the then and or else statement

Write the program and then add the program Instead of device or scene

If i had a say in it, I'd choose zwave. Its in testing so it's not like a large number will be affected by not being able to restore and it's more important to make sure both zwave and insteon both coexist properly on polisy before trying to swap.... especially since many use both zwave and insteon together. As testing expands, the restore function will matter more since more people would want to partake in testing knowing that both protocols were supported.

There wouldn't be an app for a zwave version since it would require a controller to work via an app. Honeywells website should be able to say whether there is a remote sensor. At it's price point I'd be surprised if there was

Did you even read the guide that comes with the switch? That information is in there. You can pull up the manual for the switch. It gives step by step instructions for what the wires stand for and where they go. Not trying to offend you but if it's hard to understand (wiring isn't for everyone), I would recommend getting an electrician. You can find the manuals on the product webpage under the manuals tab. https://www.smarthome.com/products/switchlinc-dimmer-insteon-2477d-remote-control-dimmer-dual-band-white

Does the switch wired to the light turn on when manually controlled? If the lights aren't turning on at all, the switch is bad, you have it wired incorrectly or the scene is setup incorrectly.

Code requires this already. Wouldn't pass inspection if a permit job. Good advice if he's doing his own wiring though.

I always recommend wiring for dummy switches and then automating. While more work initially, it'll be cheaper in the long run. Since you're already thinking about the future, the likelihood of you selling is greater. Whoever buys the house may not want an automation system. This will either cause a buyer to take off from the cost to get it fixed or cost you to get it fixed prior to selling. As hot as the market is right now, there's no guarantee of that in the future. Put the time and work in today as it'll be cheapest today

It probably is. Popped in and disappeared just as quick.

True but he didn't say anything about his system. If he has the 300 board zwave he wouldn't be able to update to that.

So simple yet no one ever does it.

Double post. I answered on your other post. You should delete this one

You must be on the 5.0 branch to be able to change the motion sensor parameters. Since you did not provide any information about your setup i would recommend that you update to 5.0.16c

Instead of coming on here posting as you have, why not take a moment to actually read. Had you done so, you would've found it already. None of your attitude is needed, warranted, or desired. All the extra is there for a reason