ElectricBrainUK

No that is not normal but killing the process or rebooting your server should fix

That's correct except the discovery prefix should just be homeassistant (without /tower)

Do you have auto discovery enabled in your home assistant mqtt config? And do you have it configured to the same base topic that the unraid api broadcasts on?

That is unusual you shouldn't have to do that, glad it's working now and thanks for letting me know. I'll see if something weird happens with the cookies when you upgrade and try to do it automatically for new users For cpu load and temperature I would recommend glances as it has all this information already and I didn't want to repeat someone else's work!

503 errors suggests that your unraid api can't connect to your unraid host, how is the networking set up? If you're using a custom bridge the docker network can't communicate with the host. Can you access your unraid ui yourself via a web browser? It is also is possible your username configured is not root, or the password you entered was wrong

Ah good news!

Hey, thanks for letting me know It's strange, it could be a couple of things, do you have the mqtt broker configured? The default broker is hassio Otherwise if you have entered hassio as an ip in the ui it might do that The third option is it's a bug but I think I would've noticed myself as I also use pihole, let me double check that though!

Ah right, weird that it can't connect. Are you sure that you can connect to the unraid host? Doing a test from a VM doesn't necessarily mean it will work as it is to do with how the docker engine handles the custom network: I would test using the console in a docker just to be sure if that's okay?

Glad that it is working now - let me know if you need anything else

That is weird, sounds like all should be fine then. Is there a chance the password entered was wrong?

Okay interesting, can you access the unraid ui normally? 503 suggests it's struggling to connect to unraid so it could be a username password thing, it could also happen if the unraid ui was down, or it could happen if you have the api on a bridge with its own ip address and you're trying to connect to the host (unraid network setup doesn't let you do this).

Hi, For the username did you use the root account? Others don't work at the moment.

Thanks, glad you found it useful and could use it to make something even more useful

Hi, I don't maintain or have anything to do with UUD sorry. If the docker containers work in the ui for the unraid api then you will have to ask for support from the UUD guys.

Ah yeah you can kind of do this already, in the burger menu on the left there is manual config where you can disable sections or individual entities

Hey, yeah sorry I will add it in the next update but Im working on a rehaul for the whole application, to improve future rework and performance so it might be another week or two

Glad it's all working for you now! It's a good point, I'll have a think and maybe I'll swap it but I also don't want to break anyone's automations! Thank you as well

That would be great thanks (You can also click the advanced button and do force update if you wanted)

Is that IP for your unraid server or the MQTT Broker? If you have the MQTT broker configured (you can see the devices that are configured in the UI, in the "burger" menu on the left, under manual config, if the MQTT broker is there hit delete and that should remove that from being spammed) If the device is your unraid IP though that could mean the api is struggling to communicate with it, are you using HTTPS, is the docker bridged or does it have its own static IP? Finally I have fixed the bug that caused it to crash when stopping the array - if you update it should be working

Ah okay that's something, it doesn't matter that you are running ha and mqtt on a different host, shouldn't make a difference at all but thanks for the detail. If you restart the unraid api with the ha and mqtt host running it may post all the entities (it should do this on a routine basis as well but if that doesn't work restarting it manually triggers the process). Regarding the array stop I'll have to look into that it seems like you may have found a bug

Ah sure, in that box you enter you unraid details (root and then password) you fill in your mqtt details in the docker configuration

Hey, sure that is odd I've not seen that before. Can you control the server via the unraid apis ui?

Okay sure thanks

Ah yeah that is the standard as most users shouldn't need to change them from the defaults, check here for details if you'd like to change them (you can just press add variable at the bottom): https://github.com/ElectricBrainUK/UnraidAPI/wiki/Docker-installation But seeing as yours are the default it is clearly a problem with the api itself. Do you know the percentage values for your graph? I can't tell if it's a jump in 10% or 50%. Also do you have one server configured or multiple? Cheers

That is quite intense, what is your Cache and Refresh rate at the moment? Ill look into it but in the meantime slowing those down should calm it down. Also cheers for the heads up on the HA thing