Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API URL #313

Open
Morbeas opened this issue Nov 14, 2024 · 7 comments
Open

API URL #313

Morbeas opened this issue Nov 14, 2024 · 7 comments

Comments

@Morbeas
Copy link

Morbeas commented Nov 14, 2024

Hey there. I'm running my Grocy and Home Assistant instances on my Synology 1621+ NAS. I recently installed Grocy on my NAS and wanted to integrate it with Home Assistant. When I go to fill out the API URL, it just says "Something went wrong" after spinning for about 60 seconds or so. I was thinking maybe I need to put "localhost" since both apps are on the same server, but that didn't work either.

Any ideas?

@xTim18
Copy link

xTim18 commented Nov 17, 2024

Same issue here. Running home assistant os in proxmox vm with nabucassa subscription for https. Grocy api url looks like:
https://myurl.ui.nabu.casa/api/XXX/XXX/api.
Neither https with nabucasa adress nor local adress is working. Any ideas how to solve?

@Morbeas
Copy link
Author

Morbeas commented Nov 17, 2024

I was able to fix my issue by upgrading my installation to HAOS.

@xTim18
Copy link

xTim18 commented Nov 17, 2024

I was able to fix my issue by upgrading my installation to HAOS.

@Morbeas What do you mean by upgrading your instance?

@Morbeas
Copy link
Author

Morbeas commented Nov 17, 2024

I mean I upgraded my Home Assistant to the OS version and was able to just add Grocy from the addons store, which fixed my issue.

@jlong5795
Copy link

Also having this problem. None of the local urls work and I'm not seeing guidance on where to find the correct one.

@xTim18
Copy link

xTim18 commented Dec 16, 2024

For me (running the Grocy Add-On in Home Assistant on a VM using Nabucasa Cloud for remote access) the solution was to disable SSL in the Add-On Settings and set custom Port 9192 for the add-on.
image
Aftwards the custom-component integration from hacs worked perfactly fine with the local ip adress of the home assistant instance, no ssl and port 9192 specification.

@jlong5795
Copy link

Yes, this worked! Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants