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.