I'd really like to see how DeviceJS is evolving, particularly at the interface level. Ideally via a release of the updated code.
I'm making my own "super nodes" (see my thread by that name) and need to commit to an interface layer in the next week or so. (So far, I'm rolling my own in Python, using JSON for messages.)
WigWag really needs to roll out support NOW to help developers create "Made for WigWag" devices. I want to create nodes that "Just Work" (TM) when plugged into the WigWag ecosystem, with no need for any kind of custom support or configuration (ideally, just a QR sticker on the device). "Made for WigWag" devices would work even if the WigWag system had never before seen that particular set of features combined in that specific way.
Well, I suppose I'm actually seeking four related things:
1. A device description specification and interface, where all of a device's capabilities can be fully described and shared (capabilities present, available settings and defaults, events generated, commands accepted, etc.).
2. A device discovery process (algorithm, API, protocol, whatever) to facilitate adding new devices (of possibly new and previously unknown types) to the system.
3. A mechanism for dynamically (re)configuring devices (that have configurable settings).
4. The event generation/response mechanism, along with the interfaces to the rule creation/processing system.