Kwikset 912

valharick · January 26, 2019, 8:55pm

I’m having a similar issue as posted by dadof3and3 - “Entity not available:lock.front_door_lock_locked”
My Network key is setup and working correctly and I am showing battery status, however the lock status is Unknown.
I can lock and unlock it with no problems - any thoughts on what I might have overlooked?

firstof9 · January 26, 2019, 10:03pm

Did you rename your lock to lock.front_door_lock_locked ?

If not go to the <> menu and edit the name:

valharick · January 26, 2019, 10:55pm

I copied the code from earlier in this post (Kwikset 912) as a first step into figuring out HA - I’ve got zero experience with linux and or coding, so I may have bitten off more than I can chew.

That said - your pictures pointed out to me that I can change the name of the entities of the node and by default they were something like zwave.kwikset.a.bunch.of.other.things.

So I’m playing around with those. I now have the status fixed but I somehow broke the battery, so working on that. Appreciate the detailed info - it definitely pointed me in the right direction.

chickenandporn · February 11, 2019, 8:29am

FWIW, when you set your Network Key in the configuration.yaml, manually check the options.xml files in the same directory to ensure they’re getting copied there. I still have the issue that it’s not being copied – too far down the list of things to figure out – but don’t trust that if it’s in the YAML, then it’s problem-free. It’s XML -commented out by default, but check that it’s uncommented, and matches your values.

kshunterco · June 24, 2020, 7:29pm

Hi Liwen,

Thanks for this info on disconnecting the zstick, pairing just the stick, then adding through secure_node. Is there any additional details to add? I am very new to this, tried to pair my Kwikset 909 to my Aeotech Z-Stick Gen5 while attached with no luck, so I tried your approach. I plugged the zstick back in while it was flashing yellow, and it stopped, but now HA marks it as unavailable. After a reboot it’s available again… “ADD NODE SECURE” just causes the pair, or did you again set the 909 in pairing mode? Or…

Thanks for any & all info…

Kendall

kshunterco · June 24, 2020, 9:02pm

OK… so manually (button on the Aeotech) excluding the lock (thank you all), resetting the Aeotech (not sure if both of those were needed), and as far as I can tell, the lock added:

2020-06-24 14:32:27.580 Info, Adding node ID 4 - Secure
2020-06-24 14:32:27.580 Detail, Notification: ControllerCommand - InProgress
2020-06-24 14:32:27.892 Detail,   Received: 0x01, 0x07, 0x00, 0x4a, 0x0a, 0x05, 0x04, 0x00, 0xb9
2020-06-24 14:32:27.892 Detail, 
2020-06-24 14:32:27.892 Info, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2020-06-24 14:32:27.893 Info, ADD_NODE_STATUS_PROTOCOL_DONE
2020-06-24 14:32:27.893 Detail, contrlr, Queuing (Command) Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2020-06-24 14:32:27.893 Detail, Notification: ControllerCommand - InProgress
2020-06-24 14:32:27.893 Detail, 
2020-06-24 14:32:27.893 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x4a) - Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2020-06-24 14:32:27.945 Detail, contrlr,   Received: 0x01, 0x07, 0x00, 0x4a, 0x0a, 0x06, 0x04, 0x00, 0xba
2020-06-24 14:32:27.946 Detail, 
2020-06-24 14:32:27.946 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2020-06-24 14:32:27.946 Info, contrlr, ADD_NODE_STATUS_DONE
2020-06-24 14:32:27.946 Info, Node004,   Basic device class    (0x04) - Routing Slave
2020-06-24 14:32:27.946 Info, Node004,   Generic device Class  (0x40) - Entry Control
2020-06-24 14:32:27.946 Info, Node004,   Specific device class (0x03) - Secure Keypad Door Lock
2020-06-24 14:32:27.946 Info, Node004,     COMMAND_CLASS_BASIC will be mapped to COMMAND_CLASS_DOOR_LOCK
2020-06-24 14:32:27.946 Info, Node004,   Mandatory Command Classes for Node 4:
2020-06-24 14:32:27.947 Info, Node004,     COMMAND_CLASS_BASIC
2020-06-24 14:32:27.947 Info, Node004,     COMMAND_CLASS_DOOR_LOCK
2020-06-24 14:32:27.947 Info, Node004,     COMMAND_CLASS_USER_CODE
2020-06-24 14:32:27.947 Info, Node004,     COMMAND_CLASS_MANUFACTURER_SPECIFIC
2020-06-24 14:32:27.947 Info, Node004,     COMMAND_CLASS_VERSION
2020-06-24 14:32:27.947 Info, Node004,     COMMAND_CLASS_SECURITY
2020-06-24 14:32:27.947 Info, Node004,   Mandatory Command Classes controlled by Node 4:
2020-06-24 14:32:27.947 Info, Node004,     None
2020-06-24 14:32:27.947 Detail, Node004, Queuing (Security) SecurityCmd_SchemeGet (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x98, 0x04, 0x00, 0x25, 0x0b, 0x53
2020-06-24 14:32:27.947 Info, Node004,   Optional command classes for node 4:
2020-06-24 14:32:27.947 Info, Node004,     COMMAND_CLASS_SECURITY (Existing)
2020-06-24 14:32:27.947 Info, Node004,     COMMAND_CLASS_MANUFACTURER_SPECIFIC (Existing)
2020-06-24 14:32:27.947 Info, Node004,     COMMAND_CLASS_VERSION (Existing)
2020-06-24 14:32:27.948 Info, Node004,     None
2020-06-24 14:32:27.948 Detail, Node004, AdvanceQueries queryPending=0 queryRetries=0 queryStage=None live=1
2020-06-24 14:32:27.948 Detail, Node004, QueryStage_ProtocolInfo
2020-06-24 14:32:27.948 Detail, Node004, Queuing (Query) Get Node Protocol Info (Node=4): 0x01, 0x04, 0x00, 0x41, 0x04, 0xbe
2020-06-24 14:32:27.948 Detail, Node004, Queuing (Query) Query Stage Complete (ProtocolInfo)
2020-06-24 14:32:27.948 Info, Node004, Initializing Node. New Node: true (true)

my best guess is that the value_template @netopiax mentions must correspond to an existing state and its attributes. I don’t have battery_level or lock_status attributes. I have:

lock.kwikset_spectrum_brands_touchpad_electronic_deadbolt_locked

with attributes

node_id: 4
value_index: 0
value_instance: 1
value_id: 72057594110836736
friendly_name: Back Door Lock

Additionally the add secure node process added two sensor services, but neither have those attributes. I will continue to plod on…

firstof9 · June 24, 2020, 9:21pm

If you have lock.kwikset_spectrum_brands_touchpad_electronic_deadbolt_locked you’re done, don’t mess with it any more

kshunterco · June 24, 2020, 9:42pm

Hi @firstof9, thanks for your reply. I’m messing with it because it does not seem to be configurable. Many of the states/attributes mentioned in this thread do not seem to exist for this state.

But more specifically,

Asking the device to lock or unlock doesn’t work:

2020-06-24 15:39:31.468 Info, Node004, Value::Set - COMMAND_CLASS_DOOR_LOCK - Lo
cked - 0 - 1 - True
2020-06-24 15:39:31.468 Info, Node004, Value_Lock::Set - Requesting lock to be L
ocked
2020-06-24 15:39:31.469 Detail, Node004, Queuing (Send) DoorLockCmd_Set (Node=4)
: 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x62, 0x01, 0xff, 0x25, 0x0e, 0x56
2020-06-24 15:39:31.469 Detail, Node004, Queuing (Send) DoorLockCmd_Get (Node=4)
: 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x62, 0x02, 0x25, 0x0f, 0xa9
2020-06-24 15:39:31.469 Detail, 
2020-06-24 15:39:31.469 Info, Node004, Sending (Send) message (Callback ID=0x0e,
 Expected Reply=0x04) - DoorLockCmd_Set (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 
0x03, 0x62, 0x01, 0xff, 0x25, 0x0e, 0x56
2020-06-24 15:39:31.477 Detail, Node004,   Received: 0x01, 0x04, 0x01, 0x13, 0x0
1, 0xe8
2020-06-24 15:39:31.477 Detail, Node004,   ZW_SEND_DATA delivered to Z-Wave stac
k
2020-06-24 15:39:32.755 Detail, Node004,   Received: 0x01, 0x07, 0x00, 0x13, 0x0
e, 0x00, 0x00, 0x80, 0x65
2020-06-24 15:39:32.755 Detail, Node004,   ZW_SEND_DATA Request with callback ID
 0x0e received (expected 0x0e)
2020-06-24 15:39:32.755 Info, Node004, Request RTT 1286 Average Request RTT 1206
2020-06-24 15:39:32.755 Detail,   Expected callbackId was received
2020-06-24 15:39:41.470 Error, Node004, ERROR: Dropping command, expected respon
se not received after 1 attempt(s)
2020-06-24 15:39:41.470 Detail, Node004, Removing current message
2020-06-24 15:39:41.470 Detail, Node004, Notification: Notification - TimeOut

Going to Configuration->Z-Wave->Z-Wave Node Management, there is apparently no way to set codes for the device. Lower down on the page, there are “Node Configuration Options”, but the primary parameters are 30 "User Code Type"s, rather than just User Codes. So…

Or maybe I’m just not understanding these messages. That very well could be the case. But the device isn’t responding to commands. That much is clear.

firstof9 · June 24, 2020, 9:45pm

How many nodes do you have?

squirtbrnr · June 24, 2020, 9:46pm

If you are unable to lock/unlock the device from HA, then the lock is either not paired through the add secure node process, or your network key is not set or malformed. You should not try and pair the lock manually with the stick disconnected. You should only pair it through the Zwave configuration page in HA.

firstof9 · June 24, 2020, 9:47pm

Try restarting Home Assistant, sometimes the add node process goes wonky too.

kshunterco · June 24, 2020, 9:53pm

@firstof9 this is the first node. Baby steps for me

@squirtbrnr I simply cut and pasted the code from https://www.home-assistant.io/docs/z-wave/adding/ into an xterm to generate the code, but… who knows. I can post it here, and simply regenerate another one, it was:

zwave:
  usb_path: /dev/ttyACM0
  network_key: [originally shown but now removed]

Although I did manually exclude it and then reset the zstick, my secure pairing - which seemed successful (given the log output above) - was performed through HA (Zwave config page). Not sure what the logs would have indicated if

The network key was bad; or
The secure pairing actually failed…

…?
At the top of OZW_Log I always get this message:

2020-06-24 15:36:16.777 Info, Setting Up Provided Network Key for Secure Communications

and nothing that seems to indicate this failed…

This is under aarch64 not sure if that makes any difference… just putting that out there.

firstof9 · June 24, 2020, 10:01pm

Please remove your key from the post.

Try excluding the lock via Home Assistant, and re-adding it IF restarting Home Assistant doesn’t help.

kshunterco · June 24, 2020, 10:06pm

Sure thing… @squirtbrnr mentioned it might be malformed, so I thought I would include it. I’ll delete it now.

I have excluded / (re-)added the lock several times now, after I factory reset the zstick and the lock… I can keep doing it. I followed the other directions, which were to heal the network, and yeah for good measure I also restarted HA… this did not help

firstof9 · June 24, 2020, 10:10pm

Check inside your ozwcache_XXXXX.xml see if your node has a TriggerRefreshValue under CommandClass id ='113' and post that please.

Example:

				<TriggerRefreshValue Genre="user" Instance="1" Index="0">
					<RefreshClassValue CommandClass="98" RequestFlags="0" Instance="1" Index="1" />
				</TriggerRefreshValue>

kshunterco · June 24, 2020, 10:16pm

There is no TriggerRefreshValue in that file at all… I used grep just to make doubly sure …

Additionally if two devices should appear in that file, well it looked like just the zstick info was there. Nothing on the kwikset… (no node 4)… yeah that’s it, just node 1, the stick, nothing more.

I see there’s config stuff in /usr/share/hassio/addons/data/core_zwave/ozw/config/kwikset … that probably should have been added to the cache file?

firstof9 · June 24, 2020, 10:20pm

In the zwave control panel click save network I believe it’s called, then check the file again.

kshunterco · June 24, 2020, 10:22pm

Thanks for working with me in nearly real-time.

There’s a “Save Configuration” button, pressing it did not change the cache file.

kshunterco · June 24, 2020, 10:25pm

I’m going to do this. Please advise… (reset as much as possible)

Exclude the lock
Shut down HA
Remove the cache xml file
Remove the database file under homeassistant/
Shut down the RP
Factory reset the zstick and the lock
Bring it all back up and see how it recognizes the zstick
Attempt to add node secure for the lock

Any reset steps I forgot?

Hold the phone, zwcfg_0xf06a24be.xml in homeassistant/ has:

<TriggerRefreshValue Genre="user" Instance="1" Index="0">
      <RefreshClassValue CommandClass="98" RequestFlags="0" Instance="1" Index="1" />
</TriggerRefreshValue>

which yes, is under CommandClass id="113"…

I’ve accepted the invite to discord and am over there but never have used it before (I’m old )… it will take 10 minutes before I can chat. Oh and I have run out of posts for my first day on this site! Hah! Thanks for the help.

firstof9 · June 24, 2020, 10:30pm

You don’t need to nuke the database.
Also if you like to we can take this to discord: https://discord.gg/kK7BcV in the #zwave channel.