Mecheng70

Stupid question here, how do you get "Battery 2.3" and those other nodes? I have the Node Server but none of those nodes show up in AC. I can't tell you how many times I have pressed the "Load Configuration" button.

I keep bouncing around moving everything over to HA. But then my redundancy brain kicks in and I default to keeping the eisy.

I created my own script and card (using existing cards). Can update lock codes and delete them. Has been working well enough.

I recommend the Google backup addon. Have used it when my system died. Does full backups.

You can hide them or just ignore them. I have 500+ and hide a lot of them. Don't think it's a big issue.

I use a 10ft USB (make sure it is of high quality) that allows the Zmatter module to be mounted at the top of the closet. As for the zwave locks, have you attempted to heal the network to see if that helps? Or update it with interview? Maybe one of the experts will confirm is removing and readding it in the place where the final resting area is makes any sense.

I'll have to look for those. These are what I found for door locks.

Working on integrating Node Red with changing the Access Code Alarm to Text. Leaving them here incase someone has any interest. Here are the codes to text: IXA_AC-0 = Idle IXA_AC-1 = Manual lock IXA_AC-2 = Manual unlock IXA_AC-3 = RF lock IXA_AC-4 = RF unlock IXA_AC-5 = Keypad lock IXA_AC-6 = Keypad unlock IXA_AC-7 = Manual not fully locked IXA_AC-8 = RF not fully locked IXA_AC-9 = Auto locked IXA_AC-10 = Auto lock not fully locked IXA_AC-11 = Lock jammed IXA_AC-12 = All user codes deleted IXA_AC-13 = Single user code deleted IXA_AC-14 = User code added IXA_AC-15 = User code not added (duplicate) IXA_AC-16 = Keypad temporary disabled IXA_AC-17 = Keypad busy IXA_AC-18 = New program code entered IXA_AC-19 = Manual code entry limit IXA_AC-20 = Unlock by RF with invalid user code IXA_AC-21 = Locked by RF with invalid user code IXA_AC-22 = Window/door is open IXA_AC-23 = Window/door is closed IXA_AC-24 = Window/door handle is open IXA_AC-25 = Window/door handle is closed IXA_AC-32 = Messaging User Code entered via keypad

those are all I use... I will continue to watch them

Thanks again @shbatm I will leave this here if someone is looking to create a way to update or delete user codes. My situation is that I need to update a lock based on who is renting the unit (airbnb). Here is the card layout: Row 1 - Left - uses a dropdown helper called "user_number_idooruser" Row 1 - Right - users a text helper called "door_code_idoorcode" Row 2 - uses a dropdown helper called "locks", here the drop down options are lock.front, lock.casita, etc Row 3 - Left - Uses a button that calls a service when activated. The service for the left button is the one that sets the lock.front, users 3 to 8675309. Row 3 - Right - Users the same button but calls a different service when clicked. The service for the right button deletes the user number 3 on the lock.front entity. Example of the lock selector: Script to set the lock code service: isy994.set_zwave_lock_user_code data: user_num: "{{ states('input_select.user_number_idooruser') | int }}" code: "{{ states('input_text.door_code_idoorcode') | int }}" target: entity_id: "{{ states('input_select.locks') | string }}" Script to delete the lock code. service: isy994.delete_zwave_lock_user_code data: user_num: "{{ states('input_select.user_number_idooruser') | int }}" target: entity_id: "{{ states('input_select.locks') | string }}" Have tested this and the ISY does report the status of user added or user deleted. Thanks again @shbatm

Is this automatically installed with the 4.0.8? New Python Module repo: https://github.com/shbatm/pyisyox

@shbatm Awesome on the example code!!!! That made my day!

Claims it is not a zwave device. Heading over to upload the logs.

In the example, can you use 8675309? 😆

@shbatm found two issues, see github issues.

you're killing me!!!! thats awesome. I will check it out!

My advice would be to grab the Google backup addon. I was able to restore a ton of stuff when my HA became unsupported on Ubuntu. (I run it on proxmox now)

Update 4.0.10 now has the ability to set and delete user codes from HA!!!!! THANK YOU @shbatm No REST - kinda I have the need to be able to change lock codes and control when lock codes are used or not used. Typically I use HA for user interaction programs and ISY for more system control (almost scene control - lock unlocks then turn on patio light). However there is no functionality that suits my need to be able to update ISY when not having direct access to my network. That and having something that my SO is comfortable using. Here is the basic set up: ISY Create two integer variables. iDoorUser - make note of the variable ID. In my case the ID was 28 iDoorCode - ID was 27 Create two Network Resources for each lock. Add User - Named mine Program Doors.NAMEOFDOOR Create a New Resource HTTP GET host: user:pass@172.16.5.251 user - your username pass - your password port: 8080 Path: /rest/zmatter/zwave/node/ZY022_1/security/user/${var.1.28}/set/code/${var.1.27} ZY002_1 - substitute your device number here. ${var.1.27} - iDoorCode ID ${var.1.1.28} - iDoorUser ID Click UPDATE and SAVE Delete Code - Named mine Delete Code Doors.NAMEOFDOOR Create a New Resource HTTP GET host: user:pass@172.16.5.251 user - your username pass - your password port: 8080 Path: /rest/zmatter/zwave/node/ZY022_1/security/user/${var.1.28}/delete ZY002_1 - substitute your device number here. ${var.1.1.28} - iDoorUser ID Click UPDATE and SAVE Create one program for each ZWAVE lock - Take note of the Program Number IF - nothing needs to be here THEN - add the RESOURCE for the Add User ELSE - add the RESOURCE for the Delete User HOMEASSISTANT In home assistant, in an automation: Set the iDoorUser and iDoorCode - each require a call service for the Number: Set service Call the ISY/IoX Send Program Code- service using the Program Number. That's pretty much it. On the ISY I have created a repeat function that will wipe out all the codes and reprogram User 1. So have fun with that.

My situation maybe different. I run an Airbnb and change the door code based on the last four of their phone number. Lock configuration is important to me so that my wife can do it without having to access AC.

Yesterday. In order to "wake" up devices because the query all doesn't seem to work right and devices disappear from HA. The basic configuration doesn't have color change by default. The panels have to be manually modified for each device and color scheme. Maybe including a default would help. Can you update user codes? I prefer Over this In my career I spend a lot of time with understanding the user and designing products for them, so maybe my expectations are different from others.

https://github.com/shbatm/hacs-isy994

For some reason I thought that the naba casa was $30/mo. $5/mo isn't so bad. I'm gonna have to look into it for the Google home integration.

Oh ok. I agree in supporting the devs too. I do a lot of the "buy me a coffee/beer" every couple of months for the integrations that are used. Which reminds me that shbatm needs to fix his link. I've only been able to get it to work once.

@asbril curious, why are you paying $5/mo for the HA mobile app. Personally, I am not a fan of the UD mobile app. It is too rigid and cumbersome to use. HA offers so much in the human factors and ability to customize the dashboard. Agave was even a step ahead of UD mobile. Another functionality aspect is that door locks are not even supported in the mobile app. They are on the road map, but who knows when that will be updated. I have been able to create a script in HA that pulls the code from a text box and calls the REST command to update the lock. HA is much easier to get it to do what I need it to do.