Z-wave user code via UI is broken #11018
Comments
|
That's wierd.. I just tested with my own lock, different though (BTZE150) And it works like it should. |
|
Here's another example trying to delete a code. Manually setting the code to UI is virtually unchanged pre and post button press. (After pressing the button and the response comes back, the text Here is the log from the event: Any suggestions on what to try to resolve this? Should I delete the node? |
|
I came here seeking answers regarding this as well. My lock is a Schlage BE469NXCEN. When I select a Code Slot the User code field remains empty. Looking at the ozw.log I don't see any calls to that node. Perhaps I am misunderstanding how this UI works, isn't it supposed to retrieve the usercode and put it in the input field in the UI? On a side note I also attempted retrieving a code using the dev services page: This logs the following to the logs: No I did not censor that, it actually came through that way. I also tried sending a code which I think is successful:
after calling a subsequent The OZW.log file is not showing any of these commands |
|
The clear usercode function is only partially supported by OZW, hence it will not work on all locks. It does not work on my test lock (Danalock V2). Some people have reported other locks to be working, but there are no guarantee for it to work. |
|
@turbokongen - While that may be true, all of these functions worked fine on v.58 for my installation, including remote code setting, code clearing, and viewing codes. Now, it seems like none of these work. Is there a way to downgrade hass.io? |
|
@turbokongen are you sure your config is okay? I wouldn't think a new version would break everything. I know of another guy with that lock, will confirm with him his version of hass. |
|
The actual services has not changed, only the input from the UI. Maybe there are encoding issues? |
|
@turbokongen regarding the issue I thought was at hand here (the title of this issue). I read from others in forum that setting the usercode to '0000' on some locks simply clears it. https://community.home-assistant.io/t/schlage-connect-zwave-locks/6220/81?u=nalipaz Is it possible that the |
|
@nalipaz I know that the author want to keep HA as simple and maintain free, thus avoiding workarounds at the most. There are a fix in the pipeline of OZW OpenZWave/open-zwave#1059 |
|
This is not limited to resetting the user code. This applies to setting of new user codes and what is shown in the GUI when you update the codes. Right now, it shows gibberish. |
|
@poldim |
|
I will try this when I get back from traveling and post a reply.
…On Sun, Dec 24, 2017 at 2:13 AM John Arild Berentsen < ***@***.***> wrote:
@poldim <https://github.com/poldim>
Could you provide the following:
Set usercode 1234 in UI. (\31\32\33\34) and provide logsnippet from
OZW_Log.txt from the transaction.
Set usercode 1234 with developer services menu. (lock.set_usercode
{"node_id": YOUR_NODE_ID, "code_slot": YOUR_CODESLOT, "usercode": 1234}"
and provide logsnippet from OZW_Log.txt from the transaction.
That way I can see what is going on.
I see some random characters with my lock too, but that does not seem to
matter, and is in the response, not in the sent message to the lock. Before
we limited the ui to oonly show numbers. BEcause of the ability to set hex
numbers for some devices, we show the raw message now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11018 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQFpUTyT_LNb8LHttCgKK_H-oUhl9z3Mks5tDWXrgaJpZM4Q6kbU>
.
|
|
Hopefully this provides a hint... I have some automations which set/reset user codes on the lock automatically. they were working in 0.58, but are now busted on 0.60. I get the following error when I attempt to set the code from my automation: The automation is triggering the following service call: The same error (above) is triggered by calling the set_usercode service from the dev-services menu with the following JSON: Nothing shows up in OZW_Log.txt related to these calls. |
|
@kmwoley |
|
I'm currently on 60.1, installed via a Docker image (I can point you at
which one if it matters).
…On Mon, Jan 8, 2018, 4:58 AM John Arild Berentsen ***@***.***> wrote:
@kmwoley <https://github.com/kmwoley>
Huh, that error reports some older code....
lock_node = network.nodes[node_id] is on line 132 in current code.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11018 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AF1jeDm9w8PVVkHbGSSLKf11lj_4duhCks5tIhEDgaJpZM4Q6kbU>
.
|
|
@turbokongen - your link is to the dev branch, which has changes not deployed to master. Also, it looks like the lock/zwave.py hasn't changed in ages; so there's something outside of that file going on. |
|
@kmwoley |
|
I feel like an idiot; I recently removed / re-added my lock to attempt to
fix an unrelated problem which obviously changed the node_id. You can
ignore my comments on this issue - user error.
…On Wed, Jan 10, 2018 at 5:42 AM John Arild Berentsen < ***@***.***> wrote:
@kmwoley <https://github.com/kmwoley>
I can only reproduce your error by using a nonexisting node_id in the
network.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11018 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AF1jeF0s3X2iM12j_-ssLZHuznSlG-eoks5tJL40gaJpZM4Q6kbU>
.
|
|
I'm still having this issue on 0.65. |
|
Also still having issues. This is what it looks like when I first click on a user code. It should be just four numbers. @turbokongen, I don't think this should be closed. |
|
@turbokongen - Any thoughts? |
|
@poldim |
|
@turbokongen wouldn't it be \x31\x32\x33\x34 |
|
yes, a typo. |
|
@turbokongen I can do this when I get home tonight. Which logs can I see the result of get_usercode in? OZW or HASS? |
|
homeassistant.log will show the data sent to OZW and ozw_log.txt will show what ozw gets and returns to HA. |
|
UI: Developer services menu: |
|
@turbokongen: I am also having the same trouble setting, changing, and deleting user code. I am on 0.66.1 HASS.io. When I attempt to add codes normally via zwave menu, I get this in the homeassistant.log: Nothing shows up in the OZW log. I am also seeing if you use "\x31\x32\x33\x34" the user displays correctly underneath (1234) and the lock is able to be unlocked using that code after setting it. However, the page refreshes shortly after and displays: OZW Log for using \x31\x32\x33\x34: Now when I try to delete a code slot, it does not work. I can still use 1234 (set by using "\x31\x32\x33\x34"). I try to set the code to "\x30\x30\x30\x30 (0000) or \x00\x00\x00\x00" (blank) but then I can use 0000 to unlock the door or 1234 still works. OZW Log while trying to delete a code slot: |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Home Assistant release (
hass --version):0.59
Component/platform:
Z-Wave Manager
Description of problem:
Yesterday I was able to set codes via GUI running the previous version 0.58. Today, after updating to the current release, the change to using hex input has broken the ability to update user codes. I was working great when it accepted regular text characters. I can deal with it being hex, but it's now not accepting the codes.
Maybe @turbokongen can advise as I saw he added the ascii comments in the docs.
Expected:
Be able to set usercode via GUI
Steps to reproduce:
Additional info:
Yale Z-Wave Lock YRD210-ZW-605
The text was updated successfully, but these errors were encountered: