Docker Start Commands

[andrelahl]

Hi,
when will you give us those docker commands to use the addon with a manual installation of home assistant? :)
My tests to run the image end in this error message:
raise RuntimeError("Please provide a valid url and token!")
RuntimeError: Please provide a valid url and token!

Best regards and thanks for your awesome work

Andre

[bitmadao]

I am also looking forward to those start commands for docker 👍

In the meantime, I was able to get the image going by passing Environment variables HASSIO_TOKEN and HASS_URL in my docker-compose.

That gets me far enough that I am able to see a "Home Assistant" bridge with the right IP-address in the Bridge pairing menu for Hue Essentials, but I haven't found a way to "Press the push-link button on the bridge."

Anyway, we all thank you for your development efforts!

version: "3.3"
services:
  hassemulatedhue:
    image: marcelveldt/hass-emulated-hue
    container_name: hassemulatedhue
    network_mode: host
    environment:
      HASSIO_TOKEN: "MyLongtermToken"      
      HASS_URL: "https://MyIPAddress:8123/"
    restart: unless-stopped

[alexyao2015]

Sorry for the delay on this one! Seems like notifications on discussions do not work.

There is currently a bug with the latest version, requring -t for entertainment to function. In the future, this will be fixed.

docker run -t -d --network=host -e HASS_TOKEN=abc -e HASS_URL=123 ghcr.io/hass-emulated-hue/core:0.2.0

[alexyao2015]

Make sure the url is accessible from your browser and from within the container. Ensure the port is correct and networking works. Furthermore, read the documentation regarding the home assistant API and ensure it is accessible from the same network and works correctly. I'm leaning toward this being a networking issue more than anything.

[Cyanogenbot]

after some troubleshooting, Nmap has no issues whatsoever when connecting to the port:

my http://192.168.0.218:8123/lovelace/default_view is how i connect to my home assistant from an external source

Starting Nmap 7.70 ( https://nmap.org ) at 2021-04-14 15:19 UTC
Nmap scan report for laptopDocker.lan (192.168.0.218)
Host is up (0.00018s latency).

PORT     STATE SERVICE
8123/tcp open  polipo

Nmap done: 1 IP address (1 host up) scanned in 0.29 seconds```

**another shot at my compose:** ```  hassemulatedhue:
   
    image: hassemulatedhue/core
    container_name: hass-emulated-hue

    network_mode: host
    environment:
      - HASS_URL=http://192.168.0.218:8123
      - HASS_TOKEN=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJhYjVmZjM2MDUwNWY0NDVlYTUzN2UzOTRkN2I2N2U4ZCIsImlhdCI6MTYxODQxMTc4MSwiZXhwIjoxOTMzNzcxNzgxfQ.ghE-uhtWA0QzUoeCWvUjo1nLcoLkBXi_k0XfZvPXSaw
      - DATA_DIR=/config/.emulated-hue
      
    volumes:
      - ./hass-emulated-hue:/config/.emulated-hue
    restart: unless-stopped ```

**and at last the error:** ```[15:17:36] INFO: Starting Emulated Hue...


2021-04-14 15:17:37,188 INFO  emulated_hue.config -- Auto detected listen IP address is 192.168.0.218


2021-04-14 15:17:37,212 ERROR asyncio -- Task exception was never retrieved


future: <Task finished name='Task-1' coro=<run.<locals>.new_coro() done, defined at /usr/local/lib/python3.8/site-packages/aiorun.py:219> exception=CannotConnect('Cannot connect to host 192.168.0.218:8123 ssl:default [Connection refused]')>


Traceback (most recent call last):


  File "/usr/local/lib/python3.8/site-packages/aiohttp/connector.py", line 969, in _wrap_create_connection


    return await self._loop.create_connection(*args, **kwargs)  # type: ignore  # noqa


  File "uvloop/loop.pyx", line 2017, in create_connection


  File "uvloop/loop.pyx", line 1994, in uvloop.loop.Loop.create_connection


ConnectionRefusedError: [Errno 111] Connection refused




The above exception was the direct cause of the following exception:




Traceback (most recent call last):


  File "/usr/local/lib/python3.8/site-packages/hass_client/client.py", line 241, in connect


    self._client = await self._http_session.ws_connect(


  File "/usr/local/lib/python3.8/site-packages/aiohttp/client.py", line 754, in _ws_connect


    resp = await self.request(


  File "/usr/local/lib/python3.8/site-packages/aiohttp/client.py", line 520, in _request


    conn = await self._connector.connect(


  File "/usr/local/lib/python3.8/site-packages/aiohttp/connector.py", line 535, in connect


    proto = await self._create_connection(req, traces, timeout)


  File "/usr/local/lib/python3.8/site-packages/aiohttp/connector.py", line 892, in _create_connection


    _, proto = await self._create_direct_connection(req, traces, timeout)


  File "/usr/local/lib/python3.8/site-packages/aiohttp/connector.py", line 1051, in _create_direct_connection


    raise last_exc


  File "/usr/local/lib/python3.8/site-packages/aiohttp/connector.py", line 1020, in _create_direct_connection


    transp, proto = await self._wrap_create_connection(


  File "/usr/local/lib/python3.8/site-packages/aiohttp/connector.py", line 975, in _wrap_create_connection


    raise client_error(req.connection_key, exc) from exc


aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host 192.168.0.218:8123 ssl:default [Connection refused]




The above exception was the direct cause of the following exception:




Traceback (most recent call last):


  File "/usr/local/lib/python3.8/site-packages/aiorun.py", line 229, in new_coro


    await coro


  File "/app/emulated_hue/__init__.py", line 54, in async_start


    await self._hass.connect()


  File "/usr/local/lib/python3.8/site-packages/hass_client/client.py", line 257, in connect


    raise CannotConnect(err) from err


hass_client.exceptions.CannotConnect: Cannot connect to host 192.168.0.218:8123 ssl:default [Connection refused]```

[alexyao2015]

It seems like there may be an issue with connecting because its on the same device. Try using 127.0.0.1. Its probably easiest to exec into the container using docker exec -it container_name /bin/bash, install curl, and try to determine the correct url to curl the hass api.

[Cyanogenbot]

got an interesting find, my home assistant connection is fine but results in the page loading saying: No WebSocket UPGRADE hdr: None Can "Upgrade" only to "WebSocket".****
seems like a home assistant issue on docker?

[Cyanogenbot]

okay, my bad, that appears to be normal, regardless I tried some more approaches and it doesn't seem to work, every attempt returns the same error as shown above. portainer console has no trouble accessing the api page and it all displays the same as the desktop does

[oleksandr-belei]

[alexyao2015]

This discussion pertains to running it not as a home assistant add-on but as a separate container. If you are in fact using it as a separate container, it's not working because you haven't correctly defined the url. Please create your own discussion if it is unrelated to this.