[denonmarantz] Marantz AV-7005 and Denon HEOS 1 not discovered

[jrodvball8]

I am a first time user of OpenHAB. I have openhab2-2.4.0-1 installed on my Ubuntu Server 18.04.1 LTS machine and installed the DenonMarantz Binding 2.4.0.

I have a Marantz AV-7005 and Denon HEOS 1 speaker that cannot be discovered. My system could discover and add Amazon Echos and Philips Hue bulbs. I do not know what to do because I search and see others are able to discover Denon & Marantz products. My OpenHAB server computer can ping and telnet to my Marantz and HEOS 1.

I did read through that document which says it supports any with the web-based controller or Telnet so I charged forward. I can view the AV-7005 using http, telnet, and I have the AVR-Remote app for Android that works great. I think I saw others with the SR-7005 (same electronics as the AV-7005) who have it working.

If the binding polls all real IP addresses in the subnet I would have thought it would pick up my AV-7005 and my HEOS 1. The log does not say it even initiated discovery, though. I manually initiated discovery many times, even rebooted the computer, and it does not do anything.

I started a post in the OpenHAB community and it was thought to open a github issue on the binding.

2019-01-23 21:06:29.008 [DEBUG] [org.openhab.binding.denonmarantz    ] - BundleEvent [unknown:512] - org.openhab.binding.denonmarantz
2019-01-23 21:06:29.090 [DEBUG] [org.openhab.binding.denonmarantz    ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.mdns.MDNSDiscoveryParti$
2019-01-23 21:06:29.100 [DEBUG] [org.openhab.binding.denonmarantz    ] - BundleEvent STARTING - org.openhab.binding.denonmarantz
2019-01-23 21:06:29.105 [DEBUG] [org.openhab.binding.denonmarantz    ] - BundleEvent STARTED - org.openhab.binding.denonmarantz
2019-01-23 21:06:33.981 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2019-01-23 21:06:34.115 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Time zone set to 'America/New_York'.
2019-01-23 21:06:34.133 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Locale set to 'en_US'.
2019-01-23 21:06:34.136 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Measurement system set to 'ImperialUnits'.
2019-01-23 21:06:34.486 [INFO ] [ebuilder.internal.HomeBuilderServlet] - Started Home Builder at /homebuilder
2019-01-23 21:06:39.524 [DEBUG] [org.openhab.binding.denonmarantz    ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}=$
2019-01-23 21:06:51.866 [INFO ] [thome.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2019-01-23 21:06:54.675 [INFO ] [.handler.FlashBriefingProfileHandler] - FlashBriefingProfileHandler initialized
2019-01-23 21:06:56.372 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at http://192.168.1.2:8080
2019-01-23 21:06:56.375 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at https://192.168.1.2:8443
2019-01-23 21:06:57.675 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui

[wborn]

Maybe @jwveldhuis knows why discovery doesn't work for you?

[jwveldhuis]

@jrodvball8 the binding is not scanning all possible IP's in your network, it's using mDNS: the device broadcast their presence and capabilities to the network. In your OS terminal, please check the output of the following: avahi-browse -kvr _raop._tcp (you might need to install the avahi-utils package) and post back the result.

[jwveldhuis]

Even when discovery does not work, you can still add a receiver as a Thing manually in Paper UI and add the details like IP address, port, telnet on/off (off means http is used).

[jrodvball8]

Thank you for the reply! I hope I am not wasting your time; the Amazon Echo and Philips Hue devices discovered right away so I thought something was wrong. I can ping both my AV-7005 and HEOS 1 from my server but nothing is being found:

$ avahi-browse -kvr _raop._tcp
Server version: avahi 0.7; Host name: geonosis.local
E Ifce Prot Name                                          Type                 Domain
: Cache exhausted
: All for now
^CGot SIGINT, quitting.

[jwveldhuis]

@jrodvball8 no problem! Are both receivers turned on? Sometimes you need to enable the network standby in the setup menu? Otherwise it might be a network issue, that somewhere the mDNS/avahi/bonjour packets are getting blocked. Are you using a firewall? Are the receivers connected by cable or through WiFi? Try with cable to diagnose, if it works the WiFi router might be causing the issue. You can Google for “mDNS not working denon” or something like that to search for possible solutions. The binding cannot discover as long as the above command returns nothing.

You could also try avahi-browse -avr to see all devices using mDNS. Maybe that will give a clue. Hue is always connected with a cable so it could be listed there.

And still, manually adding the receivers should still work. Discovery just saves you 1 minute of one time setup ;)

[jrodvball8]

My AV7005 receiver was on and network standby enabled. I tried putting it on the same router, wired, as the server but that did not change anything. The DenonMarantz binding never autodiscovers anything but I am able to manually add it.

That avahi-browse -avr command could not find my AV7005 processor. It could find the Denon HEOS 1 wireless speaker, a wireless Roomba, and several other devices. The AV7005 processor may be in an intermediate stage of network capability. I bought it in 2012 and it supports some network services but not Spotify; maybe my processor does not use mDNS like the modern ones even though it has a web and telnet interface? Anyway, manual seems to work.

I guess the next issue would be why the binding does not discover the Denon HEOS 1 speaker? Is the binding intended to work with those network speakers or just receivers? The command you gave me does see the speaker but the binding discovery does not.

[jwveldhuis]

Ah ok, didn’t realize the AV7005 is such an “old” model, then yes, that model can’t be auto discovered. HEOS speakers are not supported by this “AVR” binding, there is another binding for HEOS though (I don’t have HEOS myself, check the forums for support): https://github.com/Wire82/org.openhab.binding.heos

This issue can be closed then I guess.

[jrodvball8]

Agreed, many thanks!