Roku devices not recognized as player entities

[jurgenhaas]

My HA knows my Rokus devices and I can control them with the media player.

But MA doesn't recognize them as player entities, I can only select my VLC players but nothing else. Is there any additional setop I need to take to make that work?

[OzGav]

Please go through the trouble shooting steps here #709 for my player is not showing up or working and let us know what you find

[jurgenhaas]

I went through all that, the IP and URL of my HA instance are correct and I then went to #622 where the first item applies: the Roku device shows in the standard media browser and I can start mp3 with the caveat that the player starts but then also stops playing it. But that seems to be a different issue, see home-assistant/core#83819

But from that, it sounds like the Roku device should be shown in the MA configuration, but it isn't.

[jurgenhaas]

I have updated to b21 and I now see at least some providers, but still no players. The logs show this:

2023-03-30 06:21:45 ERROR music_assistant.websocket_api  -- [139792734593808] Error handling message: CommandMessage(message_id=11, command='config/players', args=None)
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/music_assistant/server/providers/websocket_api/__init__.py", line 219, in _run_handler
    result = handler.target(**args)
             ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/music_assistant/server/controllers/config.py", line 240, in get_player_configs
    for player_id, raw_conf in self.get(CONF_PLAYERS).items()
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'items'

[OzGav]

MA 2 detects players itself. See here for what works out of the box https://github.com/orgs/music-assistant/discussions/710#discussioncomment-3343044

I wasn’t sure if the Roku might appear as a DLNA player?

When MA first starts up the log will show what it can find. The log does get overwritten though and since it is still in beta there is a lot of logging. So keep an eye on it as it first starts up and see if anything is detected.

Not sure about the error I’ll have to check with the devs.

[OzGav]

Looking at a related question on discord. You cant have a firewall sit between MA and your speakers. Note this from the docs “ You must run the docker container with host network mode and the data volume is /data.”

if you are on Discord you can read this which might help https://discord.com/channels/753947050995089438/1088870211719008390/1088875819633487882

[jurgenhaas]

The log output looks like this:

2023-03-30 09:33:44 INFO  music_assistant  -- Starting Music Assistant Server (e908b08bcb0a471ab766c4a61c3e2371) - autodetected IP-address: 192.168.3.58
2023-03-30 09:33:45 INFO  music_assistant.web  -- Starting webserver on port 8095
2023-03-30 09:33:45 INFO  music_assistant.streams  -- Started stream controller (using ffmpeg version 4.3.5 with libsoxr support)
2023-03-30 09:33:45 INFO  music_assistant.providers.lms_cli  -- Registering jsonrpc endpoints on the webserver
2023-03-30 09:33:45 INFO  music_assistant  -- Loaded player provider SONOS
2023-03-30 09:33:45 INFO  music_assistant  -- Loaded metadata provider TheAudioDB Metadata provider
2023-03-30 09:33:45 INFO  music_assistant  -- Loaded music provider URL
2023-03-30 09:33:45 INFO  music_assistant  -- Loaded plugin provider Websocket API
2023-03-30 09:33:45 INFO  music_assistant  -- Loaded metadata provider fanart.tv Metadata provider
2023-03-30 09:33:45 INFO  music_assistant  -- Loaded metadata provider MusicBrainz Metadata provider
2023-03-30 09:33:45 INFO  music_assistant  -- Loaded player provider UPnP/DLNA Player provider
2023-03-30 09:33:45 INFO  music_assistant.providers.lms_cli  -- Starting (telnet) CLI on port 9090
2023-03-30 09:33:45 INFO  music_assistant  -- Loaded player provider Chromecast
2023-03-30 09:33:45 INFO  music_assistant  -- Loaded plugin provider LMS CLI
2023-03-30 09:33:46 INFO  music_assistant.providers.slimproto  -- Starting SLIMProto server on port 3483
2023-03-30 09:33:46 INFO  music_assistant  -- Loaded player provider Slimproto
2023-03-30 09:33:47 INFO  music_assistant  -- Loaded player provider Airplay

and no Roku devices are detected. However, that might be due to the network setup which looks like this:

The host has 2 network adapters, a LAN with IP 192.168.3.58 and a WLAN with IP 192.168.8.16

The Rokus are on a separate WLAN of their own with IPs like 192.168.7.10 - but that .7 WLAN is routable from the host and I can ping all of the Rokus just fine. But may that be a problem for the detection mechanism?

Unfortunately, I currently can't add the host to the same network as the Rokus.

[OzGav]

Yes as I understand it that is the issue. Marcel said in that Discord disussion I linked "it needs to be on the same LAYER 2 network
no layer 3 routing in between" because "discovery protocols work on layer 2". Another user did manage to get it to work but pretty much opened every port between the two networks "... to allow mdns and upnp discovery ? but even then, callback ports are random so it just will not work reliably"

[jurgenhaas]

OK, I grabbed an old notebook and added that to the network of my IOT devices. Started MA b22 and it recognizes 3 of my Chromecasts. But no Rokus recognized. Here is the log output:

2023-03-30 15:33:25 INFO  music_assistant  -- Starting Music Assistant Server (ac74e0bd8ea54d4e87d8907ffda93545) - autodetected IP-address: 192.168.7.66
2023-03-30 15:33:25 INFO  music_assistant.web  -- Starting webserver on port 8095
2023-03-30 15:33:26 INFO  music_assistant.streams  -- Started stream controller (using ffmpeg version 4.3.5 with libsoxr support)
2023-03-30 15:33:26 INFO  music_assistant.providers.lms_cli  -- Registering jsonrpc endpoints on the webserver
2023-03-30 15:33:26 INFO  music_assistant  -- Loaded metadata provider MusicBrainz Metadata provider
2023-03-30 15:33:26 INFO  music_assistant  -- Loaded plugin provider Websocket API
2023-03-30 15:33:26 INFO  music_assistant  -- Loaded metadata provider TheAudioDB Metadata provider
2023-03-30 15:33:26 INFO  music_assistant  -- Loaded metadata provider fanart.tv Metadata provider
2023-03-30 15:33:26 INFO  music_assistant  -- Loaded player provider UPnP/DLNA Player provider
2023-03-30 15:33:26 INFO  music_assistant  -- Loaded player provider SONOS
2023-03-30 15:33:26 INFO  music_assistant  -- Loaded music provider URL
2023-03-30 15:33:26 INFO  music_assistant  -- Loaded player provider Chromecast
2023-03-30 15:33:26 INFO  music_assistant.providers.lms_cli  -- Starting (telnet) CLI on port 9090
2023-03-30 15:33:26 INFO  music_assistant  -- Loaded plugin provider LMS CLI
2023-03-30 15:33:26 WARNING pychromecast.dial  -- Failed to determine cast type for host <unknown> (<urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:992)>) (services:{ServiceInfo(type='mdns', data='Blaupunkt-PMR100-c7abc6ac7fd179295369c45b16dc3426._googlecast._tcp.local.')})
2023-03-30 15:33:26 WARNING pychromecast.dial  -- Failed to determine cast type for host <unknown> (<urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:992)>) (services:{ServiceInfo(type='mdns', data='Blaupunkt-PMR100-c7abc6ac7fd179295369c45b16dc3426._googlecast._tcp.local.')})
2023-03-30 15:33:26 INFO  music_assistant.players  -- Player registered: c7abc6ac-7fd1-7929-5369-c45b16dc3426/Badezimmer OG
2023-03-30 15:33:26 INFO  music_assistant.players  -- Player registered: fcb25af1-76a7-3133-6725-75bf50f87704/SchlafzimmerA
2023-03-30 15:33:27 INFO  music_assistant.providers.slimproto  -- Starting SLIMProto server on port 3483
2023-03-30 15:33:27 INFO  music_assistant  -- Loaded player provider Slimproto
2023-03-30 15:33:27 WARNING pychromecast.dial  -- Failed to determine cast type for host <unknown> (<urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:992)>) (services:{ServiceInfo(type='mdns', data='Blaupunkt-MR100-7d2ff7695498ffb21bbaccb05d80b79f._googlecast._tcp.local.')})
2023-03-30 15:33:27 WARNING pychromecast.dial  -- Failed to determine cast type for host <unknown> (<urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:992)>) (services:{ServiceInfo(type='mdns', data='Blaupunkt-MR100-7d2ff7695498ffb21bbaccb05d80b79f._googlecast._tcp.local.')})
2023-03-30 15:33:27 INFO  music_assistant.players  -- Player registered: 7d2ff769-5498-ffb2-1bba-ccb05d80b79f/Wohnzimmer Audio
2023-03-30 15:33:28 INFO  music_assistant  -- Loaded player provider Airplay

[OzGav]

Looks like there is some issue with that Blaupunkt device as well. I was hopeful the Rokus may have shown up as DLNA players but looks like no dice. If they have any config options to turn that on you may have some success. Otherwise I will take it away and see if we can add it to the dev roadmap to provide support for them. There has been a separate discussion opened a while ago https://github.com/orgs/music-assistant/discussions/430

[jurgenhaas]

There are actually 2 Blaupunkt devices and the warnings indicate some issues with the SSL certificates. But I just tested, they do work properly with MA and I can actually use them as players without any other issues.

[OzGav]

Just saw this unanswered question. If it is still unresolved there are new options you can try with DLNA devices. If they still don't work then it is unlikely we will find the resources to look at it further.

[jurgenhaas]

Over at HA there is somebody who analysed the traffic between the Roku app and their devices, it looks as if replicating that in other tools isn't that complicated, see home-assistant/core#83819 (comment)