lilyoyo1

I suspect not enough users need the feature enough to warrant adding it. Most likely you'd want to keep your Isy separate from polisy if it's that important vs running everything on a single box

That could be true but as slow as they sold it really didn't matter

Is this truly the older 2842 sensor or newer 2844 sensor

Click on the controller in the scene itself

What does the controller setup look like?

I'm sure it'll improve. How the Isy works with zwave now is infinitely better than earlier firmwares

It'll probably be easier for him if you post your error so he doesn't have to go digging through other threads

I still push buttons but only because I factory reset, test, and add prior to installation. I do wish zwave would come up with a way to add with addresses to so one doesn't have to run around lost install The Nokia line adds the ability to scan a bar code

You're confusing the mesh network communication with a device level capability. The same with insteon, adding a device is different than communicating with a device. For example, your newer 700 series device processors will make your 500 series controller seen faster because they work quicker but that doesn't mean your 500 series is communicating at a faster pace. The devices themselves simply work better.

For the end user it sucks but it was a good business decision. It would take years to sell them. They wrote off more product each year than they actually sold

You're confusing nwi with something different. Nwi is device based so as long as devices support it, then it will work (not all devices support nwi). This is why some people with 500 series devices still can't use nwi. If you were to remove all of your 500 series devices and tried nwi from a distance with your 300 series devices, you'll find it doesn't work A similar thing can be seen with battery powered devices. 500/700 series devices would last longer regardless of what series controller is used simply because improvements that led to it are device based vs controller based.

That is incorrect. Zwave will not use 700 speeds etc. If you have 300 series mixed in. It will use the lowest class for all communication. It does not pick and choose based on path etc. Since you're just starting out, you'd be better served to have all 700 series devices. Leviton has 700 series receptacles. Aeotech has the smart switch 7 which monitors energy use if your dryer uses 110. Keep in mind that range claims is all open air testing which doesn't always translate well once indoors. I've tested PowerG sensors outdoors and have seen them communicate over looking distances only to take them inside and have communication issues 40 feet away. It depends on your environment. Be prepared to invest in your mesh

No there is not. Generally you'll have to look at your model# to see what it is online. Generally anything you buy today will have the information concerning what series it is on the packaging and started online where you buy it from.

Yes they can. Zwave is backwards compatible. With that said, by using 300 series devices, you would not get the full benefits of 500/700 series

Protocol-wise, there's no difference in insteon and Nokia. Technically you can add Nokia devices to the Isy and control them except you won't receive status if manually controlled and a few other things since the Isy doesn't know it's info. The devices themselves are better than insteon in quality and look. They are also designed specifically for led bulbs which makes them better than insteon on that point alone. Who's knows when they'll be released. Even the employees are in the dark

It would help if you gave system details such as firmware and UI. Generally yes, you can mix scenes with insteon and zwave. You just have to configure your devices within the scene and controller to do so. You only need the switch on/off in the scene not the other stuff

My advice is to keep it simple. While it sounds good to set someone up, providing too much information will overwhelm them. You're better off finding someone who can step in to manage the installation when you're unavailable. Everytime I've sold my home, I left the devices but removed all automations except for basic timers such as the outside lights turning on/off. Anything custom was erased. If the new owners wanted custom programming, they could hire me to program for them. I do have people that can step up in my absence to manage my system and other client systems. That's the route you should take. Most people do not process and understand technology the way we do so them trying to maintain and program probably won't happen. Giving them a lot of info only lessens that chance even more. Reality is, it's easier to factory reset everything than to fix someone else's work. Especially for someone not familiar with the Isy. In the time it would take me to learn your programming style, read through all your programs and topology, and understand why you did certain things, I could've just started over which leads to how I handle things. For every client, they get a USB drive with 3 backups on it. The first is what I call a clean slate backup. This has all devices added to the isy with zero links except for true multi-way switches. Each device is renamed and grouped in folders that corresponds to the room that they are located in. The load switch is identified in the system as well as marked on the wall plate (I use Screwless wall plates). The secondary switches are numbered as well in the same manner. The next contains all scenes with no programming done. The last backup contains their final configuration. No matter what i change in the home later on, these 3 remain. This allows them or a future programmer, to factory reset the system and re-add everything cleanly should they choose too at whatever level they decide. The file also contains how to set/change the password (along with current password), what each backup contains, and how to factory reset the system and restore backup's. I do my own sort of topology and glossary of terms. There's a copy of what each keypad looks like and what's connected to each button. It also contains the expected behaviors of each button and switch when turned on/off (ie: Turning Music button on starts wife's playlist. Double tap starts husband's playlist for that room. Off, stops music). This not only provides the client with a resource on how the system works but also allows someone coming behind me to know what is supposed to happen, when, and how. This way, should they need to rebuild things, they can use their own style of programming to accomplish the same thing. It also allows me to know what I was attempting to accomplish should I need to go back years later to add or change something.

eBay

In addition to what @simplextechsaid, the fact that they don't have a level 2 course specific to Ra3 leads me to believe they'll continue the same openness with Ra3. The only thing you really have to be willing to do is pay what it costs.

Old information. That's stuff from the new Nokia line whenever they decide to release it. The PLM had not been produced yet

This is what you fail to realize. Zwave fits your needs not mine. What you want from your system isn't the same as what I want from mine. It's similar to a discussion that I had with @upstatemike about homes. He prefers older while I prefer newer. If we both were in the market at the same time, he'd probably stay in his current home before buying a New home. Ditto for me.

That's what I said originally but @asbril focused on the dumb switch part. I'd use dumb switches and hue bulbs where I needed smarts.

That's like saying you're too rigid against insteon because of the PLM. With their issues right now, it's obviously a wise decision but over the years, you've spent more time and money replacing zwave devices to get where insteon is at than you would've just swapping the PLM. I never told anyone what to do. I specifically stated what i would do. I'm not the only one that feels that way. Back when I first started, I ripped out quite a few zwave systems because the home owner hated the experience. There were a couple that was turned off from automation completely (ditto for insteon).

Depends on where you started from. If someone's motor was acting up for their windows, I guarantee they wished they had manual windows at that moment. Had I never known different I'd probably would feel that way. However, with the things I've experienced, I couldn't allow myself to spend the kind of money it takes to outfit a whole house for a lesser experience. It's just not worth it. We all have the things that we can live with and those we cannot. As I've always said, automation for me is about the complete experience not simply being able to control something.

That's your opinion. It's just not an experience I'd choose to live with. Some people are ok with driving a pinto. I'm not one of them. Luckily for me, I can afford better so that's not an issue