My fork

[mrgadget]

Hi Max - I read your comment on the smart-bus PR and that got me thinking - presently I've forked your repo to get the additional functionality I as after - specifically storing state of devices based on monitoring feedback and a collection of different nodes for specific activities - would you be interesting in bringing any of that fuctionality back into your repo? If so I'll open a PR and we can work through it.

Have a look at my [incomplete] README.md here.

Thanks,
Ben.

[efa2000]

Hi Ben

Yes, I think that would be interesting.
I need some time to watch your changes.

can you tell a little more about how these additional nodes are used?

[mrgadget]

Sure - it's really more about UI functionality that any new features as such - anything I'm doing is achievable in your existing library. What I add with my additional nodes is:

• Channel input: specify address/channel/level - when that criteria is met (at the change point), a message is emitted.
• Channel output: specify address/channel/level (both can be over-ridden in the incoming message) to be sent to the HDL network.
• UV input: specify UV switch and on, off or on/off - when that criteria is met, a message is emitted.
• UV output: specify a UV switch and state (on or off) (both can be over-ridden in the incoming message) to be sent to the HDL network.
• Panel brightness: (undocumented) specify a panel address and brightness - changes the brightness of backlights/buttons on DLPs and capacitive switches - haven't tested on the older 'big button' switches.
• Button colour: (undocumented) specify a panel address, button and colour - update the colour of a button dynamically (only tested on capacitive touch switches).

As far a using them in flows - probably easiest to just show you a pic: