Hi, mongodb support is still experimental and available for amd64 architecture only at this time. Generally speaking this is intended for a scenario in which someone is willing to host dozens of houses and having everything in memory (like redis does) would not scale. For standard, on-prem installation the egeoffrey-database (based on redis) is and will always be the preferred choice (so to avoid stressing the raspberry SD card with too many reads). Thanks

Hi, it is possible indeed, you need to set an "alias" to the module name when listing it in the EGEOFFREY_MODULES variable. If you open up your docker-compose.yml file you will see something like: EGEOFFREY_MODULES=service/mysensors_serial If you want to create multiple independent instances change it to e.g.: EGEOFFREY_MODULES=service/mysensors_serial=mysensors_serial_1,service/mysensors_serial=mysensors_serial_2 In this way you will have service/mysensors_serial1 and service/mysensors_serial2 with independent configuration files (clone your existing config into config/service/mysensors_serial_1.1.yml and config/service/mysensors_serial_2.1.yml). Let me know if you need additional details of course. Thanks for the reporting the issue with general discussion, fixed it.

Hi and welcome to the forum! I'm assuming you are already familiar with https://developer.egeoffrey.com right? If not, there you can find described in detailed most of the internals. Despite eGeoffrey is based on docker containers, there is no need to do anything with docker since the egeoffrey-cli has plenty of helpers to initialize repos, committing new version and finally building the docker image (egeoffrey-cli -h for details, ensure you have the latest version) without other additional actions. As for the development process, if willing to build a brand new module (e.g. a service called XXX) the process is more or less the following: egeoffrey-cli init_repo service XXX <your_github_user> to create a new local repo and configure remote URL automatically Do you changes to the service/XXX.py file Test your module by running it manually outside docker with python -m sdk.python.module.start (you need to define at least the variables EGEOFFREY_GATEWAY_HOSTNAME and EGEOFFREY_MODULES to make it connecting to an already running gateway egeoffrey-cli commit "First version" to commit the changes and push it to your github repository egeoffrey-cli build amd64,arm to build the docker images and push them to you dockerhub account Add your module to https://github.com/egeoffrey/egeoffrey-marketplace with a PR so to show up in the marketplace Of course I highly recommend to review existing packages and their code before starting developing something. Out of curiosity, what are you looking forward to building? Thanks!

Please note, for those using the app, ensure to update at least to v1.0-3 (which has being pushed to Google Play at this time) to ensure notifications will continue to work correctly. This new version ships also with the latest GUI release (with new widgets) and fix an issue with notifications which are now all delivered when the device goes back online and not just the latest.

Hi @newatthis and welcome! Yes we are fully operational but being this forum brand new you don't see much traffic yet, hope to grow soon also with your contribution Feel free to drop in the General Discussion forum whatever question or comment you may have. Thanks