@halpplz - I sat down and took a stab at this lat night - no luck at all. I’m looking for some help with this thing. I can see it added under ozwcp - but I can’t get it to lock or unlock under ozwcp at all. I keep getting something about ERROR: Dropping command, - what’s so annoying is I get the lock to show up in terms of seeing 2 sensors at the top of HASS - Alarm Level and Alarm Type - and I now see a Lock Group on the frontpage of HASS and it says Schlage BE469NXCEN touchscreen Deadbolt Locked and a toggle.
Like I said, I can’t get OZWCP or HASS to lock or unlock the lock.
-
Does the key need to be there under the options.xml file - see here for what I’m asking - See Network Key Section In This Link?
(I have done this by the way…but my options.xml file is not in the path they talk about - it’s in the path specified in my configuration.yaml for zwave) -
I reset the lock last night - tried adding and re-adding several times. Lik eI said - no luck - but if I do it severla times, I get multiple sensors in HASS - ugh. How do you remove zwave devices from HASS (I tried the developer tools - remove_node) - but the little yellow light on the lock on the door would just stay on sometimes. Do you delete the zwcfg_xxx.xml file or something like that?
-
Do I hit add_node_secure in HASS under dev options and then do the programming on the lock or is it the other way around? Like I said - I could see the device in OZWCP but it didn’t seem to want to lock or unlock.
-
How do you lock/unlock the device to test in OZCWP?
I think that’s it for now - thanks for any help!!