Announcement

Collapse
No announcement yet.

Docker Chromecast audio issue due to URL not being accessible

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Docker Chromecast audio issue due to URL not being accessible

    Hi,

    I have recently changed to using a docker setup and Chromecast has broken. However I can see where it appears to be broken.

    Homeseer HS4 Standard Edition 4.1.11.0 (Linux)
    Mono JIT compiler version 6.12.0.107 (tarball Thu Dec 10 05:28:17 UTC 2020)
    Lan IP 172.17.0.2 (d5f905df362e)

    Plugins:
    Chromecast 4.0.17.0,
    Harmony Hub 3.7.2.0,
    mcsMQTT 5.3.0.4,
    Z-Wave 3.0.2.0

    When I test TTS I get this message

    Playing http://172.17.0.2:80/Chromecast/audio/chromecast20210127221412573.mp3 on Bedroom speaker

    I am unable to play this file because 172.17.0.2 is the internal IP of the container and not externally accessible.

    If I change the IP 172.17.0.2 to the IP of my docker host I can play the audio file.

    Ideally it would be good if somewhere we could specify the IP / hostname that is used and this would fix the problem for anyone behind some kind of proxy device or using docker. This does not appear to be an issue for the HomeSeer UI as it seems to be using relative URLs which allows HS to run on one IP:PORT and have me map it to another with Docker.

    Brad


    #2
    In Setup > Labs > Bind server to IP Address, enter the correct IP address for your HS server, then restart the Chromecast plugin

    Comment


      #3
      Thanks for the response but this doesn't fix the problem. When running under docker using default networking setups, the container gets an IP in a private range (my case 172.17.0.2) that isn't routed onto the host network (my case 192.168.155.X). If you bind the Homeseer server to an IP on the host network (192.168.155.X) that doesn't belong to the container network it will never get the traffic as no traffic destined for 192.168.155.X will ever be delivered to the HomeSeer server. When I had this setup I was unable to even contact the HomeSeer interface.

      The only fixes I can see are attempting to bridge the docker IPs directly onto the LAN, having docker run on a new subnet and then routing between subnets or having URLs return a configurable hostname to use. A configurable hostname would also allow HomeSeer to operate behind other firewall and load balancing setups.

      I was playing with the docker networking, I think it might work but will take a bit of custom network configuration to get working.

      Comment

      Working...
      X