camsoper / puppet Goto Github PK

By refactoring an interface out of AutomationFactory, alternate event handler paradigms could be implemented other than reflection-over-a-C#-assembly. An abstract factory pattern could be used so multiple paradigms could be used at the same time.

I am looking into building an asp.net web app that could use the current reflection factory as well as a javascript-parser that hooks up and executes script-based event handlers configured from a UI while also executing a set of standard handlers built in an assembly.

Do you have any information on how to get the wiring between Puppet and Hubitat setup? I am having trouble finding out how to get all of the access tokens and the Mqtt information. I am also rather new to Hubitat. So, I apologize if that is common knowledge. I haven't found anything about it online, and your documentation is more around what to do after you are wired up.

The current implementation does the config, startup, and event watching in the program class/main method. To better support other implementations like an asp.net core process, a service class could be refactored out of program that could be started from any app/process. It would probably also make sense to move that refactored service and supporting code to Puppet.Common so other app types could avoid referencing Puppet.Executive.

To simplify use in projects that use DI (like asp.net core web apps) and to make it easier to inject mock implementations for testing, etc., AutomationFactory (and a service refactored from Program in #1) could be made singletons with injectable constructors with no static methods.