cglatot Posted December 19, 2016 Share Posted December 19, 2016 When you are about to install it (or after you have done so), you just need to make 2 changes to the config: 1. Change "Network Type" to "Bridge" 2. Add a port that points to 8123 in the container Quote Link to comment
tmchow Posted December 31, 2016 Share Posted December 31, 2016 When you are about to install it (or after you have done so), you just need to make 2 changes to the config: 1. Change "Network Type" to "Bridge" 2. Add a port that points to 8123 in the container Thanks for this tip. Installed with no issues and could load Web UI. Quote Link to comment
tmchow Posted December 31, 2016 Share Posted December 31, 2016 Scratch my last comment. If i set network type to "Bridge" instead of "Host", Home Assistant "Discovery" does not work for some reason. None of my devices cannot be discovered like sonos. I had to also remove the port mapping since it's in host mode since it's not necessary. Default port of 8123 works fine to load webui Quote Link to comment
KShips Posted January 12, 2017 Share Posted January 12, 2017 I've setup docker and seems to work well, currently trying to get MySensors working. I have to set a file location (persistence_file: 'path/mysensors3.json'), not sure what I need to specify here to map file to docker home directory? https://home-assistant.io/components/mysensors/#presentation Thanks. Quote Link to comment
PanteraGSTK Posted January 18, 2017 Share Posted January 18, 2017 Love this docker. The more I get used to it the better it gets. However, I'm having an issue with my options.xml that is stored in the container. I need that .xml to contain my secure key for my deadbolt and every time the docker updates it overwrites the file. Is there any way to direct the docker to look for it in the config folder? Quote Link to comment
DZMM Posted January 20, 2017 Share Posted January 20, 2017 can someone help me configure smartthings please. I've installed HA, Mosca and smartthings-mqtt-bridge as per this post https://home-assistant.io/blog/2016/02/09/Smarter-Smart-Things-with-MQTT-and-Home-Assistant/ and I'm seeing ST talking to the bridge in the bridge logs, but my devices aren't appearing in ST: configuration.yaml: mqtt: broker: localhost port: 1883 config.yml mqtt: host: 192.168.1.10 port: 8080 Quote Link to comment
demonspork Posted January 25, 2017 Share Posted January 25, 2017 Love this docker. The more I get used to it the better it gets. However, I'm having an issue with my options.xml that is stored in the container. I need that .xml to contain my secure key for my deadbolt and every time the docker updates it overwrites the file. Is there any way to direct the docker to look for it in the config folder? This issue is resolved in the community.home-assistant.io forums. https://community.home-assistant.io/t/docker-zwave-secure-add-device/5622 Check this out! Quote Link to comment
dave Posted February 8, 2017 Share Posted February 8, 2017 Im curious, with this Docker (or any other Docker where config files are changed), how do you edit your files with a text editor? Obviously vim can be used from terminal, but I'd rather mount my appdata share and use a decent text editor to make changes to config files. What is the best way of doing this? I was getting permission errors sometimes while mounting through SMB. Same question here. Anyone have some tips? Thanks! Quote Link to comment
kal Posted February 19, 2017 Share Posted February 19, 2017 Im curious, with this Docker (or any other Docker where config files are changed), how do you edit your files with a text editor? Obviously vim can be used from terminal, but I'd rather mount my appdata share and use a decent text editor to make changes to config files. What is the best way of doing this? I was getting permission errors sometimes while mounting through SMB. Same question here. Anyone have some tips? Thanks! Give the user rw access chmod 666 configuration.yaml for example Quote Link to comment
dave Posted February 22, 2017 Share Posted February 22, 2017 On 2/19/2017 at 8:33 AM, kal said: Give the user rw access chmod 666 configuration.yaml for example Thanks, that worked! Quote Link to comment
a_n_d_y Posted February 23, 2017 Share Posted February 23, 2017 How do I install an earlier version of this docker? 0.38.4 is giving me trouble. Quote Link to comment
dave Posted February 24, 2017 Share Posted February 24, 2017 5 hours ago, a_n_d_y said: How do I install an earlier version of this docker? 0.38.4 is giving me trouble. Edit the Docker container and change the Repository field to "homeassistant/home-assistant:0.37.3" or whatever version you want. Quote Link to comment
a_n_d_y Posted February 24, 2017 Share Posted February 24, 2017 That did the trick, thank you. Quote Link to comment
indy5 Posted February 24, 2017 Share Posted February 24, 2017 I wanted to poll the group on what people are doing passing through USB devices to this container, more specifically the Aeon Labs ZW090 Z Stick. When testing out this installation in the past, I had issues where the USB port for the device would switch after a reboot of the Unraid server (ie ttyACM0 to ttyACM1). This of course, breaks HA's configuration and requires a change to the config files for the device to function again. Is there any kind of more permanent solution to this case? Is there a way, to force the USB device to always use the same port? I have HA running on a raspberry pi2 at the moment and things are working fine (other than having to use a separate physical device). I would much rather run this app on my Unraid server. I appreciate the feedback and other's experiences. Quote Link to comment
JonathanM Posted February 24, 2017 Share Posted February 24, 2017 1 hour ago, indy5 said: Is there any kind of more permanent solution to this case? Is there a way, to force the USB device to always use the same port? Passing through an entire USB controller instead of the individual device should work. Quote Link to comment
indy5 Posted February 24, 2017 Share Posted February 24, 2017 4 hours ago, jonathanm said: Passing through an entire USB controller instead of the individual device should work. I will give this approach a try, thanks! Out of curiosity, how does passing through the controller vs the specific USB device prevent the issue that I have seen? Thanks for your help Quote Link to comment
JonathanM Posted February 25, 2017 Share Posted February 25, 2017 28 minutes ago, indy5 said: I will give this approach a try, thanks! Out of curiosity, how does passing through the controller vs the specific USB device prevent the issue that I have seen? Thanks for your help Honestly, I was thinking you were talking about a VM, not a docker, but the same principle should apply. Problem is, I'm not sure there is a way to pass an entire controller to a docker. In the case of a VM, when you pass the entire controller then the guest VM assigns the ID to the USB device, and can control it directly. When you rely on the host OS to ID the device, the ID will change, as you found out. I don't know if you can even do what you need in a docker. Quote Link to comment
kstile Posted August 3, 2017 Share Posted August 3, 2017 On 2/24/2017 at 11:50 AM, indy5 said: Is there any kind of more permanent solution to this case? Is there a way, to force the USB device to always use the same port? I have HA running on a raspberry pi2 at the moment and things are working fine (other than having to use a separate physical device). I would much rather run this app on my Unraid server. necro response since this thread came up first on a search for hass Quote Link to comment
bobokun Posted August 17, 2017 Share Posted August 17, 2017 @balloob are there any plans on upgrading the docker container to Hass.io? Quote Link to comment
balloob Posted August 17, 2017 Author Share Posted August 17, 2017 No. I'll leave that to someone else. Quote Link to comment
Living Legend Posted August 29, 2017 Share Posted August 29, 2017 Anyone else have trouble getting this docker to work as host, rather than bridge? If I set as bridge, I can port 8123 over to 8123 and then log in to the Web UI with http://serverip:8123. When I change to host, the same IP no longer works. The log shows everything loading, and most importantly, HASS Discovery doing it's job. But for some reason, I can't access the UI. Quote Link to comment
joeshmoe1 Posted September 4, 2017 Share Posted September 4, 2017 On 8/29/2017 at 9:37 AM, Living Legend said: Anyone else have trouble getting this docker to work as host, rather than bridge? If I set as bridge, I can port 8123 over to 8123 and then log in to the Web UI with http://serverip:8123. When I change to host, the same IP no longer works. The log shows everything loading, and most importantly, HASS Discovery doing it's job. But for some reason, I can't access the UI. It works for me. Is something else using that port? Quote Link to comment
Living Legend Posted September 5, 2017 Share Posted September 5, 2017 On 9/3/2017 at 9:24 PM, joeshmoe1 said: It works for me. Is something else using that port? Well by golly that was it. I had an old Pi still plugged in using port 8123 on a different IP address. I guess this creates a conflict on host mode though. Glad I saw your response. Thanks! Quote Link to comment
kri kri Posted September 24, 2017 Share Posted September 24, 2017 On 8/16/2017 at 8:00 PM, bobokun said: @balloob are there any plans on upgrading the docker container to Hass.io? Would like to see this, I have hass.io running on a raspberry pi but a docker would be sweet. 1 Quote Link to comment
Living Legend Posted October 11, 2017 Share Posted October 11, 2017 (edited) I recently had a problem with one of my z-wave devices. There was an issue that was resolved with updating manufacturer_specific.xml. It looks like this docker is using an older version of this file. For anyone interested, I went into the docker and changed to this location: /usr/local/lib/python3.6/site-packages/python_openzwave/ozw_config and overwrote the file with this: https://github.com/OpenZWave/open-zwave/blob/master/config/manufacturer_specific.xml In my case, it was a Z-Wave Radio Thermostat CT100Plus that was being improperly identified due to an older version of this file not containing the proper product type and ID. Edited October 11, 2017 by Living Legend Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.