ABEIDO

Hi Been having issues with UPS clients (servers thats using the UPS) power off when NUT plugin is updating. Am i right to think that changing the Kill UPS Power: Yes to No will solve this?

@Booker First checking if im using correct repo. Im using bokker/unraidapi-re:6.12 and i am again having issues after restarting HA that all sensors goes unavailable and i need restart UnraidApi container to get the sensors working again. Wrote here about but no one else seemed to have this issue. This was fixed before new restart/button updat. So im wondering if im using incorrect repo or something? Also a new issue that ive traced back to UnraidAPI. Whenever this docker is running my Unraid log gets spammed but below. Have had this a while but didnt know what was the source. Other people have talked about it (unknown if they were running UnraidAPI) and said that its most likely it isnt more than logspamm, but it would be nice to not have them. Example: Oct 7 14:14:01 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:14:34 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:15:07 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:15:40 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:16:13 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:16:46 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:17:20 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:17:53 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:18:26 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:18:59 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:19:32 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:20:05 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:20:39 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:21:12 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:21:45 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:22:18 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:22:51 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:23:24 SERVER-NAME monitor: Stop running nchan processes

Yeah theres more integrations with the same issue with naming. Ive never really understood the issue fully more than that entity cannot have the devicename in its name. And i rename everything to fit my naming scheme. With thats said keep it simple and set unraidapi or unraid, short and simple. FYI: When you do update i noticed that parity-check button was misspelled, now we are on a really shallow level of problems :) And regarding the HA restart issue that was back for me (where you need to restart UnraidAPI docker after HA restart), did anyone else notice this or is it something at my setup only?

Hi, that you went with the restart and buttons, awsome to see that the integration grows. Good work Bokker. Im having 2 issues thou: HA Restart bug: But it seems that the HA restart issue is back which you fixed a couple of updates before. When i restart HA the sensors/switches/buttons goes unavailable again. Doubled naming: Same as above that has strange naming on the 5 ”new” button/switch, doubled unraidserver name. button.unraidservername_unraidservername_mover button.unraidservername_unraidservername__partitycheck button.unraidservername_unraidservername__power_off button.unraidservername_unraidservername__reboot switch.unraidservername_unraidservername__array

First off, massive thanks to you Bokker for keeping Unraid-API alive and continue improving the functionality. The last fix that fixed HA reboot issues was really nice. Regarding buttons/switches: I think reboot/shutdown/parity check was seen as button before some updates, i could be wrong thou. And also everything works fine anyway with the switch as it is now. It does what is supposed to and the switch goes to on for a bit then back to off(as it is not a static on or off activity) So it just estetics i my mind, like below from a another mqtt service i use. Here reboot is considered as button and gets press the "Press" in ui. So nothing big on the user end, and its really up to you. Restart Functionality for Unraid API Im trying to find a way to restart UnraidAPI container via HA. As stop/start wont work as stop kills the container and then no more connection. All other containers i can work with stop then start. Is there any way to add a restart for especially unraid-api?

Another reflection i had was the Shutdown, Reboot and Parity Check actions should be set as buttons and not as switches which they are now. Or am i missing something?

I tested it to but and the issues with unavailabe after HA restart seems fixed. What do you mean by that it retains statsus on:true?

@BoKKeR Have you added that all mqtt devices (dockers) ends up under the same device in HA? It seems that everything is moved under the same roof now. i couldnt find any release info abou but if so, awsome job!

Not happening for me atleast.

@Bokker Some nice to haves, just if its possble. Im really glad that you fixed it as it is so everything else is icing on the cake. Restart fix If i restart HA the unraid api devices will go unknown and i need to restart urnaid api docker to get it up and running again. Old problem and not a major issue. Is there something that can be done from Unraid APIs side? Sorting The dockers and vms is own devices under HA MQTT plugin, is it possible to group them under UNRAID mqtt device. I use HASS Agent for windows machines and that adds all sensors and switches under the machine. So my machine called Server gets for examble plex on and off buttons under itself, would be nice to get all dockers switches/sensors under Unraid. Its just less cluttered and is easier to find stuff.

Im not sure this helps, but a while back (on vanilla unraidapi)i had rate limit issues aswell. with similar errors like you. Unraid has authlimit on UI . So it its not just Upnraid API that can affect it. https://github.com/ElectricBrainUK/UnraidAPI/issues/23 https://forums.unraid.net/search/?&q=authlimit&search_and_or=or I tried som of those commands in first link but some other issues occured (so make sure u dont lock your self out as my unraid gui got stuck and i needed to ssh and reset ui via cli) But what solved it for me in the end as i remember was to disable unraid api and wait 24 hours (to clear the auth) and try again, b

For me as it worked when i put bokker/unraidapi-re:6.12 in repository, as Bokker said to me. That is depending on if you run 6.12.x

Its works nicely, and also with Unraid 6.12.3 that was just released. Great work man, BIG thumbs up. For me this is core feature as i use automations to control dockers and now i will also will start using VM controls for that.

Ive been awaiting somekind of a fix and was glad to see you fork it. So thank you for commiting your time to it. Ive replaced it now and i have problems with not beeing able to control anything. Im using lastest Unraid and latest Homeassistant. Also tried resetting Unraid-Api after fork change. When installing your fork i get back my old issues with VM not beeing controllable. Thats fine as it was that way before unraid update and i dont need to control VM(could be nice thou). Get VM Details for ip: ip:port Failed Cannot read properties of undefined (reading '0') Get VM Details for ip: ip:port Failed Cannot read properties of undefined (reading '0') But i get error controlling Unraid, stopping/starting array from HA for example (something i could do with vanilla unraid-api). I get in unraid-api log: Received MQTT Topic: homeassistant/unraid/array and Message: Stopped assigning ID: MQTT-R-lk2e6ayi But nothing happens. When i try and start/stop a container from HA i get: Received MQTT Topic: homeassistant/unraid/organizr/dockerState and Message: stopped assigning ID: MQTT-R-lk2elcf8 Part of MQTT-R-lk2elcf8 failed. And nothing happens When i do the same from Unraid API webui i first get a popup: Please Enter Your Password For ip:port And if i fill that in manually (even thou it should be taken from my serversetup i unraid-ui which is correct) I get nothing in unraid-api logs and nothing happens to the container. Home Assistant can read the container state. So when i turn on a container within unraid manually, the sensor in HA gets turned on aswell. It seem there is something with the auth/write but Im not sure what you need more specified so just ask and i will try my best to give logs and so on.

Hi Im hoping im posting in correct subforum. Looking for some input regarding storage setup for my unraid: As im awating deals on hardware im using a Dell OptiPlex 7080 Micro (16gb ram/i5-10500T) while wating. So i will be using my present as Qnap NAS as storage until i got new hardware and move that data to Unraid then and retire the QNAP(reuse as backup). So Unraid will be used for Docker applications and 1 Home Assisntant VM as im moving from a windows server and Raspberry PI to Docker/VM aswell. And when i gotten new hardware with more sata ports and hdd slots i will move to that and then start using it as NAS aswell. Until i gotten my new hardware i have (from work so no costs involved), im not wanting to buy new drives until i built the full hardware. 3 x 256gb SSD 1 x 500gb SSD 2 x 256gbs NVME 2 x M.2 NVME slots on Optiplex 1 x SATA 2.5 slot on Optiplex Im not wanting to buy new drives until i built the full hardware. Opt 1 (present setup as test) 1 x SSD 500GB as array Used size as full test with everthing configured at 3.5 gb. -isos -download, temporary then rrs-apps dumps it to remote Qnap media share (no cache setting to stop downloads affect io for dockers/vm) 2 x NVME 256GB as cache RAID1 Used size as full test with all dockers installed at 22.6 gb. -appdata prefer cache setting so these folder get full speed and has raid1 for security, -domain prefer cache setting so these folder get full speed and has raid1 for security -system prefer cache setting so these folder get full speed and has raid1 for security. Or Opt 2 1 x SSD 500GB as parity (reuse for real build as cache when its time) 2 x NVME 256GB as part of array (reuse for real build as cache when its time) I realize that trim not supported or experimental at best. Whats the best way until i got fullsetup, is other options i should consider?

hiya, any possbility for an update on the container to 2.0.15?