That's exactly the same reason why I bought the Razberry. If I wanted a home automation platform I would have bought something like Fibaro HC2 or the Zipabox instead. Subscribing to events is a feature I also hoped was available as ZWay seemed to be a bit more hacker/developer focused.bc-109 wrote: When I bought a Razberry, I didn't want to buy a "home automation software". I wanted to buy a "Z-Wave transceiver", with an API, so that I can control it from my software
I'm having a similar struggle where I want to integrate zway with MQTT (2-way):
1. publish all zwave device events to mqtt topics
2. react to specific mqtt topics and execute commands on zwave devices
I need this to be implemented in the most generic way (i.e. no need to re-configure anything when I add/remove z-wave devices). I don't want to maintain any mapping-files.
All in all, requirements sound pretty similar to your UDP/event needs. My main problem though is limited JS knowledge and time (day job + family), but at some point I hope to have a working solution.
On another note, I'm not sure why you would use UDP for transmitting events: to me UDP is, by definition, an unreliable protocol - on top of being quite low level. Unless you've already ruled it out I would recommend taking a look at MQTT instead. It's a lightweight publish/subscribe messaging protocol, simle to set up and use. My impression is that it's widely used in the HA/IoT communities.
My goal is to use MQTT as a central hub for interfacing with all my devices regardless of their protocol (z-wave, wifi, http, philips hue...). This means that my chosen rule-engine (openHAB) for smart home logic can control all devices as it already speaks MQTT.
Let me know if you find a generic way of listening to zway events for any/all zway devices, AND/OR if you should choose to go down the MQTT way instead of UDP