Getting MySensors MQTT Gateway working on OpenHAB 2.2 (Stable)
-
Hi all, and thanks for the previous posts.
I was having the same issue where the Bridge would stay as INITIALIZING. My set up is a little different as I use Openhan on docker with the following volumes mounting in /opt/openhab:
-v /etc/localtime:/etc/localtime:ro \ -v /etc/timezone:/etc/timezone:ro \ -v /opt/openhab/conf:/openhab/conf \ -v /opt/openhab/userdata:/openhab/userdata \ -v /opt/openhab/addons:/openhab/addons \ -v /opt/openhab/.java:/openhab/.java \I'm using OH2.3 with the Docker Image: openhab/openhab:2.3.0-amd64-debian and the location of the org.eclipse.smarthome.mqttbroker.cfg file is in /opt/openhab/userdata/config/org/eclipse/smarthome.
After making all the changes above I couldn't get the Brdige to work, until finally I downloaded the MySensors addon 2.4.0 from http://www.oberfoell.com/openhab2/org.openhab.binding.mysensors-2.4.0-SNAPSHOT.jar as suggested by @MasMat and placed it in /opt/openhab/addons.
Immediately the status of the bridge changed to ONLINE.
Hope this helps sombedy.
C
-
@timo I did. I can't figure out where it's finding that .0 it adds to the 1883 port I have in the cfg-file
Were You able to find out what is wrong regarding MQTT port 1883.0
Suddenly I have the same error...no idea why. It was working just yesterday. -
This post is deleted!
-
I am very new to openHAB but I am really getting crazy with it. I did exactly what was on top of the screen. But I get an error the MYSensors MQTT Gateway was initializing.. and never came out. So I continue too read and I switch to the binding v 2.4.0. But wathever I do I get an error:
mysensors:bridge-mqtt:gateway' changed from INITIALIZING to UNINITIALIZED (HANDLER_INITIALIZING_ERROR): org/eclipse/smarthome/io/transport/mqtt/MqttActionCallbackI am not sure where to look and what to change. This is in my demo.things file.
Bridge mysensors:bridge-mqtt:gateway [ brokerName="mosquitto", topicPublish="mygateway1-in", topicSubscribe="mygatewa$ temperature temp01 [ nodeId=5, childId=0 ] }org.eclipse.smarthome.mqttbroker.cfg:
name=mosquitto host=192.168.10.4 <- This points to the MySensors gateway PI (different then the openHAB) secure=false port=1883 retain=falseAny idears what I can try?
-
I am very new to openHAB but I am really getting crazy with it. I did exactly what was on top of the screen. But I get an error the MYSensors MQTT Gateway was initializing.. and never came out. So I continue too read and I switch to the binding v 2.4.0. But wathever I do I get an error:
mysensors:bridge-mqtt:gateway' changed from INITIALIZING to UNINITIALIZED (HANDLER_INITIALIZING_ERROR): org/eclipse/smarthome/io/transport/mqtt/MqttActionCallbackI am not sure where to look and what to change. This is in my demo.things file.
Bridge mysensors:bridge-mqtt:gateway [ brokerName="mosquitto", topicPublish="mygateway1-in", topicSubscribe="mygatewa$ temperature temp01 [ nodeId=5, childId=0 ] }org.eclipse.smarthome.mqttbroker.cfg:
name=mosquitto host=192.168.10.4 <- This points to the MySensors gateway PI (different then the openHAB) secure=false port=1883 retain=falseAny idears what I can try?
@martim I'm running OpenHAB with a few MYS sensors (and other subsystems) and I really like the system system. It is complex with a steep learning curve but incredibly flexible and powerful.
As for your problems with MYS/MQTT I have no solution but to use the direct connection over ethernet instead. I have tried switching to MQTT twice and failed miserably both times.
The MYS addon requires the new MQTT binding which easily collides with the old one. (The new MQTT binding is almost ready for release so it may have been fixed, if you are lucky.)
I don't know if the cause of this problem is with the OpenHAB MQTT bindings or with the MYS binding but it was not trivial to fix with the instructions available. As I could not really see any upside of using MQTT except to have an "all MQTT System" I went back to the ethernet connection which works fine.
I would recommend connecting it as ethernet connection first and get it working that way. Then you can switch to MQTT if you want to. The biggets hurdles are installation of supportive packages (mqtt and serial transports) and getting MQTT to work in parallel with MQTT binding version 1. If you post your logs (WARN level for the Mys binding) I can try help you decode it.
-
@martim I'm running OpenHAB with a few MYS sensors (and other subsystems) and I really like the system system. It is complex with a steep learning curve but incredibly flexible and powerful.
As for your problems with MYS/MQTT I have no solution but to use the direct connection over ethernet instead. I have tried switching to MQTT twice and failed miserably both times.
The MYS addon requires the new MQTT binding which easily collides with the old one. (The new MQTT binding is almost ready for release so it may have been fixed, if you are lucky.)
I don't know if the cause of this problem is with the OpenHAB MQTT bindings or with the MYS binding but it was not trivial to fix with the instructions available. As I could not really see any upside of using MQTT except to have an "all MQTT System" I went back to the ethernet connection which works fine.
I would recommend connecting it as ethernet connection first and get it working that way. Then you can switch to MQTT if you want to. The biggets hurdles are installation of supportive packages (mqtt and serial transports) and getting MQTT to work in parallel with MQTT binding version 1. If you post your logs (WARN level for the Mys binding) I can try help you decode it.
-
I spend again a few hours. I really want to get it to work with MQTT as I have my complete system based on it. But Apparently, the binding does not work and also the log does not say much. Only those errors:
2018-12-17 11:38:03.559 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occurred while initializing handler of thing 'mysensors:bridge-mqtt:gateway': org/eclipse/sma ansport/mqtt/MqttActionCallback java.lang.NoClassDefFoundError: org/eclipse/smarthome/io/transport/mqtt/MqttActionCallback at java.lang.ClassLoader.defineClass1(Native Method) ~[?:?] at java.lang.ClassLoader.defineClass(ClassLoader.java:763) ~[?:?] at org.eclipse.osgi.internal.loader.ModuleClassLoader.defineClass(ModuleClassLoader.java:276) ~[?:?] at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.defineClass(ClasspathManager.java:655) ~[?:?] at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findClassImpl(ClasspathManager.java:578) ~[?:?] at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClassImpl(ClasspathManager.java:538) ~[?:?] at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:525) ~[?:?] at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:328) ~[?:?] at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:368) ~[?:?] at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:446) ~[?:?] at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:395) ~[?:?] at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:387) ~[?:?] at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150) ~[?:?] at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:?] at org.openhab.binding.mysensors.internal.protocol.mqtt.MySensorsMqttConnection.<init>(MySensorsMqttConnection.java:44) ~[?:?] at org.openhab.binding.mysensors.internal.gateway.MySensorsGateway.setup(MySensorsGateway.java:99) ~[?:?] at org.openhab.binding.mysensors.handler.MySensorsBridgeHandler.initialize(MySensorsBridgeHandler.java:81) ~[?:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?] at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [101:org.eclipse.smarthome.core:0.10.0.oh230] at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [101:org.eclipse.smarthome.core:0.10.0.oh230] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?] at java.lang.Thread.run(Thread.java:748) [?:?] Caused by: java.lang.ClassNotFoundException: org.eclipse.smarthome.io.transport.mqtt.MqttActionCallback cannot be found by org.openhab.binding.mysensors_2.4.0.201812040738 -
I spend again a few hours. I really want to get it to work with MQTT as I have my complete system based on it. But Apparently, the binding does not work and also the log does not say much. Only those errors:
2018-12-17 11:38:03.559 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occurred while initializing handler of thing 'mysensors:bridge-mqtt:gateway': org/eclipse/sma ansport/mqtt/MqttActionCallback java.lang.NoClassDefFoundError: org/eclipse/smarthome/io/transport/mqtt/MqttActionCallback at java.lang.ClassLoader.defineClass1(Native Method) ~[?:?] at java.lang.ClassLoader.defineClass(ClassLoader.java:763) ~[?:?] at org.eclipse.osgi.internal.loader.ModuleClassLoader.defineClass(ModuleClassLoader.java:276) ~[?:?] at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.defineClass(ClasspathManager.java:655) ~[?:?] at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findClassImpl(ClasspathManager.java:578) ~[?:?] at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClassImpl(ClasspathManager.java:538) ~[?:?] at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:525) ~[?:?] at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:328) ~[?:?] at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:368) ~[?:?] at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:446) ~[?:?] at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:395) ~[?:?] at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:387) ~[?:?] at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150) ~[?:?] at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:?] at org.openhab.binding.mysensors.internal.protocol.mqtt.MySensorsMqttConnection.<init>(MySensorsMqttConnection.java:44) ~[?:?] at org.openhab.binding.mysensors.internal.gateway.MySensorsGateway.setup(MySensorsGateway.java:99) ~[?:?] at org.openhab.binding.mysensors.handler.MySensorsBridgeHandler.initialize(MySensorsBridgeHandler.java:81) ~[?:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?] at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [101:org.eclipse.smarthome.core:0.10.0.oh230] at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [101:org.eclipse.smarthome.core:0.10.0.oh230] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?] at java.lang.Thread.run(Thread.java:748) [?:?] Caused by: java.lang.ClassNotFoundException: org.eclipse.smarthome.io.transport.mqtt.MqttActionCallback cannot be found by org.openhab.binding.mysensors_2.4.0.201812040738@martim Don't use the binding! Use plain MQTT.I'd love to have a simple working binding but it isn't there yet. Use plain mqtt elements and it'll work great.The new mqtt binding works. I don't like the mechanism needed to configure the broker, and then each thing, but works, and it is in fact more integrated with openhab than ever.
If you have any questions do not hesitate to contact me.
-
java.lang.NoClassDefFoundError: org/eclipse/smarthome/io/transport/mqtt/MqttActionCallbackThe new MQTT binding requires parts of the new automation engine. This is missing from your system for some reason. Should be automatically installed when MQTT or the MySensors binding are installed.
I'd love to have a simple working binding but it isn't there yet. Use plain mqtt elements and it'll work great.
This statement is not correct. The OH 2.4 release officially supports the new binding and if any errors are reported, they are getting fixed. The new binding allows Paper UI and textual configuration so there is no reason to start with mqtt1 nowadays.
Cheers,
David -
java.lang.NoClassDefFoundError: org/eclipse/smarthome/io/transport/mqtt/MqttActionCallbackThe new MQTT binding requires parts of the new automation engine. This is missing from your system for some reason. Should be automatically installed when MQTT or the MySensors binding are installed.
I'd love to have a simple working binding but it isn't there yet. Use plain mqtt elements and it'll work great.
This statement is not correct. The OH 2.4 release officially supports the new binding and if any errors are reported, they are getting fixed. The new binding allows Paper UI and textual configuration so there is no reason to start with mqtt1 nowadays.
Cheers,
David@davidgraeff Yes David, you are correct. The new binding works. I'm in fact using it and with the corresponding changes on the items files its ok.
I would love some kind of auto discovery though. In order to create each thing you have to manually enter the topic (which on mysensors is very complex)
Anyways, I will try to edit previous message which is in fact wrong.
-
@jogant Finally had time to double check this:
Paper UI:Broker Name mosquitto Subscription Topic mygateway1-out Publish Topic mygateway1-in Send Delay 100 Startup check enabled Metric answer enabled Network sanity check enabled Interval to launch network sanity check 3 Attempts before disconnecting the bridge 3 Heartbeat disabled Attempts before disconnecting nodes 10EDIT: I noticed I have different topics in MQTT, corrected AND I did:
cd /usr/share/openhab2/addons/ wget http://www.oberfoell.com/openhab2/org.openhab.binding.mysensors-2.4.0-SNAPSHOT.jar <== THIS probably fixed it! chown for the same file rm org.openhab.binding.mysensors-2.3.0-SNAPSHOT.jarNow my MQTT Gw is ONLINE, in Paper UI I just selected the bridge for every individual Thing and now it works.
Hope this helps people strugling with this.@masmat Yes!!!! Thank you man. I found 2.4.0 thanks to your message and now it's working!
Love
-
This post is deleted!
-
Hi all, I am a Newbie an trying to get OH2.4 to work with MySensors nodes.
I have a MYS Mqtt ethernet GW up&running (seems to work, can talk to other sensors)
Now I can't get MQTT thing/broker/binding to work in OH2.4. I first tries the manual above, then I read that Musquitto is not needed any more....right??
I have to use MQTT 2.4 Ting binding and MQTT broker right? -> I have installed this and have MQTT broker running on localhost (online) (no channels addes in MQTT broker)
I have added in Things: MysensorsMQTT gateway: broker name: "MQTT Broker" and 'startup check' and 'sanity check' ON
Then I checked from the CLI the file "org.eclipse.smarthome.mqtt.cfg" ->there was still the musquitto entries I made... Also in mqtt-eventbus.cfg was still broker=musquitto. What do I do with this??
In OH log I get errors:****2019-02-10 21:52:35.274 [me.event.ThingUpdatedEvent] - Thing 'mysensors:bridge-mqtt:9954d183' has been updated. 2019-02-10 21:52:35.682 [hingStatusInfoChangedEvent] - 'mysensors:bridge-mqtt:9954d183' changed from UNINITIALIZED (HANDLER_INITIALIZING_ERROR): org/openhab/binding/mysensors/internal/protocol/mqtt/MySensorsMqttConnection$MySensorsMqttPublishCallback to INITIALIZING 2019-02-10 21:52:35.685 [hingStatusInfoChangedEvent] - 'mysensors:bridge-mqtt:9954d183' changed from INITIALIZING to UNINITIALIZED (HANDLER_INITIALIZING_ERROR): org/openhab/binding/mysensors/internal/protocol/mqtt/MySensorsMqttConnection$MySensorsMqttPublishCallback**** ---*Next problem:
I installed the MySensors Ethernet gateway thing in OH, configged it with IP of Arduino running the Mys GW. -> This Thing will NOT come 'online'. I can Ping the GW board, all looks OK in GW log:0 MCO:BGN:INIT GW,CP=RNNGA---,REL=255,VER=2.3.1 4 TSM:INIT 5 TSF:WUR:MS=0 11 TSM:INIT:TSP OK 13 TSM:INIT:GW MODE 15 TSM:READY:ID=0,PAR=0,DIS=0 17 MCO:REG:NOT NEEDED 580 GWT:TPC:IP=192.168.178.87 1583 MCO:BGN:STP 1585 MCO:BGN:INIT OK,TSP=1 1588 GWT:TPC:IP=192.168.178.87 2590 GWT:RMQ:MQTT RECONNECT 2798 GWT:RMQ:MQTT CONNECTED 2801 GWT:TPS:TOPIC=mygateway1-out/0/255/0/0/18,MSG SENT 2807 TSM:READY:NWD REQ 2844 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK: 0 MCO:BGN:INIT GW,CP=RNNGA---,REL=255,VER=2.3.1 4 TSM:INIT 5 TSF:WUR:MS=0 11 TSM:INIT:TSP OK 13 TSM:INIT:GW MODE 15 TSM:READY:ID=0,PAR=0,DIS=0 17 MCO:REG:NOT NEEDED 580 GWT:TPC:IP=192.168.178.87 1583 MCO:BGN:STP 1585 MCO:BGN:INIT OK,TSP=1 1588 GWT:TPC:IP=192.168.178.87 2590 GWT:RMQ:MQTT RECONNECT 2798 GWT:RMQ:MQTT CONNECTED 2800 GWT:TPS:TOPIC=mygateway1-out/0/255/0/0/18,MSG SENT 2807 TSM:READY:NWD REQ 2844 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK: 3810 TSF:MSG:READ,254-254-0,s=255,c=3,t=21,pt=1,l=1,sg=0:0 3815 GWT:TPS:TOPIC=mygateway1-out/254/255/3/0/21,MSG SENT 636790 TSF:MSG:READ,254-254-0,s=255,c=3,t=0,pt=1,l=1,sg=0:99 636795 GWT:TPS:TOPIC=mygateway1-out/254/255/3/0/0,MSG SENT 637304 TSF:MSG:READ,254-254-0,s=255,c=3,t=1,pt=0,l=0,sg=0: 637309 GWT:TPS:TOPIC=mygateway1-out/254/255/3/0/1,MSG SENT 637815 TSF:MSG:READ,254-254-0,s=1,c=1,t=16,pt=2,l=2,sg=0:0 637820 GWT:TPS:TOPIC=mygateway1-out/254/1/1/0/16,MSG SENT 637827 TSF:MSG:READ,254-254-0,s=1,c=1,t=15,pt=1,l=1,sg=0:1 637832 GWT:TPS:TOPIC=mygateway1-out/254/1/1/0/15,MSG SENT 637838 TSF:MSG:READ,254-254-0,s=7,c=1,t=0,pt=4,l=4,sg=0:44 637844 GWT:TPS:TOPIC=mygateway1-out/254/7/1/0/0,MSG SENT 637850 TSF:MSG:READ,254-254-0,s=255,c=3,t=0,pt=1,l=1,sg=0:99 637855 GWT:TPS:TOPIC=mygateway1-out/254/255/3/0/0,MSG SENT 900006 TSF:SAN:OKHow do I proceed? Ive tried to find more posts on getting MySensors to work under OH24 but I think it is sooo simple that nobody has any problems to post....right?!
Hope you guys can get this Newbie back on track.... thx a lot! -
Hi all, I am a Newbie an trying to get OH2.4 to work with MySensors nodes.
I have a MYS Mqtt ethernet GW up&running (seems to work, can talk to other sensors)
Now I can't get MQTT thing/broker/binding to work in OH2.4. I first tries the manual above, then I read that Musquitto is not needed any more....right??
I have to use MQTT 2.4 Ting binding and MQTT broker right? -> I have installed this and have MQTT broker running on localhost (online) (no channels addes in MQTT broker)
I have added in Things: MysensorsMQTT gateway: broker name: "MQTT Broker" and 'startup check' and 'sanity check' ON
Then I checked from the CLI the file "org.eclipse.smarthome.mqtt.cfg" ->there was still the musquitto entries I made... Also in mqtt-eventbus.cfg was still broker=musquitto. What do I do with this??
In OH log I get errors:****2019-02-10 21:52:35.274 [me.event.ThingUpdatedEvent] - Thing 'mysensors:bridge-mqtt:9954d183' has been updated. 2019-02-10 21:52:35.682 [hingStatusInfoChangedEvent] - 'mysensors:bridge-mqtt:9954d183' changed from UNINITIALIZED (HANDLER_INITIALIZING_ERROR): org/openhab/binding/mysensors/internal/protocol/mqtt/MySensorsMqttConnection$MySensorsMqttPublishCallback to INITIALIZING 2019-02-10 21:52:35.685 [hingStatusInfoChangedEvent] - 'mysensors:bridge-mqtt:9954d183' changed from INITIALIZING to UNINITIALIZED (HANDLER_INITIALIZING_ERROR): org/openhab/binding/mysensors/internal/protocol/mqtt/MySensorsMqttConnection$MySensorsMqttPublishCallback**** ---*Next problem:
I installed the MySensors Ethernet gateway thing in OH, configged it with IP of Arduino running the Mys GW. -> This Thing will NOT come 'online'. I can Ping the GW board, all looks OK in GW log:0 MCO:BGN:INIT GW,CP=RNNGA---,REL=255,VER=2.3.1 4 TSM:INIT 5 TSF:WUR:MS=0 11 TSM:INIT:TSP OK 13 TSM:INIT:GW MODE 15 TSM:READY:ID=0,PAR=0,DIS=0 17 MCO:REG:NOT NEEDED 580 GWT:TPC:IP=192.168.178.87 1583 MCO:BGN:STP 1585 MCO:BGN:INIT OK,TSP=1 1588 GWT:TPC:IP=192.168.178.87 2590 GWT:RMQ:MQTT RECONNECT 2798 GWT:RMQ:MQTT CONNECTED 2801 GWT:TPS:TOPIC=mygateway1-out/0/255/0/0/18,MSG SENT 2807 TSM:READY:NWD REQ 2844 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK: 0 MCO:BGN:INIT GW,CP=RNNGA---,REL=255,VER=2.3.1 4 TSM:INIT 5 TSF:WUR:MS=0 11 TSM:INIT:TSP OK 13 TSM:INIT:GW MODE 15 TSM:READY:ID=0,PAR=0,DIS=0 17 MCO:REG:NOT NEEDED 580 GWT:TPC:IP=192.168.178.87 1583 MCO:BGN:STP 1585 MCO:BGN:INIT OK,TSP=1 1588 GWT:TPC:IP=192.168.178.87 2590 GWT:RMQ:MQTT RECONNECT 2798 GWT:RMQ:MQTT CONNECTED 2800 GWT:TPS:TOPIC=mygateway1-out/0/255/0/0/18,MSG SENT 2807 TSM:READY:NWD REQ 2844 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK: 3810 TSF:MSG:READ,254-254-0,s=255,c=3,t=21,pt=1,l=1,sg=0:0 3815 GWT:TPS:TOPIC=mygateway1-out/254/255/3/0/21,MSG SENT 636790 TSF:MSG:READ,254-254-0,s=255,c=3,t=0,pt=1,l=1,sg=0:99 636795 GWT:TPS:TOPIC=mygateway1-out/254/255/3/0/0,MSG SENT 637304 TSF:MSG:READ,254-254-0,s=255,c=3,t=1,pt=0,l=0,sg=0: 637309 GWT:TPS:TOPIC=mygateway1-out/254/255/3/0/1,MSG SENT 637815 TSF:MSG:READ,254-254-0,s=1,c=1,t=16,pt=2,l=2,sg=0:0 637820 GWT:TPS:TOPIC=mygateway1-out/254/1/1/0/16,MSG SENT 637827 TSF:MSG:READ,254-254-0,s=1,c=1,t=15,pt=1,l=1,sg=0:1 637832 GWT:TPS:TOPIC=mygateway1-out/254/1/1/0/15,MSG SENT 637838 TSF:MSG:READ,254-254-0,s=7,c=1,t=0,pt=4,l=4,sg=0:44 637844 GWT:TPS:TOPIC=mygateway1-out/254/7/1/0/0,MSG SENT 637850 TSF:MSG:READ,254-254-0,s=255,c=3,t=0,pt=1,l=1,sg=0:99 637855 GWT:TPS:TOPIC=mygateway1-out/254/255/3/0/0,MSG SENT 900006 TSF:SAN:OKHow do I proceed? Ive tried to find more posts on getting MySensors to work under OH24 but I think it is sooo simple that nobody has any problems to post....right?!
Hope you guys can get this Newbie back on track.... thx a lot!Hi @rene-mullie,
Seems like the mysensors binding mqtt gw doesnt play nice with the mosquitto broker. You can try running the embedded broker of openhab (paperUi->addons->misc->embedded broker i beleive). Dont forget to configure it under services->misc (not shure since im on my phone right now). And connect your mqtt gateway to this broker. I was not succesful in this because i need the embedded broker on port 1884 since i allready have mosquitto on port 1883 for other stuff. And i <think> mysensors mqtt gateway doesnt want to connect to 1884 but 1883. But you can give it a try. If you have ethernet gateway going and dont have plans to use different controllers (for example to do FOTA updates) i would stick to the ethernet gw for now. Greets
-
I have configged the embedded broker in right way, broker is online on localhost.
I tried to connect Mys mqtt gateway to Embedded mqtt broker in paper UI:Broker Name
MQTT Broker (-> not sure about this name....??)
name of the MQTT broker as defined in the org.eclipse.smarthome.mqtt.cfg file``` (-> if I check this cfg file there is NOTHING about the embedded broker, only old Musquitto stuf...)All is on default port 1883 on both sides...
I get fault in OH log file:
2019-02-10 23:40:56.626 [ERROR] [al.protocol.ip.MySensorsIpConnection] - Failed connecting to bridge...next retry in 10 seconds (Retry No.:15) -
@waspie tried that, still same errors...
What should be the entries in the org.eclipse.smarthome.mqtt.cfg file ? -
@waspie tried that, still same errors...
What should be the entries in the org.eclipse.smarthome.mqtt.cfg file ?@rene-mullie delete it
-
@waspie tried that, still same errors...
What should be the entries in the org.eclipse.smarthome.mqtt.cfg file ?@rene-mullie if im not mistaken that file is to configure mqtt v1 and your using mqtt v2
-
Thx4 your support! I gave up on fixing the old install and started over with brand new install of OH2.4: All was up&running in 45mins!! MQTT2.4 with embedded broker works like a charm. On top the Mysensors MQTT GW Ting was online with 1-click! All my MYsensor nodes where recognized immediately! What a relief!
Hope someone will update Mysensors docu so others will be spared the pain...