ElectricBrainUK

Members
  • Posts

    125
  • Joined

  • Last visited

Recent Profile Visitors

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

ElectricBrainUK's Achievements

Apprentice

Apprentice (3/14)

24

Reputation

  1. Hmm, everything looks correct - do the mqtt topics continue to be updated? I may have to try and replicate this as the hide function has always worked in the past and I don't really know why it isn't for you sorry
  2. The 503 error means it is failing to authenticate but there could be a lot of different reasons as to why - check your unraid server logs, it might be that because of the restarts etc the server has blocked it for too many requests, may just be worth stopping the docker over night and trying again in the morning. Otherwise there could be new security changes on the new rc but unfortunately I won't be able to check until next week as I'm going on holiday tomorrow. One thing to check though, what is the network config for the docker itself? Is it just a port on the servers IP? Or have you bridged it its own ip? If it has its own ip it can't communicate with the host
  3. Hi, The logs from the unraid api are what I need, the error you have shared is when the request comes via mqtt however when you do it from the unraid apis ui itself the logs will not contain mqtt etc. and may give a better idea of the issue. Once you have hidden a device from that menu you need to delete it from home assistant as it remembers old devices even once they stop sending messages Cheers
  4. Hi, are you able to start and stop that docker from the unraid api ui? What about from the unraid ui as well? Could you share the logs for the former as well Thanks
  5. Okay thanks for letting me know, it is very odd and I've not seen this behavior before but I will try to reproduce it using the details you've provided
  6. That looks relatively normal, do you have any mappings other than /app/config?
  7. Hi, I'm afraid I've not seen this error before and I don't know what could be causing it. Is there anything in the logs for the unraid api that is suspicious? Or the system logs when the writes are high? Otherwise there is this issue where forcing the api onto a background thread causes it to behave unusually: https://github.com/ElectricBrainUK/UnraidAPI/issues/33
  8. Assuming you have zigbee2mqtt set up with an mqtt broker that is connect to home assistant? If not look into zigbee2mqtt and an mqtt broker Once you have that set up, you want to set up the unraid API adding all of your mqtt broker details in the docker set up, then on the UI adding your unraid server details. There is currently no way to trigger user scripts from the API. So what you would do is create an automation in home assistant that when you press your zigbee button, it turns on VM A and then VM B rather than calling the script.
  9. Hi guys, For the first issue I'm unsure what the problem would be unless pi hole is blocking the api somehow, though I doubt that as it doesn't really use domain names. Try reconfiguring the server in the unraid api and failing that checking the logs of both the api and the unraid server itself @Irithor glad you appreciate, happy it's worked so far. I'm surprised you got the ha app working at all as it has a few problems that I need to sort out! I guess the main thing would be to check the share it is pointing to when it tries to write to config/* and make sure it's properly mapped outside of the docker onto the host somewhere. Not a problem on the unraid docker as the mappings all work but it can be a bit more fiddly in HA! Let me know if you need more help and how you get on. Check here to start with, it should be mapped to a /share folder but it may not be: https://developers.home-assistant.io/docs/add-ons/configuration/
  10. I'm not as familiar with grafana but the auth is set by setting the authorization header to the base64 of username:password
  11. Hey - that is unusual Im guessing the API is sending a cached response probably something I need to fix and not a problem with your config.. Ill look into it - it should mean that you cant perform actions without auth but the bug with the cache means the data about the server is still shared
  12. Those are the logs from unraid api however I mean the ones from unraid itself - there may be something there which explains why the api is failing to connect, did you try reconfiguring the server in the api as well?
  13. Okay, I have heard a couple of users report a similar issue, I would suggest not using the HA VM one as that is in alpha and not consistently working at the best of times. For the unraid one, have you tried deleting the server altogether (in the menu on the left under manual config) and then restarting the docker and reconfiguring? This may help otherwise try deleting the config folder and starting from scratch. You could also check the server logs on unraid itself to see if there is any extra details on why it is failing to connect there.
  14. Hey, That is odd, 503 suggests it cannot authenticate or is being blocked, try re entering your server details in the ui as sometimes they expire especially if you have the config location set to secure. If you have changed the network config to have its own ip on br0.1 etc then it will not work and will throw this error though this may not be the case. You do not need the unraid api on both, the unraid one works more reliably so I would suggest using only that.
  15. Hey, it should prompt you for a username and password if you set the keystorage variable to secure, however you will also have to authenticate rest requests. Otherwise you could put the UI behind some other reverse proxy or something that adds auth