[support] digiblur's Docker Template Repository


94 posts in this topic Last Reply

Recommended Posts

  • Replies 93
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

With my dive into the Home Automation scene my appetite for additional containers to use on the unRaid server has grown.  All of the templates point to a docker container that I was able to import fro

Thanks, I'll take a look at it.

See my previous post about the UNMS issue

Posted Images

  • 2 weeks later...
  • 2 weeks later...

Hello!

 

I'm trying to get the sub containers of homeassistant_supervisor to be setup with a bridged VLAN, i can't seem to edit settings within the docker tab on unraid.

The hassio_dns has network = default, homeassistant has network = host.

I'd like to set that to br:3, does anyone know how?

 

Also, do i need to change the underlying config?

 

@MikelillOi check this thread 

 

Edited by ezra
Link to post
  • 4 weeks later...

Anyone else having problems with the UNMS docker? It's saying config files are missing for postgres and stuff when I try to use it.

 

postgres: could not access the server configuration file "/config/postgres/postgresql.conf": No such file or directory

 

Looked in the postgres folder and it's completely empty. It's almost like permissions are missing or something..

Edited by Jerky_san
Link to post
2 hours ago, rasmus said:

I wanted to set this up and reverse proxy it through my letsencrypt docker, which works for about a minute and then i get an Error 502.

 

Is this because of the build in nginx proxy?

I think it is because of the nginx proxy proxy on LE because UNMS docker has a built-in nginx proxy as well...I feel like the certificates are fighting against each other?? On my Unraid box, I have nginx proxy manager installed and running great...I use it for the domain name I use as the server for this UNMS container unmx.domain.com and then fwd my ports from nginx proxy manager to the external container ports on the UNMS container. No bueno. 

I'm not getting any postgres errors. What I'm seeing is the exact same thing that @phil1c ran into on the 1st page threads:

 

"HS: ws upgrade response not 101"

I'll let you all know if I can get past it.
 

Link to post
  • 2 weeks later...
On 2/5/2020 at 5:49 PM, muslimsteel said:

Hello, I had the hassio_supervisor docker working yesterday and it seems that they did an update to the docker container and now it will not start. I have tried the small fix with adding the letter in the description to have it repull the container but still do not stay started. These are the lines from the log:


[32m20-02-05 10:37:42 INFO (MainThread) [__main__] Initialize Hass.io setup[0m
[32m20-02-05 10:37:42 INFO (SyncWorker_0) [hassio.docker.supervisor] Attach to Supervisor homeassistant/amd64-hassio-supervisor with version 195[0m

[32m20-02-05 10:37:42 INFO (SyncWorker_0) [hassio.docker.supervisor] Connect Supervisor to Hass.io Network[0m
[32m20-02-05 10:37:42 INFO (SyncWorker_0) [hassio.docker.interface] Cleanup images: [][0m
[32m20-02-05 10:37:43 INFO (MainThread) [__main__] Setup HassIO[0m
[33m20-02-05 10:37:43 WARNING (MainThread) [hassio.dbus.systemd] No systemd support on the host. Host control has been disabled.[0m

[33m20-02-05 10:37:43 WARNING (MainThread) [hassio.dbus.hostname] No hostname support on the host. Hostname functions have been disabled.[0m

[33m20-02-05 10:37:43 WARNING (MainThread) [hassio.dbus.rauc] Host has no rauc support. OTA updates have been disabled.[0m

[33m20-02-05 10:37:43 WARNING (MainThread) [hassio.dbus.nmi_dns] No DnsManager support on the host. Local DNS functions have been disabled.[0m

[32m20-02-05 10:37:43 INFO (MainThread) [hassio.host.apparmor] Load AppArmor Profiles: set()[0m
[32m20-02-05 10:37:43 INFO (MainThread) [hassio.host.apparmor] AppArmor is not enabled on host[0m
[32m20-02-05 10:37:43 INFO (SyncWorker_1) [hassio.docker.interface] Attach to homeassistant/amd64-hassio-dns with version 1[0m

[32m20-02-05 10:37:43 INFO (MainThread) [hassio.misc.forwarder] Start DNS port forwarding to 172.30.32.3[0m
[32m20-02-05 10:37:43 INFO (SyncWorker_1) [hassio.docker.interface] Restart homeassistant/amd64-hassio-dns[0m
[32m20-02-05 10:37:44 INFO (SyncWorker_0) [hassio.docker.interface] Attach to homeassistant/intel-nuc-homeassistant with version 0.104.3[0m

[32m20-02-05 10:37:44 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/core repository[0m
[32m20-02-05 10:37:44 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/git/a0d7b954 repository[0m
[32m20-02-05 10:37:44 INFO (MainThread) [hassio.store] Load add-ons from store: 62 all - 62 new - 0 remove[0m
[32m20-02-05 10:37:44 INFO (MainThread) [hassio.addons] Found 0 installed add-ons[0m
[32m20-02-05 10:37:44 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json[0m

[32m20-02-05 10:37:44 INFO (MainThread) [hassio.snapshots] Found 0 snapshot files[0m
[32m20-02-05 10:37:44 INFO (MainThread) [hassio.discovery] Load 0 messages[0m
[32m20-02-05 10:37:44 INFO (MainThread) [hassio.ingress] Load 0 ingress session[0m
[32m20-02-05 10:37:44 INFO (MainThread) [hassio.secrets] Load Home Assistant secrets: 1[0m
[32m20-02-05 10:37:44 INFO (MainThread) [__main__] Run Hass.io[0m
[32m20-02-05 10:37:44 INFO (MainThread) [hassio.api] Start API on 172.30.32.2[0m
[32m20-02-05 10:37:44 INFO (MainThread) [hassio.supervisor] Update Supervisor to version 198[0m

[32m20-02-05 10:37:44 INFO (SyncWorker_6) [hassio.docker.interface] Update image homeassistant/amd64-hassio-supervisor:195 to homeassistant/amd64-hassio-supervisor:198[0m
[32m20-02-05 10:37:44 INFO (SyncWorker_6) [hassio.docker.interface] Pull image homeassistant/amd64-hassio-supervisor tag 198.[0m
[32m20-02-05 10:37:49 INFO (SyncWorker_6) [hassio.docker.interface] Tag image homeassistant/amd64-hassio-supervisor with version 198 as latest[0m

[32m20-02-05 10:37:49 INFO (SyncWorker_6) [hassio.docker.interface] Stop hassio_supervisor application[0m
[32m20-02-05 10:37:49 INFO (MainThread) [__main__] Stopping Hass.io[0m
[32m20-02-05 10:37:49 INFO (MainThread) [hassio.api] Stop API on 172.30.32.2[0m
[32m20-02-05 10:37:49 INFO (MainThread) [hassio.misc.forwarder] Stop DNS forwarding[0m
[32m20-02-05 10:37:49 INFO (MainThread) [hassio.core] Hass.io is down[0m
[32m20-02-05 10:37:49 INFO (MainThread) [__main__] Close Hass.io[0m

Let me know your thoughts on this. Thanks!

 

I am having the same problem, but even on a fresh install of hassio-supervisor!

Have you solved what to do to make it work?

I am wondering why it is using amd64 code... using Intel Xeon here.

 

It HAS installed some containers, including homeassistant. So I assume that I have to use that homeassistant container in the future instead of my current HA container which is working quite well, correct?

 

Edited by b0m541
Link to post
22 minutes ago, b0m541 said:

 

I am having the same problem, but even on a fresh install of hassio-supervisor!

Have you solved what to do to make it work?

I am wondering why it is using amd64 code... using Intel Xeon here.

 

It HAS installed some containers, including homeassistant. So I assume that I have to use that homeassistant container in the future instead of my current HA container which is working quite well, correct?

 

I'm getting a similar error:

 

[32m20-04-18 14:38:39 INFO (MainThread) [__main__] Initialize Hass.io setup[0m
[32m20-04-18 14:38:39 INFO (SyncWorker_0) [hassio.docker.supervisor] Attach to Supervisor homeassistant/amd64-hassio-supervisor with version 200[0m

[32m20-04-18 14:38:39 INFO (SyncWorker_0) [hassio.docker.supervisor] Connect Supervisor to Hass.io Network[0m
[32m20-04-18 14:38:43 INFO (MainThread) [__main__] Setup HassIO[0m
[33m20-04-18 14:38:43 WARNING (MainThread) [hassio.dbus.systemd] No systemd support on the host. Host control has been disabled.[0m

[33m20-04-18 14:38:43 WARNING (MainThread) [hassio.dbus.hostname] No hostname support on the host. Hostname functions have been disabled.[0m

[33m20-04-18 14:38:43 WARNING (MainThread) [hassio.dbus.rauc] Host has no rauc support. OTA updates have been disabled.[0m

[33m20-04-18 14:38:43 WARNING (MainThread) [hassio.dbus.nmi_dns] No DnsManager support on the host. Local DNS functions have been disabled.[0m

[32m20-04-18 14:38:43 INFO (MainThread) [hassio.host.apparmor] Load AppArmor Profiles: set()[0m
[32m20-04-18 14:38:43 INFO (MainThread) [hassio.host.apparmor] AppArmor is not enabled on host[0m
[32m20-04-18 14:38:43 INFO (MainThread) [hassio.dns] No CoreDNS plugin Docker image homeassistant/amd64-hassio-dns found.[0m
[32m20-04-18 14:38:43 INFO (MainThread) [hassio.dns] Setup CoreDNS plugin[0m
[32m20-04-18 14:38:43 INFO (SyncWorker_0) [hassio.docker.interface] Pull image homeassistant/amd64-hassio-dns tag 1.[0m
[32m20-04-18 14:38:58 INFO (MainThread) [hassio.dns] CoreDNS plugin now installed[0m
[32m20-04-18 14:38:58 INFO (MainThread) [hassio.dns] Start CoreDNS plugin[0m
[32m20-04-18 14:38:58 INFO (MainThread) [hassio.misc.forwarder] Start DNS port forwarding to 172.30.32.3[0m
[32m20-04-18 14:39:10 INFO (SyncWorker_1) [hassio.docker.dns] Start DNS homeassistant/amd64-hassio-dns with version 1 - 172.30.32.3[0m

[32m20-04-18 14:39:10 INFO (MainThread) [hassio.homeassistant] No Home Assistant Docker image homeassistant/intel-nuc-homeassistant found.[0m
[32m20-04-18 14:39:10 INFO (MainThread) [hassio.homeassistant] Setup HomeAssistant landingpage[0m
[32m20-04-18 14:39:10 INFO (SyncWorker_2) [hassio.docker.interface] Pull image homeassistant/intel-nuc-homeassistant tag landingpage.[0m
[32m20-04-18 14:39:27 INFO (MainThread) [hassio.homeassistant] Start HomeAssistant landingpage[0m
[32m20-04-18 14:39:31 INFO (SyncWorker_9) [hassio.docker.homeassistant] Start homeassistant homeassistant/intel-nuc-homeassistant with version landingpage[0m

[32m20-04-18 14:39:36 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance[0m
[32m20-04-18 14:39:37 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/core repository[0m
[32m20-04-18 14:39:37 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/git/a0d7b954 repository[0m
[32m20-04-18 14:39:37 INFO (MainThread) [hassio.store] Load add-ons from store: 62 all - 62 new - 0 remove[0m
[32m20-04-18 14:39:37 INFO (MainThread) [hassio.addons] Found 0 installed add-ons[0m
[32m20-04-18 14:39:37 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json[0m

[32m20-04-18 14:39:37 INFO (MainThread) [hassio.snapshots] Found 0 snapshot files[0m
[32m20-04-18 14:39:37 INFO (MainThread) [hassio.discovery] Load 0 messages[0m
[32m20-04-18 14:39:37 INFO (MainThread) [hassio.ingress] Load 0 ingress session[0m
[32m20-04-18 14:39:37 INFO (MainThread) [hassio.secrets] Load Home Assistant secrets: 0[0m
[32m20-04-18 14:39:37 INFO (MainThread) [__main__] Run Hass.io[0m
[32m20-04-18 14:39:37 INFO (MainThread) [hassio.api] Start API on 172.30.32.2[0m
[32m20-04-18 14:39:37 INFO (MainThread) [hassio.supervisor] Update Supervisor to version 217[0m

[32m20-04-18 14:39:37 INFO (SyncWorker_14) [hassio.docker.interface] Update image homeassistant/amd64-hassio-supervisor:200 to homeassistant/amd64-hassio-supervisor:217[0m
[32m20-04-18 14:39:37 INFO (SyncWorker_14) [hassio.docker.interface] Pull image homeassistant/amd64-hassio-supervisor tag 217.[0m
[32m20-04-18 14:40:54 INFO (SyncWorker_14) [hassio.docker.interface] Tag image homeassistant/amd64-hassio-supervisor with version 217 as latest[0m

[32m20-04-18 14:40:54 INFO (SyncWorker_14) [hassio.docker.interface] Stop hassio_supervisor application[0m
[32m20-04-18 14:40:54 INFO (MainThread) [__main__] Stopping Hass.io[0m
[32m20-04-18 14:40:54 INFO (MainThread) [hassio.api] Stop API on 172.30.32.2[0m
[32m20-04-18 14:40:54 INFO (MainThread) [hassio.misc.forwarder] Stop DNS forwarding[0m
[32m20-04-18 14:40:54 INFO (MainThread) [hassio.core] Hass.io is down[0m
[32m20-04-18 14:40:54 INFO (MainThread) [__main__] Close Hass.io[0m

 

Link to post

I think the problem is that it cannot install HA:

[supervisor.docker.interface] Update image homeassistant/intel-nuc-homeassistant:landingpage to homeassistant/-homeassistant:0.108.6[0m
[32m20-04-18 20:59:40 INFO (SyncWorker_9) [supervisor.docker.interface] Pull image homeassistant/-homeassistant tag 0.108.6.[0m
[31m20-04-18 20:59:40 ERROR (SyncWorker_9) [supervisor.docker.interface] Can't install homeassistant/-homeassistant:0.108.6 -> 400 Client Error: Bad Request ("invalid reference format").[0m
[33m20-04-18 20:59:40 WARNING (MainThread) [supervisor.homeassistant] Error on install Home Assistant. Retry in 30sec[0m

I already replaced homeassistant/intel-nuc-homeassistant with homeassistant/home-assistant but that did not work either.

 

Any ideas?

Link to post
  • 2 weeks later...
On 4/30/2020 at 8:03 PM, ssinseeme said:

I just installed Hassio supervisor and ran with no other editing. I don'tt see the new HASSIO tab in home assistant core?

an other question home do i set up HA with reverse proxy to access from outside.

 

Home Assistant renamed the tab (hass.io) to "Supervisor".

As for a reverse proxy, I had to edit it to point to the IP vs. the Container name to get it to work. Any add-ons you install with Home Assistant you will have to proxy them too as they have different port mappings.

Link to post
On 5/10/2020 at 5:00 AM, Jokerigno said:

Am I wrong or our config (supervisor container on a generic - unraid - linux) will be deprecated?

https://www.home-assistant.io/blog/2020/05/09/deprecating-home-assistant-supervised-on-generic-linux/

Looks like they put it on hold for a little while. 

 

The trick that worked for me, which was mentioned above, regarding the Supervisor container not running was to edit the Supervisor docker in advanced mode and add any letter or anything to the description. I will pull that container again and should restart fine. You may have to restart your HA docker as well. 

 

For now I am going to take daily snapshots in the event we need to switch sometime soon. I don't really want to but if Ihave to I can setup a VM of it and run it that way. Loosing the add-ons and supervisor would really suck. 

Link to post

Yes I will be a pity loose the dockers. In my opinion is easier than a VM.

 

Regarding your trick I use it as well but I noticed that sometimes fails. Moreover every time I backup my appdata and dockers reboot not all cointainer starts in the right sequence. For example I have HA and mqtt running but I have to manually switch on deconz every time 

Link to post
  • 2 weeks later...

SPEEDtest

 

I want to see the tests that have been done without sharing the url.

When I put it like this on the stats page nothing appears:

 

TELEMETRY: true

ENABLE_ID_OBFUSCATION: true

 

 

When I put it this way on the stats page if the results appear but also the url to share the test appears:

 

TELEMETRY: true

ENABLE_ID_OBFUSCATION: false

 

 

Is there a way to view the tests performed but that the url does not appear?

Link to post

Similar problem as of some others. Happens at least twice in 24 hours:

[32m20-05-21 09:55:43 INFO (MainThread) [supervisor.supervisor] Update Supervisor to version 222[0m
[32m20-05-21 09:55:43 INFO (SyncWorker_3) [supervisor.docker.interface] Pull image homeassistant/amd64-hassio-supervisor tag 222.[0m
[32m20-05-21 09:55:45 INFO (MainThread) [supervisor.supervisor] Fetch AppArmor profile https://version.home-assistant.io/apparmor.txt[0m
[32m20-05-21 09:55:46 INFO (MainThread) [supervisor.host.apparmor] Add or Update AppArmor profile: hassio-supervisor[0m
[32m20-05-21 09:55:51 INFO (MainThread) [__main__] Stopping Supervisor[0m
[32m20-05-21 09:55:51 INFO (MainThread) [supervisor.hwmon] Stop Supervisor hardware monitor[0m
[32m20-05-21 09:55:51 INFO (MainThread) [supervisor.api] Stop API on 172.30.32.2[0m
[32m20-05-21 09:55:51 INFO (MainThread) [supervisor.misc.forwarder] Stop DNS forwarding[0m
[32m20-05-21 09:55:51 INFO (MainThread) [supervisor.core] Supervisor is down[0m
[32m20-05-21 09:55:51 INFO (MainThread) [__main__] Close Supervisor[0m
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

The update part is wrong though. The version in the UI is stated to be 223 so I understand why no update happens, but at the very least I'd expect for the container to attempt starting.
I can start manually the supervisor afterwards and it works fine though, but if that goes on, I should be the one called "assistant" ¬¬

Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.