Something is wrong when I am copying it out of the code
I'll proofed it and it matches my code now.
Any requests for features are welcome.
That fixed it, thanks.
I want to be able to control the Denon from Webcore, but it appears that none of the controls are able to be controlled. Can you add it?
Add it to webcore as an actuator and device
Sorry, I was used to seeing the things that I could control as State Variables. When I did not see them, I thought I could not control it. But I added the device in Webcore as you suggested and it looks like I can control all the variables that are in the GUI boxes from a Webcore piston.
Could you add some status to the Current State on the GUI screen to dynamically display the state of the receiver, like Power On/Off, volume, input, etc?
I'm not sure I understand you. All the states are there in the pull-down to select from. Can you describe what gui you aren't seeing them?
I am about to come out with a major driver update for this and I need to hear your input.
Toggle debug updates is taken care of.
Anything else is welcome.
- Http fall-back is taken care of
- Telnet 'overload' should be taken care of
Telnet overload has been known to stop the AVR from receiving commands from Telnet, altogether.
If you need anything in the API, I can put it in.
I haven't learned child drivers yet.
The release schedule will be beta to release candidate to release.
Until a Denon releases a new telnet protocol and I get that same amp, I don't see many other improvements.
An updated child driver will probably cost a donation though. 
So! Tell me what you want,and, it will be done.
1 Like
This alone sounds pretty awesome 
My Denon Receiver connected to Hubitat using this driver creates 18+ log entries per second when playing music. If there is a way to ID which version of the driver I have, please let me know how.
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?
There does not seem to be a toggle for turning on or off debug, but even if there were, wouldn't that just mask all this traffic? I'd like to reduce this excessive traffic.
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)
What makes you say the traffic is excessive?
There may be very frequent events coming from the AVR but that doesnāt mean itās excessive if thatās how the Denon API is intended to work and things are working as expected.
However you as the user should have the option to turn off debug logging unless you need it to be active for troubleshooting purposes. That would be up to the driver developer to implement.
8+ events per second on the Hubitat, repeatedly every second, from the same device, when I've not set up the device to have such activity, seems excessive to me.
If the Denon API is intended to work that way, I'd like the Hubitat driver to have the ability to either turn that off or have the Hubitat ignore it because that is alot of processing.
However:
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?
8 events per second is a lot for a human to process, but itās not necessarily a problem for a computer.
I think you may be assuming there is some kind of problem here when none exists. It likely has nothing to do with how you personally configured the integration on your hub.
That said, you should be able to turn off debug logging if you donāt want to look at all those debug events in the hub log.
It appears as though @abuttino has already incorporated that change into a new version of the driver that hasnāt been released yet, based on his last post from just a few weeks ago.
ETA: in fact if you had just reviewed some of the prior posts in this thread since the beginning of this year youād see that thereās already been a discussion of this.
The relevant discussion starts here:
My feature request is to add a comment section to the top of the driver code with information about licensing/re-using the code, as well as prior versions of the driver 
.
1 Like
