-
-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSGiConsole outputs to where thread was started, not in current console window #1545
Comments
The OH3 class is |
Interesting. Can you describe a case with any of the core console commands where this can be reproduced? |
This is currently happening with the Insteon binding |
I am not using Insteon and was hoping for a way to reproduce with a core console command. |
I use very few of the core commands. BTW, this worked just fine when I run it using the eclipse dev env. |
@kaikreuzer, here is a binding that reproduces the issue. The steps you can use to reproduce:
You can enter the command |
The class
org.eclipse.smarthome.io.console.karaf.internal.OSGiConsole
prints to the output stream associated with the thread usingSystem.out.print*
methods. This can cause the results from console commands to potentially get displayed elsewhere. I have encountered this while trying to implement support to configure and monitor Insteon devices. An example of what is happening is:Ideally the output would show up in the console that sent the message. The workaround is to write stdout to a log file and monitor the log file while sending commands to a device. For example I use the following to stat up OH:
/opt/openhab/start.sh server >/opt/openhab/userdata/logs/console.log 2>&1 &
The text was updated successfully, but these errors were encountered: