Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Jan 05, 2014 12:41 pm
It's indeed Linux X86, but same error
Home Automation Domotica Forum Europe, Bwired Forum
Domotica - Home Automation Forum
https://www.domoticaforum.eu/
Opentherm Gateway 4.0 alpha/beta testers wanted
Page 12 of 20
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Jan 05, 2014 12:48 pm
It only starts when running a Xwindows
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Jan 05, 2014 12:49 pm
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.)
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Jan 05, 2014 1:28 pm
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).
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Jan 05, 2014 2:55 pm
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.trie wrote:Do you also have a Linux x86_64 or the raspberry version of this? Then I can get the logging on console as well.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Jan 05, 2014 3:52 pm
You're right, I was also trying to use the dbus... but that gave the same error as otmontior..hvxl wrote:That's a completely different error.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Jan 05, 2014 3:58 pm
hvxl wrote: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
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Jan 05, 2014 4:01 pm
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.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Jan 05, 2014 4:18 pm
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
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
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Jan 05, 2014 5:49 pm
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?hvxl wrote: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.trie wrote:Do you also have a Linux x86_64 or the raspberry version of this? Then I can get the logging on console as well.
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?
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Jan 05, 2014 5:51 pm
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:
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.
Code: Select all
dbus-launch --exit-with-session ./otmonitor --webserver 8085 --daemon &Note: I think dbus-launch was the key, not eval.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Jan 05, 2014 6:03 pm
You can specify several command line options to otmonitor. Use the -o option to specify a logfile, e.g.:trie wrote: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?
./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
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Jan 05, 2014 8:18 pm
Otmonitor is running with the dbus-lauch, but connecting to it with dbus is still not working :hvxl wrote: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:After that you can control otmonitor via dbus, even from another shell running under the same user.Code: Select all
dbus-launch --exit-with-session ./otmonitor --webserver 8085 --daemon &
Note: I think dbus-launch was the key, not eval.
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 X11Code: Select all
Error org.freedesktop.DBus.Error.ServiceUnknown: The name com.tclcode.otmonitor was not provided by any .service filesIs the name com.tclcode.otmonitor setup by otmonitor, or must I configure this manually?
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Jan 05, 2014 11:06 pm
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.
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.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Jan 05, 2014 11:13 pm
unfortunately... 
I will try it on a fresh normal Debian installation.. (now using Voyage debian Linux)
I will try it on a fresh normal Debian installation.. (now using Voyage debian Linux)