BoKKeR

Members
  • Posts

    144
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

BoKKeR's Achievements

Apprentice

Apprentice (3/14)

42

Reputation

1

Community Answers

  1. After the files from @light2089 I have fixed so the version returns an empty string in the meanwhile if the version is not found. I will investigate further since it works on my test machines and I suspect its some kind of a custom setting which hides the version on the main page
  2. @BlaM I would like to add this also, but unfortunately I dont own a UPS, is there a way I can emulate a UPS? Since once a feature is implemented it has to be maintained going forward. @light2089 Thanks for finding this bug and opening a PR (I somehow didnt get a github notification). I cant reproduce it on my 2 systems running 6.12.6, Are you using any custom theme? Could you run the container with WRITE_HTML_OUTPUT=true and send me over the dashboard.html file from your /config folder in private? So I can find a version a code that works for all of us. @ABEIDO The logs are coming from unraid itself. Since the container needs to ping the dashboard there is no way this container can fix it. The unraid team might be able to help in the future how to surpress them. I will look into the HA problem
  3. I have ended up using the terminal/ssh. example command: docker logs --follow `docker ps -aqf "name=Unraid-API-RE"`
  4. I have seen some reports of it working and not working on 6.12.6, I am currently away from my computer so I can’t test it but please submit your dashboard html files after running the container with WRITE_HTML_OUTPUT=true and send them over to me in a PM since they are not anonymised. @k11su @mkono87 @chompy18 try running npm ci instead, alternatively check how the docker file is setup. The packages are broken since before I took over the fork I will have to revisit the Unraid dashboard getting slow once I find more time to write a backing off strategy
  5. @syper @ByteHeaven could you try using the MQTTRefreshRate=60 env variable. Setting the refresh to every 60 seconds or even 120. Instead of the default 20 seconds. Also close the website since I noticed that the web browser has its own 3 second times, each tab would start a new 3s process. I will have to rewrite that... I suspect that when the server/ui becomes slow the unraid-api does not back off and just queues up more tasks ending up slowing down the UI indefinitely. I would like to rewrite that whole logic but my current fix would require an external redis service. Or implement some sort of logic for exponential backoff https://stackoverflow.com/a/52772266/2515404 @skank Does the entity show up as following?
  6. Are you able to wipe the /config folder and start again?
  7. @apedance 6.9-2 is not supported, update to 6.12 for maximum support
  8. Keep the variable false if it works
  9. Did you update to the naming fork? @Blade007 Are you able to add WRITE_HTML_OUTPUT=true to your env variables, it should log every time the site gets scraped. Additionally you could try to remove the config and start fresh. About the memory leaking @Foehammer1982. I am not saying that its not happening but I cant seem to reproduce it on my server (last 7 days view)
  10. I have potentially fixed the naming problem. Do try out this branch bokker/unraidapi-re:6.12-naming I have also grouped the VM usb devices under the VM There is also an option to set icons in the MQTT messages for entities. I have not had time to choose any. https://pictogrammers.com/library/mdi/
  11. Interesting idea but I dont think its as clear cut as you might think. You will have to come up with a common structure that the url would have to supply. Or alternatively add a little script inside of unraid-api where you could transform the data to the desired output. Its quite a lot of work currently for me. As always, contributions are welcome. You can probably find me on discord for discussions
  12. @Foehammer1982 I ran some script to detect potential node leaks and it triggered right away. I am not sure if its false positives, will have to investigate more. The whole polling is done with multiple setTimeout calls so if anything thats my suspect. Also I am questioning the need for multiple server support, now with the MQTT change. Considering that users could just run multiple docker instances for multiple servers and it would possibly solve some of the problems around MQTT naming. The list of issues currently are looking into are: - new home assistant MQTT entity names - server shut down ends with ON state - HA entities go unavailable on HA restart (can be fixed with retain:on but those messages have to be cleaned up) - memory leak - make the image support multiple unraid releases with single docker image - deleted dockers end up on HA (unconfirmed)
  13. sorry, I have been mostly focused on 6.12, please update if you are able to. Going forward I will try to support older OS. The problem is that the project needed so much rewrite to get to a good shape. And the work is still not done. To be able to do that in two branches turned out to be much harder than expected. Currently I am focusing on fixing up the codebase in 6.12
  14. Could you tell me more how you detected the memory leak? What was your setup? @lanky8804 did you manage to figure it out? Could you try removing the info config file and starting fresh? there is also an env variable that might show if the scraping is working: WRITE_HTML_OUTPUT=true