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

Channel config reference #14

Open
5iver opened this issue Aug 2, 2020 · 5 comments
Open

Channel config reference #14

5iver opened this issue Aug 2, 2020 · 5 comments

Comments

@5iver
Copy link

5iver commented Aug 2, 2020

When adding a config for a Channel, I always end up looking up another device to get it right, assuming I can find one. At a minimum, it would be nice to have some sort of reference to look these up. IMO it would look better if config was fully spelled out too.

image

After clicking Help, it looks like this would be a good place for them...

image

@cdjackson
Copy link
Contributor

I always end up looking up another device to get it right, assuming I can find one.

At a minimum, it would be nice to have some sort of reference to look these up

Ok, so what I suggest is we start to document these here. When we do a lookup on another device, let's write it down here so we can build the list. There is a help button on this form - it doesn't do anything except pop up a dialog that has nothing in it, but we can change that if we have stuff to put in it...

I don't really have a big list of these, so we'd have to generate them as we go, but I certainly agree - it would be good to improve this. WDYT?

@5iver
Copy link
Author

5iver commented Aug 2, 2020

Sounds good. Here are a few to start things off...

Name Config
Relative humidity type=RELATIVE_HUMIDITY
Temperature type=TEMPERATURE
Luminance type=LUMINANCE
Burglar type=BURGLAR
Motion type=BURGLAR, event=8
Tamper type=BURGLAR, event=3
Contact type=BURGLAR, event=2
External switch type=BURGLAR, event=254

@cdjackson
Copy link
Contributor

Thanks...

Note that Alarms should not require these settings any more. The alarms use configuration directly in the binding to select the events and type - what's important is the channel name.

You can find the list here -: https://github.com/openhab/org.openhab.binding.zwave/blob/2.5.x/src/main/java/org/openhab/binding/zwave/internal/converter/ZWaveAlarmConverter.java#L60

Further down this file is a big table of definitions of all these events and which ones are used for what states is in the top of this file (as per the reference above).

@bwosborne2
Copy link
Collaborator

I was going to say the mapping of config Name & channel Name are already determined for the binding.

The Channel name should be read-only and based on the Config choice which could use a drop-down since the values are from a predefined list.

@bwosborne2
Copy link
Collaborator

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

3 participants