lilyoyo1

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.

There's something interfering with the communication during the linking process. I'd make a jumper, and try looking from a different location

Factory reset the keypad and try again. Also make sure your firmware and UI are the same and up to date

Either way could work. Since all of them would need to be at the same level for the light to stay on, should any device change the light would turn off.

Hopefully it works

Under the then, say: Turn lamp on enable Monday program turn lamp off. See if that enables your monday program

Just to make sure I'm understanding properly, It only activates when clicking another program prior to checking it to see if its enabled? Before my next thought; do you have an extra device you can use to test an idea?

To expand on what Techman said, you would need to add every device to your program's if statement. For example: If status kitchen 1 is not 60% And status kitchen 2 is not 60% And status kitchen 3 is not 60% Then set kpl button C off

I assume that you are running the then clause of your program which is why it turns green. I highly doubt it will run. Most likely you will need to create another program which enables those programs in the then clause

It's harder to get a device linked than it is for 2 devices to simply talk to one another. During the linking process, a device on sends out it's information once. When 2 devices are talking, you have 3 chances for a signal to get through. Since your device was already linked it is possible that it could overcome any issues that plagued the first device. It's for that reason (and others), I link all my devices prior to install. This includes zwave. With that said, I would factory reset once more just to ensure proper reset and hook it to your test bench to link.

That message generally means there's a communication issue. The switch itself is most likely fine

Factory reset the device then try.

Even if it was something big like a panel issue, the smaller things could still be part of the problem. It's cheaper to solve the micro problems than trying to fix a major problem that may or may not be there.