Thanks to the great work of others, I was able to acquire a Denon AVR 1912 receiver that connects to Hubitat, which is TERRIFIC. I can make sure the thing is turned from On to Standby when the house shuts down at night which saves electricity, and I can keep the receiver in a remote closet and control it from Hubitat.
Today, for the first time ever, I happened to look at the logs while the receiver is playing and was shocked at the amount of activity the Hubitat is logging while the receiver plays. I presume I have something incorrectly configured, but since I barely got the thing connected, I'm now throughly beyond my expertise. What setting do I need to fix?
Setup:
Hubitat C-7, on 2.4.2.157
Denon AVR 1912, connected to my local network via ethernet. At the router it is not blocked from accessing the internet (maybe it should be??)
Hubitat Devices/ Device Details/ Type is "User" with "Denon AVR Master Device" selected from the dropdown, which I presume means the User (vs native) driver for Denon.
The way I play music is all the CD's are ripped to files copied to an SD card, which is in an old Android phone that takes SD cards. The phone has Kodi on it, which I use to send the music to the receiver.
Here is an image of the Log:
(All of the Debug entries are the AVR-1912; the blacked out entries are where the artist, album or song are reporting on the Hubitat log;
the only other entries are changing lux at a MultiSensor; blacked out part is part of name)
Thank you for responding. The community driver does not appear to have that option...certainly not on the Preferences tab, and I also checked the other tabs...
When I click on driver editor, the top of the driver contains this info: def NAME = "Denon AVR Master Device"; def NAME_SPACE = "Denon AVR"; def TYPE = "Main";
I am fairly sure I downloaded it via HPM, because that is the way I've installed most programs & drivers...but I'm 100% sure that I got it via a link from one of the Denon discussions on this board as that is the ONLY way I get programs & drivers.
(Am I the only person who does not remember exactly how I got something that was installed over a year ago? I really wish Hubitat had a consistent naming convention for the built in drivers & programs vs the community created drivers & programs, as well as a naming convention for both...)
I recall that I tried both the built in driver and the community driver, and the community driver did something that the built in one could not do; I no longer recall exactly what that was...
If you’re looking at the device’s settings page, under the device info tab, built-in drivers will always show up under “system” when you look in the drop down menu for “type.”
User device drivers will be under “user” in the same dropdown menu.
But obviously there is still quite a bit of confusion around this issue.
In addition to what @marktheknife noted:
First, while this forum regularly refers to drivers, there is no data within the device details labeled "Driver." The driver is on the Device Details tab, under "Type." So Hubitat calls a Driver a "Type."
Second, I also know if you select a user created driver, you get a little blue note to the right of "Type" labeled user which you can click on and will take you directly to the driver code. But if you select a Virtual or System driver there is no note detailing that (or link to it for that matter).
Third, the name of the driver is insufficient for people to clearly recognize whether it is a System or Community driver.
This discussion demonstrates the above issues. In my original post, I wrote (verbatim) Hubitat Devices/ Device Details/ Type is "User" with "Denon AVR Master Device" selected from the dropdown
yet those trying to help asked what driver I was using, and if I was using a System or Community Driver. I thought it was clear from my original post, but those who know much more than I do asking made me think I did not properly understand the meaning of the driver info I provided.
It would be clearer to all if there was a naming convention for drivers and apps. There is already a convention for Virtual device; they all start with the word "Virtual". Perhaps system apps and drivers should start with "Hubitat" with the little trademark T, and User created community apps and drivers should start with "User" or "3P" (for 3rd party) or "HPM" if they can be downloaded via HPM, then the year + version + name of the device + the type of device + author.
And I'm still trying to figure out how to stop the Denon receiver from sending 18 messages per second to Hubitat whenever the receiver is on....does anyone have any additional ideas?
There is no link in this case because this does not make sense for built-in drivers. User drivers are custom code you have added to your hub. Their source code is visible to you, and this is what this link points to. Built-in drivers (and apps) are included with the hub software and closed-source.
This can be confusing, but I think less so now that the hub notes this for you.
This detail was probably just missed by whoever asked. There's always a lot of information to go through when dealing with peer-to-peer help like this, so you'll find that once in a while. This information is also fairly new to this location in the UI, so not everyone may know to look for it. Never hurts to provide whatever information you know, however!
Unfortunately, Hubitat cannot control what third parties name their drivers. I think from the above it should be apparent that there are other ways to identify system vs. user drivers (this was not always as easy). That be enough for this concern; otherwise, you'll have to convince all third-party developers to agree on something (and change existing things).
But it sounds like that is only part of this request. Unfortunately, you'll have to know how you got the code, which also seems like part of the issue above. Even if something is in HPM, that is not the only way it can be installed (manually is always an option), and keep in mind that HPM itself is third-party code outside the control of Hubitat. If you forgot, looking in HPM (which can show apps and drivers you've used it to install and often a link to the Community thread on the driver or app) can provide a good starting point; otherwise, you can look at the code itself for the author name or any comments, usually towards the top, that will help you figure it out. A forum search may be particularly helpful for the last thing, or seeing if there's a link to their code (often GitHub) or other clues that can help.
I would figure out where you got the code and see if the developer or fellow users of the driver are willing to provide support (often the case, but, of course, not guaranteed for third-party code; keep this in mind when asking). Often there will be a thread here that you can find with a search, or find via HPM as above if that is how it was installed originally.
It might also just be normal-ish device behavior that you're only noticing because logging is enabled. That does seem like quite a bit of traffic, and I think you're on the right track to see if that can address that and not just cover it up; but fellow users of the device might know what or isn't. Good luck!
No, not really, because I can't find that the driver has a versioning, but there is a thread in which I posted about 11 months ago, so I presume that is the driver I'm using.
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.
That would save you some time vs. comparing what you have on your hub against what’s in the forum thread you might have obtained the code from.
