[WITHDRAWN] Denon Network AV Receivers

It gets messier.

To determine the input, you need both InputFuncSelect and NetFuncSelect. The formMainZoneXml.xml gives both - eg:

<InputFuncSelect><value>NET</value></InputFuncSelect>
<NetFuncSelect><value>SERVER</value></NetFuncSelect>

But this one doesn’t give mute or volume status, so you also need to query formMainZone_MainZoneXmlStatus.xml - unless there’s another hidden call that does both…

Setting the input function does use PutZoneInputFunction. Oddly, although the media server is NET and SERVER as above, to set it you call MEDIA+SERVER (or MEDIA%20SERVER if you prefer):

index.put.asp?cmd0=PutZone_InputFunction%2FMEDIA%20SERVER

Other inputs are CD, TUNER, SPOTIFY, IRADIO (internet radio), USB and I’d guess IPOD, but that will only work with one attached.

So it might - might - still be possible to do it with a common codebase, calling formMainZone_MainZoneXmlStatus.xml if volume and mute aren’t found in formMainZone_MainZoneXml.xml, but for input selection it looks like a hardcoded lookup table is needed. The power on/off will also have to be varied according to model, unless the Marantz version also works on Denon.

Happy to have a go at editing it, either as a Marantz fork or a change to the existing code.

Hey Sean, I am writing a universal handler for lots of AVRs. If you want to fork this one go for it and I will roll it into the universal one :slight_smile:

@Kristopher dude I just want to say that you are absolutely KILLING IT with these integrations. You make ST better with every code release, thanks so much for all your work here.

1 Like

i love this app and i hope you guys continue building on it. denon/marantz are gonna be huge with the community. thanks.

1 Like

@Kristopher Great work! I have the Device type working with my Denon E400 (power on/off, mute, volume, etc). I am however having a weird issue when trying to tie it to Alexa Helper speaker control. When sending voice commands via the Echo, odd volume inputs are coming in on receiver end. I have tried both modes, -79-18dB and 0-98 with no luck. Any help you may be able to provide would be greatly appreciated

Hi All,

I’ve updated this device to range the volume from 0…100, so the volume acts like a proper dimmer now. Have fun!

Kristopher

1 Like

Sweet! Thanks Kristopher!

I haven’t forgotten this, but lately my ST has been a bit flaky on lights, let alone anything else, so it’s been hard to know if things not working are the code or the ST platform :frowning:

Anyway. new discovery - since the iOS app worked, I thought I’d try and point it at my server and see what it called. It calls goform/DeviceInfo.xml, which gives lots of useful info, including all of the sources (it’s a bit long to post here)

The issue I’ve got now is trying to use hubaction to call multiple xml files and combine the results - I don’t even know if that can be done. At the moment I’m thinking it might be simpler to build an API and have ST talk to my server which then talks to the device. Which also gives me an alternative for when ST is playing up :slightly_smiling:

You can make multiple hubAction calls all at once and then piece them together in parse() using state for temporary data storage. Or you can chain hubAction calls together via parse – eg. make the first hubAction call, then in the parse() method for the first response, store the first response in state and make another hubAction() call for the second command… then when you process the second response you can pull the data out of state and combine the results.

I would love to have my Onkyo TX-NR636 work in ST if you can help. Im no coder but I can test and break any app just ask @Mike_Maxwell

3 Likes

OK, thanks for the tip.

I’ve got it working again on the original code by removing and re-adding the device. Does that have to be done after every change of device handler code?

EDIT: scratch that, I changed the IP of the device and although I changed it in ST it didn’t seem to work until I’d re-added it. Changes to the code are immediate once published.

I still can’t get multiple hubActions working. Wherever I put the second call to hubAction, parse only gets called once.

@Sean_B thanks for continuing to work on this!

1 Like

Right, I’ve got a sort of workable Marantz M-CR610 version. Differences from Kristopher’s original are as follows:

  • Changed the power on/off commands to use standby.

  • Removed the 0.9 multiplier for volume, as the actual value seems to map to the expected volume.

  • Temporarily limited the volume range to 0-30, as I was having issues with clumsy fingers and didn’t want to blow up my speakers :slightly_smiling:

  • Added a hardcoded list of a few functions for test purposes - again, temporary if I can figure out how to get the device capabilities, but this makes the next input button to work.

  • Removed bits that aren’t relevant to this device for clarity (mainly for my own benefit)

It’s far from perfect, but at the moment it’s working for me so I thought I’d post it in case it helps other Marantz users.

Now, a disclaimer and apology to @Kristopher - I am new to Github and the associated etiquette, so for simplicity I’ve set up a new repository under my own account and renamed the file. Please feel free to PM me if I haven’t gone about it the right way.

Anyway, here it is: https://github.com/seanb-uk/marantz-avr

Like I say, new to Github, so if you download this and issue pull requests don’t be surprised if it takes me a while to figure out what to do with them!

EDIT: doh! Figured out the multiple hubAction issue and it’s ridiculously simple - you can return an array of actions… github code and comments above amended accordingly

1 Like

Should the AVR be on wireless network to get the app work? Mine one is on LAN and when trying to configure Button to AV mode the app will not recognize any receiver

Can you connect to it in your web browser? Wireless to wired shouldn’t be an issue. My receiver does not have wireless.

Yes, no problem to connect through web browser.

hey guys, any new work done on this? still holding out hope :slight_smile:

What are you waiting for?

basically more control over zone 2 and input switching based on name. next input can cause problems if you have inputs with constant audio feeds. i need zone 2 control so i can control outdoor system and input switch to pandora/network/radio.

Any updates for onkyo users? I tried searching and keep coming back to this thread