ERP beyond your fridge! A groceries & household management solution for your home.
Grocy - ERP beyond your fridge is a powerful groceries & household management solution for your home, delivering features like:
- Stock management
- Shopping list
- Recipes
- Chores & tasks
- Inventory
- and many more.
Try out the online demo of Grocy.
The installation of this add-on is pretty straightforward and not different in comparison to installing any other Home Assistant add-on.
- Search for the "Grocy" add-on in the Supervisor add-on store.
- Install the "Grocy" add-on.
- Start the "Grocy" add-on.
- Check the logs of the "Grocy" add-on to see if everything went well.
- Click on the "OPEN WEB UI" button to get into the interface of Grocy.
- The default login is user:
admin
password:admin
. - Enjoy the add-on!
Note: Remember to restart the add-on when the configuration is changed.
Example add-on configuration:
culture: en
currency: USD
entry_page: stock
features:
batteries: true
calendar: true
chores: true
equipment: true
recipes: true
shoppinglist: true
tasks: true
tweaks:
chores_assignment: true
multiple_shopping_lists: true
stock_best_before_date_tracking: true
stock_location_tracking: true
stock_price_tracking: true
stock_product_opened_tracking: true
log_level: info
ssl: false
certfile: fullchain.pem
keyfile: privkey.pem
Note: This is just an example, don't copy and paste it! Create your own!
The log_level
option controls the level of log output by the addon and can
be changed to be more or less verbose, which might be useful when you are
dealing with an unknown issue. Possible values are:
trace
: Show every detail, like all called internal functions.debug
: Shows detailed debug information.info
: Normal (usually) interesting events.warning
: Exceptional occurrences that are not errors.error
: Runtime errors that do not require immediate action.fatal
: Something went terribly wrong. Add-on becomes unusable.
Please note that each level automatically includes log messages from a
more severe level, e.g., debug
also shows info
messages. By default,
the log_level
is set to info
, which is the recommended setting unless
you are troubleshooting.
Enables/Disables SSL (HTTPS) on the web interface of Grocy
Panel. Set it true
to enable it, false
otherwise.
The certificate file to use for SSL.
Note: The file MUST be stored in /ssl/
, which is the default
The private key file to use for SSL.
Note: The file MUST be stored in /ssl/
, which is the default
Is used for setting the language. Choose between:
da
(Danish)de
(German)en
(English)es
(Spanish)fr
(French)it
(Italian)nl
(Dutch)no
(Norwegian)pl
(Polish)ru
(Russian)sv_SE
(Swedish - Sweden)ta
(Tamil)tr
(Turkish)
Determines the currency as displayed in the Grocy interface, specified by the ISO4217 three digit currency code.
Examples: USD
, CAD
, GBP
or EUR
.
Allows you to specify an custom homepage if desired.
You can use the one of the following values:
batteries
calendar
chores
equipment
mealplan
recipes
shoppinglist
stock
tasks
By default the homepage is set to the stock overview.
Is used for enable or disable features in Grocy. Disabled features are hidden from the web interface. The following features can be enabled or disabled:
batteries
calendar
chores
equipment
recipes
shoppinglist
tasks
Set it true
to enable it, false
otherwise.
These options are used to tweak part of the core behavior of Grocy. The following sub features can be enabled or disabled:
chores_assignment
multiple_shopping_lists
stock_best_before_date_tracking
stock_location_tracking
stock_price_tracking
stock_product_opened_tracking
Set it true
to enable it, false
otherwise.
The following sub features can be set to specify a day (0-6), where 0 would equal Sunday:
calendar_first_day_of_week
meal_plan_first_day_of_week
- Grocy support to provide custom lookup resources to lookup information on the internet based on the product barcode. This is currently not yet supported by the add-on.
This repository keeps a change log using GitHub's releases functionality. The format of the log is based on Keep a Changelog.
Releases are based on Semantic Versioning, and use the format
of MAJOR.MINOR.PATCH
. In a nutshell, the version will be incremented
based on the following:
MAJOR
: Incompatible or major changes.MINOR
: Backwards-compatible new features and enhancements.PATCH
: Backwards-compatible bugfixes and package updates.
Got questions?
You have several options to get them answered:
- The Home Assistant Community Add-ons Discord chat server for add-on support and feature requests.
- The Home Assistant Discord chat server for general Home Assistant discussions and questions.
- The Home Assistant Community Forum.
- Join the Reddit subreddit in /r/homeassistant
You could also open an issue here GitHub.
This is an active open-source project. We are always open to people who want to use the code or contribute to it.
We have set up a separate document containing our contribution guidelines.
Thank you for being involved! 😍
The original setup of this repository is by Franck Nijhof.
For a full list of all authors and contributors, check the contributor's page.
Want some more functionality to your Home Assistant instance?
We have created multiple add-ons for Home Assistant. For a full list, check out our GitHub Repository.
MIT License
Copyright (c) 2019-2020 Franck Nijhof
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.