You don’t need the light definitions AND the to/from joins.
If all you need is to connect analog/digital/string joins to home assistant for them to appear as lights, thermostats, shades, binary_sensors, sensors, switches or media_players, just use the native HA yaml token (light, climate, cover, binary_sensor, sensor, switch, media_player) with the platform: crestron sub-token without any matching to_joins or from_joins.
The to_joins and from_joins are meant for allowing the use of templates and scripts. In hindsight, the to_joins and from_joins terminology is confusing Image may be NSFW.
Clik here to view.
Since templates are a way to set things in HA with arbitrary logic/complexity when a Crestron join changes, I called it from_joins (Crestron → HA). And since scripts are a way to set Crestron joins with arbitrary logic/complexity when something in HA changes, I called it to_joins (HA → Crestron).
To add to the confusion, the custom component’s implementation of the core HA object types (light, climate, cover, binary_sensor, sensor, switch, media_player) already provide two-way synchronization. So if you use one of these in your config, there is no need to add a to_joins or from_joins to get 2-way sync.
In hindsight, to_joins should probably have been called template and from_joins should probably have been called script. I will try and update the readme to better explain this.
I’m starting to work on adding a config flow so that the component can be set up from the UI. This has the added benefit of adding “devices” to the integration which will allow for locations, device triggers, etc.
The trick is finding time to work on it Image may be NSFW.
Clik here to view.
-Nick
