@OldSurferDude use a host name for the broker in the configure command (--my-controller-url-address=). Add the host name to /etc/hosts on the rpi where the gateway is. Start the MySensors gatway. When you want to switch brokers, modify /etc/hosts again and restart the MySensors gateway.

@evb Still haven't had a chance to look at your PR, sorry. Yes, the database tends to grow :-) I have about 80MB after a year of use. Just added a function to delete all messages older than, say, a year.

@Yveaux said in serial, Ethernet to MQTT: Of course, but MySensors MQTT gateway runs just as fine when connected over cabled ethernet, as when connected over wifi I do not know that :) Now on this tool, I do not see much benefit from ethernet to MQTT ;) Still, it is good from serial to MQTT.

Perhaps my definition about "controller", is a bit broad here. What could be done, is to have a thin "controller", that receives MQTT from the existing gateway, hands out IDs if they are requested from a new node, and translate the message into homie compliant topics. That is all it has to do, should not care about the rest of the automation at all. Should also be able to translate back from homie compliant to mysensors. This could be written in python, c#, javascript, rust etc. The benefit is that you have (relatively) easy editing of configurations at hands, without re-uploading sketches to your gateways / nodes, if you decide that node X should be named Y instead. And I am in no way trying to treat anyone as a fool!

https://web.archive.org/web/20201201193332/https://github.com/aetas/mqgateway might be somewhat useful

@kimot Thank you for your comment & tips.

Hello Thanks it worked -- with mock sensor sketch for now. I think I should be able to use this in production. :-) Cheers Puneit

After more investigations I believe the problem is caused by a mqtt server connection timeout. By default the gateway tries to send the radio message 5 times. If I lower the number of retries , 2 for example, no more loop. Probably now much more then 25 messages cause a loop. For testing I added _MQTT_client.loop() in transportSendWrite() (MyTransport.cpp) and, no more loop with default 5 retries.

Hi, for everyone who reads all of this, forget about the last few posts. I don't know why it works even when the Interrups are masked out on the radio, but it works now. The error I had occured because of the config of the OrangePi-Gateway. I removed: --extra-cxxflags="-DMY_RF24_DATARATE=\(RF24_250KBPS\) -DMY_RF24_BASE_RADIO_ID=\(0x00,0xFC,0xE1,0xA8,0xA8\) -DMY_DEBUG_VERBOSE_RF24" and wrote: --extra-cxxflags="-DMY_RF24_DATARATE=\(RF24_250KBPS\) -DMY_DEBUG_VERBOSE_RF24" Now I think I have an working OrangePi-Gateway without signing but with interrupt enabled. If there are new problems I will come back here. The next step for me is to activate signing again and bring the node into homeassistant.

By creating the file org.eclipse.smarthome.mqttbroker.cfg in the service folder (/usr/local/etc/openhab2/services in my case, chown to openhab), with the contents name=mosquitto host=192.168.1.69 secure=false port=1883 username= password= retain=true I was able to just create the MySensors MQTT gateway (using paperui) and it stayed online (no mqtt broker defined, but its addon is installed). I had the impressions that with the latest versions it should be possible to do everything in the PaperUI, and that the broker would use the mqtt2 addon (but in paper ui, service, config, mqtt tab, mqtt system broker connection, manage->plus button -> expert mode, I get to see the contents of the cfg file above) But unfortunately, it seems that the discovery services enters a endless loop (maybe I need to update my arduinos sketch to the latest mysensors code?) and I don't get any auto discovered things. If I trigger a new discovery it will stop the previous one and start again. Finally, I was able to manually create a thing, and link items on it. Eventually my battery level and humidity were displayed in the paper ui control page (after some weird delay, not updating once it shows in the log. the temperature didn't show up though). Not sure if my understanding is off (or paperui is limited in this sense) but in the "thing" creation page I only get to specify one child id. Then my multi sensors/value nodes would need to be define in multiple things? As I can't properly define channels for each child id, and I'm not sure what var1-5 are all about. I'll try defining things/channels/items directly in files in the following days, because so far I couldn't enjoy most of the benefits of this new version (auto discovery, logical grouping of physical device in "things", questionable "do-it-all in paper ui"), and I'm almost considering using mqtt1 binding in the new install :(

@yakcrac try the download link in the top menu

Just one final question... is the approach to MQTT correct or should I stick with simple Ethernet? I was planning on using OpenHab or Home Assistant. Thank You all

what version of esp8266 definitions are you using?

After upgrading Wemos from 2.3.0 to 2.4.0-RC2 version, OTA works well know :smiley:

Thanks for your fast reply. That sounds easy. And you think that the communication between sensor nodes and Gateway are still possible via wired RS485? I tried to find an example on this site for sending Information from Gateway to sensor nodes. (via SendMessage ?) For example I like to Switch on/off an light that is connected to an relay board at my sensor node. Communcation Flow: OpenHab2 --> MQTT --> Gateway --> RS485 --> Sensor Node --> Relay Board Currently I have an working RS485 Connection between my Arduino Uno's with the use from SoftwareSerial library. During my testings I realized, that the message that I triy to send "Hello" will be sent to the other arduino char by char. Is that true? Because I tried to raise up an pin on HIGH with "if(msg == "Hello")..." But it doesn't worked. Will the sendMsg method from the MySensor library handle this out of the box? Regards, Simon

I'd say it is the same but it would you will need to do more coding I guess. There is a node-red Google group if you want to ask there also.