Just installed UNMS, but when I open the web UI, my browser says "Secure Connection Failed" with code SEC_ERROR_INADEQUATE_KEY_USAGE.

Is it normal that the UNMS container is so bloated?
unms container: 3.67 GB writable: 1.81 GB log: 28.2 MB

 

If not, what can I do to get it back to normal?

 

On 9/2/2020 at 2:02 PM, b0m541 said:

Is it normal that the UNMS container is so bloated?
unms container: 3.67 GB writable: 1.81 GB log: 28.2 MB

 

If not, what can I do to get it back to normal?

 

Add this to extra parameters in the docker config page (you need to click "advanced view")

"--log-opt max-size=10G" without the quotes, this will append the log when it reaches 10Gb. You can set this to what you want though. 

 

It is normal when the log is allowed to grow as it pleases. 

22 hours ago, Abnorm said:

Add this to extra parameters in the docker config page (you need to click "advanced view")

"--log-opt max-size=10G" without the quotes, this will append the log when it reaches 10Gb. You can set this to what you want though. 

 

It is normal when the log is allowed to grow as it pleases. 

This may be normal for this container, I wouldn't call it optimal.

So you are right, the logs count against "Writable" instead of "Log", and actually the logs should be placed in the log folder on appdata...

 

But hey, you get what you pay for and thanks for your help.

 

On 9/10/2020 at 12:33 PM, Abnorm said:

Add this to extra parameters in the docker config page (you need to click "advanced view")

"--log-opt max-size=10G" without the quotes, this will append the log when it reaches 10Gb. You can set this to what you want though. 

 

It is normal when the log is allowed to grow as it pleases. 

how can i prevent this from happening again? Can i export the logs somewhere else?

On 10/1/2020 at 5:35 AM, gbdavidx said:

how can i prevent this from happening again? Can i export the logs somewhere else?

you might be able to reconfigure the log location, adding a location in your variables but you'll need to look into the unms config files i presume. I have not tried it myself, maybe @digiblur have some ideas ? Maybe it would be possible to setup the docker to let us configure log locations ourselves? 

I'm not able to update HomeAssitant Core. It keeps stating that the system is in an unstable state in Supervisor logs. 

But I only see warnings for typical lack of OS support. 

 

Is there anyway to manually update the HomeAssistant Core? 

How do I disable unms 2fa?

Hello

I hope it is alright I post questions about Neolink here, it wasn't specifically mentioned in the topic.
Anyways, I've tried to install Neolink, but I run into a small problem

Unraid 6.9.1 seems to insist that the variable 'neolink_config:' is a directory, but it seems that Neolink expects it to be a file:
 

[2021-04-11T09:13:55Z INFO neolink] Neolink 0.3.0 (unknown commit) release
Error: IoError(Os { code: 21, kind: Other, message: "Is a directory" })

I've tried deleting the directory and making it a config.toml file, but this causes the docker to throw an error "Execution error: bad parameter" and not start at all.

I'm bit at a loss on how to proceed from here, and any help would be greatly appreciated

I am getting a similar error to LeetDonkey, is there a setup step i am missing?  Its not wanting to pickup the config toml i created. 

On 4/19/2021 at 5:41 PM, Dravas said:

I am getting a similar error to LeetDonkey, is there a setup step i am missing?  Its not wanting to pickup the config toml i created. 

I edited the dockerfile to look for the neolink.toml file in a subdirectory rather than /etc/neolink.toml

I don't think this is a good way of doing it since it will no longer follow the thirtythreeforty repository.

Anyways, if you'd like you can simply change the repository to leetdonkey/neolink:

Then change the neolink_config path configuration:

 

then put neolink.toml in /etc/mnt/user/appdata/neolink/ and start the docker.
Note that the container use the name neolink.toml instead of config.toml

If there is a way of linking directly to a file instead of a directory I am not aware of it, but I must confess that I am very new at this docker stuff
 

Edited April 20, 20215 yr by LeetDonkey

ESPHome: Is it possible for the container to update EspHome automaticly when there's a new release?

 

The installed version is 16.2 (2021-02-20).

GitHub latest release is 17.3 (2021-05-09).

zigbee2mqtt: Is it just a case of plugging in a USB coordinator and it'll find it, or is there a process to follow?

The auto-generated config file shows:

 

# Serial settings
serial:
  # Location of CC2531 USB sniffer
  port: /dev/ttyACM0

 

How does unraid pass a USB device to a docker?

Abount ESPHome, I'm currently running it pretty successfully (can flash my devices), but I've noticed a couple of problems:

• I seem to have less gui option than what I see online (maybe it's because it's running via http instead of https?
• colour indicator of the node doesn't work, it's always red (this bug me). Nodes have static ip, they work as intended (and I can OTA them from ESPHome dashboard). I can also ping nodename.local both whithin my LAN from other client, from Unraid console but not from docker console

Thanks for the help

19 hours ago, melagodo said:

I can also ping nodename.local both whithin my LAN from other client, from Unraid console but not from docker console

 

Try this:  Go to settings -> Docker (disable docker) then -> change "Host access to custom networks" to YES, then restart docker.

Edited June 22, 20215 yr by jj_uk

ESPHome:

 

Any idea how to get this to run over https ?  Some features require this.

16 hours ago, jj_uk said:

 

Try this:  Go to settings -> Docker (disable docker) then -> change "Host access to custom networks" to YES, then restart docker.

Tried but still same problem, logs and flashing work beautifully, though

 

13 hours ago, jj_uk said:

ESPHome:

 

Any idea how to get this to run over https ?  Some features require this.

I guess you need a ssl certificate, but this involves reverse proxy and so on, I'm facing the same issue with another docker which requires https (but I want to run it local only).

I think an invalid cert should work, although not sure.

 

I can set this up with a reverse proxy accessible from the internet but like you I want this local only.

 

Hopefully someone will know the answer on how to access the docker over https locally.

Any options to configure the Speedtest docker to use Appdata so we can edit the telemetry settings?  I would love to log the Speedtest results from external users.

@digiblur is it worth including "--restart unless-stopped" in the zigbee2mqtt template or something to that effect. I have TubeZB's POE coordinator and everytime my ubiquiti controller pushes an update across my network, the container stops with "adapter disconnected" in the log.

 

Is there any way zigbee2mqtt can be more resilient? Is that something better managed on the template or with the project itself on github?

 

Thanks! 

On 11/20/2021 at 9:57 AM, bigbangus said:

@digiblur is it worth including "--restart unless-stopped" in the zigbee2mqtt template or something to that effect. I have TubeZB's POE coordinator and everytime my ubiquiti controller pushes an update across my network, the container stops with "adapter disconnected" in the log.

 

Is there any way zigbee2mqtt can be more resilient? Is that something better managed on the template or with the project itself on github?

 

Thanks! 

@digiblurI have the same problem as well. Also, on reboot of the server the container will not autostart either. @bigbanguswere you able to find a solution?

Hello

I am trying to set up zigbee2mqtt but having issues connecting to Web frondend. Both mosquitto broker and zigbee2mqtt has verified the connection.

Frontend have started on 0.0.0.0:8080 and I have forwarded port in docker configuration. I just can't figure out what I am missing....

 

What to do?

 

EDIT: uploaded screenshots

Edited March 6, 20224 yr by thostr
uploaded screenshots

On 3/5/2022 at 1:55 PM, Twinkie0101 said:

@digiblurI have the same problem as well. Also, on reboot of the server the container will not autostart either. @bigbanguswere you able to find a solution?

 

Yeah I just added:  to extra parameters in the docker template. That keeps it alive in case of any issues.

 

Also I added a NodeRed automation to notify my phones through Home Assistant if the docker ever goes down.

 

Also I turned off automatic updates on my Unifi controller because that was the cause of it going down because my z2m is on a POE device from TubeZB.

Not hopeful for a response as it looks like everyones questions are unanswered but here goes!

 

On the TasmoAdmin docker, the notes are "PLEASE Stop this container while not in use and during Tasmota upgrades"

 

My question is why must I stop the docker if I am not using it? I like to look at the info every few days and wonder why I have to manually start the docker each time?

On 3/6/2022 at 5:43 AM, thostr said:

Hello

I am trying to set up zigbee2mqtt but having issues connecting to Web frondend. Both mosquitto broker and zigbee2mqtt has verified the connection.

Frontend have started on 0.0.0.0:8080 and I have forwarded port in docker configuration. I just can't figure out what I am missing....

 

What to do?

 

EDIT: uploaded screenshots

 

 

Try adding this one your yaml.

 

frontend:
port: 9442