lilyoyo1

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

It's zwave 0lus with all the features that comes with zwave plus. Some not yet supported. https://www.vesternet.com/what-is-z-wave-plus/

3300 SQ feet with 2 repeaters! Needing to move them closer to Isy! Most likely the lack of repeating devices is your issue

Michel, Out of curiosity, does the new board allow for ota updates or will it in the future?

I'll beta test Michel. Where do I sign up?

Is it showing the event based off the scene itself being triggered or any light being triggered? I ask because it may be capturing the controller doing it's job rather than knowing the scene itself is on. This ties into what Larryllix is saying.

The way you explain things sounds much more complicated than needed. My away buttons and all off buttons accomplish what you are trying to do without going through all that you say. I simply have a program that turns off all the lights when pressed and turns off the backlight on the button a few seconds later. While the button isnt lit up if a light is on, it doesnt matter since it will automatically turn off anything that is on. For smaller things such as my outdoor lights, I do have it setup in the isy to turn the outdoor light button on should any of them be on (floodlights dont count). Scenes is simply a term used to define what you are doing with insteon devices and yes, mine follows what I am doing. For example, some of my buttons are in single device scenes which allow me to control the backlights individually with the ISY. My KPL's are also set up to turn on and off when I move from scene to scene. For example, If I hit my relax button, it will turn off the other buttons on the kpl. If I turn on the can lights it will turn off any of the other buttons that was in use at that time. Scenes also work outside the ISY. For the most part, should my ISY die, I will not lose control over my house. I lose the convenience controls but everything else will work as normal. This is why we have scenes.

From your specific description yes tracking could work. However, for most situations, tracking scene states can prove detrimental to the system. For example, my relax scenes has 2 functions. A single tap sets the room up for my girl while a dbl tap sets it up for me. 2 completely different actions involving the same exact devices. Late night, my motion sensors kick in. Same exact devices but different results. If you dont mind me asking, which controller were you using that had this feature? I've used a lot of different insteon managers and havent seen one with that feature. Depending on what your intended use of this button, there could be other ways to achieve your desired results. There is more than 1 way to skin a cat.

I agree completely. For me, if I walk into the family room and hit the relax button it sets my lights to the preset brightness. If I increase or decrease it a little bit for whatever reason, its still my relax scene. Certain aspects will change things such as turning on the overhead lights (which will then turn off my relax button).

There can be a multitude of scenes involving the same exact devices in a single room let alone the whole house. All of which can be setup in different ways as well as controlled by different devices. Less programming is great for any and everyone. However, ease of use/less work doesn't necessarily mean it's better. In the case of most systems, the use of programs actually gives more capabilities which allows one to dial their system in perfectly.

There are too many variables at play when it comes to devices to ensure everything is kept up properly. If anything, it would require constant polling which would impact system performance. The likelihood of detrimental behavior increases exponentially the larger the install.

That's where the if statements come in. It allows you to change the state of the kpl based on specific conditions you set forth. Due to the nature of scenes, it would be impossible for the Isy to ascertain on its own what a person wants. For example, a room has 3 lights. Turning button "B" on turns on all lights. That would be a scene. However, what if the lights were all turned on individually? That would not be the scene. While the Isy does keep track of everything, it doesn't know what your intentions are unless you tell it what you want to happen hence the "if" statements. Programs is what allows for customizing your scenes.