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

Mealie Custom Service is not working #721

Open
DevFreezing opened this issue Nov 9, 2023 · 2 comments · May be fixed by #723
Open

Mealie Custom Service is not working #721

DevFreezing opened this issue Nov 9, 2023 · 2 comments · May be fixed by #723

Comments

@DevFreezing
Copy link

Describe the bug
Mealie Custom Service is not working, Homer does not connect to the API.

Expected behavior
Should show the number of recipes Mealie is keeping organized or the planned meal for today if one is planned

Logs & errors
I suspect that is s due to the URLs of the API are not properly set in the file src/components/services/Mealie.vue
For example at line 47 is calling /api/meal-plans/today/ but if we look at the mealie API documentation the URL is api/groups/mealplans/today

Screenshots
If applicable, add screenshots to help explain your problem.

Configuration
My yml for mealie is:
- name: "Applications" icon: "fas fa-cloud" items: - name: "Mealie" logo: "assets/icons/mealie.png" type: "Mealie" keywords: "self hosted recipe manager " url: "http://10.10.1.102:9000" target: "_blank" # optional html a tag target attribute apikey: "XXXX"

@bobonthenet
Copy link

I'm experiencing issues with this too. I tried changing the urls to match the api docs, but it still isn't working.

@bobonthenet bobonthenet linked a pull request Nov 16, 2023 that will close this issue
7 tasks
@bobonthenet
Copy link

Turns out my Nginx config had issues too which is why changing the urls initially didn't work. I've created a PR to update those urls.

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

Successfully merging a pull request may close this issue.

2 participants