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

Most of the device paramaters are missing #6010

Open
2 tasks done
skull791 opened this issue Jul 13, 2023 · 12 comments
Open
2 tasks done

Most of the device paramaters are missing #6010

skull791 opened this issue Jul 13, 2023 · 12 comments
Labels
config ⚙ Configuration issues or updates

Comments

@skull791
Copy link

Checklist

Which device is missing?

building 36 ADC-T40K HD

Manufacturer ID

400

Product Type

1

Product ID

10

Firmware Version

1.6

Is the device listed on the Z-Wave Alliance website?

no

Do you have a manual?

No response

@skull791 skull791 added the config ⚙ Configuration issues or updates label Jul 13, 2023
@AlCalzone
Copy link
Member

Do you have a manual or something that explains which device parameter exist and what they do?

@skull791
Copy link
Author

skull791 commented Jul 13, 2023 via email

@AlCalzone
Copy link
Member

I went through a similar procedure with another user for this:
#5557

That involved setting up a Zniffer, changing each parameter to their min/max limits via the alarm.com interface, documenting each change and then using that info to reverse-engineer the Zniffer traces to write the config file.

@skull791
Copy link
Author

skull791 commented Jul 13, 2023 via email

@skull791
Copy link
Author

I have not heard back, any plans to look in to this? I can offer any help needed as long someone walk me through

@AlCalzone
Copy link
Member

You need a Windows PC, the Zniffer software (available after logging in, but I can send it to you if that doesn't work), if Security is used the network keys, and a Zniffer stick.

Zniffers are essentially Z-Wave sticks flashed with the firmware from the above download.
Ideally use an UZB3 for your region:

When you have that set up, start the Zniffer application, configure it to use the Zniffer stick and start capturing.
Then change each parameter to their min/max limits via the alarm.com interface, documenting each change (which parameter was changed to which value when?).
When done, send me that information along with the Zniffer trace file. We can do that on Discord.

@skull791
Copy link
Author

skull791 commented Jul 21, 2023 via email

@skull791
Copy link
Author

skull791 commented Jul 25, 2023 via email

@AlCalzone
Copy link
Member

Please send me an email to the address in my profile. I can't see yours here.

@skull791
Copy link
Author

skull791 commented Jul 25, 2023 via email

@sdt16
Copy link

sdt16 commented Jan 31, 2024

I’m willing to take this on. Just ordered the ACC-UZB3-U-STA. I have a SILabs account, so I can grab the software. The rub is I don’t have an alarm.com system, so hopefully there’s another way to enumerate everything, or at least make some progress.

@AlCalzone
Copy link
Member

You can use a driver function in Z-Wave JS UI:

const node = driver.controller.nodes.get( 2 ); // assuming 2 is your node ID
node.commandClasses.Configuration.scanParametersLegacy()

This should scan through all possible parameters and print their size and value to the log.
You can then use the "custom configuration" fields to GET and SET their values.

The hard part will be figuring out what actually happens when changing the parameters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
config ⚙ Configuration issues or updates
Projects
None yet
Development

No branches or pull requests

3 participants