Hi @wint0178, when you logged in to the server, if you see this error, it was happened before login.
If it comes only one time and all other functions are working as expected, please ignore this error.

Thanks @wint0178 !!
I will go through the installation documentation and sync with your update.

@skywatch I was able to setup several MQTT Gateways using NodeMCU boards with attached I2C sensors. The Gateways are all Wifi gateways, but I have been able to use my DDNS in place of the IP address to send data from several locations including one that is international. I think this is working well at this point. Thank you for your reply!

@wint0178 on the other post, I see you were able to see the nodes. Still do you see this issue?

OK, I'm not exactly sure what I did, but my student was able to edit the example sketch from MySensors V2 "GatewayESP8266MQTTClient" and add in code to send data from the Adafruit BME680 over MQTT. Once I added that code to my NodeMCU and added the # to the subscribe list in my gateway, it all just seemed to automatically add.

I should acknowledge that I had a misunderstanding about what physical components were nodes, sources, and fields. For some reason I thought that my NodeMCU was a gateway (this is true), it was also a node (this was not true), and that the BME680 was the source with several fields on it (TEMP, PRESS, HUMM). I believe I see now that the Node is actually the BME680 board and it has several separate sources, the physical sensors for each of the conditions it monitors and those numeric values, once acquired, become fields that the MC server can publish.

I am going to play some more with this since I would like to add all sorts of other nodes with a wide range of sources.

@wint0178 You can use letsencrypt certification setup with https_acme to your DDNS setup, https://v2.mycontroller.org/docs/installation/advanced-installation/backend-configuration/

@jkandasa I have fixed this. available in the docker container(2.1.0-devel). yet to update in executable.

@wint0178 No, keep default labels. as @JeeLet mentioned can you check any other service is consuming the serial port? Do you see any error on the gateway?

@wint0178 At the time of writing the document in RPI the default installation does not have docker 20.x or above. Hence I proposed this method. In your installation if you have latest version of docker, you can install with apt install... command. I think I took the steps from https://github.com/docker/docker-install

@JeeLet @wint0178 recently I released the version 2.0.0, the location changes. also I changed some of the paths. I will go through the installation steps soon as possible and update the required corrections

hi @wint0178,

MQTT Broker - if you plan to connect your gateway via MQTT, you need an mqtt broker. If you already one. you can use that. You can have MQTT broker in any system, that should be accessible for MyController and your gateway device. If you do not have complex system, you can keep everything on the same system. MongoDB - for storage the default option is in-memory database. It keeps all the configurations(except metrics) in memory and dumps to dis in an interval. It will be faster. You can take a frequent backup with schedule. But someone wants to keep the storage in mongoDB, may be due to large setof configurations or to keep the data in remote location, or other reasons. It is up to you. fyi, I am using in-memory db and I do not see an issue till now(about 2 years) InfludDB - you need to have this database, if you want graphs and metrics details

I hope I have addressed your queries

Hello @jkandasa

an idea in pictures, it's easier
https://nsmf01.casimages.com/f/2023/06/28//23062802265523870811442.pdf

..... it's an idea 🙂

@wint0178 I am trying to respond your queries to my best. You may have better approach then my response too.

I assume that, you are using MySensors hardware in your setup.
As you have your gateways in different locations, you can connect all your gateways with MQTT connection (I would recommend secure MQTT).
You have to run a MyController server for 24x7, so you can go with RPI, it will save lot of your electricity and space.

Ultimately, I need to give data access to the communities themselves through the dashboard and SMS or email notifications. I would also like to have remote access to the data, but this is slightly less critical.

With MyController you can configure Email and web-hook(you may use it for SMS), For now there is no role based access in MyController v2. In MyController all the metric data will be in influx database. So you may share the details with Grafana dashboard too. I think it has read only dashboard.

@JeeLet some special cases you need 2mqtt. For example you want to share your USB GW for MyC and other software (via mqtt). If you are using your USB GW only with MyC. 2mqtt is not required.

2mqtt creates a mqtt communication to your USB GW

.... happy holidays to you Jkandasa

I'm rethinking my vision / use of the Mys protocol

as I have chosen a Usb gateway and mostly a communication bus in rs485 (RF is for specific cases)

MyC <---usb---> Gateway Mega2560/Gui-Oled <----RS485---> Nodes1 2 3 <---- RF ---> NodeX

the controller in a closet the gateway on the desk (usb 3 meters) the nodes everywhere in the house (in the technical parts)

and as the "real" Node to Node doesn't work (yes a gateway is mandatory for routing)

I'll see how I'm going to do a state management.
I'm testing a feedback on the OLED display of the gateway.

an example of the sketch on the gateway of a remote node

//------ node 36 Link distant ------ const byte LINKY_NODE_ID = 36 ; // node linky const byte CHILD_ID_PAPP = 1 ; // ID papp uint16_t valPAPP ; // variable valeur PAPP //-------- linky papp ------------------ if (message.sender == LINKY_NODE_ID && message.sensor==CHILD_ID_PAPP && message.type == V_VA ) { // val PAPP valPAPP = message.getInt(); Serial.print("val PAPP. : "); Serial.println(valPAPP); } //------------ OLED valeur PAPP -------------------------- void valPaPP() { oled.set2X(); oled.setCursor(37,2); oled.print(valPAPP); oled.print("va "); }