Refresh Device Configuration

Silver_Bullet · July 1, 2018, 2:24pm

I have a Kwikset SecureCode 888, and I recently updated the device database with some corrections to the channels and configuration parameters. I am trying to refresh my local device to pull down the new configuration settings so I can try it out. However, I am not able to do so. I have tried excluding and re-including it. I have also completed the ‘Reinitialize Device’ on the advanced options dropdown for the device. I have also excluded it, deleted the Thing entry for the device and then completed the inclusion process again for the device. Along with various reboots along the way. Nothing seems to make it pull down the updated config. Is there something I am doing wrong or is there some way I can force this in a different manner?

Thanks in advance,

–silverbullet

sihui · July 1, 2018, 5:07pm

You did not mention you downloaded the new zwave binding version
The binding was updated about 9 hours ago, so you need a pretty new snapshot to get the changes.

github.com

openhab/org.openhab.binding.zwave/blob/master/ESH-INF/thing/kwikset_smartcode888_0_0.xml

<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:thing="http://eclipse.org/smarthome/schemas/thing-description/v1.0.0"
  xsi:schemaLocation="http://eclipse.org/smarthome/schemas/thing-description/v1.0.0
                      http://eclipse.org/smarthome/schemas/thing-description/v1.0.0">

  <thing-type id="kwikset_smartcode888_00_000" listed="false">
    <label>SmartCode 888 Touchpad Electronic Deadbolt</label>
    <description><![CDATA[
Touchpad Electronic Deadbolt<br /><h1>Overview</h1><p>The following table provides a reference of the Alarm_Number related messages.</p> <p>Alarm Type Alarm Level Notification Event<br />021 001 Lock Secured using Keyed cylinder or inside thumb-turn<br />022 001 Lock Un-Secured using Keyed cylinder or inside thumb-turn <br />026 001 Lock Auto Secured – Bolt Jammed (Not fully extended) <br />027 001 Lock Auto Secured – Successful (Fully extended)   <br />017 001 Lock Secured at Keypad – Bolt Jammed (Not fully extended)   <br />018 000 or User ID Lock Secured at Keypad – Successful (Fully extended)  <br />019 User ID Lock Un-Secured by User (User-ID) at Keypad <br />023 001 Lock Secured by Controller – Bolt Jammed (Not fully extended) <br />024 001 Lock Secured by Controller – Successful (Fully extended)   <br />025 001 Lock Un-Secured by Controller – Successful (Fully retracted) <br />112 User ID# New User Code (User-ID#) added to the lock <br />032 001 All User Codes deleted from lock</p> <p>161              001                      Failed User Code attempt at Keypad  <br />162              User-ID#*             Attempted access by user (User-ID#) outside of scheduled   <br />167              001                      Low battery level   <br />168              001                      Critical battery level  <br />169              001                      Battery level too low to operate lock  </p> <p>* User-ID# values: 001 to 030</p> <br /><h2>Inclusion Information</h2><p> Press button “A” on the lock one time to include it in your system.</p> <br /><h2>Exclusion Information</h2><p> Press button “A” on the lock one time to include it in your system.</p>
    ]]></description>
    <category>Lock</category>

    <!-- CHANNEL DEFINITIONS -->
    <channels>
      <channel id="lock_door" typeId="lock_door">
        <label>Door Lock</label>
        <properties>
          <property name="binding:*:OnOffType">DOOR_LOCK</property>

This file has been truncated. show original

sihui · July 1, 2018, 5:52pm

As I just saw in the database history their have been a lot of changes to that device, which not all have it made into the binding yet.
You need to wait for the next PR and then download the newest snapshot zwave binding.

Because of the several changes to that device I recommend to discuss any problems here in the forum.

sihui · July 1, 2018, 5:54pm

BTW, your last changes (if you are Adam) can not be approved:

Silver_Bullet · July 1, 2018, 5:57pm

I apologize. I should have mentioned that. I installed the latest snapshot on 6/27. When I do “bundle:list” it lists my binding as version “2.3.0.201806262322”. I wasn’t aware that the bindings are built specific to the device database, I thought the device configuration could be refreshed dynamically without having to update the bindings. Am I understanding your statement? Are you saying at every time that a device is updated in the database a new version of the zwave binding needs to be released to include those changes? I can definitely download the latest snapshot and see if that fixes my issue. I just wanted to understand this process a bit more.

Thanks for your help!

–silerbullet

sihui · July 1, 2018, 5:58pm

Yes.

sihui · July 1, 2018, 6:00pm

And please don’t forget: any changes to the database effect all users, not only you

sihui · July 1, 2018, 6:21pm

From the manual I could find (just uploaded to the database) there is no config parameter 31!
Wherever your sources are for that, please upload that as pdf doc.
If you by accident misconfigured that device, we need to ping @chris to get the old database version back in place

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/864

Silver_Bullet · July 1, 2018, 7:54pm

I created the entry, so I will go ahead and update the device configuration. I must have used the wrong guide when I set it up in the device database. Thanks for finding that info.