So, auto discovery picked up all my devices, except for one Denon AVR. I have two and one worked fine, not sure why it didn’t see the other. I was going to manually add it to the known_devices.yaml, but oddly I don’t see the working Denon AVR listed. Most of the devices in that file appear to my wireless devices. Is there another file where I am supposed to add it or is there a way to force it’s discovery?
I had to put this in my config yaml
discovery:
enable:
- dlna_dmr
1 Like
Make sure that the Device is powered on and available during Home Assistant startup. I’ve seen sometimes that my Chromecast gets only discovered if it was powered on during HA Startup.
Tried this, but the missing AVR never appeared. However, I now have a duplicate of my one working AVR. My Sonos amp also duplicated. How do I remove the duplicate devices?
One of the first things I tried, unfortunately it did not work. 
Okay, I removed the…
enable:
- dlna_dmr
restarted and the duplicates are now gone. Now just need to get that other AVR up and working.
I am not sure if you have it fixed, but here is my 2 cents.
First of all, make sure you have your configuration properly setup. If you dont mind, paste your configuration here so we can see what is wrong.
Now notice this:
If you have something else using the IP controller for your Denon AVR 3808CI, such as your URC controller, it will not work! There is either a bug or security issue with some models where only one device could be controlling the IP functionality.
Could this be your problem? You dont mention your model, so…
Thanks for the reply, I have still not fixed the issue. I have not input the denonavr platform into my config file, as my 3300w picks up fine with just device discovery. My other denon receiver is a 6300h. Oddly, I am almost positive that it was visible in HA at one time. Here is my config.yaml, minus all login information.
homeassistant:
# Name of the location where Home Assistant is running
name: Home
# Location required to calculate the time the sun rises and sets
latitude:
longitude:
# Impacts weather/sunrise data (altitude above sea level in meters)
elevation:
# metric for Metric, imperial for Imperial
unit_system: imperial
# Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
time_zone:
# Customization file
customize: !include customize.yaml
# Show links to resources in log and frontend
introduction:
# Enables the frontend
frontend:
# Enables configuration UI
config:
http:
# Secrets are defined in the file secrets.yaml
api_password:
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
base_url:
ssl_certificate:
ssl_key:
# Checks for available updates
# Note: This component will send some information about your system to
# the developers to assist with development of Home Assistant.
# For more information, please see:
# https://home-assistant.io/blog/2016/10/25/explaining-the-updater/
updater:
# Optional, allows Home Assistant developers to focus on popular components.
# include_used_components: true
# Discover some devices automatically
discovery:
# Allows you to issue voice commands from the frontend in enabled browsers
conversation:
# Enables support for tracking state changes over time
history:
exclude:
domains:
- group
entities:
- remote.master_bedroom
# View all events in a logbook
logbook:
# Enables a map showing the location of tracked devices
map:
# Track the sun
sun:
# Weather prediction
sensor:
- platform: yr
name: Weather
monitored_conditions:
- temperature
- humidity
- precipitation
- windSpeed
- windDirection
# Text to speech
tts:
- platform: google
# History Recorder
recorder:
purge_keep_days: 7
# Cloud
cloud:
alexa:
filter:
exclude_entities:
- group.nest_protect_entryway
- group.nest_thermostat_kitchen
- group.nest_protect_office
- group.nest_protect_dining_room
- group.nest_protect_hallway
- group.nest_thermostat_master_bedroom
- group.nest_protect_master_bedroom
- group.nest_protect_guest_bedroom
- group.nest_protect_landing
- group.nest_protect_basement
- media_player.denon_avrx3300w
- media_player.kitchen_tv
- media_player.living_room_tv
- media_player.master_bedroom_speaker
- media_player.pool
- media_player.roku__theater
- media_player.un40c6500_samsung_dtv_rcr
- climate.kitchen_first_floor
- climate.master_bedroom_second_floor
exclude_domains:
- group
# Nest
nest:
client_id:
client_secret:
# UniFi
device_tracker:
- platform: unifi
host:
username:
password:
verify_ssl: false
track_new_devices: no
consider_home: 180
detection_time: 150
ssid_filter:
- 'Aperture Science'
- 'Aperture Enrichment Center'
# Apple Homekit
homekit:
# Virtual Sensors
binary_sensor:
- platform: template
sensors:
mary_home:
friendly_name: Mary's Home Virtual Sensor
device_class: door
value_template: >-
{{ is_state('device_tracker.marys_pixel_2', 'home') }}
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yamlI would suggest trying to configure it manually:
media_player:
- platform: denonavr
host: IP_ADDRESS
name: NAME
show_all_sources: True / False
timeout: POSITIVE INTEGER
zones:
- zone: Zone2 / Zone3
name: NAME
I know there is the discovery component, but sometimes for unknown reasons it can fail, like in your situation. Try adding the denonavr component in your configuration and tell us how it goes.
Also, the documentation says your device is not supported… Well… at least it is not in the supported devices. So, I wouldnt expect much.
Configure it manually and you may be lucky. 
Looks like the manual meda_player entry did the trick. It now shows up in HA. Guess I should just disable discovery, create a media_player.yaml file and move everything over.
Hmm wait a minute, I just checked all my media players and I now have a media_player.denon_avrx6300h_2 listed?!? Why is it listed as number 2?
You said in your previous post:
So, here is the first one!
Here is another suggestion: Setup both your Denons manually. Give a different name to both of them and you should be fine.
Also disable them from the auto discovery.
discovery:
ignore:
- denonavr
I think I explained it poorly. Right now I see both Denon receivers. This is with having discovery enabled and manually adding the 6300h. This is what is currently listed…
media_player.denon_avrx3300w
media_player.denon_avrx6300h_2
What I don’t understand is why there is a_2 after the 6300h. Shouldn’t it just be media_player.denon_avr6300h? Or is that just the way HA names entities? If I add another denon receiver will it be media_player.denon_avrXXXX_3?
In that case, it should be.
That is why I suggested to ignore the auto discovery and configure both receivers manually. See what happens then.
Hmm I wonder where the first media_player.denon_avrx6300h is located. Is there anyway to access a database for all known entities> This way I can remove the original and rename the existing one?
Try looking at the .storage folder inside the config directory of HA. I found my KODI media player in the core.entity_registry file.
Okay, so this is weird. In the core.entity_registry file I see the following denon receivers listed…
media_player.denon_avrx6300h
media_player.denon_avrx3300w_2
The registry is showing the wrong receiver with the _2 on the end. In Hassio the 6300h has the _2 added on, in the core.entity_registry it’s the 3300 with the_2 and the 6300 looks fine. No other denons are listed. WTH?
So, played around with the core.entity.registry file today. I don’t understand why, but if I add _2 to the end of the entity ID for the Denon receivers
"entity_id": "media_player.denon_avrx3300w_2",
Hassio shows it as media_player.denon_avrx3300w in the GUI. If I remove the _2 in the core.entity.registry file it shows media_player.denon_avrx3300w_2 in the GUI. I’m at a complete loss for why that would be. Any ideas?
Possible Reason: When my denon avr [X2400H] was working (still having issues getting to work) & added a second Zone on AMP, this added a 2nd Media player & was listed in Hassio with the suffix “_2”
Do you have multiple Zones on your Dennon AVR?