Announcement

Collapse
No announcement yet.

Logging questions

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • nfrobertson
    replied
    Also, to be clear, this only turns off the logging of either humidity or temp updates. The actual HS3 device status changes are unaffected. Thought I'd mention in case the question comes up.

    Leave a comment:


  • claude
    replied
    Originally posted by nfrobertson View Post
    I just posted 3.0.3.5 which includes two new checkboxes on the General config tab so you can turn off Humidity and/or Temp updates. This would allow you to leave INFO level on and selectively turn off those pesky Humidity updates if you want.

    Nathan
    Thanks, works great so far.

    Leave a comment:


  • nfrobertson
    replied
    I just posted 3.0.3.5 which includes two new checkboxes on the General config tab so you can turn off Humidity and/or Temp updates. This would allow you to leave INFO level on and selectively turn off those pesky Humidity updates if you want.

    Nathan

    Leave a comment:


  • nfrobertson
    replied
    I'm tied up with work through the weekend but will see what I can do here soon. Good suggestions.

    Nathan

    Leave a comment:


  • automateme
    replied
    Originally posted by claude View Post
    Hi Nathan,

    As others have mentioned, I too get frequent humidity updates, which for me are not as relevant as program or temperature changes.

    If I uncheck "Info" logging, am I right in assuming I will lose program, humidity and temperature change entries, in effect all 'normal' logging?

    If so, would it be possible to further break down the 'info' reporting, by offering for example, in addition to debug and raw, the following:
    - temperature info
    - humidity info
    - program change info (would target any other normal logging as a group)

    This would be the ideal, but really for me and others I believe, we want to get rid of the humidity change entries. Not so much that it grabs log bytes, but rather that they are noise when searching the log for something.
    Turning off info logging does appear to get rid of all of the status information from the Tstat's. Like you, humidity was adding a lot of entries to my log. With 3 Tstats, my temperature logging was also fairly chatty. That is a great idea to be able to control what info gets logged. I hope that Nathan can make that work.

    Leave a comment:


  • claude
    replied
    Originally posted by nfrobertson View Post
    I just posted version 3.0.3.2 to the updater which has a Config page setting to turn on/off INFO level logging ...
    Hi Nathan,

    As others have mentioned, I too get frequent humidity updates, which for me are not as relevant as program or temperature changes.

    If I uncheck "Info" logging, am I right in assuming I will lose program, humidity and temperature change entries, in effect all 'normal' logging?

    If so, would it be possible to further break down the 'info' reporting, by offering for example, in addition to debug and raw, the following:
    - temperature info
    - humidity info
    - program change info (would target any other normal logging as a group)

    This would be the ideal, but really for me and others I believe, we want to get rid of the humidity change entries. Not so much that it grabs log bytes, but rather that they are noise when searching the log for something.

    Leave a comment:


  • automateme
    replied
    3.0.3.2 working great Nathan, Thanks!

    Leave a comment:


  • automateme
    replied
    Originally posted by nfrobertson View Post
    Do you maybe have the updater_override.txt still in place? I have already updated both my production and development machines using the regular updater process.

    Nathan
    No updater_override, but I just tried from my PC vs. IPad browser and the update is showing up now. Maybe some Safari caching issue.

    Leave a comment:


  • nfrobertson
    replied
    Do you maybe have the updater_override.txt still in place? I have already updated both my production and development machines using the regular updater process.

    Nathan

    Leave a comment:


  • automateme
    replied
    Thanks Nathan! That was quick. It hasn't shown up in the updater yet, but I will install and test as soon as it is available.

    Leave a comment:


  • nfrobertson
    replied
    I just posted version 3.0.3.2 to the updater which has a Config page setting to turn on/off INFO level logging.

    Please install/test when you have time.

    Thanks
    Nathan

    Leave a comment:


  • automateme
    replied
    Originally posted by nfrobertson View Post
    Sure. I hadn't been asked that yet but there's no reason I couldn't put in another INFO checkbox on the config page to turn off that level as well. I'll see what I can work up here soon. Thanks for the suggestion.

    Nathan
    Thanks Nathan. The plugin is working great. Let me know if you want me to test anything.

    Leave a comment:


  • nfrobertson
    replied
    Originally posted by automateme View Post
    Different logging question than this original post but, are there any plans to control the logging level in the plugin? I get tons of entries with three Tstats and a Humidity sensor changing values continuously throughout the day. Debug is there, but maybe an Info setting to get all of these messages or an Error setting to get only errors.

    Sure. I hadn't been asked that yet but there's no reason I couldn't put in another INFO checkbox on the config page to turn off that level as well. I'll see what I can work up here soon. Thanks for the suggestion.

    Nathan

    Leave a comment:


  • automateme
    replied
    Different logging question than this original post but, are there any plans to control the logging level in the plugin? I get tons of entries with three Tstats and a Humidity sensor changing values continuously throughout the day. Debug is there, but maybe an Info setting to get all of these messages or an Error setting to get only errors.

    Leave a comment:


  • nfrobertson
    replied
    Fixed in HS3.0.0.191

    To answer field888's original question. I've been working with Mark Sandler and he with HST. Looks like HS3.0.0.191 or later should fix the "double hit" logging.

    I encountered this myself on my PROD (but not DEV) system. On my PROD system I also run EZFlora which registers as another external device to Mark's Insteon plugin. It seems there was something in HS3 that would cause duplicate messages to be sent by HS3 from Mark's to the other plugins registered with his. I've just done prelim testing on HS3.0.0.191 and it appears to be fixed.

    Nathan

    Leave a comment:

Working...
X