I've been able to get MySensors working with HomeGenie using the MQTT gateway. It doesn't have two-way communication or software-based pairing yet, but I'll work on those in the future.
@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)
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
@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.
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
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.
@sentur since it was launched 6 days ago, I seriously doubt anyone has had the ability to try it.
Anyway, please don't post the same question in multiple places. It wastes people's time. Most users don't have as much time as they would like to spend on projects, and wasting their time by splitting the discussion to multiple threads isn't very nice.
In case anyone wants to follow the existing discussion, head over to https://forum.mysensors.org/post/84076
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.
