Read the statement by Michael Teeuw here.
MMM-MealieMenu Fetch Error
-
@zanix Restarting the MM service fixed the issue with no additional steps so it may well be an expiring token or something.
I have updated the Mealie container so I am now on v1.7.0 and switched to using the API key for auth. I have also checked and I am using the current version of your module, v1.5.0.
I’ll report back if anything interesting happens. Thanks again for your advice.
-
@WallysWellies Thanks!
I think the token does expire. I just checked the token on my instance and it expires 1 month from now.
I will work on fixing that soon. -
@WallysWellies I just updated the module to account for token expiration.
It took me a bit to test since I needed to let the token expire to make sure it worked. -
@zanix that’s dedication, thanks!
I see the update notification so I’ll get it updated tonight. Cheers.
-
@zanix Hi Zanix. Just updated the module and all meal entries now seem to use the default image. I updated the docker image in case that was the problem but they’re all still showing the default orange image.
Possible bug introduced in the latest release?
-
@zanix Sorry, ignore me - it seems to only be using default images on my laptop. On the actual screen it’s showing the images. Maybe it’s something to do with resolution or something. Apologies.
-
@WallysWellies I opened MM on my desktop (MM runs on a Pi5) and I can see the meal images.
The default image only displays when the meal image cannot load. Maybe the URL of the images isn’t accessible on your laptop? -
@zanix You are correct. Looking in the console it’s trying to load from localhost. I’m not greatly fussed but one day I might look into where I can fix that.
Cheers!
-
@WallysWellies Are you running MM and Mealie on the same computer? And do you have the MMM-Mealie URL set as
localhost?
If so, try changing the MMM-Mealie URL to the IP address of the computer it’s running on.
