I've been attending the Masters Sales classes over the last several days and I'm finally convinced to give Crestron Home a go at some level.? It appears that they are working on??
user-editable scene controls.? When available, I'd like to use these in my lighting and shade projects.

At this point, however, I'd like to continue using SIMPL/VTProe for everything else.? It was suggested that this is doable.??

Can someone provide an approximate roadmap for how to get this done?? e.g., have the TSR remote that's part of the SIMPL system control lights that are on the Home system.? Normally, I'd use a EISC but I don't think that the answer here.??

If it's not obvious, I have never used Home.

Thanks.

开云体育

The PYNG Listen and Trigger symbols tie SIMPL to HOME. There are videos on how to do it on the CTI site under the Technician Certification Track in the Crestron Home videos.?

My understanding and my previous experience doing just this (SMW for everything except Lighting/Shades in Pyng/OS3/CH) is that the only interface is the VTPro PYNG smart objects and the SMW trigger and Listen modules.
They work well and it is an easier integration to be sure compared to D3, though completely fixed.
It limits your controls to digital button presses and feedback, with the Smart Objects providing a lot of direct control to the devices on CH.
However, the smart objects are fixed in their design and function (unless you go down the deep hole of creating your own Theme). This could clash with other parts of your UI, or require you to build your UI to match.

Unless they have announced some new features and capabilities at Masters, My Problems with this approach are as follows:
1. CH Lighting still has many programming/feature limitations compared to D3 or SMW-based Lighting control? (And yes, FTR I will kill myself if I have to program another system in D3)
2. The lack of Shared Gateway in CH requires that an hybrid system use 1 set of GWEXERs for any wireless devices on CH, A 2nd, parallel set of GWEXERs for SMW remotes and other devices, all needing to co-exist with your WIFI network. This makes for a very dense and complex RF environment.
3. Limited integration functions and UI aesthetics - You always need 'One more thing'...? for ex: no ability to set Analog levels from SMW to CH, except via the S/O, which is not accessible from SMW.
4. When you have issues on the CH side, you have no way to deal with it other than to report the issue to Crestron and wait for them to resolve it - which currently everything is taking forever to be resolved...

I would live to hear about anything that mitigates what I've detailed, as I don't hate CH, I just think that its nature creates limitations that our industry sector can't/shouldn't live with...