Andrew Welker

I wonder if it makes sense to add a 4th type of join to indicate that something is used for XSig data rather than standard serial data. That at least...

I'm assuming that this still needs to be done or at least verified in internal Essentials Devices, correct?

I think a lot of this can be addressed through the documentation effort that has started and will be ongoing. The goal will be to have things like supported input...

We'll also have to add a factory to allow for creation of the device in Essentials.

Something @ndorin and I were just discussing on the training call is moving all the interfaces to an appropriate namespace in each assembly. This would necessitate updating `using` statements when...

I think the following changes would make this work: 1. Make the `PanelDriverBase` class inherit from `EssentialsDevice`. This would enable Essentials to use the existing mechanisms to load classes that...

As for the changing rooms for a roaming panel, that capability does exist with the`SetupPanelDrivers` method, as you can feed in a room key to change the room the panel...

> I like ideas 1-3. Not sure what you're getting at for item for as I'm assuming the panel driver would hold a reference to the simpl # pro panel...

I'm not sure that really works with the paradigm/dependency structure. The panel drivers need to know about the Crestron touch panel, which is only created once the `EssentialsTouchpanelController` is built....

After some discussion yesterday between myself, @ndorin, and @jtalborough, I think what we've figured out as the best solution is 2 things: 1. Create a base class that is something...