BoKKeR

yes, have just tried that, still no activity in intel-gpu-top

Thank you, unfortunately that link did not give more details, the CPU is supported and the setup I have should be working.

Could you please check this thread out, I am at the end of my rope

I ran out of things to try getting my 8700k to transcode with jellyfin. This is what I have - original jellyfin/jellyfin container - latest intel-gpu-top for monitoring - enabled Intel QuickSync transcoding - added/removed i915 modprobe from boot/go file (should not be needed since I have intel_top_gpu) - added device in docker template as /dev/dri/ (also tried extra properties) - device shows up in both container and host when I list. Is there anything more to be done? When I play a stream I expect intel-gpu-top to show some kind of activity. unraid-diagnostics-20230920-2017.zip

The main problem is that currently there is no best practice from the unraid team with plugins extending the UI as its still a DIY OS/service. Its free for all and developers implement features as they wish. Updates notifications are: - inline - popups - notifications - external services as telegram. The UI would need a rework from a UX designer but this could also result in a worse DIY experience for aspiring Community Developers trying to create new breaking features.

I created a fix for this, could you try it by changing your docker tag from bokker/unraidapi-re:6.12 to bokker/unraidapi-re:6.12-retain

@ABEIDO yes, I posted about it earlier. @Orishas I can double check this

@valiente Can you try this docker tag: bokker/unraidapi-re:6.12-usb-device-name

I have pushed an update which should group all docker devices under a single mqtt entity and the unraid server info. There will be another entity for each VM and VM USB device

Sorry, I accidentally wrote the wrong variable in the code, if you update the container it should work as expected EDIT: you can switch back to 6.12, and remove the env variables, it should work without them

It should be in your appdata or docker folder

Could you check if there is an existing vm object in your config/servers.json file? If so could you remove it and restart the container

Did you change the tag ?

Could you try the following tag: bokker/unraidapi-re:6.12-no-vm I added the following 2 variables which can be set to false using docker env variables VM_ENABLE, DOCKER_ENABLE This should disable VM checking for you. I will have to do more work on it, since I think its possible to have this work just by detecting if the VM tab is available or not in the UI, without using the env variable.

do you mean that your VM feature is disabled in unraid settings ? Or that you don’t have any VM

Yes, just how the original repo worked

happy it works, you should remove the env variable. What fixed the container for you was pulling the latest version.

Do you get the free space data in the unraid-api dashboard? I will have to look into mqtt grouping.

@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