troubleshooting

🆘 Troubleshooting & FAQ

Having issues with your integration? Check these common solutions before opening a GitHub issue.

---

👻 Issue: Items reappear after I click a button ("Ghost Items")

Cause: This happens if the Home Assistant backend fails to communicate with your Grocy server, but the frontend's "Optimistic UI" hid the item anyway. Fix: 1. Ensure your API key in the integration configuration is still valid. 2. Ensure your Grocy Server is fully updated to the latest version. 3. Check your Home Assistant logs. The backend should initiate a "Direct API Strike" if the standard library fails.

⚠️ Issue: I see Pydantic warnings in my logs!

Cause: You might see something like UserWarning: Pydantic serializer warnings.... This is caused by the Grocy server returning an empty list [] for a field that the Python library expected to be a dictionary {}. Fix: None required! We have implemented a God-Tier Polish script in __init__.py that actively silences these harmless warnings so they don't clog up your logbook.

🚫 Issue: "Custom element doesn't exist: grocy-action-card"

Cause: You successfully added the JavaScript module to your resources, but your browser is holding onto an old cache. Fix: Force refresh your browser:

• Windows/Linux: Ctrl + Shift + R
• Mac: Cmd + Shift + R
• Mobile App: Navigate to Settings > Companion App > Debugging > Clear Frontend Cache.

❌ Issue: The "Waste" button throws a generic error

Cause: Deleting generic entities requires precise endpoint mapping. Fix: Ensure you are using the patched services.py from this repository. The God-Tier overhaul bypasses the broken delete_generic library function and uses raw HTTP DELETE requests to guarantee the item is removed from your database.