Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dev request - exposing other devices under Ultrasync control #28

Open
illigtr opened this issue Sep 5, 2023 · 6 comments
Open

Dev request - exposing other devices under Ultrasync control #28

illigtr opened this issue Sep 5, 2023 · 6 comments

Comments

@illigtr
Copy link

illigtr commented Sep 5, 2023

I have started testing your ultrasync-ha. I have an Ultrasync panel that is part of NOWA's water leak detection and shutoff system. I also have Aqua-Protect (sewer backup cut-off system) wired into the Ultrasync panel. I added a Z-wave keypad deadbolt to the system and I can see it's status and control the deadbolt with the Android Ultrasync app.

How can I expose the door lock in ultrasync-ha. The docs suggest all devices/zones are automatically exposed. I do have the status of the Z wave water detectors as well as the Aqua-Protect, but I don't see the door lock. Any assistance would be appreciated.

@Ay1tsMe
Copy link
Contributor

Ay1tsMe commented Sep 11, 2023

What part of the ultrasync app is the device listed under? Is it under a category called Output Control? If so, I'm currently adding support for this: #29

@illigtr
Copy link
Author

illigtr commented Sep 11, 2023

Thanks for replying, I couldn't find a category called Output Control in the GUI, but I have attached some screen shots which may help. I am logged into my Ultrasync panel with the "Installer" code.

Briefly my configuration is not used as a traditional home alarm system, but rather a multi-room water leak and sewer backup detection and mitigation system. The water leak pucks are Z-wave devices. These devices do appear in HA with your integration. Last year I added a Z-wave daughterboard to the front door keypad electronic deadbolt. I can control the deadbolt via Ultrasync, but it doesn't appear in HA.

image

image

image

If there is a way to dump the Ultrasync configuration to some sort of file, perhaps via telnet or SSH, or even the GUI, let me know and I'll try to provide you with the information you need.

@Ay1tsMe
Copy link
Contributor

Ay1tsMe commented Sep 12, 2023

Okay the output control support I linked doesnt look related to your problem. You would need to wait until @caronc gets back to you.

In the meantime though, you could post your --debug-dump using the CLI tool here. A step by step guide that @caronc has wrote is below:

The first thing to do is just create a text file. You can use notepad.exe if you're in Windows, or any editor of your choice in Linux/Mac. The text file just has to have 3 entries in it; this will be your config file to use this script. It's the same things you need to provide Home Assistant in order for it to work there too:

# the ip to your ComNav Security Panel
host: 192.168.0.30
# The Web User ID you use to log into it with:
user: My Username
# Your Pin:
pin: 1234

Check out a copy of ultrasync if you can't access it from your Raspberry Pi (where Home Assistant is) as it will be already available to you there. You'll need to do a --debug-dump for me:

  1. Use your Home Assistant Pi instance if you can:
# Call the ultrasync tool referencing your configuration file you created
# along with --debug-dump
bin/ultrasync -c /path/to/config --debug-dump
  1. Use git:
# Clone the repository:
git clone https://github.com/caronc/ultrasync.git

# Change to the directory you just cloned to (with respect to the above, you'd
# have created an ultrasync directory):
cd ultrasync

# Now call the ultrasync tool referencing your configuration file you created
# along with --debug-dump
bin/ultrasync -c /path/to/config --debug-dump
  1. Use pip if you already have Python (v3) installed on your pc:
# Install ultrasync:
pip install ultrasync

# Now call the ultrasync tool referencing your configuration file you created
# along with --debug-dump
ultrasync -c /path/to/config --debug-dump

This will produce a zip file you can pass back to me with slightly more files then the ones you already shared. It will allow me to see your panel information (so i can recreate your crash and fix it).

Also, all UltraSync devices only allow 1 login per user at a time. So create a separate account for your Home Assistant user (and these tests). Also, if your Home Assistant configuration is still set up, remove it (otherwise Home Assistant will be competing with your testing as it will continuously try to log in over and over again) while you help me out here 🙂 . Hopefully this all makes sense!

Please let me know if you have any questions or concerns or are having any issues with the info above.

@illigtr
Copy link
Author

illigtr commented Sep 12, 2023

Thank you for the detailed instructions. I should be able to put the necessary files together from my HA (Pi4) host. I already have a unique user account for Ultrasync integration with HA.

@illigtr
Copy link
Author

illigtr commented Sep 12, 2023

I was not able to create the dump on the HA host. The host is based on the basic Pi4 image of HA available in the Pi Imager software. Even though I can access via SSH, I could not find python or pip or bin/ultrasync. (find / -iname ultrasync).

I do have Python installed on my development PC and was able to create the dump. During the dump creation I did have these errors:

Creating debug archive  [###---------------------------------]    9%  
00:00:592023-09-12 11:37:48,663 - ERROR - Failed to query http://10.254.254.10/user/outputs.htm
Creating debug archive  [####################################]  100%

The zip is attached. I checked it quickly to ensure no private information is shared (WiFi keys, user/pass, etc.)
20230912113743.ultrasync-dump.zip

@Ay1tsMe
Copy link
Contributor

Ay1tsMe commented Sep 13, 2023

the outputs.htm error is fine. That just means you don't have output control on your panel. You have a lot of .json files in your debug which is interesting.

Chris will have a look at the debug and he will let you know if there's anything you can do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants