Opentherm Gateway 4.0 alpha/beta testers wanted

[sappien]

It's indeed Linux X86, but same error

[sappien]

It only starts when running a Xwindows

[hvxl]

That's a completely different error. Why are you running this as root? That should not be necessary. (You may have to add the user to a special group to allow access to the serial port.)

[hvxl]

Try 4.0b2.2. That doesn't crash in case of dbus problems (of course you won't have dbus control of the application in that case).

[hvxl]

Do you also have a Linux x86_64 or the raspberry version of this? Then I can get the logging on console as well.

You can run the 32-bit linux version on a 64-bit linux platform with 32-bit libraries installed. I have uploaded otmonitor 4.0b2.2 for raspberry pi.

[sappien]

That's a completely different error.

You're right, I was also trying to use the dbus... but that gave the same error as otmontior..

[sappien]

Try 4.0b2.2. That doesn't crash in case of dbus problems (of course you won't have dbus control of the application in that case).

It's working.. Now I've got to figure out why dbus isn't working

[hvxl]

In a next version I can make otmonitor (optionally) use the system dbus instead of the session dbus. But that requires some advanced security configuration on the system that may be a bit too much for the average user.

[sappien]

Code: Select all

dbus-send --print-reply --dest=com.tclcode.otmonitor / com.tclcode.otmonitor.Command :PR=A[/b]

Failed to open connection to "session" message bus: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

When I'm using eval it starts without the Display error

Code: Select all

eval 'dbus-launch --auto-syntax' "dbus-send --print-reply --dest=com.tclcode.otmonitor / com.tclcode.otmonitor.Command :PR=A"

Error org.freedesktop.DBus.Error.ServiceUnknown: The name com.tclcode.otmonitor was not provided by any .service files

Any idea? I've tried creating .service files, but I'm unknown with dbus, so just messing around

[trie]

Do you also have a Linux x86_64 or the raspberry version of this? Then I can get the logging on console as well.

You can run the 32-bit linux version on a 64-bit linux platform with 32-bit libraries installed. I have uploaded otmonitor 4.0b2.2 for raspberry pi.

Great, working now on the RPi which also has the OTGW connected. Unfortunately, the daemon/webinterface does not show logging as you've requested in my other topic about time/date losing. Any other way or do I need the graphical version?

Other question: is there some documentation about the T/B/A/R output and meaning (which code is what and how to interpret the values) of the OTGW? And any documentation of the status bits PS=1 provides?

[hvxl]

OK, that appears to work. I wasn't aware of dbus-launch, but it seems you can use it to start otmonitor with a session dbus:

Code: Select all

dbus-launch --exit-with-session ./otmonitor --webserver 8085 --daemon &

After that you can control otmonitor via dbus, even from another shell running under the same user.

Note: I think dbus-launch was the key, not eval.

[hvxl]

Great, working now on the RPi which also has the OTGW connected. Unfortunately, the daemon/webinterface does not show logging as you've requested in my other topic about time/date losing. Any other way or do I need the graphical version?

Other question: is there some documentation about the T/B/A/R output and meaning (which code is what and how to interpret the values) of the OTGW? And any documentation of the status bits PS=1 provides?

You can specify several command line options to otmonitor. Use the -o option to specify a logfile, e.g.:
./otmonitor -o $(date +otlog-%Y%m%d.txt) --daemon /dev/ttyUSB0

The opentherm messages are decoded by otmonitor. For more details look at the opentherm specification.

The information reported by PS=1 is documented on the web site

[sappien]

OK, that appears to work. I wasn't aware of dbus-launch, but it seems you can use it to start otmonitor with a session dbus:

Code: Select all

dbus-launch --exit-with-session ./otmonitor --webserver 8085 --daemon &

After that you can control otmonitor via dbus, even from another shell running under the same user.

Note: I think dbus-launch was the key, not eval.

Otmonitor is running with the dbus-lauch, but connecting to it with dbus is still not working :

without eval I still get :

Code: Select all

Failed to open connection to "session" message bus: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

with eval :

Code: Select all

Error org.freedesktop.DBus.Error.ServiceUnknown: The name com.tclcode.otmonitor was not provided by any .service files

--edit--

Is the name com.tclcode.otmonitor setup by otmonitor, or must I configure this manually?

[hvxl]

It's hard for me to come up with different suggestions since the previous one worked for me (on a raspberry pi).

You could try:
$ dbus-launch > /tmp/dbusenv
$ ./otmonitor.ahf --daemon --webserver 8085

And then in another session:
$ . /tmp/dbusenv
$ dbus-send --print-reply --dest=com.tclcode.otmonitor / com.tclcode.otmonitor.Command :PR=A

The com.tclcode.otmonitor name doesn't require any manual configuration.

[sappien]

unfortunately...

I will try it on a fresh normal Debian installation.. (now using Voyage debian Linux)