Docker Compose help

[bgnzo818]

I was able to get this running using the venv option. However, I would like to run this in docker. I have limited experience with docker-compose, but I do have a few containers running. Whenever I attempt to run in docker, i get an error. I copied the export_mesh file to the config directory and changed the CYNC_MQTT_URL to my mqtt addon running on home assistant along with username and password.

Below is the error. Can someone let me know if I'm missing a step? I'm using the sample docker-compose.yaml file.

[baudneo]

Check your mqtt URL for formatting issues would be my guess.

Alternatively, you can specify CYNC_MQTT_HOST , CYNC_MQTT_USER and CYNC_MQTT_PASS env vars. CYNC_MQTT_PORT defaults to 1883 and CYNC_MQTT_HOST defaults to homeassistant.local

[bgnzo818]

Thanks for the reply. I've tried the URL and host (commenting out the other when not using), but still no luck. Below is my docker compose.

[baudneo]

Kk, let me try a few things here and see if I can reproduce it. Haven't seen that error before and your config looks fine.

[baudneo]

Alright, starting to narrow things down. I can recreate the error, it only happens when using the CYNC_MQTT_* env vars, if you set mqtt_url: in the config file (with or without removing env var), things work. Use that as a workaround for now until I build and push a new image with fixes for env var processing.

I recently changed libraries from amqtt to aiomqtt and something must not be parsing correctly. Should be a fix shortly.

[baudneo]

Pull in the new image (v0.1.7) and things should work using just env vars now as well. If you are in the same directory as your docker compose file for cync lan you can run docker compose pull otherwise, docker pull baudneo/cync-lan:latest

[bgnzo818]

Sorry for the delayed response. I finally got around to doing more testing. After using the latest image, I started getting the following error:

I was using an IP address to my home assistant server as homeassitant.local was not resolving on the server.

CYNC_MQTT_URL: "mqtt://mqtt_user:[email protected]:1883/"

It seems like the IP address is being ignored and only using homeassistant.local as the host. After adding a host record for homeassistant.local to my docker server, i was able to get the docker container up and running. Thanks again for your assistance.

[baudneo]

That's weird, in my testing, everything works as it should. I have no config entries in the config file, am only setting CYNC_MQTT_URL and it is connecting to the broker.
You may need to pull in the newest image and then recreate the container: docker compose pull && docker compose up -d --force-recreate

❯ docker compose up -d --force-recreate && docker compose logs -f --no-log-prefix | bat --style changes,header,rule,snip --paging never -l log
[+] Running 1/1
 ✔ Container cync-lan  Started                                                                                                      0.7s
  STDIN
  12/31/24 11:36:33.110 DEBUG [cync-lan:2204] > CyncLAN: reading devices from exported Cync config file...
  12/31/24 11:36:33.150 DEBUG [cync-lan:2250] > CyncLAN: No MQTT config found in config file, checking ENV vars...
  12/31/24 11:36:33.150 INFO [cync-lan:2252] > CyncLAN: LEGACY CYNC_MQTT_URL set by ENV vars, parsing into its own components (host, port
  , username, password)...
  12/31/24 11:36:33.150 DEBUG [cync-lan:2301] > CyncLAN: Device 'Dimmer - Furnace' (ID: 12) is disabled in config, skipping...
  12/31/24 11:36:33.150 DEBUG [cync-lan:2301] > CyncLAN: Device 'Dimmer - Bsmt Living Room' (ID: 13) is disabled in config, skipping...
  12/31/24 11:36:33.150 DEBUG [cync-lan:2301] > CyncLAN: Device 'Dimmer - Stairs' (ID: 14) is disabled in config, skipping...
  12/31/24 11:36:33.151 DEBUG [cync-lan:2301] > CyncLAN: Device 'Dimmer - Tyler's Desk' (ID: 26) is disabled in config, skipping...
  12/31/24 11:36:33.152 DEBUG [cync-lan:4036] > main: Setting up event loop signal handlers
  12/31/24 11:36:33.154 DEBUG [cync-lan:2059] > CyncServer: Starting, creating SSL context...
  Could not gracefully disconnect: 4. Forcing disconnection.
  12/31/24 11:36:33.157 DEBUG [cync-lan:3494] > mqtt:connect: Connecting to MQTT broker...
  12/31/24 11:36:33.159 INFO [cync-lan:2073] > CyncServer: Started, bound to 0.0.0.0:23779 - Waiting for connections, if you dont see any
  , check your DNS redirection, VLAN and firewall settings.
  12/31/24 11:36:33.161 INFO [cync-lan:3512] > mqtt:connect: Connected to MQTT broker: 10.0.1.20 port: 1883
  12/31/24 11:36:33.161 INFO [cync-lan:3851] > mqtt:hass: Starting device discovery...
  12/31/24 11:36:33.189 DEBUG [cync-lan:3927] > mqtt:hass: Discovery complete
  12/31/24 11:36:33.189 DEBUG [cync-lan:3585] > mqtt:start: Seeding all devices: offline
  12/31/24 11:36:33.209 DEBUG [cync-lan:3603] > mqtt:start: Starting MQTT listener...
  12/31/24 11:36:33.213 DEBUG [cync-lan:3610] > mqtt:rcv: Subscribed to MQTT topics: ['cync_lan/set/#', 'homeassistant/status']. Waiting
  for MQTT messages...

[bgnzo818]

Thanks. As stated, I'm pretty new to this. I have things working now, but I am getting the following warnings. These just continue to repeat. I do seem to have full control of the lights (again, I have the undercabinet lights) through Home Assistant.

cync-lan | 01/02/25 22:22:19.472 WARNING [cync-lan:2960] > 172.16.1.173[1]:parse:x73:mesh: dev_id is 0 when using index: 14, trying index 15 = 1
cync-lan | 01/02/25 22:22:20.121 WARNING [cync-lan:2960] > 172.16.1.107[214]:parse:x73:mesh: dev_id is 0 when using index: 14, trying index 15 = 214
cync-lan | 01/02/25 22:22:20.178 WARNING [cync-lan:2960] > 172.16.1.243[56]:parse:x73:mesh: dev_id is 0 when using index: 14, trying index 15 = 56
cync-lan | 01/02/25 22:22:49.881 WARNING [cync-lan:2960] > 172.16.1.173[1]:parse:x73:mesh: dev_id is 0 when using index: 14, trying index 15 = 1
cync-lan | 01/02/25 22:22:49.902 WARNING [cync-lan:2960] > 172.16.1.107[214]:parse:x73:mesh: dev_id is 0 when using index: 14, trying index 15 = 214
cync-lan | 01/02/25 22:22:49.968 WARNING [cync-lan:2960] > 172.16.1.143[100]:parse:x73:mesh: dev_id is 0 when using index: 14, trying index 15 = 100
cync-lan | 01/02/25 22:22:49.987 WARNING [cync-lan:2960] > 172.16.1.243[56]:parse:x73:mesh: dev_id is 0 when using index: 14, trying index 15 = 56
cync-lan | 01/02/25 22:22:49.996 WARNING [cync-lan:2960] > 172.16.1.231[178]:parse:x73:mesh: dev_id is 0 when using index: 14, trying index 15 = 178
cync-lan | 01/02/25 22:23:21.47 WARNING [cync-lan:2960] > 172.16.1.173[1]:parse:x73:mesh: dev_id is 0 when using index: 14, trying index 15 = 1

[baudneo]

You can safely ignore the warnings, they don't have an effect on anything, just some logging I put in while debugging newer devices that have slightly different data packets.