Athens428 Posted October 19, 2017 Share Posted October 19, 2017 Currently having an issue with discovery in my docker. When i have discovery enabled i get the following error: 2017-10-19 15:39:32 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved Traceback (most recent call last): File "/usr/local/lib/python3.6/asyncio/tasks.py", line 182, in _step result = coro.throw(exc) File "/usr/src/app/homeassistant/components/discovery.py", line 127, in scan_devices results = yield from hass.async_add_job(_discover, netdisco) File "/usr/local/lib/python3.6/asyncio/futures.py", line 332, in __iter__ yield self # This tells Task to wait for completion. File "/usr/local/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup future.result() File "/usr/local/lib/python3.6/asyncio/futures.py", line 245, in result raise self._exception File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run result = self.fn(*self.args, **self.kwargs) File "/usr/src/app/homeassistant/components/discovery.py", line 153, in _discover netdisco.scan() File "/usr/local/lib/python3.6/site-packages/netdisco/discovery.py", line 54, in scan self.mdns.start() File "/usr/local/lib/python3.6/site-packages/netdisco/mdns.py", line 21, in start self.zeroconf = zeroconf.Zeroconf() File "/usr/local/lib/python3.6/site-packages/zeroconf.py", line 1670, in __init__ socket.inet_aton(_MDNS_ADDR) + socket.inet_aton(i)) OSError: [Errno 105] No buffer space available If I turn off the discovery component the error goes away. Did I miss something in setup? I am running in host mode with privileges on. Quote Link to comment
mgworek Posted November 2, 2017 Share Posted November 2, 2017 On 2/24/2017 at 6:42 PM, 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 did you have luck with passing USB? I am about to setup Home Assistant but need USB for a device. I could use a Pi3 for it but would rather run it as a docker. Thanks Quote Link to comment
DZMM Posted November 2, 2017 Share Posted November 2, 2017 I'm curious. I'm running home-assistant by adding the docker that comes up when you search in CA: What's the difference between that version and this one? Thanks Quote Link to comment
popwebz Posted November 29, 2017 Share Posted November 29, 2017 I am also having issues with this docker. Auto discovery is not working. Running the docker in br0 removes the error message but because it is a bridge the auto discovery doesn't actually see anything. Have you found a solution yet? On 10/19/2017 at 3:43 PM, Athens428 said: Currently having an issue with discovery in my docker. When i have discovery enabled i get the following error: 2017-10-19 15:39:32 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved Traceback (most recent call last): File "/usr/local/lib/python3.6/asyncio/tasks.py", line 182, in _step result = coro.throw(exc) File "/usr/src/app/homeassistant/components/discovery.py", line 127, in scan_devices results = yield from hass.async_add_job(_discover, netdisco) File "/usr/local/lib/python3.6/asyncio/futures.py", line 332, in __iter__ yield self # This tells Task to wait for completion. File "/usr/local/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup future.result() File "/usr/local/lib/python3.6/asyncio/futures.py", line 245, in result raise self._exception File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run result = self.fn(*self.args, **self.kwargs) File "/usr/src/app/homeassistant/components/discovery.py", line 153, in _discover netdisco.scan() File "/usr/local/lib/python3.6/site-packages/netdisco/discovery.py", line 54, in scan self.mdns.start() File "/usr/local/lib/python3.6/site-packages/netdisco/mdns.py", line 21, in start self.zeroconf = zeroconf.Zeroconf() File "/usr/local/lib/python3.6/site-packages/zeroconf.py", line 1670, in __init__ socket.inet_aton(_MDNS_ADDR) + socket.inet_aton(i)) OSError: [Errno 105] No buffer space available If I turn off the discovery component the error goes away. Did I miss something in setup? I am running in host mode with privileges on. Quote Link to comment
live4soccer7 Posted December 20, 2017 Share Posted December 20, 2017 (edited) I'm trying to get this installed on my unraid install, however everything I've tried results in the following when I go to access the webUI. Any Ideas? I have tried bridged and host connection. Would it be better to just run HA in a linux VM of some sort? This site can’t be reached 192.168.5.150 refused to connect. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_REFUSED Edited December 20, 2017 by live4soccer7 Quote Link to comment
shremi Posted January 8, 2018 Share Posted January 8, 2018 Hey guys i need some assistance regarding this docker maybe someone can point me in the right direction. I have nabaged to install everything and its working. now that i want to edit the config.yaml file i cant seem to get permisions on how to edit the file ..... what are you guys using to edit the file ? and also is there a way to ckeck if the configuration file is ok like via terminal ? i saw a couple of youtube videos but they all used the PI3 so i am a bit lost here . Any help would be appreciated Quote Link to comment
digiblur Posted January 15, 2018 Share Posted January 15, 2018 Been playing with the current HA dockers and it seems to work well.... looking to bridge me SmartThings hub in using this documentation but it looks like I need another docker. https://home-assistant.io/blog/2016/02/09/Smarter-Smart-Things-with-MQTT-and-Home-Assistant/ https://github.com/stjohnjohnson/smartthings-mqtt-bridge Any tips? Quote Link to comment
squirrellydw Posted January 26, 2018 Share Posted January 26, 2018 I got the docker setup and working fine but how do I run this script from my Mac so I can get the 3 files I need to get my Lutron Caseta lights working? https://home-assistant.io/components/lutron_caseta/ Quote Link to comment
squirrellydw Posted February 11, 2018 Share Posted February 11, 2018 can anyone tell me what I need to do to get Floor Plan setup and working with Home Assistant? I tired before but couldn't get it to work. https://github.com/pkozul/ha-floorplan Quote Link to comment
DZMM Posted February 11, 2018 Share Posted February 11, 2018 (edited) 2 hours ago, squirrellydw said: can anyone tell me what I need to do to get Floor Plan setup and working with Home Assistant? I tired before but couldn't get it to work. https://github.com/pkozul/ha-floorplan Copy the files from the instructions into your home-assistant appdata folder e.g. appdata/home-assistant/www and then add the config elemenets to your config file. If you're stuck I'd ask on the HA forum for more help as it's standard HA fare to be honest and not docker/unRAID related. Edited February 11, 2018 by DZMM 1 Quote Link to comment
SeppDK Posted March 13, 2018 Share Posted March 13, 2018 Hi, have anyone gotten google home / google assistant connected to this docker? Quote Link to comment
mkono87 Posted March 18, 2018 Share Posted March 18, 2018 IM also having issues with permissions with the home-assistant folder. im unable to copy my existing contents from my pi HASS to this. How can enable myself to copy over and be able to edit the yaml files? Quote Link to comment
Squid Posted March 18, 2018 Share Posted March 18, 2018 10 hours ago, mkono87 said: IM also having issues with permissions with the home-assistant folder. im unable to copy my existing contents from my pi HASS to this. How can enable myself to copy over and be able to edit the yaml files? Quite often the permissions within any particular application's appdata is not compatible with how unRaid deals with permissions and what doing things over the network expect. You will have no problems however if you copy via the command line. Quote Link to comment
mkono87 Posted March 18, 2018 Share Posted March 18, 2018 4 hours ago, Squid said: Quite often the permissions within any particular application's appdata is not compatible with how unRaid deals with permissions and what doing things over the network expect. You will have no problems however if you copy via the command line. Thanks for your reply squid. so what you're saying is there is no way around it and I have to use cli to edit the yaml files? might as well stick with it on the pi. can you point me in the right direct to using cli on raid to access dockers? please and thank you Quote Link to comment
mgranger Posted March 19, 2018 Share Posted March 19, 2018 This is probably an easy question but I am learning. I have set up home assistant and I have configured Let's Encrypt to give me a cert so that I am able to access Home Assistant using a DDNS however I am not sure how I get my configuration.yaml to point to the cert and key file which reside in the Let's Encrypt container. I tried setting up a Host Path from Home Assistant but I don't think I did this correctly. Quote Link to comment
DZMM Posted March 19, 2018 Share Posted March 19, 2018 46 minutes ago, mgranger said: This is probably an easy question but I am learning. I have set up home assistant and I have configured Let's Encrypt to give me a cert so that I am able to access Home Assistant using a DDNS however I am not sure how I get my configuration.yaml to point to the cert and key file which reside in the Let's Encrypt container. I tried setting up a Host Path from Home Assistant but I don't think I did this correctly. I didn't do anything special in my config.yaml file. In there I've got: base_url: 192.168.30.75:8123 which is the IP of my docker. To get ha at ha.my-domain.com I've got this in a ha file in nginx/site-confs in the LE docker: map $http_upgrade $connection_upgrade { default upgrade; '' close; } server { # Update this line to be your domain server_name ha.MYDOMAIN.com; # These shouldn't need to be changed listen 80 default_server; #listen [::]:80 default_server ipv6only=on; return 301 https://$host$request_uri; } server { # Update this line to be your domain server_name ha.MYDOMAIN.com; # Ensure these lines point to your SSL certificate and key ssl_certificate /config/etc/letsencrypt/live/MYDOMAIN.duckdns.org/fullchain.pem; ssl_certificate_key /config/etc/letsencrypt/live/MYDOMAIN.duckdns.org/privkey.pem; # Use these lines instead if you created a self-signed certificate # ssl_certificate /etc/nginx/ssl/cert.pem; # ssl_certificate_key /etc/nginx/ssl/key.pem; # Ensure this line points to your dhparams file ssl_dhparam /config/nginx/dhparams.pem; # These shouldn't need to be changed listen 443 ssl ; add_header Strict-Transport-Security "max-age=31536000; includeSubdomains"; ssl on; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_ciphers "EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4"; ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; proxy_buffering off; location / { # Update this line to be your HA servers local ip and port proxy_pass http://192.168.30.75:8123; proxy_set_header Host $host; proxy_redirect http:// https://; proxy_http_version 1.1; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $connection_upgrade; } } remember to add ha.yourdomain.com to your subdomains in the LE docker config Quote Link to comment
mgranger Posted March 19, 2018 Share Posted March 19, 2018 (edited) @DZMM I got it to work with your information. I was trying to follow the reverse proxy instructions using https://cyanlabs.net/tutorials/the-complete-unraid-reverse-proxy-duck-dns-dynamic-dns-and-letsencrypt-guide/ however it did not have information to use Home Assistant however when I used something similar for the home assistant line it did not work. I was hoping to be able to use some of these and add home assistant to it however that did't seem to work. Here is the default file from the above guide. upstream backend { server 192.168.1.3:19999; keepalive 64; } server { listen 443 ssl default_server; listen 80 default_server; root /config/www; index index.html index.htm index.php; server_name _; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ssl_prefer_server_ciphers on; client_max_body_size 0; location = / { return 301 /htpc; } location /sonarr { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.3:8989/sonarr; } location /radarr { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.3:7878/radarr; } location /htpc { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.3:8085/htpc; } location /downloads { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.3:8112/; proxy_set_header X-Deluge-Base "/downloads/"; } #PLEX location /web { # serve the CSS code proxy_pass http://192.168.1.3:32400; } # Main /plex rewrite location /plex { # proxy request to plex server proxy_pass http://192.168.1.3:32400/web; } location /nextcloud { include /config/nginx/proxy.conf; proxy_pass https://192.168.1.3:444/nextcloud; } location ~ /netdata/(?<ndpath>.*) { proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass http://backend/$ndpath$is_args$args; proxy_http_version 1.1; proxy_pass_request_headers on; proxy_set_header Connection "keep-alive"; proxy_store off; } } UPDATE: It seemed to work when I brought those locations into @DZMM default above. Edited March 19, 2018 by mgranger Quote Link to comment
DZMM Posted March 19, 2018 Share Posted March 19, 2018 9 minutes ago, mgranger said: UPDATE: It seemed to work when I brought those locations into @DZMM default above. that's not my default file. My default file is where I have my sites that are mydomain.com/nzbget e.g. nzbget.mydomain.com/nzbget. I have a seperate file in the same folder for the sites that are docker.mydomain.com e.g. a file called 'ha' for ha.mydomain.com - that's the file above. I have others e.g. 'nextcloud' for nextcloud.mydomain.com - one file per sub-domain. I'd recommend you set your sites up that way. For the sites that are in your default file, I'd recommend still checking the main LE thread or each docker's support thread to make sure you're happy with the entries. Saying that, I'm sharing my default file as it might help, but I'm no expert here so there are probably errors in here: # listening on port 80 disabled by default, remove the "#" signs to enable # redirect all traffic to https #server { # listen 80; # server_name _; # return 301 https://$host$request_uri; #} # main server block server { listen 443 ssl default_server; root /config/www; index index.html index.htm index.php; server_name _; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ssl_prefer_server_ciphers on; client_max_body_size 0; location / { try_files $uri $uri/ /index.html /index.php?$args =404; } location ~ \.php$ { fastcgi_split_path_info ^(.+\.php)(/.+)$; # With php7-cgi alone: fastcgi_pass 127.0.0.1:9000; # With php7-fpm: #fastcgi_pass unix:/var/run/php7-fpm.sock; fastcgi_index index.php; include /etc/nginx/fastcgi_params; } # calibre-web location /books { proxy_bind $server_addr; proxy_pass http://192.168.30.72:8083; proxy_set_header Host $http_host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Scheme $scheme; proxy_set_header X-Script-Name /books; } # deluge location /deluge { proxy_pass http://192.168.50.73:8112/; proxy_set_header X-Deluge-Base "/deluge/"; } # headphones # location /headphones { # include /config/nginx/proxy.conf; # proxy_pass http://192.168.50.74:8181/headphones; # } # jackett location /jackett/ { rewrite /jackett/(.*) /$1 break; proxy_bind $server_addr; proxy_pass http://192.168.50.78:9117; } # lazy librarian location /lazy { include /config/nginx/proxy.conf; proxy_pass http://192.168.50.79:5299/lazy; } # Lidarr location /lidarr { auth_request /auth-admin; proxy_pass http://192.168.50.69:8686/lidarr; include /config/nginx/proxy.conf; } # nzbget location /nzbget { proxy_pass http://192.168.30.86:6789; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } # nzbhydra location /nzbhydra { include /config/nginx/proxy.conf; proxy_pass http://192.168.50.77:5075/nzbhydra; } # Ombi location /plexrequest { return 301 $scheme://$host/plexrequest/; } location /plexrequest/ { proxy_pass http://192.168.50.87:3579; proxy_set_header Host $host; proxy_set_header X-Forwarded-Host $server_name; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Ssl on; proxy_set_header X-Forwarded-Proto $scheme; proxy_read_timeout 90; proxy_redirect http://192.168.50.87:3579 https://$host; } if ($http_referer ~* /plexrequest/) { rewrite ^/dist/(.*) $scheme://$host/plexrequest/dist/$1 permanent; } # PLEX location /web { # serve the CSS code proxy_pass http://192.168.30.90:32400; } location /plex { # proxy request to plex server proxy_pass http://192.168.30.90:32400/web; } # Radarr location /radarr { include /config/nginx/proxy.conf; proxy_pass http://192.168.50.92:7878/radarr; } # Sonarr location /sonarr { include /config/nginx/proxy.conf; proxy_pass http://192.168.50.95:8989/sonarr; } # tautulli location /tautulli { proxy_pass http://192.168.50.91:8181; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } } # sample reverse proxy config without url base, but as a subdomain "cp", ip and port same as above # notice this is a new server block, you need a new server block for each subdomain #server { # listen 443 ssl; # # root /config/www; # index index.html index.htm index.php; # # server_name cp.*; # # ssl_certificate /config/keys/letsencrypt/fullchain.pem; # ssl_certificate_key /config/keys/letsencrypt/privkey.pem; # ssl_dhparam /config/nginx/dhparams.pem; # ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; # ssl_prefer_server_ciphers on; # # client_max_body_size 0; # # location / { # auth_basic "Restricted"; # auth_basic_user_file /config/nginx/.htpasswd; # include /config/nginx/proxy.conf; # proxy_pass http://192.168.1.50:5050; # } #} Quote Link to comment
mgranger Posted March 19, 2018 Share Posted March 19, 2018 Well I am not even an amateur on this. Is there a good place to read up more on this. All I have right now is a duckdns. I do have my own domain though but have never set that up for websites although I don't know if this is possible to set up for websites/letsencrypt. I would like to figure this out but not sure where to start. I am sure this is outside the scope of this forum but would take any advice on where to start. Quote Link to comment
daemian Posted April 11, 2018 Share Posted April 11, 2018 I have been working on setting up various components of this for some time now, now I am suddenly running into this issue where the docker runs for a while, and then I go to use soemthing I have setup in there and it doesnt work. I go into unraid and it turns out the docker is stopped. I don't know why or what happened. I think it must be the app crashing, but perhaps its an unraid thing? I have numerous other dockers running without issues. here is the log from the Docker: [32m2018-04-09 17:25:43 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room to 172.17.0.4 (auth: False)[0m [31m2018-04-09 17:25:44 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting[0m [32m2018-04-09 17:25:44 INFO (MainThread) [homeassistant.core] Bus:Handling <Event system_log_event[L]: timestamp=1523312744.138154, level=ERROR, message=Timer got out of sync. Resetting, exception=, source=core.py>[0m [32m2018-04-09 17:25:46 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room to 172.17.0.4 (auth: False)[0m [32m2018-04-09 17:25:46 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room_2 to 172.17.0.4 (auth: False)[0m [33m2018-04-09 17:25:56 WARNING (SyncWorker_24) [homeassistant.components.switch.tplink] Could not read state for TP-Link Switch: Communication error[0m [32m2018-04-09 17:25:56 INFO (MainThread) [homeassistant.core] Bus:Handling <Event system_log_event[L]: timestamp=1523312756.2240956, level=WARNING, message=Could not read state for TP-Link Switch: Communication error, exception=, source=components/switch/tplink.py>[0m [32m2018-04-09 17:26:01 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room_2 to 172.17.0.4 (auth: False)[0m [32m2018-04-09 17:26:01 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room to 172.17.0.4 (auth: False)[0m [32m2018-04-09 17:26:20 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room to 172.17.0.4 (auth: False)[0m [32m2018-04-09 17:26:21 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room_2 to 172.17.0.4 (auth: False)[0m [32m2018-04-09 17:26:21 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room_2 to 172.17.0.4 (auth: False)[0m [32m2018-04-09 17:26:22 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room to 172.17.0.4 (auth: False)[0m [33m2018-04-09 17:26:27 WARNING (SyncWorker_37) [homeassistant.components.switch.tplink] Could not read state for TP-Link Switch: Communication error[0m [32m2018-04-09 17:26:27 INFO (MainThread) [homeassistant.core] Bus:Handling <Event system_log_event[L]: timestamp=1523312787.199906, level=WARNING, message=Could not read state for TP-Link Switch: Communication error, exception=, source=components/switch/tplink.py>[0m [32m2018-04-09 17:26:41 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room to 172.17.0.4 (auth: False)[0m [32m2018-04-09 17:26:41 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room_2 to 172.17.0.4 (auth: False)[0m [32m2018-04-09 17:26:41 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room_2 to 172.17.0.4 (auth: False)[0m [32m2018-04-09 17:26:42 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room to 172.17.0.4 (auth: False)[0m [33m2018-04-09 17:26:58 WARNING (SyncWorker_33) [homeassistant.components.switch.tplink] Could not read state for TP-Link Switch: Communication error[0m [32m2018-04-09 17:26:58 INFO (MainThread) [homeassistant.core] Bus:Handling <Event system_log_event[L]: timestamp=1523312818.239955, level=WARNING, message=Could not read state for TP-Link Switch: Communication error, exception=, source=components/switch/tplink.py>[0m [32m2018-04-09 17:26:58 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room to 172.17.0.4 (auth: False)[0m [32m2018-04-09 17:26:59 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room_2 to 172.17.0.4 (auth: False)[0m [32m2018-04-09 17:27:04 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room_2 to 172.17.0.4 (auth: False)[0m [32m2018-04-09 17:27:05 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room to 172.17.0.4 (auth: False)[0m [31m2018-04-09 17:27:05 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting[0m [32m2018-04-09 17:27:05 INFO (MainThread) [homeassistant.core] Bus:Handling <Event system_log_event[L]: timestamp=1523312825.4261618, level=ERROR, message=Timer got out of sync. Resetting, exception=, source=core.py>[0m [32m2018-04-09 17:27:15 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room to 172.17.0.4 (auth: False)[0m [32m2018-04-09 17:27:15 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room_2 to 172.17.0.4 (auth: False)[0m [32m2018-04-09 17:27:16 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room_2 to 172.17.0.4 (auth: False)[0m [32m2018-04-09 17:27:16 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room to 172.17.0.4 (auth: False)[0m [33m2018-04-09 17:27:28 WARNING (SyncWorker_30) [homeassistant.components.switch.tplink] Could not read state for TP-Link Switch: Communication error[0m [32m2018-04-09 17:27:28 INFO (MainThread) [homeassistant.core] Bus:Handling <Event system_log_event[L]: timestamp=1523312848.5120802, level=WARNING, message=Could not read state for TP-Link Switch: Communication error, exception=, source=components/switch/tplink.py>[0m [32m2018-04-09 17:27:33 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room_2 to 172.17.0.4 (auth: False)[0m [32m2018-04-09 17:27:34 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room to 172.17.0.4 (auth: False)[0m [32m2018-04-09 17:27:34 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room_2 to 172.17.0.4 (auth: False)[0m [32m2018-04-09 17:27:35 INFO (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.living_room to 172.17.0.4 (auth: False)[0m [31m2018-04-09 17:27:35 ERROR (SyncWorker_29) [miio.device] failed to send msg: [Errno 9] Bad file descriptor[0m [33m2018-04-09 17:27:35 WARNING (SyncWorker_29) [homeassistant.components.vacuum.xiaomi_miio] Got exception while fetching the state: [0m [32m2018-04-09 17:27:35 INFO (MainThread) [homeassistant.core] Bus:Handling <Event system_log_event[L]: timestamp=1523312855.6656325, level=ERROR, message=failed to send msg: [Errno 9] Bad file descriptor, exception=, source=components/vacuum/xiaomi_miio.py>[0m Any ideas what might be happening? Thanks! Quote Link to comment
mgranger Posted April 11, 2018 Share Posted April 11, 2018 Are there supposed to be python packages with Home Assistant in Unraid. I looked at my deps/lib/python3.6 folder is something I added for my Sony TV. When I used home assistant prior to unraid there were a lot more folders in here. I copied my files over however did not copy the python folder over which was 3.5. I thought this would populate automatically however nothing is showing up. I am getting errors for my honeywell thermostat and myq garage door and a chromecast and I was wondering if it was related to not having these python files. Quote Link to comment
CorneliousJD Posted April 14, 2018 Share Posted April 14, 2018 I'm having some trouble with this container also. I want to use the letsencrypt container to do a reverse proxy on this so I can access from outside, however the issue I'm running into is whether in bridge or host mode, HomeAssistant can never see any of my devices, and can only be seen if I put it into br0 mode and give it its own IP address. I have tried privilege on/off in bridge/host most but it cannot auto-discover my devices still. Is there a way to get this to work without assigning it a separate IP? Once I do that I lose access to allow my letsencrypt container to do a reverse proxy, unless I go back and reconfigure a bunch of containers... Oof. Quote Link to comment
CorneliousJD Posted April 14, 2018 Share Posted April 14, 2018 28 minutes ago, CorneliousJD said: I'm having some trouble with this container also. I want to use the letsencrypt container to do a reverse proxy on this so I can access from outside, however the issue I'm running into is whether in bridge or host mode, HomeAssistant can never see any of my devices, and can only be seen if I put it into br0 mode and give it its own IP address. I have tried privilege on/off in bridge/host most but it cannot auto-discover my devices still. Is there a way to get this to work without assigning it a separate IP? Once I do that I lose access to allow my letsencrypt container to do a reverse proxy, unless I go back and reconfigure a bunch of containers... Oof. Looks like OpenVPN-as in Host mode was causing some overlap which made discovery not work at all... Turning off OpenVPN-as and then booting this container up seems to let it run fine. I should probably change OpenVPN to use br0 mode instead of host mode I guess. Quote Link to comment
mgranger Posted April 14, 2018 Share Posted April 14, 2018 (edited) I am having a lot of issues with this container. The honeywell component went seem to stay connected 2018-04-14 09:06:34 WARNING (MainThread) [homeassistant.helpers.condition] Value cannot be processed as a number: 2018-04-14 09:06:34 WARNING (MainThread) [homeassistant.helpers.condition] Value cannot be processed as a number: 2018-04-14 09:06:34 WARNING (MainThread) [homeassistant.helpers.condition] Value cannot be processed as a number: 2018-04-14 09:52:52 ERROR (MainThread) [homeassistant.components.sensor.wunderground] Error fetching WUnderground data: ContentTypeError("0, message='Attempt to decode JSON with unexpected mimetype: '",) 2018-04-14 10:06:43 ERROR (SyncWorker_7) [homeassistant.components.climate.honeywell] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) 2018-04-14 10:16:45 ERROR (SyncWorker_37) [homeassistant.components.climate.honeywell] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) 2018-04-14 10:26:48 ERROR (SyncWorker_34) [homeassistant.components.climate.honeywell] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) 2018-04-14 10:30:19 ERROR (SyncWorker_22) [homeassistant.core] Error doing job: Task was destroyed but it is pending! 2018-04-14 10:30:19 ERROR (SyncWorker_22) [homeassistant.core] Error doing job: Task exception was never retrieved RuntimeError: cannot reuse already awaited coroutine 2018-04-14 10:36:47 ERROR (SyncWorker_16) [homeassistant.components.climate.honeywell] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) 2018-04-14 10:56:51 ERROR (SyncWorker_11) [homeassistant.components.climate.honeywell] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) 2018-04-14 11:06:52 ERROR (SyncWorker_7) [homeassistant.components.climate.honeywell] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) 2018-04-14 11:26:56 ERROR (SyncWorker_36) [homeassistant.components.climate.honeywell] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) 2018-04-14 11:46:33 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.dark_sky_precip_intensity is taking over 10 seconds 2018-04-14 11:46:54 WARNING (MainThread) [homeassistant.components.sensor] Updating darksky sensor took longer than the scheduled update interval 0:00:30 2018-04-14 11:47:00 ERROR (SyncWorker_31) [homeassistant.components.climate.honeywell] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) 2018-04-14 11:51:35 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.pws_precip_today_in is taking over 10 seconds 2018-04-14 11:51:35 ERROR (MainThread) [homeassistant.components.sensor.wunderground] Error fetching WUnderground data: TimeoutError() 2018-04-14 14:00:29 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.pws_feelslike_f is taking over 10 seconds 2018-04-14 14:00:29 ERROR (MainThread) [homeassistant.components.sensor.wunderground] Error fetching WUnderground data: TimeoutError() 2018-04-14 14:36:34 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.pws_temp_high_record_f is taking over 10 seconds 2018-04-14 14:36:34 ERROR (MainThread) [homeassistant.components.sensor.wunderground] Error fetching WUnderground data: TimeoutError() Edited April 14, 2018 by mgranger Quote Link to comment
mgranger Posted April 15, 2018 Share Posted April 15, 2018 (edited) I went back to 0.61.1 and it seems to be working so it must be something changed within the docker which causes the error. Edit: Well i am still getting the error in 0.61.1 however it seems to be less often and the automation seems to still work probably because it doesn't cut out as often and not at the time it was running the automation. Not sure why it seems better in 0.61.1 but it does seem a little better Edited April 16, 2018 by mgranger 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.