@chrishiscox said in OH3 Serial Gateway Problem:

I tried and tried with my serial gateway, and never got it to function porperly. The serial port was working I could see it and data, but OH3 just refused to recognise the data. After a week, I decided to abandon the serial and flashed a esp8266 attached the nRF to it and bobs my uncle as we say. It goes via MQTT, so takes a little more settting up but works fine. If you want more info I will dig out the pages I used to make it work.

Hmmm, the pi OH is running on already has an active MQTT broker. So you got me thinking: Wouldn't it be possible to use the MQTT gateway instead of the serial gateway? It should be able to translate radio messages (Hope RF69 in my case) to mqtt messages which are already recognized by OH. I'll have to find a spare pi and try it.

Hello,

trying to update a OH2.5 installation to the current release 3.2 I ran into a problem with the MySeonsors Serial Gateway Binding. So far I found a link to Tim's Binding mysensors-3.1.0.jar (by the way: a big thank you @TimO) and was able to install it. I also added feature:install openhab-transport-serial and feature:install openhab-core-io-transport-mqtt. But now OH throws an error:
Could not resolve module: org.openhab.binding.mysensors [270]
Unresolved requirement: Import Package: org.apache.commons.lang; version "[2.6.0.3.0.0]"

I have no idea how to resolve this. I added the package libcommons-lang-java via apt, but it didn't help. Would I need to wait for a Version 3.2 of the binding or is there a way to adapt it myself? Am I missing some component in OH? Any help is highly appreciated.

just a small correction: it's a Raspberry Pi Gateway, but probably this makes no difference

Dear Forum
I would appreciate some pointers making a gas meter sensor working in openhab using a serial gateway. I used the water meter sketch and redefined S_WATER with S_GAS. The sensors shows up in openhab and reports data, but the data never gets stored as item.

The Sensor sketch uses:
#define CHILD_ID 1 // Id of the sensor child
MyMessage flowMsg(CHILD_ID,V_FLOW);
MyMessage volumeMsg(CHILD_ID,V_VOLUME);
MyMessage lastCounterMsg(CHILD_ID,V_VAR1);

things definition:
Bridge mysensors:bridge-eth:mybridge [ ipAddress="127.0.0.1", tcpPort=5003, sendDelay=100, networkSanCheckEnabled=true ] {
Thing gasMeter Meter_Gas [ nodeId=100, childId=1 ] {
Channels:
Type number : volume []
Type number : flow []
Type number : var1 []
}
}

items definition:
Number Gas_Flow "GasFlow" <flow> (Gas) ["Meter"] {channel="mysensors:gasMeter:mybridge:Meter_Gas:flow"}
Number Gas_Volume "GasVol" <volume> (Gas) ["Meter"] {channel="mysensors:gasMeter:mybridge:Meter_Gas:vol"

openhab receives the messages and shows them in the gateway debug output:
Message from gateway received: 100;1;1;0;24;36
Node 100 found in gateway
Child 1 found in node 100
Message from gateway received: 100;1;1;0;35;0.360
Node 100 found in gateway
Child 1 found in node 100

But the output of the other (working) sensors is then processed and stored:
Updating channel: hum(V_HUM) value to: 49.2
Humidity1 changed from 48.2 to 49.2

How can I specifythe channels correctly in the things and items file? Would it be better to use seperate child Ids instead of channels?