BoKKeR

@Algiarept can you pull the latest and do as said above?

Is there a possibility to have automount:ON, but have one specific drive not automount?

Do you have the chance to run this command while the container is running: docker logs --timestamps `docker ps -aqf "name=Unraid-API-RE"` >> unraid-api-re.txt And attach the unraid-api-re.txt file. In case the container freezes the UI you can also use this command to kill it docker stop `docker ps -aqf "name=Unraid-API-RE"`

@song I have tested the vm start/stop functionality on a test machine, it works on 6.12.3, Can you tell me more about your system, any logs when this happened? Also could you send the HTML files as stated above?

@retsamel and @johntdyer, could you pull the latest 6.12, I have added the option to write the html files to config/html_output, as long you use the environment variable: WRITE_HTML_OUTPUT=true These files are not anonymised they are the copy of the VM page and the Dashboard page as seen in the unraid dashboard. Feel free to send them over in a PM if you wish so, I will take a look why the parser has failed. With these files I can possibly debug what is happening

the usb name should be fixed, I pushed it yesterday, have you pulled since? I will have to look into the ON/OFF loop

No idea, have you tried restarting your OS/container, authenticating again using the web-ui ? PS, the USB devices are fixed now

The usb device names get scraped wrong, will have to check on that, its unrelated to the usb plugin

Has the grouping worked on the original project?

I think the old devices dont disappear but there should be a new device with grouped entities. Could you double check

I updated the master and the 6.12 branch, currently this is the info I get on my test device. The grouping seems to work also on my device, but I havent done any changes there, maybe the other changes fixed the HA groups

I am looking into the option of grouping the mqtt devices into a single device. Currently only found this https://community.home-assistant.io/t/how-to-group-entities-into-a-device/262600 without luck of it working. Only a single device shows up. Also looking at fixing the missing/broken properties, like cpu/motherboard/ram. I will need to change the way we extract the data from html dom, currently the project just uses string.substring() manipulation. I am looking into a way using xpath. There might be better frameworks for selectors in nodejs/xml that I am not aware of. Preferably the selectors should be editable from the UI (loadable from a config file). In case there is a new version, users should be able to fix the broken properties themselves just by replacing the selectors. Has anyone managed to find a way of running the webGui https://github.com/unraid/webgui without the underlying unraid OS?

root will work fine, I am not sure about the errors, you are getting. Do you use a config folder?

Which version of unraid and which tag of the image?

Thanks for the great detailed feedback! I have setup an extra machine with a trial key for testing (will need to find a better solution). There was a problem with extracting the CSRF token from the new UI, and other problems with getting VM details. (legacyUSB devices still wont show up, not sure what they are) Please pull the latest and give it a try. Both VM-s and dockers should work now on 6.12 I would also like to add better logs and a screen for better overview, maybe if I find more time.

I had the same problem, high docker usage, had to downgrade to 6.11 which works great.

I created a new docker image based on the old repo, fixed 6.11 and 6.12. I also created a new forum thread not to mix it with this one.

Overview: Support for Docker image unraid-api-re in the bokker/unraid-api-re repo (fork of the original). Docker Hub: https://hub.docker.com/repository/docker/bokker/unraidapi-re Github/ Docs: https://github.com/BoKKeR/UnraidAPI-RE If you feel like supporting my work: just say thanks! This is a fork of https://github.com/ElectricBrainUK/UnraidAPI I managed to fork and make the original project work on github ci. I will try to keep this project alive with newer unraid releases, its an exact dropin for the original https://github.com/ElectricBrainUK/UnraidAPI just replace the image electricbrainuk/unraidapi with bokker/unraidapi-re I will create a tag for each minor release as in: bokker/unraidapi-re:6.12 which will cover 6.12.0 <-> 6.12.2 I mostly test the functions related to reporting status, if you have special needs as removing/editing containers, vms, switch gpus please tell if the container malfunctions for you. I cant stress enough that this is not a proper solution, this container scrapes the unraid UI. Every minor update will possibly break functionality. I would love to setup automated tests, but to be able to do that I need a way to spin up the unraid os (or frontend) in a test environment. Happy to hear what ideas people can come up with. Until then please call up your local Unraid congressman and tell them how much you care about a publicly available API.

I am having the same issue after hitting update-all

thanks for the help, it works now!

Hello, I am in dyre need of replacing my cache SSD, I disabled VM and docker services. All my shares look like this: Its obvious that mover wont move anything since it only affects new files. What is the new way of moving files from Cache to Array? unraid-diagnostics-20230620-1430.zip

I agree, had an interview early 2023 with the unraid team and they only talked about working on unraid plugin and the different ways to monetise it. As in one-click SSL for people who cant set it up etc. It really put me off from this product since the UI needs a remake as its made in multiple different languages and technologies but the focus was not there. It SEEMS that with the plugin they introduced a graphQL api on unraid, and I vaguely remember reading a comment that they want to make it public but I cant find this comment on the forum.

I updated the template with the redis env variables

Sorry I forgot to update the template, the container now uses a redis queue and it is much more reliable. With support for multiple chats . Check the docker page