@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

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.

I have posted a question regarding what i think could be the fix to my issue over at: https://community.openhab.org/t/push-state-of-one-mqtt-topic-to-another/27597 Not sure if it will become of anything though. If anyone else has any experience with MQTT and openhab2 over here, then please be sure to shout a thought. It seems that not many people have got this sketch to work with openhab, google searches are bringing up posts from a year or two ago made on our forum here regarding this issue with no clear/simple solution.

I am not able to install the Library . I am getting Error Invalid library found in C:\Documents and Settings\User\My Documents\Arduino\libraries\ESP8266MQTTMesh: C:\Documents and Settings\User\My Documents\Arduino\libraries\ESP8266MQTTMesh. I changed the name of the zipped file to ESP8266MQTTMesh as the name of .cpp file ESP8266MQTTMesh.cpp. Still it is saying Invalid Library found in .... What could be the problem.

good, give it a try

Might be helpful for somebody... Things configuration for OpenHab2: Bridge mysensors:bridge-eth:gateway_2 [ ipAddress="192.168.178.50", tcpPort=5003, sendDelay=200, enableNetworkSanCheck=true ] { /** define things connected to that bridge here */ light sonoff01 [ nodeId="0", childId="0", requestAck=true ] }

@Michael_K , If we go from the front to the back this is what is needed: 1 Node: For example a door bell. This node sends information to a gateway. 2 The gateway takes the message from the node and sends this to a controller. For instance Openhab or Domotics. This can be done in several ways. MqTT being one. 3 Controller: takes the information and displays it to you. So in my case, I hardcode Node ID and CHILD ID (the complete door bell is a NODE whereas CHILD IDs may be the button pressed and maybe temperature reading at the same time). This sends to Gate way that takes the information and creates a MqTT message. What this message is, please read the instructions on this site.

Yes, a release is coming. But we haven't set any date yet. Suggest you install it manually.

by hek: This PR was merged a few days ago: https://github.com/mysensors/MySensors/pull/633

nevermind. now after all upgrades AND BATTERY CHANGE to sensebender it's all fine

Ive started out with openHAB2. I was using a Ethernet gateway and tested the mysensors binding but found the combo was too limited. I much prefer having the MQTT gateway and the data be accessible to anything that subscribes, although I also now use openHAB to republish its item changes to MQTT as well which is probably a better approach. I don't think the main new features in version 2 are very mature at the moment as well, discovered things for example get put in to a non human readable database and the web ui's are not fully functional. With that being said I'm using node red to provide node ID's and configuring items manually and since beta3 it's been solid as a rock.

wdt.h is included on Arduino IDE. This example show how it's work: #include <avr/wdt.h> int counter=0; void setup(){ wdt_disable(); Serial.begin(9600); Serial.println("Starting..."); delay(1000); wdt_enable(WDTO_8S); } void loop(){ wdt_reset(); Serial.println(counter); counter++; if(counter==5){ while(true){} } delay(500); }```

@Eric-Buhring I found that changing the line in the my sensors program that sends the message as below allowed me to use a Contact rather than a Switch if (value != sentValue2) { // Value has changed from last transmission, send the updated value send(msg2.set(value==HIGH?"OPEN":"CLOSED")); sentValue2 = value; }

@Eric-Buhring great to hear that you managed to get it working. I have used solution like this (arduino+eth. shield+rf24) for some time. Now I have switched to esp8266+rf24(version with antenna) as a gateway, it is a cool (and smaller) solution

can you login to the mqtt server with any mqtt client for computer (like mqtt spy or similar)?

Qu3Uk, I did get a chance to test with a Fitbit recently. It technically worked, but not all that well. The thing is, the Fitbit only advertises every 2 seconds so latency is a bit high. But worse, its apps really want to be connected to it often to sync; and whenever it's connected, it stops advertising and the detector then can't pick it up. TommySharp, At this point I don't plan to modify the board much but having it read environmental sensors would be a cool feature! For that, would be nice to make little beacons that read sensors and advertise/broadcast the readings every few seconds. Then they could be very low-power, run on coin-cells for months, and could be placed anywhere instead of needing it to be hooked up to USB power like the main board is. Like these: https://sen.se/peanuts/ I'm curious if it could read them. As for enclosures, I know. I would love to have some nice ones but at this point I'm making too many boards to 3D print enclosures, but too few to afford injection-molding tooling to make a custom case.

Never mind figured it out. There was a problem somewhere in that sketch. basically started from scratch again. merged the W5100 MQTT client gateway sketch and the relay sketch. then referred to here for serial MQTT syntax. Hope anyone else thats struggling finds this info useful.

@micah said in Can't get OpenHAB2 to see my MQTT messages: I'm still not sure if the second and third line in the mqtt-eventbus.cfg is correct. I don't have MyMQTT anywhere else, so I think I may try different combinations to see what works. MyMQTT should be replaced with brokername (mysensors in this example). openhab will then publish the event to the mqtt broker on its topics (useful if you use f.eks. node-red for openhab rules)

@UglyKidJoe I have been using OpenHAB and MQTT for a number of years now. The reason for using MQTT and not just a serial connection from the MySensors GW is partly the flexibility as many have stated previously here. Easy to test, using e.g. the mqtt.fx tool. If you want to know what is going on you simply connect to the MQTT stream and "snoop" on the messages. Another reason is that I am running three geographical sites on one OH installation. OH is running on a NUC at my home. There is also an MQTT GW here. Two other My Sensors MQTT-GW are running remotely in two summer houses. The three GW connect over internet to a cloud-based MQTT broker and OH connects to the same broker. In that way I do not have to open any ports into my home network for access should I have had a local MQTT-broker at home.

@DirkB19 Think you will get another advantage by changing as well - must be a lot easier to monitor the MQTT messages when topic clearly shows the difference.

@hek That was very visible, please excuse my ignorance. Even though I have looked at this page I managed to leave the change unnoticed.

Now the RPi based on a new install of Raspbian Jessie, OpenHab 1.8.0 and Mosquitto is up and running and the ESP8266 MQTT client does connect without any problems. I have not changed anything in the code but Mosquitto is now based on the RPi repository for Jessie and not the mosquito_wheezy one. That seems to have fixed it so those versions are likely different but I have not put any time into checking this.

@drock1985 I guess your switch string should be as follows, #Switches (Lights) switch 1: platform: mqtt state_topic: "mygateway1-out/2/1/1/0/2" command_topic: "mygateway1-in/2/1/1/0/2" name: "test1" payload_on: "1" payload_off: "0"

Although i like the idea, it will force you to send a value even if it has not changed. Defeats a bit a battery optimized sensor node.

I think the something about order of initialisation was changed that fixed this problem. Try 1.4.1

@kunall the best recommendation against openhab for me was ugly interface and problems with running it (java). I was using domoticz since early version with own interface on arduino,now I've switched everything for MySensors. It still lacks some functions but Inwait for further development as even programmers of domoticz start to use MyS hardware

Hey there @Chaotic ! This is Fay from codebender.cc Thank you for using codebender! I just wanted to let you know that one of the sketches you are using in this comment has been deleted and so it is not available for users to view it. Let me know if you have any question.

Although it should not be too difficult to make the MQTT Gateway with WiFi work on hardware and software level it is a bad idea on system level: WiFi and MySensensor NRF24L01+ use the same 2.4 GHz band and with the antennas close a transmit from one will block the other and vice-versa.

@celonunes generally raspberry pi with serial usb but also you can see some mqtt logs. Same problem with mac os with serial usb. I also tried rpi uart pins for serial bu there is no logs for it. Maybe someone gives his Openhab dir i can understand better problem isnt related with hardware

@alexeinz figured it out, apparently had to add experimental and get latest mosquitto for the conf file to work correctly , now the bridge is working perfectly --- broker.conf file in /etc/mosquitto/conf.d the topics coming from gw will appear under sensor/# on mosquitto connection MMQTTtoSensor address 192.168.1.234 <-gw ip clientid MyMQTT cleansession true notifications true topic # in 2 sensor/ MyMQTT/

Any updates?

@catcher Thanks, I tried this Perl script and it is working out of the box with OpenHAB2! And I'm sending with MySensors 2.

@lafleur I abandoned it due to the fact that my Nano cannot fit it together with signing support.

I have a project going with openhab and thethingbox. I only use Mqtt with a combination of nrf24l01 and esp8266 modules. thethingbox server is simply used as a catch all for all mqtt messages from sensors or openhab. i parse all the message coming into ththingbox and take action depending on the message. If my door or window sensor is tripped a message is sent to Twitter. I also send temp and humidity readings to thingspeak and my cell phone reports long and lat coordinates to thingspeak so that my lights can come on as I approach the house. My next project is to setup ip cameras and motion sensors and sent pics to drop box. Openhab is really not hard, you just have to keep at it, once you get it you will kick yourself for over complicating it Mike

Very cool! Any more detail you can give on this setup?

Sorry. Hek, I using this code. Vera3 find relay and it works, but also appears 3 door sensors instead of 3 temp sensors. I try to use the my arduino board only with sd18b20 sketch and it work's and show temperature. Is it sketch suitale for vera? @Gambituk said: and here is the modified relay/temp sketch // Running DS temperature sensor(s) and relay(s) on one mysensor arduino node // Combines Onewire and Relay code // 2014-10-14 Pego: Tested and Running on Uno/Clone and MQTT gateway // Example sketch showing how to send in OneWire temperature readings // Example sketch showing how to control physical relays. // This example will remember relay state even after power failure. #include <MySensor.h> #include <SPI.h> #include <DallasTemperature.h> #include <OneWire.h>presen #define ONE_WIRE_BUS 3 // Pin where dallase sensor is connected #define MAX_ATTACHED_DS18B20 16 #define RELAY_1 4 // Arduino Digital I/O pin number for first relay (second on pin+1 etc) #define NUMBER_OF_RELAYS 2 // Total number of attached relays #define RELAY_ON 1 // GPIO value to write to turn on attached relay #define RELAY_OFF 0 // GPIO value to write to turn off attached relay unsigned long SLEEP_TIME = 30000; // Sleep time between reads (in milliseconds) 30000 orig OneWire oneWire(ONE_WIRE_BUS); DallasTemperature sensors(&oneWire); MySensor gw; float lastTemperature[MAX_ATTACHED_DS18B20]; int numSensors=0; boolean receivedConfig = false; boolean metric = true; // Initialize temperature message MyMessage msg(0,V_TEMP); void setup() { // Startup OneWire sensors.begin(); // Startup and initialize MySensors library. Set callback for incoming messages. //gw.begin(); gw.begin(incomingMessage, AUTO, true); // Send the sketch version information to the gateway and Controller gw.sendSketchInfo("Temp and Relays", "1.0"); // Fetch the number of attached temperature sensors numSensors = sensors.getDeviceCount(); // Present all sensors to controller for (int i=0; i<numSensors && i<MAX_ATTACHED_DS18B20; i++) { gw.present(i, V_TEMP); } // Fetch relay status for (int sensor=1, pin=RELAY_1; sensor<=NUMBER_OF_RELAYS;sensor++, pin++) { // Register all sensors to gw (they will be created as child devices) gw.present(sensor, S_LIGHT); // Then set relay pins in output mode pinMode(pin, OUTPUT); // Set relay to last known state (using eeprom storage) digitalWrite(pin, gw.loadState(sensor)?RELAY_ON:RELAY_OFF); } } void loop() { // Process incoming messages (like config from server) gw.process(); // Fetch temperatures from Dallas sensors sensors.requestTemperatures(); // Read temperatures and send them to controller for (int i=0; i<numSensors && i<MAX_ATTACHED_DS18B20; i++) { // Fetch and round temperature to one decimal float temperature = static_cast<float>(static_cast<int>((gw.getConfig().isMetric?sensors.getTempCByIndex(i):sensors.getTempFByIndex(i)) * 10.)) / 10.; // Only send data if temperature has changed more then 1 degC and no error if (int(lastTemperature[i]) != int(temperature) && temperature != -127.00) { //added integer // Send in the new temperature gw.send(msg.setSensor(i).set(temperature,1)); lastTemperature[i]=temperature; } } //gw.sleep(SLEEP_TIME); //no sleep for relays!!!! } void incomingMessage(const MyMessage &message) { // We only expect one type of message from controller. But we better check anyway. if (message.type==V_LIGHT) { // Change relay state digitalWrite(message.sensor-1+RELAY_1, message.getBool()?RELAY_ON:RELAY_OFF); // Store state in eeprom gw.saveState(message.sensor, message.getBool()); // Write some debug info Serial.print("Incoming change for sensor:"); Serial.print(message.sensor); Serial.print(", New status: "); Serial.println(message.getBool()); } }

@bomber Did you find a way to use CC3000 as gateway?

I use a cheap Chinese 5100 module together with the MQTT gateway and it is warm but have not measured any actual temperature. Works 24 hours a day (now for a couple of months). Most problems have been due to the MQTT code implementation itself . But for most "simple" sensors it runs OK with Openhab.

http://forum.mysensors.org/topic/802/mqtt-and-batterylevel/2

@TommySharp Hmm dont really remember, but I think this was the solution https://github.com/knolleary/pubsubclient/issues/46

I have been away for a while but it seams quite some of you are experiencing problems, I'll try to take a look at it. If you find any more details, please let me know!

sensor id is not the same as node id. sensor id = 255 is used for internal stuff like id request and battery level for node. You can assign 0-254 to your own attached sensors (to the arduino node).

Hi @doctor64 , How did you solve the battery reporting? Did you implement the changes in h and cpp file from the link and compiled/uploaded the gateway sketch again?

@ericvdb Yes, I know about the 5V. But the adapter brings it down to 3.3V for the radio, that is the reason for using it and the adapter is equipped with the AMS 1117 3.3V chip. Seems to work OK but I really do not have any hard facts to prove it. One thing I may test is to wire the 5V also directly to this adapter instead of taking it out from the Arduino 5V pin. This is to find out if this Arduino Nano clone might have too small capacity for feeding the radio at certain occasions.

Actually, it's not 100% MySensors-related, but I have a working setup consisting of iBeacon (either HM10-based or PI-based) and Beecon app. When Beecon senses the iBeacon it can trigger various actions, eg make http requests or call IFTTT recipes

And be aware of this thread where the ENC module is hanging after a while.. http://forum.mysensors.org/topic/536/problems-with-enc28j60-losing-connection-freezing-using-uipethernet-or-ethershield-read-this

I think that: It does overlap with MySensors for the wireless network. MQTT-SN assumes a network that provides a bi-directional data transfer service between any node and a particular one (a gateway). MySensors wireless network could provide data transfer but the message are really tailored to transport sensor and actuator values. MQTT-SN for the gateway - controller interface is not needed MQTT is for that more than fine That said I like the idea of MQTT-SN but for it a "transparent network" makes more sense.

I can nothing say about OpenHAB or PiDome but: Started! 0;0;3;0;9;read: 0-0-0 s=0,c=0,t=0,pt=0,l=0: 0;0;3;0;9;version mismatch 0;0;3;0;9;read: 0-0-0 s=0,c=0,t=0,pt=0,l=0: 0;0;3;0;9;version mismatch Does not look good, it seems an error from the gateway.

Hi John, appLog.txt I also tried using datatype string but it doesen't work. Meanwhile I have studies the log files more detailed and found the following behavior: when defining the device skeletal and when updating the derived device (first approx. 25 lines in the log file V_STATUS is declared as string with values 51 resp. 52 as specified in the web interface. The entity is "Modul 433 MHz". Later on, when using the toggle switch in the web interface the value has changed in the decription in the log file (see line 164 or 185) value has been changed to on/off. With this definition it seem that the mysensors-Plugin is feeded has been changed from the specified values. My conclusion is that the change is taking place somewhere outside the mysensors-plugin. By the way, if I change the type to string do I have to use quotation marks in the web interface? Thanks a lot for your support. Martin

@scurb This looks very interesting and my factor now to save me from having to create my own :-). I have been planning to do the same thing (although maybe on a smaller software scale) by writing a simple Python server that would pull serial packets off of a gateway arduino (either running mysensors or something I write myself) and pipe this through MQTT to openHAB. I have two questions: How do you interface with a sensor network? Do you go through a serial connection to read the serial packet format (a,b,c,d)? I see several implementations that put the mqtt client directly on the Arduino, but it seems much cheaper for me to just plug it into a USB port to get a virtual serial port instead of investing in a separate ethernet shield How does an item configurations look like for a switch in openHAB? I'm looking to build a toggle switch which toggles light on or off every time it is activated, and I cannot really understand how to configure the switch to allow this behaviour for an mqtt input. Feel free to take the second question with me directly since this might not be very interesting to the others in the forum