Setup

English | Deutsch

Setup

The short version is in the adapter documentation shown inside the admin. This page covers what happens underneath — useful when something does not look the way you expect.

Do I need this page?

Read on if a device was not found, if only part of your receiver shows up, or if you want to understand why the first start takes a while.

What happens on the first start

1. Discovery — the adapter sends a network search (SSDP) and asks every answering device who it is. Devices you entered by hand are started immediately and are never delayed by the search.
2. All three protocols are tried in parallel — YNCA, MusicCast and XML. Whatever answers is used; a protocol that stays silent simply does not appear.
3. The device is asked what it can do. This is the part that takes time on a receiver: the adapter asks it function by function. Expect roughly half a minute on a first contact.
4. The result is remembered per device. The next start uses it, so it is fast. The memory is thrown away by itself when the model or the firmware changes — or when an adapter update changes how the questioning works.

Which protocol is my device using?

Look at <device>.info.transports.* — one flag per protocol, true if it answered:

What you see	What it means
ynca: true only	a network AV receiver, roughly 2010–2020, no MusicCast
ynca: true + yxc: true	a MusicCast AV receiver — the common case from ~2015
yxc: true only	a speaker, soundbar or CD receiver
xml: true only	a receiver from before ~2010
everything false	the device did not answer at all — see Troubleshooting

You never choose a protocol. Each datapoint is served by whichever one reports it best, and a value written by you is routed to the protocol that can actually set it.

Devices that cannot be found automatically

A receiver from before about 2010 does not answer a network search and must be entered by hand with its IP address. The same applies whenever the device sits in a different network segment than ioBroker, because the search does not cross subnet borders.

Give a receiver you enter by hand a fixed address in your router — the adapter cannot follow a typed address. A found device is recognised by its serial number and followed when its address changes.

Found devices, typed devices and the cards

How devices you enter and devices the search finds run side by side, what the setting Search the network for devices does, and what the device cards show and let you edit is part of the setup — it is in the adapter documentation. Underneath, one rule matters: the object id is the device's model and the end of its serial number (rx-v6a-1a2b), decided once and never changed — what you type is the display name, so renaming never costs you datapoints, history or VIS bindings.

The setting "XML query interval (seconds)"

The XML protocol reports no changes on its own, so the adapter asks for them every so often — every 60 seconds by default, adjustable from 30 to 300. On receivers from before 2010 that covers every value; on receivers that also speak YNCA or MusicCast it only covers the few datapoints XML serves, everything else arrives at once.

The network interface setting

This setting decides which network card the search leaves through. If you have several network cards and the search finds nothing, naming the right one here usually fixes it. The MusicCast event port shown next to it is fixed by the protocol and cannot be changed.