Disregard this question. The reason to try to do this does not exist anymore.

@eporocrail excellent, let me know of course if you need any additional information or you face additional issues. Thanks!

Hi, I've taken this good question as an excuse to revisit the developer website (https://developer.egeoffrey.com), re-organize the contents as well as provide additional details on the development and building process and workflows. Thanks

Just to let you know MongoDB support is now officially available and supported by egeoffrey-controller starting from v1.1. controller/db configuration file is automatically upgraded to allow choosing the database type. However, this is still intended for a complex ISP scenario when hosting multiple houses and redis approach to keep everything in memory would come with a high cost. For this reason the package egeoffrey-database-mongodb is available for amd64 architectures only but no customisations have been made in mongo so any local installation would do the job if for some reason required on a different architecture. For a standalone, raspberrypi-based installation, redis (e.g. egeoffrey-database) is and will be the way to go. Just to share a data point, in my local deployment with 180 sensors configured, the database size (and hence memory utilization) is still below 40 Megabytes and I'm retaining 3+ years of data.

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.

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