Use of QLC+ headless: almost but not quite

[Treets]

Hi lighting enthusiasts,

I have a setup at home where QLC+ is running alongside Openhab (home automation) on a Linux server without gui. The scenes are designed under windows and the config file is then copied over to the Linux server. I can trigger QLC+ functions/scenes from openhab via DMX. This is all working remarkably well.

QLC+ has been installed using xvfb as x-server and automatically started using cron.

The only issue now is that after a computer restart I have to manually (via the web interface) change the input universe to <[E.31] 192.168.0.40> because it defaults to <E.31 127.0.0.1>; which does not work.

The output universe (E.31 as well) is defined in the .qxw file but the input universe is not. Adding it to the .qxw file does not do anything.

Does anyone have an idea how to set the output universe to a fixed value? It's the only thing preventing QLC+ flawlessly on a headless system!

[edogawa]

The PDF version of the manual shows "1 Configuration file location" in the TOC, the online version regrettably not...

anyways, input universe mapping is saved to that config file, named $HOME/.config/qlcplus/Q Light Controller Plus.conf in linux.

https://www.qlcplus.org/docs/html_en_EN ... uning.html

[Treets]

Thanks edogawa,
I had not found that config file and it does contain inputmap and outputmap settings. Unfortunately the IP address is not one of them. Here is the whole file:

Code: Select all

[inputmap]
universe0\input=None
universe0\plugin=None
universe0\profile=None
universe1\input=1
universe1\plugin=E1.31
universe1\profile=None

[outputmap]
universe0\feedback=None
universe0\feedbackplugin=None
universe0\output=1
universe0\plugin=E1.31
universe1\feedback=None
universe1\feedbackplugin=None
universe1\output=None
universe1\plugin=None

[workspace]
recent0=/usr/share/qlcplus/autostart.qxw

There does not seem to be a complete parameter list available for the config files, so no idea if an IP address can be added and how the syntax would be.

[mcallegari]

There's no IP address. There's the so called "line number".
In your case it is 1 for input, meaning the second network interface (I guess 0 is loopback)

By the way, a project overrides the global settings. So if you save a project file with the desired IO configuration and then load it with QLC+ it will restore exactly what you want.

[Treets]

Thank you very much!

my project file contained the following line:

Code: Select all

    <Input Plugin="E1.31" Line="0" Profile="Generic DMX input Openhab">

by changing Line="0" into Line="1" the correct interface is used after a reboot, so that's a success.
Thanks again!

[decorideas]

There's no IP address. There's the so called "line number".
In your case it is 1 for input, meaning the second network interface (I guess 0 is loopback)

By the way, a project overrides the global settings. So if you save a project file with the desired IO configuration and then load it with QLC+ it will restore exactly what you want.

thanks mate it worked for me too

[MDAR]

Just to throw in my experience.

I have a similar setup, with the addition of NodeRed on the same machine.

I experienced something similar when I added ZeroTier to the machine for off site access.

ZT added a network interface, at the TOP of the list, so I had to edit my configuration and shift my Universe configuration by One.


I guess the same would apply if moving a configuration from one machine to another, as there's no way to fix the order that an OS assigns the network interfaces (or at least, I'm not aware of it, certainly not between wildly different OS platforms)


I use NotePad++ bulk find and replace as a very quick solution.