lilyoyo1

If the synchronize nodes doesn't work then I'd remove and then re-add. I don't know why they disappeared. Maybe the prices of adding another controller erased the links. I've never experienced that.

I dont think the trane can be added as it's a hub by itself. It allows you to add zwave devices and control those. I believe trane has it locked to the nexia line.

You'd be in the same boat with that one as well. The 2441th is still rf only.

All of my rooms have all on/off commands. I found it better to write a program controlling those scenes 1 at a time to achieve all on/off vs. 1 large scene.

I'm with everyone else on using voice control to open/unlock stuff. Why bother! Anyone that I would open the door by voice for already has their own code to my place so they can get in. While I do value convenience and take a risk/reward outlook when it comes to security I feel voice control over access control devices goes to far.

I think you're making a sound decision by going with the ISY. I would focus my technologies on Insteon and zwave. This will allow native control of your devices should something ever happen to your Isy. It's tempting to use a multitude of other devices such as your to link module via network resources but I would limit the use of non native devices that need network resources or polyglot to non critical devices such as your lights strips. UDI is supposed to be coming out with an accessory module with polyglot preconfigured which could save you a lot of work trying to figure things out. I'm not sure when it will be released but I think it's worth waiting for.

Either would work. Personally I'd go with the inlinelinc that way each device is completely independent of one another. Should one go bad, I'm only replacing/reprogramming that one unit vs 2. Minor detail that really doesn't matter. I'm assuming it will also be installed where it can't be seen. If it were visible, I would definitely go with the inlinelinc since I don't like wall warts.

Ask away. We're all here to help each other besides our usual debates. Lol. My sensors are set up to send only On commands. The motion sensor itself doesn't turn them off. I have a simple program written that turns the lights off for me. If control motion is switched off and is not switched on wait 5 minutes turn off.

Youre welcome. My pleasure. Yes you can directly link them to another device. Create a scene and add both devices to the scene with your sensor as a controller. My half bathroom sensors are linked to my insteon switches in that way (Still needs the isy since it's a mixed scene). Since you have all zwave, this will speed up the communication as you take out the middle man. You do have less control over how things operate vs. programs but it's much faster. I do it for my half baths because I don't have windows in them and want the lights on each time someone enters. The other devices are via programs but it's more like a 1-2 second Max before things respond.

If they are linked to your devices via programs then there will be a delay since it goes to the ISY then the ISY talks to the device. If that delay is 3-4 seconds then that would be different. I use the fibaro motion sensors which I love. I recently picked up a couple of the dome motion sensors to play with. I must say, I had low expectations but I think I like them better than the fibaro.

You won't get better performance until everything is replaced. With that said how is your performance lacking right now?

Technically if a device talks directly to the controller, it would have the features. However if any device on the path is not zwave plus then all devices are downgraded for that articular path. I could be interpreting their information wrong but the way I read it, zwave defaults to the lowest firmware of that route to avoid conflicts.

That is correct. Some features will still be available though (those not based on routing). With that said, it's still worth an investment (especially for sensors).

No. Zwave automatically downgrads to the lowest firmware. I'd still get it as some features would still be applicable such as lower battery life, firmware upgrades, and features

The way I do mine is to disable my program when the light is manually turned on and re-enable it when the light is manually turned off. The motion is also auto enabled after midnight

To add upon what Techman was saying; the ISY is unaware of any links made outside of it. This can cause undesirable effects later due to half links (when you move devices around in the ISY). These half links can slow down your system as devices continue to try to talk to other devices that may or may not be there. Once in the Isy, you can link all of your devices together. Personally, I recommend starting with the new 5.0.13 branch so that you can avoid potential headaches later when you update your isy in the future.

I'd factory reset the device and then restore it from the Isy. The non toggle modes should blink to show that the button was pressed. Most likely the buttons that are blinking are responding properly while the others aren't. Me personally, I don't use the non toggle modes. I don't like how they work. I simply create a scene with the devices in the state I want them to be in and then use programs to manipulate the back lighting https://www.insteon.com/support-knowledgebase/2014/9/30/keypad-dimmer-owners-manual

The blinking indicates the action was received. Since the non toggle modes don't change in regards to status it blinks

He read it right. Since he wants both the button and the light to turn on, he has to control the scene. That's good information for him though in regards to individual button control. Insteon devices (by extension the ISY) does not send messages downstream. While it may sound counter intuitive, it's actually a good feature since allows for countless way to configure your house. If devices talked downstream, you would be limited in how much you could do.

Are you controlling the scene of the individual light?

Channel vision used to make a line of smoked plexi-glass doors for media panels. I would check them out.

When you say PLM are you referring to the Insteon PLM? If so that wouldn't help any as it doesn't talk to zwave devices.

The sensor can be put into multiple scenes which is what you are seeing with the different options. (I dont use that sensor anymore nor did I ever have a need for that setup so not sure how ISY expose activates it). With that said, depending on your use, the first option is generally enough for most people. The Open/Closed option allows you to have a scene activate when open is triggered and a completely separate scene activate when closed is triggered. The sensor sends a heartbeat ever 23hrs (give or take) so you shoudnt necessarily see anything in the column until in sends an alert saying its still working.

You have to open it up. The address is in the casing on the board. . Choose link a sensor, type in address, put into linking mode then hit ok

Zwave is rf only. There is no Powerline communication with it