more G-Labs products

Author Topic: Debugging interface plugins  (Read 859 times)

December 09, 2015, 09:52:10 PM
Read 859 times

[email protected]

  • *****
  • Information
  • Hero Member
  • Posts: 271
I have started on creating an interface plugin, and looking at others they look to have Console.Writeline within them..

I am not seeing test output around code that I know is running ok..

How do I need to launch homegenie to see the console output?

at the moment I have just done mono homegenie.exe - are there other params that can be used to filter some noise?

December 09, 2015, 10:57:12 PM
Reply #1

bkenobi

  • *****
  • Information
  • Global Moderator
  • Posts: 1525
running "mono homegenie.exe" is the best way.  What I have done on RPi is to modify the startup.sh file to redirect the primary output to a log file and the error output to /dev/null.  If you do that, you could use tail -f with grep presumably to filter as desired and get real time output.

December 11, 2015, 11:40:18 PM
Reply #2

[email protected]

  • *****
  • Information
  • Hero Member
  • Posts: 271
got this working, then ported the utility class from the zwave interface that uses Nlog and using that to log to the homegenie logs properly, cant help wondering if this should be part of the mig code though :)