lilyoyo1

How is that small thinking? It's cheaper and easier to use a separate device than rip out an entire working system. Would you remodel your whole kitchen because kitchen aide no longer makes your original microwave?

You can still accomplish the same thing with toggle vs non toggle in regards to different light levels. You would just set the lights how you want them in each controller. I never liked the copy feature but understand why people like it. If you have multiple scenes, it's possible to make things faster. Add the responders to the scene first, configure what you want them to do. Then add the controller. The Isy will automatically write everything to the controller the way you set them up. You can also hold the control button down as you click on devices. Then drag and drop to the next scene

That's true. That's why I said i prefer separate scenes for long term flexibility. Today, one might not need the flexibility but tomorrow, that could change. I tend to take the long view approach to things I suspect the fact that he has it in non toggle mode is what's causing his issues. Natively, Non toggle only wants to send specific commands with each button press

I like creating separate scenes for each button vs. using 1 scene as it gives me the most flexibility long term. To start, your keypad buttons should be set to toggle mode. Remove all devices from the scene and set the kpl to toggle mode. Create the additional scenes for each button. Start by adding your responders to each scene. Configure them for the state you want them in ie: A scene: B,c,d,e,f,g all added as responders and off. Light 1,2,3 are on, 50%, and 25% Once done, add the controller button to the scene. Everything will update accordingly in the controller

I forgot to add in my previous post to make sure you have a program that resets your variable to zero when you turn the lights off either manually or remotely

The responders should be set to command and on (whatever percentage you want). The controller shouldn't have any options other than default. If it's giving you command options then you can try it to see if that works. The scene nodes shouldn't be necessary but it depends on what the mfg. says they are for

Scenes are trickier with Zwave. Unless the controller is scene capable, I've found it not to work the way insteon does. This may be what's happening in your case. Did you update the front light controller node as well to tell the other devices what to do? If that doesn't work, you could use the program to trigger the scene itself which would be more efficient. What I'd do is take a play from @matapan advice and use a variable. Trigger the lights on/off with your program (whether you use the app or voice). Add a line to your program that changes the variable to 1 whenever the program runs. There's multiple ways to run your motion program. I separate my off program from my on program. If you do your motion program this way, you could say If motion variable is zero and (motion is switched off and not switched on) Then Wait x minutes and turn scene off

What kind of room is this in? What ways do you control the light?

I'd actually use status as the light could be manually controlled as you say but also via app and voice which wouldn't be captured

While a nodeserver would help, its not the same as the built in IR that the ISY has and depends on what a person is trying to accomplish. Itach devices can actually be added to the ISY pretty easily now without a nodeserver. The hard part is the initial setup and getting them to talk to whatever you want it to. I used to use them with the command fusion app back before most electronics became easily connected.

This will be a little hard since there is no IR port on Polisy.

The good thing is if Polisy ends up supporting Ra3 (it currently supports Ra2), you'd be able to use your existing receptacles as well which would make it a moot point

What's your UI

Unfortunately there is not. I'd start with your board. If you have the 300 board then it doesn't matter the devices. Everything will operate at 300 level. If you have the 500 board, I'd look at when you purchased your devices. Anything you bought in the last few years increases the likelihood of being zwave plus. Zwave doesn't pick and choose based on device series so any older devices will affect your system.

Then why bother asking on here instead of those sites if you're going to argue with the answer. It's already been well established as fact that zwave send signals at the lowest common denominator.

Try using Firefox

As answered many times on these forums it's No. However the amplification could potentially help your system

The portal only shows cloud based nodeservers. You have to log into polisy

Yes and no. Aeotech range extenders do amplify the signal as well so you'll get that benefit. However, it will match whatever the lowest series your devices are

Are you logging in on the portal or your polisy

PG3 is for Polisy only. It'll allow developers to charge for their work

Unfortunately that's how you update parameters

Since we don't know what the device is, we can't say if it's a bug or not. I'd remove the device and upgrade to 5.3.4 (since no one will fix an old firmware). Once upgraded, make sure you clear your Java cache and use the launcher from the 5.3.4 page. Double check to make sure that your firmware and UI matches then re-add the device.

You can always run your isy I'm tandem with polisy so that you have ir control. Harmony hub based remotes can still be easily found as well allowing you to use the Harmony nodeserver to accomplish the same thing

What is the firmware AND UI of your isy? Did you follow the steps to get it added? Click on the nodeserver in the store for directions