Closed nworbnhoj closed 2 years ago
It sounds like that the IP 172.30.33.0
isn't guaranteed to be consistent; eg: I might be using this subnet somewhere else in my network, which generally causes Docker to avoid it. I've used RFC 5737 reserved IPs where something is "unknown".
As you probably guessed, I haven't looked at running these containers on hassio
as yet - the C-Bus+HA environment I've looked after has HA running in a Docker container on a non-hassio
Linux distribution, and has other non-HA-related containers running in it.
I'm not sure what to do about this; maybe the answer is to provide images that play nicely with hassio
, but that'll take more effort. 😆
I am new to HA, Docker, MQTT and cmqttd - and yes I am perhaps coming up against some of the challenges that you allude to in running cmqttd containers on hassio. Thank you very much for the work you have dome thus far in implementing a VERY welcome open-source cbus alternative.
I wonder if it might be possible to write a script to query the Docker DNS in order to identify any mqtt brokers on the hassio network, and then to configure cmqttd accordingly before launching? Do you think that this might be an approach worth pursuing?
I've incorporated your suggested change as 1d25bbb. Thanks!
--device /dev/ttyUSB0 is required to bind the serial port on the docker host device --network hassio is the default docker bridge network for Home Assistant