OH2/ESH DMX binding

Add-ons Bindings
,
75

That’s strange. Works perfectly for me. You can already define turnon/turnoff values for different channels. Just use the same notation as for chasers:

turnonvalue="100,100,200"

should use turn-on-value of 100 for channel 1 and 2 and 200 for channel 3. I confirmed that works with the latest build. There seems to be a bug with delegating events to wrong handlers in OH2, I can’t properly reproduce it. I’m quite sure that this has nothing to do with the DMX binding as this sometimes still happens after a restart. How do you link the things to items?

Regards,

-jnk

76

I have played around a little using the latest version (from today?).

The “switch” now controls the corresponding channels, however the slider of that channel is not updated.

things:
Bridge dmx:artnet-bridge:tubelamp [address="192.168.188.22", universe=0, applycurve="1/4"] {
 dimmer tubeRGB	[ dmxid="1/3", fadetime=3000, turnonvalue="127", turnoffvalue="0" ]
 dimmer tubeWW 	[ dmxid="4", fadetime=3000, turnonvalue="127", turnoffvalue="0" ]
 chaser tubeAmpel[ dmxid="1/3", steps="100:255,0,0:1000|100:255,255,0:500|100:0,0,255:1000|100:0,255,0:500"] 
} 

items:
Switch	TubeLampMute	"TubeLamp Mute"	{channel="dmx:artnet-bridge:tubelamp:mute"}
Color	TubeLampColor	"TubeLamp Color" {channel="dmx:dimmer:tubelamp:tubeRGB:color"}
Dimmer	TubeLampDimmer	"TubeLamp Dimmer "{channel="dmx:dimmer:tubelamp:tubeWW:brightness"}
Switch	TubeLampSwitch	"TubeLamp Switch" {channel="dmx:dimmer:tubelamp:tubeWW:switch"}
Switch	TubeLampChaser	"TubeLamp Chaser" {channel="dmx:chaser:tubelamp:tubeAmpel:switch"}

when I remove the tubelamp: in the items definition, the sliders actually do work with the switch, however, I do not get an artnet output and an error in the log: “item not linked to a channel”…

the item description is copy-pasted from the paperUI, just to be sure it is correct:

I noticed another error: when there is a minus (-) in the adress/hostname, there is another error.

77

This should be fixed now. I’ll have a look into the other thing as soon as I find time. Thanks for your testing

78

What exactly is not working? I copied your configuration and tried to switch the TubeLampSwitch via PaperUI. This turns the light on to 0x2f (which is correct). You are correct that this value is not updated in the slider in the PaperUI. However, after a refresh of the PaperUI page the slider correctly shows 49%. I think this might be related to the PaperUI, not the DMX binding.

In my own configuration I use the iOS app, this is immediately updating the silder if I turn on the switch.

Best Regards,

-jnk

79

You are right. It works now! I really wonder why this has never worked before? I guess I have forgotten another reboot.

There is one more thing I did not mention: I do have multiple bridges with different names. Each of these contained things with the same name before - now each thing or channel has a unique name. This may have been the source of the weird behaviour I experienced?

As a general observation, this binding (or openHAB?, but contrary to other bindings) seems to have some issues with initalization. I am setting up everything with text-file editor, but whenever I change the a thing/bridge It seems that at least one reboot is necessary to come into effect. Just changing a thing (without changing the name) seems to work better.

Cheers from a happy user
David

80

I’ll probably withdraw the binding from ESH. Since some bindings get reviewed and merged within less than a month while this one awaiting review for half a year, I assume that this contribution is not considered of much value.

Regards,

Jan

81

Hi Jan,
we are in the process of building up resources to make more binding reviews possible. Please do not withdraw your binding and have at little more patience. The first review will start within the next week.

Cheers,
Henning

82

I have just done a first review of your binding, please have a look.

83

During the review process we got into a discussion about 0-255 (which is the usual DMX way) or 0-100 (which is more ESH-like). What do you all think about that one?

Regards,

-jnk

84

In the configuration file using the DMX values is a must. On is not specifying openhab/esh value but rather the physical signal on the bus.

Edit:
The user can always do a sendCommand with the appropriate percentage type.

85

I agree with Spaceman_Spiff, DMX values is a must.

Maybe there is a smart way to make this configurable to switch between DMX(255) and ESH(100)?
Otherwise, I think one more sentence in the documentation in the Chaser Thing should clarify this as well.

86

Can anyone fill me in on how to create pixel chases or fades. Can we create groups for say all red. I have 21 rgb fixtures and want to create sequences for them.

87

Dynamically created fades are currently not possible.
You have to define the fade in your *.items file and attach it to a command (e.g. “ON” Command).
Otherwise you create color items and use the fade scheduler I wrote for jython.

88

It should be possible to define a chaser thing (in a .things or via PaperUI) and send new configurations via the control channel (same syntax as used for defining the thing). Please report if this is not working as expected.

1 Like
89

Can you provide a small example? This would really help.

Edit:
I think I got it :slight_smile:

Edit2:
It really works like a charm! You are my hero! Thanks for implementing this! :slight_smile: :+1:

1 Like
90

@Spaceman_Spiff, this was implemented in the first version of the ChaserThing. Maybe we need better documentation.

91

Yea - somehow I seem to have missed it. :frowning:

92

Good news: the binding has been merged into ESH today and will be available shortly.

-jnk

1 Like
93

Thank you so much!

Edit:
@J-N-K: Would it be possible to change the switch to off once the Chaser has run?
The only other possibility to know when it is done is to keep track of the time myself.

94

Hi, great work! Where do I find the documentation? The Link in your first post does not work!