lilyoyo1

Do the buttons show up? What about using programs

I was thinking the same thing!!!

I group my timed programs in folders and simply enable the folder during those hours. Helps keep track of stuff and prevents any overlapping of hours

When use use a scene with the Isy, true status is not kept as there is no status with scenes. The Isy assumes the devices turned on. It sounds like you have noise issues. How is communication to those devices if controlled individually? Are all devices in the same area? If not, you could try to break your scene into smaller scenes and turn the scenes on 1 at a time via programs to see if that helps

If you have the pro version, you can turn off write updates to battery operated devices. This will allow you to set-up your scene without have to link each individual device one at a time. If you don't have the pro, another thing you can do is add your responders to your scene and configure them how you want them to respond. Once done, add the controller (the buttons) to each scene. This will link all your responders to the controller at the preconfigured levels

You need to configure your scenes for and controllers (within the scene) with the light level that you want things to turn on to. It's the exact same process like all insteon other devices. Each button will need its own scene

When it comes to lighting, temper your expectations when it comes to zwave. While some do have a few novel (some gimmicky) features, none comes close to being as flexible and configurable as insteon for actual use. It's extremely limiting when it comes to cross linking as well as different lighting triggers the way insteon is.

I don't use them but would recommend making sure you are on the latest firmware when you get started (5.3.1) to ensure the greatest chance at success

That would be my thought too. Also, what is the rating for the lamp? Mfg, model and all could help us research for you

I agree with MrBill. Nothing to reset and the light works normally throughout. By using individual scenes, you can set the specific ramp rates and light level as well

Post your actual programs so we can review. Most likely there's some interference but unless you post your programs we can't say. Also does your firmware and ui match? Is this insteon or zwave

It could be different firmware causing this. One way to find out would be to remove an existing switch and re-add to see if it changes

Right click on device and choose update neighbors

I no longer use kwikset locks so I cannot comment on that lock specifically. When it comes to the 500 board, Ive found it works great when the system is 500 devices vs older gen-though it does work with both. My experience with yale locks has been glitchy on 5.3 and atrocious with 5.3.1 so it wouldnt surprise me if the same held true with other brands.

Not really! If you're in the admin console and you click on your network, you'll see a list of all your devices which you can sort to be in order. Unfortunately, the name you gives something isn't the names that the isy uses. That's there for your benefit in regards to knowing what something is. The isy itself is concerned with the device ID as that is what it uses for communication (trying not to get overly technical) You shouldnt remove it from the isy. Simply disable it and when you're ready to use enable the device. Since it's a plug in, you could also label it what you name it in the ish which would make it easier to find next time.

Well thats not a fair comparison being that your 10 year old car still probably costs a couple of hundred times more than your motion sensor. I would expect it to be able to do more than an old device.....especially since they've had 100+ years to add to it. On a more serious note, upgrading your isy would not give new life or features to an old device that doesnt have those features built in. You would need the new insteon motion sensor which has that ability. You dont have to change the battery every 6 months. In fact, when I used to have the original sensors, I got away with once a year. For rarely used locations, I changed about every 18 months or when 1 died (whichever was sooner).

Your network does matter in regards to where you plug it in. If it's a different network access can be lost (like it was).That has nothing to do with insteon,x10, nor zwave. If you go with zwave, make sure you purchase multiples initially as zwave requires a strong foundation to work properly

No. Unfortunately zwave devices all have different ways of accomplishing this unlike instrument.

You need to upgrade to 5.0.16c Clear your Java cache before and after you upgrade

Firmware and UI? If you arent on the latest firmware, most likely it wont work. I would recommend using at least 5.0.16c then trying. This is especially true if you are still on the 4.0 branch.

That's been discontinued for years. It wouldn't surprise me if the 2 were no longer compatible due to updates to the elk.

This is (adding zwave devices) complicated but you are right. If all devices in a system supports network wide inclusion, you should be able to add devices from their location (assuming all devices are within range). From my experience, this isn't perfect (of course). I still add devices prior to installation in order of closest to farthest. The same with locks. I'll add those after, I've added, devices that I hope they will talk to.

This firmware makes using Yale locks even worse than 5.3. which isnt saying much when compared to 5.0.16. Even after removing the locks and re-adding, there is zero communication. The ISY shows the repeaters connecting to it but no communication at all when it comes to the isy actually seeing the locks.

In addition to what MrBill stated, I use a longer period between messages to lessen the chance of an "on" signal being sent. While the motion may trigger upon movement no message gets sent. This allows the motion sensor to see you but not cause any programs to respond to the motion

I would increase the time in the motion sensor itself for when it seems an on command to lessen the likelihood of an event being sent between motion triggers. One or 2 minutes should be sufficient. Once done you can use MrBill's example above, shortening the duration to suite your needs