I am running 4 zones spread across 2 different receivers.
I have 2 indoor zones that are driven by a Marantz receiver. I was originally using the built-in Denon driver for this. It required a lot of workarounds to control zone 2. I am now using your Denon driver for this and hope to simplify my backend rules since your driver provides direct control over zone 2.
I also have 2 zones outdoors that are driven by a Yamaha receiver. I found a Hubitat Yamaha driver that works.
I am using HD+ for my dashboards and I have created a screen that manages all 4 zones from a single dashboard, as shown in the screenshot below.
Actually, it's not the new driver fault that I didn't see the child apps, it was because of that new self scroll and it was not showing children.
It's not like we are paying for LAN bandwidth. At least give an option to show all children all the time (apps, devices, both)
I put across around 10TB of local data a month on my network and Hubitat wouldn't bog my network down with more text and a few more calls., I don't see a reason it's forced that we need to keep expanding to get children.
I understand it's to reduce clutter, but it introduced new problems.
im new here not really sure im in the right place for this. ive been using denon for years with HEOS. i like it but one thing i dont like is that i cannot put the amp on a dmz and let the client HEOS app connect to it from a different network. Is that something that can be accomplished with this driver?
More audio modes for reporting (I like to know which mode the receiver is in e.g. Atmos, DTS:X, Auro-3D), have "Notifications for Fire TV" and use tasker and webCoRE to send the current audio mode to my TV. Some of these also work to change the receiver mode, some don't, but they all report well.
Does anyone know if this will work with a Denon AVR-1912?
I have an opportunity to switch out my even older receiver with no HDMI to that Denon. But I only want to make this effort if it would actually work with Hubitat.
Yeah, the AVR-1912 is from 2011 and supposedly Denon's Iphone app works with it, but Denon's own Android app does not work with these older models - only 2014 and newer.
Thus, I'm a bit concerned there is something inherent to these that might make connecting it to HE difficult.
Any insight on that?
That would mean I would need to first expend the funds to acquire the Denon AVR-1910, and secondly, expend the time and effort in connecting it to my system. As per my post above:
I only want to make this effort if it would actually work with Hubitat.
If the thing has an IP address, you can almost guarantee it will work.
If you have the chance to try it out before acquisition, just download a telnet app on your phone and connect to the network the Denon is connected to.
If it responds on port 23 (I think) with the telnet app, you can try the commands in my uploaded PDF at the beginning of this thread.
Very easy to do
The prefix and the function is part of the same word.
Sorry I was not clear about not yet owning it. I believe it does have an IP address. Searching the archived manual at Denon.com does not return anything for the phrase "IP control." However, it states the below when searching "IP." I don't know much about this stuff, so do not have a full understanding of what any of this means, but am I correct to gather it will work with HE?
With this unit, it is possible to use the DHCP and Auto IP functions
to make the network settings automatically.
• When using this unit with the broadband router’s DHCP function
enabled, this unit automatically performs the IP address setting and
other settings.
When using this unit connected to a network with no DHCP
function, make the settings for the IP address, etc., at “Network
Setup” (vpage 88).
It also says the following:
• IP Address : Set the IP address within the ranges shown below.
The Network Audio function cannot be used if other IP addresses
are set.
CLASS A: 10.0.0.1 – 10.255.255.254
CLASS B: 172.16.0.1 – 172.31.255.254
CLASS C: 192.168.0.1 – 192.168.255.254
• Subnet Mask : When connecting an xDSL modem or terminal
adapter directly to this unit, input the subnet mask indicated in
the documentation supplied by your provider. Normally input
255.255.255.0.
• Default Gateway : When connected to a gateway (router), input its
IP address.
• Primary DNS, Secondary DNS : If there is only one DNS address
indicated in the documentation supplied by your provider, input it at
“Primary DNS”. If there are two or more DNS addresses, input the
first one at “Secondary DNS”