Questions about debug logs for Denon AVR custom driver

[calinatl]

@marktheknife

If I were you I suppose I’d copy and paste both the code that’s on your hub, and the code that’s in whatever thread you’re referring to, into an LLM like ChatGPT or Microsoft Copilot, and then ask it to tell you if the two code snippets are exactly the same or not.

Great idea. I just tried. Both tell the code is too long. Also Chat GPT says suspicious content. I'll just wait for a response over at the other thread. I see they were talking about debug logs a few months ago...

[marktheknife]

Fwiw it seems like you haven’t ruled out the possibility you used HPM to install the driver?

Have you checked here?

That’s from the HPM main menu page.

[calinatl]

Thanks. I had forgotten about that. Apparently I did not use HPM to install the driver. Also based on the discussion on the other thread, I must have copied and pasted from the guy's GitHub link.

ETA: will it mess anything up if a user adds info, within the " " marks of something like the author name to add notes to remind them how they got a driver or program, or is there a better recommendation for how to track this? I know the driver/program save/install date is shown on Apps Code or Drivers Code lists in the Last Modified column, but the source info would be useful. I'd even like to insert a link to the post in this community discussion that led me to the app/driver. Mostly I do HPM but this was one I did not get that way...

[bertabcd1234]

Changing the name or namespace can break things if another app or driver depends on those values (for creating child devices), though that's only a subset of drivers and perhaps not this one.

A safe bet is to put a comment at the top of the file, or really anywhere you want. Comments in Groovy can be made single-line comments that start with // or multi-line comments enclosed by /* and */. You'll probably find some examples in the driver.

[marktheknife]

OP found the thread he was looking for here:

Denon AVR Control Driver. May 2023, new functions

Thanks to all that helped make this but it was not quite finished. Great start. Original Thread: I didn't especially like the lack of options available in the built-in version so, I finished this. I have added: Dynamic Volume Dynamic Range Compression (fixed title) Quick Selects CinemaEQ Changed some input values. Enjoy.

I’m not sure if he’s using @thomas.c.howard’s original driver or the one modified by @abuttino. But there are child devices if the AVR has more than one zone.

It probably doesn’t matter which since @abuttino recently posted in that thread he will be releasing a new version soon, and has already incorporated a feature request to add a debug log toggle to the device UI.

OP should just update to that version when it is released, regardless of which one he’s using right now.