lilyoyo1

Thanks for your help Michel. Looks like we have another snow storm coming Friday so I'll reload the backup then. I went ahead and ran all the commands though. Time to head back to Cali for the winter. Im over our weather after this week

Sorry for the delay Michel, Here's the info. uname -a: FreeBSD polisy 13.0-RELEASE-p6 FreeBSD 13.0-RELEASE-p6 #16 releng/13.0-n244774-b0c8bc5d9cd: Wed Jan 12 18:39:31 UTC 2022 ec2-user@bsdev.isy.io:/usr/obj/usr/src/amd64.amd64/sys/POLISY amd64 pkg info udx: 2.5.3_27 Freedsb version 1300139 pkg info isy: 5.3.0_19

See zwave tips and tricks at the top of this sub-forum

Thanks Michel. I'll check that when I get back to the house

Front end version and Version:2.2.9-5 & 2.2.13 ISY on polisy version 5.3 @Michel KohanimFinally got around to setting up my backup Polisy to try out the Insteon import abilities with the 2448A7 adapter. The experience was terrible to say the least. Everything imported just fine except none of the devices will talk to the ISY. They show as if connected but no status from any of the devices. Trying to restore does not work nor does writing updates to devices. Polisy goes through the motion like its working but nothing comes of it. Unsure if it was the usb adapter or not (it shows the adapter being connected with the proper insteon id), I attempted to factory reset so I could try with a PLM. Polisy does not factory reset. Doesnt even do the normal tunes that I get with my other Polisy. Ive held the button in for 3 minutes and only 2 of the lights blink. With the ISY finder open, it still shows polisy as connected (doesnt disappear the way the 994 does)

For once I agree. The fact that the avg. consumer doesnt even know about matter speaks volumes as well.

Unfortunately their manual doesn't give much information outside of the limited parameters they allow. Post the options that your switch has under command

What device is it

I'd go with option 3 as that's best for future proofing. If you can't get a plm for insteon that means X10 dies with it

Do you have other zwave devices? How far is the lock from your isy

Which lock do you have

I apologize. When you stated you were selling your insteon devices and transitioning to lutron, i mistakenly took it as you were pulling things out and installing lutron not selling unused devices. Now that statement is completely clear.

It does "sound" like the best approach. The only issue with it is natively, the device wants to send the "on" command to all devices linked to it (which sounds like part of the issue). With it not working, maybe another approach would be better. Regardless of future needs (my intention was to explain my process for better understanding), Toggle still allows him to accomplish the same thing. The only difference would be not needing a separate off for the button. Since that's the path he's chosen, everything would still work the same. Turning A on would set that scene. Turning any other button on would turn off the A button allowing him to hit that button again to start the scene as normal. His off button could still be non toggle off if he wanted it to be since it serves 1 function.

I wouldn't grapple to hard. I'd have a plan for future issues but if everything is working now, why spending thousands over 50 bucks

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.