@nathancu
Thanks any thing you can learn may be of help. @Kianoosh_Karami
Thank you for chiming in on this discussion. It is good to know folks from ST are aware of the issues and interested.
I’m wondering if you can look into an IDE option that would give users control of if using S2 or S0 for particular device. In that way we could preserve compatibility with these older devices.
In my case I have used the RFWC5 at certain locations where wiring 3 way switches would not be economical. I used the direct scenes and associations because they will still work without internet or even a hub. If I ever sell my house or the hub were gone the RFWC5 controllers would still function. I would hate to loose that advantage for these devices in my home.
I’m hoping to update the DH for the new app next winter. I’ll have to do some research one how and what to do. Hopefully the commands for reading and setting the indicators will still be able to work. With those the hub/webcore can keep the status of the button indicators in sync with the state of the devices being controlled. So when I tell google to turn on the dining room light. The indicator on the RFWC5 also lights up and it can be used to turn the light off as you would expect. Otherwise a user needs to double pump the button.
Thanks everyone for your input here, greatly appreciated. Based on @erocm1231 (Eric’s) suggestion, i was able to add my first 5x zooz switches without any issue using the “Scan Nearby” button” and they all read as " ZWAVE_LEGACY_NON_SECURE". devices. Then i configured them with one of my cooper keypad, guess what??? it worked, Yes i really worked like before, including all the features using @sainsworth Scott’s custom DH. I’m so happy and you all have taken my stress away. i’m very excited to add my remaining zooz’s and cooper keypads… now i can sleep and dream in peace
The 700 series z-wave devices all require S2 security, security it is no longer “optional”. I would expect that in the future that it will be harder to disable.
The primary z-wave controller dictates the security, so if you want to force the issue have the ST be a secondary.
At the moment I would say this is entirely up to the devices manufacturers. I have scene devices that once joined via S2 reject any message not sent via S2 and I have seen devices which accept any message once joined to the network.
Fibaro has devices that handle secure messages based on configuration options.
I cannot remember what the z-wave specification says with regards to this being a “should” vs a “shall”, but device manufactures are not uniform in this at the moment.
Happy Friday, hope all is well. just a quick question, since the classis app has been disabled forever, what are our options to program a new/replace an old/assign new device to current setup with cooper KP?
Hoping for a solution and your expert guidance in advance if i need to add/remove/replace any of my kp or switch; since the classis app no longer available.
So what will need to happen is, someone will have to use the Custom Capability and Custom Presentation features of the new platform to build them into the device handler. That featureset is currently in beta, and most developers working with it are having issues. As soon asnits stabke im sure it wont be too difficult to create some kind of LED capability and presentation to make the UI work again. Once that hapoens (and makes the device no longer show as offline) you’ll be able to get back into the settings… Which is what we need in the first place. So hope not lost. Just needs some work thay relies on other work.
thanks for the reply Nathan, glad to here that the team is working on it. Lets hope for the best and keep our fingers crossed. Really hoping for the fix to come out sooner than later.
Well. That’s a good question. I’m not sure what works and doesn’t work in the classic app anymore.
I hope to spend sometime this winter updating the DH for the new app. However, I’m not even sure the new app will accommodate the need functionality. We will see.
Anyone with experience programming for the new app that wants to take a whack at it, should feel free to take it up.
Ive been looking at it Scott, im running a few experiments today and will let you know. Might he able to make it at least operational - not pretty with a few tweaks.
Based on the following report, it was working with smartlighting in the new app. But I’m not sure of the details. ( I know you had some communication with that poster as well.)
@JDRoberts functionality wise it’s fine. The problem is right now, the newapp doesn’t understand the DTH to the point it shows offline. You cant open details view on offline devices so therefore you cant even edit the device settings.
Spent some time looking at this tonight to see if just adding in a VID or a ocfDeviceType would at least make the DTH accessible. I didnt want to hack up the working DTH too much so I created one new - from capabilities (never done it that way - what the heck…) I needed to plant in MFR, Device etc. for fingerprinting - sure OK.
It seems to associate each button back to the hub for central scene control and LOOKS like it has all the right stuff for new app. I can’t test it tonight because it also looks like it wipes out the device config and replaces with its its own… but if someone’s feeling particularly fiesty…
I switched over to it (The Eaton controller DTH) about an hour ago. It does exactly what I describe above. It also presents as one main switch and 4 child switches with independent on/off commands… Looks like the buttons are each presented to both automations as well as SmartLighting. It took me about 15 minutes to switch over to the new DTH and update all my automations. (Still haven’t been able to test if the SmartLighting actions are local)
like before, including all the features using 