Well, there is a Serial binding. You’ll still need to do a bit of potentially painful configuration to parse out the serial messages.
But that’s not what OH does and it’s not what it’s for. OH is a platform that allows one to bridge 300+ different APIs and technologies from simple web services to the full Zwave/KNX stack. It does this through bindings. Bindings are configured and from there devices are represented as Things. Things have Channels, one for each sensor and actuator. Channels are Linked to Items. Items are used in rules, in the UI, persistence, etc.
All these layers of abstraction are required to be able to present devices from this diverse set of technologies in a unified manner.
And that means to configure OH to receive a UDP packet you’ll need to:
- find and install a binding that talks UDP
- create a Thing for that binding
- configure a Channel for that binding
- create the expressions to parse the UDP message and extract that one piece of information that Channel represents; repeat for the parts of the messages and other messages
- link the appropriate type of Item to the Channel
From here you can probably follow the events.log to see the Items changing as it receives messages.
There is no screen to just print out what was received.
No, it’s work learning how OH works and figuring out how to configure complex stuff like parsing serialized data out of a string of bits without access to code.
Maybe. Remember, I’m unaware of an actual UDP binding in OH in the first place. If you want to wire it up with a serial interface look at the binding docs for that to see what it can do.
There is also the potential to code the parsing in OH rules.
Honestly, I have to ask what brings you to openHAB in the first place then. Or perhaps you haven’t been through the Concepts page in the docs or the Getting Started Tutorial to see how OH actually works.
As I said, OH is designed to bridge between different technologies. If you are happiest living at such a low level of programming to the point that MQTT is too high level for you, I can’t imagine how you’ll ever be happy with OH. OH primarily works at much higher levels and by necessity has layers of abstraction the data has to filter through so that regardless of the technology it’s presented and used in a normalized manner.
Indeed behaviors are coded in programming languages (when x happens do y). But connections to devices are configured, not coded.