While I certainly aim to have bug-free software, the inevitable glitch in computer programming is almost a certainty given enough users and enough time. And so this plugin comes with a couple of features that will help you help me if you do run into a problem.
Here's what works best, assuming your situation allows for this:
1. Turn your file logging to TRACE.
2. Capture the offending behavior.
3. Turn the log file level back to your preferred setting.
4. Download the log file.
5. Zip up the log file.
5. Provide a data dump from your TuneBlade Server.
6. Post your problem.
I'll work with you on the issue, and once resolved, will close the thread.
Thanks in advance for helping me help you!
Here's what works best, assuming your situation allows for this:
1. Turn your file logging to TRACE.
Note that there are 2 log settings: the HomeSeer Log level and the Plugin Log level. For the purposes of me understanding what's happening, I need the Plugin Log (a text file written to your Logs subdirectory under your HS3 installation folder).
If you can't get to that screen because of a problem with startup or the config page itself, you can always disable the plugin, open the plugin's INI file (in the Config subdirectory) and set the value of LogLevelFile to 6, then start the plugin back up.
If you can't get to that screen because of a problem with startup or the config page itself, you can always disable the plugin, open the plugin's INI file (in the Config subdirectory) and set the value of LogLevelFile to 6, then start the plugin back up.
2. Capture the offending behavior.
Make sure you give the plugin time to get started up before you try issuing commands - this insures I'll have the necessary data to see the communication with the TuneBlade server in the log file.
3. Turn the log file level back to your preferred setting.
Turning logging up to TRACE may have an impact on performance, so be sure and turn it back off once you've captured the offending behavior.
4. Download the log file.
You can either copy it from your HS3 Logs directory (HSPI_SKWARE_TUNEBLADE.log) or use the "Download Log File" button on the Plugin's Config page (right below where you change the log level).
5. Zip up the log file.
It could be pretty big, depending on how long you had to run it to catch the problem in the act.
5. Provide a data dump from your TuneBlade Server.
Using the server and port you configured with the plugin, navigate to "http://<server>:<port>/v2" and copy/paste the data you get as a result.
6. Post your problem.
Create a new thread in this forum for your problem, and include the following:
- Plugin version
- Description of the problem
- TuneBlade Server version
- Log file
- Data dump
- The information specified in the forum-wide sticky: Please include System Profile with Posting for Help and Suggestions
I'll work with you on the issue, and once resolved, will close the thread.
Thanks in advance for helping me help you!