Disable LogsOff

waynespringer79 · October 2, 2019, 7:36pm

Is there a way to disable the automatic debug logging turning off after 30 minutes?

I have a Chormecast Google Home JBL Link 20 Speaker, that I've been having a clicking noise that starts completely randomly (sometimes days, sometimes hours apart), there is nothing in the general logs that show anything happening during the time at which the clicking noise starts. The only way to get the clicking noise to stop is power cycling the device, or saying something that initiates a long response from "Hey, Google"

Aside from the fact that even with my Chromecast app currently "disabled" the speaker still announces TTS when rules tell it to. I try to turn debug logging on when the clicking noise is already occurring and I'm not seeing anything logged.

I would like to leave this debug logging on this device to see if anything might be logged when the clicking noise starts, but this may be hours between occurrences and not within the 30 minute window, so currently this isn't possible.

bravenel · October 2, 2019, 7:49pm

No, this is an automatic timer shut down of debug logging.

We'll have to scratch our heads a bit about what might be done to allow it to stay on. Although, I somewhat doubt you will discover anything from the logs.

waynespringer79 · October 2, 2019, 7:52pm

You're probably correct, I've tried troubleshooting what's causing this with the tools I have available. It's possible the device just may be defective. It's the randomness that has me completely stumped on it though.

For example, I've been letting it click for over an hour now seeing if it would turn itself off eventually. Just had a TTS come through from a rule running, and now the clicking stopped.

bravenel · October 2, 2019, 8:01pm

It definitely sounds like a device problem. Do you have others?

waynespringer79 · October 2, 2019, 8:06pm

No, the only other "google home" device I have is using the Sonos Integration. Which doesn't have this issue, although there is an occasional random beep sound (the one that google homes make when you say the wake word) but that could be false triggering.

This issue from the JBL Link 20 Google home is like a Metronome clicking every second.

dan.t · October 2, 2019, 8:12pm

Very brute force idea here:

Enable logs
Check the device details for when the job to disable the logs is executed
Right before it get's executed, assign a dummy driver to the device that does nothing and doesn't have logsOff implemented.
Let the scheduled job happen, you see a log message that logsOff wasn't found
Change it back to the real driver

That should keep the logs running

And yes, it is brutal but it works....

waynespringer79 · October 2, 2019, 8:18pm

Any idea of a driver doesn't implement logs off? Won't whenever I change it back to the real driver restart the clock over though?

bravenel · October 2, 2019, 8:19pm

We've never seen a need for it. You can turn them back on easily enough. Debug logs can be very verbose, and just fill logs with lots of uninteresting stuff.

dan.t · October 2, 2019, 8:22pm

Here is a Nothing driver:

github.com

danTapps/Hubitat/blob/master/Drivers/Nothing/Nothing.groovy


metadata {
    definition (name: "Nothing", namespace: "dan.t", author: "Daniel Terryn") {
        capability "Actuator"
        
    }   
}

def installed() {
}

dan.t · October 2, 2019, 8:22pm

It shouldn't... Of course it depends on how it is programmed...

waynespringer79 · October 2, 2019, 8:57pm

It worked, at least now I can further rule out other variables with the issue. Thank You

mike.maxwell · October 2, 2019, 10:46pm

My Google home mini does this too, none of my real Chromecast devices do this...
You won't get any clue to this issue with driver debugging as the issue is hapening on the hardware side, for all I know it's an unknown handled exception of some sort...

waynespringer79 · October 2, 2019, 10:53pm

At least I'm not alone, it's driving me crazy as it just started this about a month and half to 2 months ago, and never seen it before for the first 3-4 months using this on HE.

So does that mean it's not fixable? As I'm at the point to trash the device, but I'd rather keep using it.

mike.maxwell · October 2, 2019, 11:03pm

No idea what the deal is, and there haven't been any changes to the cast integration since I can't remember, probably a year at least.

natemate · October 3, 2019, 12:35am

Is the noise similar to the "tap tap" noise when you change the volume on the Mini?

mike.maxwell · October 3, 2019, 12:51am

It's not a click made from an audio file, it's not intentional. It's the same sound you would get when initially connecting a battery to a small speaker...
Thats why I think it's actually an internal reset of some sort.

Aldo · February 2, 2020, 4:31am

are those LogsOff what this topic talks about? is this issue cause when we have active the option "Enable debug logging" ??

csteele · February 2, 2020, 5:04am

This topic is referencing the standard Hubitat method of disabling Debug messages after 30 mins.

Standard Hubitat drivers have embedded 'log.debug' statements that only output to logs when Enabled. However, the action of clicking 'enable' starts a 30 minute timer that then disables.

The OP was asking if there's a way to extend the time because his 'problem' was taking more than 30 mins to appear.

Your screen capture shows the 30 min timer scheduled for the future.