opensmarthouse / opensmarthouse-web

Provides public elements of OpenSmartHouse web site including ZWave database import/export and log file processors.
0 stars 2 forks source link

Channel config reference #14

Open 5iver opened 4 years ago

5iver commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

I was thinking of this channel list. There is some algorithm to determine the Name. https://github.com/openhab/org.openhab.binding.zwave/blob/2.5.x/src/main/java/org/openhab/binding/zwave/internal/protocol/commandclass/ZWaveMultiLevelSensorCommandClass.java#L331